Host: h370 Kernel: 6.1.0-23-amd64 arch: x86_64 bits: 64 Desktop: KDE
> > Plasma
> >
> > v: 5.27.5 Distro: Debian GNU/Linux 12 (bookworm)
> >
> > rd@h370:~$
> >
> > It uses bridging network connections with libvirt work unreliable.
>
Am Donnerstag, 29. August 2024, 20:31:10 CEST schrieb Tim Woodall:
> On Wed, 28 Aug 2024, Rainer Dorsch wrote:
> > In the systemd log, the first entry indicating network problems is that
> > the DNS server switches to another interface. But it could easily be a
> > consequence and not the cause of
NU/Linux 12 (bookworm)
> rd@h370:~$
>
> It uses bridging network connections with libvirt work unreliable.
>
> I have in /etc/network/interface bridging networks e.g.
>
> iface eno1.2 inet manual
>
> # libvirt VM
> auto br2
> iface br2 inet dhcp
> # Use the MAC ad
On Wed, 28 Aug 2024, Rainer Dorsch wrote:
In the systemd log, the first entry indicating network problems is that the DNS
server switches to another interface. But it could easily be a consequence and
not the cause of the issue:
Aug 28 06:57:54 h370 dhclient[1195]: DHCPREQUEST for 192.168.4.203
Hello,
I have a (for me) weird problem on a bookworm system
rd@h370:~$ inxi -S
System:
Host: h370 Kernel: 6.1.0-23-amd64 arch: x86_64 bits: 64 Desktop: KDE Plasma
v: 5.27.5 Distro: Debian GNU/Linux 12 (bookworm)
rd@h370:~$
It uses bridging network connections with libvirt work unreliable
Just a quick bump on my issue as I've not found a solution as yet.
On Mon, 25 Oct 2021, 11:41 am Cameron Murray,
wrote:
> Hi Team,
>
>
>
> Having difficulties creating a bridge between a VXLAN interface and a
> child vlan of a bonded interface pair.
>
> br0
> --- bond0.142
> --- vx142
>
> https:
Hi Team,
Having difficulties creating a bridge between a VXLAN interface and a
child vlan of a bonded interface pair.
br0
--- bond0.142
--- vx142
https://pastebin.com/ynpRf3jf
It appears from my searching that it’s possible that as vlan 142 is
part of a bond/bridge already it will not functio
Hi
Im trying to setup a VM with aqemu and i would like my vm to connect to
the local network via dhcp.
I followed the instructions at
https://wiki.debian.org/QEMU
> my /etc/network/interfaces is
>
>
> # This file describes the network interfaces available on your system
> # and how to activate
# no forwarding delay
#bridge_ports none # if you do not want to bind to any ports
#Bridge_ports regex eth* # use a regular expression to define ports
# To restart the service after update:
# /etc/init.d/procps restart
One of my challenges is that bridging to a wireless NIC requires 4addr
I have an issue where my bridging firewall no longer drops traffic. Everything
looks like it should be working but I can still access things I shouldn't. I
am wondering if my use case is no longer supported.
This system worked well for years. When I updated from Debian 6 to Debian 7
>> The use case is that I need to bridge eth0 with eth0.2, allowing layer
>> two traffic to pass seamlessly between interfaces, yet still leave
>> eth0.3 in a usable state. The switch this system is connected to is
>> for all intents and purposes outside of my control, which is the
>> reason fo
Tim Nelson wrote:
> The use case is that I need to bridge eth0 with eth0.2, allowing layer
> two traffic to pass seamlessly between interfaces, yet still leave
> eth0.3 in a usable state. The switch this system is connected to is
> for all intents and purposes outside of my control, which is the
On 12/11/2014 03:45 PM, Tim Nelson wrote:
Greetings-
I have an interesting situation that requires bridging some VLAN enabled
interfaces together on a Debian 7.x x86 system. On the host, there is a
single physical interface passing traffic natively (eth0), and two
tagged VLANs also passing
Greetings-
I have an interesting situation that requires bridging some VLAN enabled
interfaces together on a Debian 7.x x86 system. On the host, there is a single
physical interface passing traffic natively (eth0), and two tagged VLANs also
passing traffic (eth0.2 and eth0.3).
The use case
On 10/11/14 12:50 AM, Christian Seiler wrote:
Am 10.11.2014 01:33, schrieb Gary Dale:
On 09/11/14 03:30 PM, Christian Seiler wrote:
Could you post the contents of your /etc/default/networking?
Specifically, it should have either no explicit settings (everything
commented out) or the following s
Am 10.11.2014 01:33, schrieb Gary Dale:
> On 09/11/14 03:30 PM, Christian Seiler wrote:
>> Could you post the contents of your /etc/default/networking?
>> Specifically, it should have either no explicit settings (everything
>> commented out) or the following settings (which are default):
>>
>> CONF
On 09/11/14 03:30 PM, Christian Seiler wrote:
Am 09.11.2014 21:13, schrieb Gary Dale:
You're right. Here's my default.xml (I only changed the addresses):
root@TheLibrarian:/home/garydale# cat /etc/libvirt/qemu/networks/default.xml
default
Howeve
Am 09.11.2014 21:13, schrieb Gary Dale:
> You're right. Here's my default.xml (I only changed the addresses):
>
> root@TheLibrarian:/home/garydale# cat /etc/libvirt/qemu/networks/default.xml
>
>default
>
>
>
>
>
>
>
>
>
> However when I removed the link t
ically detect that setup and provide the required options in the
host configuration for this.
So, for example, I have completely disabled the default.xml network
configuration in libvirt (no link in autostart/), and bridging still
works because libvirt detects the bridge set up by Debian's ne
n libvirt!), but rather by the distribution, and libvirt will
automatically detect that setup and provide the required options in the
host configuration for this.
So, for example, I have completely disabled the default.xml network
configuration in libvirt (no link in autostart/), and bridging still
works
On 09/11/14 05:09 AM, Karl E. Jorgensen wrote:
Hi
On Sat, Nov 08, 2014 at 05:57:41PM -0500, Gary Dale wrote:
For some reason my network card bridging has failed after working
properly for many years.
My /etc/network/interfaces is:
auto lo
iface lo inet loopback
iface eth0 inet manual
auto
On 09/11/14 05:27 AM, Christian Seiler wrote:
Am 08.11.2014 23:57, schrieb Gary Dale:
For some reason my network card bridging has failed after working
properly for many years.
My /etc/network/interfaces is:
auto lo
iface lo inet loopback
iface eth0 inet manual
auto br0
iface br0 inet static
Am 08.11.2014 23:57, schrieb Gary Dale:
> For some reason my network card bridging has failed after working
> properly for many years.
>
> My /etc/network/interfaces is:
>
> auto lo
> iface lo inet loopback
> iface eth0 inet manual
> auto br0
> iface br0
Hi
On Sat, Nov 08, 2014 at 05:57:41PM -0500, Gary Dale wrote:
> For some reason my network card bridging has failed after working
> properly for many years.
>
> My /etc/network/interfaces is:
>
> auto lo
> iface lo inet loopback
> iface eth0 inet manual
> auto
For some reason my network card bridging has failed after working
properly for many years.
My /etc/network/interfaces is:
auto lo
iface lo inet loopback
iface eth0 inet manual
auto br0
iface br0 inet static
address 192.168.1.14
netmask 255.255.255.0
broadcast
Mon, 11 Aug 2014 05:44:18 +
Any tips on using SEM India DNA-A201 modem in bridge mode?
Modem has adsl and ppp commands. No man pages.
All attempts lead to dangling IP address (wan IP) reachable only from
localhost.
> adsl
Usage: adsl start [--up] [--mod ] [--lpair <(i)nner|(o)uter>]
On Sun, Oct 6, 2013 at 2:14 PM, Ross Boylan
wrote:
> I removed network manager and have this in /etc/network/interaces:
>
> # eth2 managed by bridge and not otherwise mentioned
>
> auto br0
> iface br0 inet dhcp
>bridge_ports eth2
>
> That seems to work with the kvm-ifup script provided by w
I removed network manager and have this in /etc/network/interaces:
# eth2 managed by bridge and not otherwise mentioned
auto br0
iface br0 inet dhcp
bridge_ports eth2
That seems to work with the kvm-ifup script provided by wheezy qemu-kvm.
Note I have not rebooted since setting this up, and
On Thu, Oct 3, 2013 at 8:14 PM, Bob Proulx wrote:
>>
>> Arun made a suggestion that
>> > Your 'physical' device eth0/eth2 or whatever needs to be added to the
>> bridge.
>> I believe that is done by the /etc/kvm/kvm-ifup script that is executed
>> when I launch the virtual machine.
>
> I think tha
On Wed, Oct 2, 2013 at 3:40 PM, Ross Boylan
wrote:
>
> Arun made a suggestion that
>> Your 'physical' device eth0/eth2 or whatever needs to be added to the
bridge.
> I believe that is done by the /etc/kvm/kvm-ifup script that is executed
when I
> launch the virtual machine.
> It says, in part
>
>
On Wed, Oct 2, 2013 at 3:05 AM, Ross Boylan wrote:
> I setup bridging on my system for kvm, but on restart of the host system
> (no guest VM's running) could not ping outside my local network.
>
> Bringing the bridge down corrected the problem, but I'm trying to
> un
Ross Boylan wrote:
> Bob Proulx wrote:
> > I think that file must have been removed at some point. I have
> > the qemu-kvm package (which owns that file) installed but do not have
> > that file on my system. The qemu-kvm.postinst script in the current
> > package removes the conffile. So just a
On Thu, Oct 3, 2013 at 5:14 PM, Bob Proulx wrote:
> Greg has made some excellent explanation and answers. I wanted to
> comment on a few other things.
>
> Ross Boylan wrote:
>
> > Arun made a suggestion that
> > > Your 'physical' device eth0/eth2 or whatever needs to be added to the
> > bri
ogether in order for
everything to be functioning correctly. But in general it should work
okay.
> This is not the long-run plan. The router keeps flaking out,
> perhaps in part because of some interaction with the bridging:
The router should not care that you are using a bridge on your c
On Thu, Oct 03, 2013 at 09:44:31AM -0700, Ross Boylan wrote:
> Greg, thanks for explaining this. I'm still puzzled about one point, below.
>
>
> On Wed, Oct 2, 2013 at 4:10 PM, Gregory Nowak wrote:
>
> > On Wed, Oct 02, 2013 at 12:40:26PM -0700, Ross Boylan wrote:
> > > Can anyone explain to m
s say you
want your virtual machine(s) to be on the eth2 network. So, a bridge
would look something like this:
...
iface br0 inet dhcp
bridge_ports eth2 tap0
...
Once you do that, the virtual machine configured to use tap0 would be
able to talk to all computers on the network to which eth2 is
co
My wireless router is currently serving as a dhcp server; it has a reserved
IP for the system under discussion. This is not the long-run plan. The
router keeps flaking out, perhaps in part because of some interaction with
the bridging: I've had 2 or 3 problems since I started the bridging, and
Ross Boylan wrote:
> /etc/network/interfaces has (on the advice of a wiki page on Debian and
> kvm)
Which page is "a wiki page"? I didn't find a wiki.debian.org one that
had an example like it.
How about this one? It has good working examples.
http://wiki.libvirt.org/page/Networking
> auto
On Wed, Oct 2, 2013 at 12:35 PM, Ross Boylan wrote:
> I setup bridging on my system for kvm, but on restart of the host system
> (no guest VM's running) could not ping outside my local network.
>
> Bringing the bridge down corrected the problem, but I'm trying to
> un
How did you configured eth2? dhcp too? why you tap as bridge port intend of
eth2?
2013/10/2 Ross Boylan
> I setup bridging on my system for kvm, but on restart of the host system
> (no guest VM's running) could not ping outside my local network.
>
> Bringing the bridge d
I setup bridging on my system for kvm, but on restart of the host system
(no guest VM's running) could not ping outside my local network.
Bringing the bridge down corrected the problem, but I'm trying to
understand what is going on, and how I can make networking from the VM's
work
Hello, merry christmas at all,
after setting aup my laptop on wheezy now I got back to the
konfiguration of my server.
I have running there 3 dom0 with bridged IPv4.
I have an subnet for IPv6 with a lot of adresses and i want to use them
(my home system has tunneled IPv6)
An IPv4 subnet is too
Jon Dowland wrote:
> You don't need to remove NM. I have it managing my wifi and 3G connections,
> but manage eth0 via ifupdown (and attach it to a bridge).
That's what I have at the moment, and NM gets itself in a tizzy when I
want to use eth0 as my primary connection and borks my non-local traf
On Fri, Jun 29, 2012 at 11:47:29PM +0100, Chris Davies wrote:
> Steve Dowe wrote:
> > The issue I'm having, using wheezy, is that if I set up a bridged
> > ethernet interface for eth0 (br0), as per instructions on the Debian
> > wiki etc, NetworkManager can no longer manage my wired ethernet conne
ever preferred_lft forever
--
I no longer have any trouble firing up VMs and getting them networked. It just
works.
Granted, I mix decimal and hex; but some things are hard to avoid.
And I really don't know why Squeeze assigns IPv6 LL addresses to NIC/taps that
are members of a brid
On 02/07/12 17:34, Camaleón wrote:
>> Testing on the same subnet :)
>
> Yes but what solution? KVM, VMware, Xen, VirtualBox...
Oh heck, sorry. It's KVM. I thought I'd mentioned that. Oops.
>> Basically, you need eth0 bridged (using br0) to allow other virtual
>> machines to pick up an IP add
On 29/06/12 23:47, Chris Davies wrote:
> Steve Dowe wrote:
>> The issue I'm having, using wheezy, is that if I set up a bridged
>> ethernet interface for eth0 (br0), as per instructions on the Debian
>> wiki etc, NetworkManager can no longer manage my wired ethernet connection.
>
> You can't do t
On Mon, 02 Jul 2012 17:14:02 +0100, Steve Dowe wrote:
> I'm sorry for the tardy response - IceDove hid a load of Debian list
> mail in "Junk".
>
> On 29/06/12 18:06, Camaleón wrote:
>> Maybe is time now for you to tell us more about the kind of VM you are
>> planning to use...
>
> Testing on the
On 29/06/12 17:34, Neal Murphy wrote:
(...)
> another program running whose sole purpose is to slurp CPU cycles, take up
> screen real estate
I'm all for machine efficiency, but I don't find NM to do either of
those. On a laptop, I find it sacrifices my human efficiency to /not/
have it.
> and
I'm sorry for the tardy response - IceDove hid a load of Debian list
mail in "Junk".
On 29/06/12 18:06, Camaleón wrote:
> Maybe is time now for you to tell us more about the kind of VM you are
> planning to use...
Testing on the same subnet :)
> I still don't see the relation of using N-M and t
loopback network interface
> auto lo br0
> iface lo inet loopback
>
> # bridging
> iface br0 inet dhcp
>bridge_ports eth0
>bridge_stp off
>bridge_maxwait 0
>bridge_fd 0
NM's now doing bridging but has it been patched to understand Debian's
"/etc/network
Arun Khan a écrit :
>
> When you use bridge: To the best of my knowledge - the IP is assigned
> to the bridge and *not* eth0 the physical interface. eth0 should
> *not* have any IP assigned to it.
Except in some very specific situations.
Exemple : you want the box act as a bridge with some pro
br0 both pick up the same IP address.
>
> This is my current /etc/network/interfaces:
>
> # The loopback network interface
> auto lo br0
> iface lo inet loopback
>
> # bridging
> iface br0 inet dhcp
> bridge_ports eth0
> bridge_stp off
> bridge_maxwait 0
Steve Dowe wrote:
> The issue I'm having, using wheezy, is that if I set up a bridged
> ethernet interface for eth0 (br0), as per instructions on the Debian
> wiki etc, NetworkManager can no longer manage my wired ethernet connection.
You can't do that :-(
If you need a bridge (like I do), AFAI
On Fri, 29 Jun 2012 17:19:27 +0100, Steve Dowe wrote:
> On 29/06/12 16:54, Camaleón wrote:
>> Ah, then maybe you don't need a bridge but a virtual addressing layout:
>>
>> http://wiki.debian.org/NetworkConfiguration#Multiple_IP_addresses_on_One_Interface
>
> But that fixes the IP addresses both
On Friday 29 June 2012 10:02:57 Steve Dowe wrote:
> Hello,
>
> I have absolutely no doubt that someone reading this list knows more
> than I do on this.. :)
>
> The issue I'm having, using wheezy, is that if I set up a bridged
> ethernet interface for eth0 (br0), as per instructions on the Debian
On 29/06/12 17:19, Steve Dowe wrote:
> On 29/06/12 16:54, Camaleón wrote:
>> > Ah, then maybe you don't need a bridge but a virtual addressing layout:
>> >
>> > http://wiki.debian.org/NetworkConfiguration#Multiple_IP_addresses_on_One_Interface
> But that fixes the IP addresses both to my local net
s to allow the virtual network interfaces of virtual
machines the chance to pick up an IP address using DHCP whatever local
network they're on.
>>> There are some bridging samples here:
>>>
>>> http://wiki.debian.org/BridgeNetworkConnections#Configuring_bridgin
ple_IP_addresses_on_One_Interface
>> There are some bridging samples here:
>>
>> http://wiki.debian.org/BridgeNetworkConnections#Configuring_bridging_in_.2BAC8-etc.2BAC8-network.2BAC8-interfaces
>
> Thanks. I did look at those. And by following that configuration:
>
&g
his case, is a virtual-to-physical one.
>> This is my current /etc/network/interfaces:
>>
>> # The loopback network interface
>> auto lo br0
>> iface lo inet loopback
>>
>> # bridging iface br0
>> inet dhcp
>> bridge_ports eth0
>>
nd what's what you want to bridge? Remember that any bridge
needs at least two end points.
> This is my current /etc/network/interfaces:
>
> # The loopback network interface
> auto lo br0
> iface lo inet loopback
>
> # bridging
> iface br0 inet dhcp
>bridge_port
pback
# bridging
iface br0 inet dhcp
bridge_ports eth0
bridge_stp off
bridge_maxwait 0
bridge_fd 0
I must be missing something simple here. Could anyone point me in the
right direction please? Has anyone got a working config?
TIA...
Steve
--
Steve Dowe
Warp Universal Limited
the MAC address from the frame header. From this superficial thinking,
packet routing is more efficient than frame forwarding. Is that true?
> For you "different IP networks" setup you will need to properly configure
> both
> NAT and routing which it's a bit more difficu
tions are right, then you need to configure an
> > IP bridge between dalton's eth0 and eth1 [eth2 in the Proposed Network].
> > That's all.
>
> What are the greatest advantages in bridging eth0 and eth1 rather
> than routing through Dalton to Carnot? Bridging will
On Sb, 14 mai 11, 22:14:44, peasth...@shaw.ca wrote:
>
> What are the greatest advantages in bridging eth0 and eth1 rather
> than routing through Dalton to Carnot? Bridging will need some
> additional software, bridge-utils; routing should be possible
> without adding softw
omplete an up-to-date diagram.
It's improved now.
http://carnot.yi.org/NetworksPage.html
Ref. Extant Network & Proposed Network.
> If all my previous assumptions are right, then you need to configure an IP
> bridge between dalton's eth0 and eth1 [eth2 in the Proposed Network].
erstand that the upsteam project NetworkManager is working on adding
network bridge support.
The last ETA I read was late 2010 from there website [1] ... I was just
wondering if anyone knew this was still the case.
Network bridging support would be very useful to me for running Xen on my
Good evening,
I’m using NetworkManager to automatically connect to a number of wifi
networks as well as to ethernet networks at home and in university.
I’m also using the dispatcher to run custom scripts depending on the
network to which the computer just connected.
Now it would be nice if I coul
Works like a charm:
> auto br0
> iface br0 inet static
>address 192.168.0.113
>network 192.168.0.0
>netmask 255.255.255.0
>broadcast 192.168.0.255
>bridge_ports eth0
> auto wlan0
> iface wlan0 inet dhcp
>wpa-ssid MySSID
>wpa-pskMyPlaintextPassword
>pos
Bob van der Moezel wrote:
> I am trying to bridge a wireless channel with a wired channel (and some KVM
> tap/tun channels for virtual servers).
>
> I am running Debian Testing, bridge-utils 1.4-5 and wpasupplicant 0.6.4-3.
>
> Any ideas to get this to work? (I sent two days without any luck).
>
On Wed, Apr 01, 2009 at 11:45:08PM +0200, Bob van der Moezel wrote:
> I am trying to bridge a wireless channel with a wired channel (and some KVM
> tap/tun channels for virtual servers).
My understanding is that bridging of wireless devices is very dependant
on the wireless card (chipset)
I am trying to bridge a wireless channel with a wired channel (and some KVM
tap/tun channels for virtual servers).
/etc/network/interfaces:
auto lo
iface lo inet loopback
auto br0
iface br0 inet static
address 192.168.0.113
network 192.168.0.0
netmask 255.
aware of. I have since restarted everything again after finding these
in the logs to see if it would be reproduced, but they were not.
Daryl
Replying to myself...
Turns out above steps for bridging/dhcp still work fine. It seems the
Debian installer was refusing to request an address f
I'm attempting to bridge wlan0 with eth0. I've done this successfully
in the past with firestarter and dhcp3-server. However I'm running into
some issues trying to set this up now.
What I have done in the past is set eth0 static, and enabled internet
connection sharing in firestarter. Which en
On Mon, Feb 23, 2009 at 01:25:30PM +0100, Udo Hortian wrote:
> Hello all,
>
> I subscribed newly to this list, since I got an bridging problem
> after an upgrade from Debian etch to Debian lenny (before
> everything worked fine).
>
> The situation is as follows:
>
>
Hello all,
I subscribed newly to this list, since I got an bridging problem
after an upgrade from Debian etch to Debian lenny (before
everything worked fine).
The situation is as follows:
# brctl show
bridge name bridge id STP enabled interfaces
br0
t;> Greetings all,
>>>>>
>>>>> I have two NICs on my laptop: eth0 and wlan0, I tried to bridge them
>>>>> and use a ad-hoc connection with my cellphone to share the internet
>>>
>>> I don't think bridging of wireless and
aptop: eth0 and wlan0, I tried to bridge them
>>>> and use a ad-hoc connection with my cellphone to share the internet
>>
>> I don't think bridging of wireless and ethernet works, why not just
>> route the packets! use iptables to setup nat if you need
>>
&
Hello List !
Alex Samad wrote:
On Sun, Jan 25, 2009 at 12:03:47AM -0500, Wayne Topa wrote:
Deephay wrote:
Greetings all,
I have two NICs on my laptop: eth0 and wlan0, I tried to bridge them
and use a ad-hoc connection with my cellphone to share the internet
I don't think bridgi
On Sun, Jan 25, 2009 at 12:03:47AM -0500, Wayne Topa wrote:
> Deephay wrote:
>> Greetings all,
>>
>> I have two NICs on my laptop: eth0 and wlan0, I tried to bridge them
>> and use a ad-hoc connection with my cellphone to share the internet
I don't think bridging
wlan0
tcpdump will show the ARP request message again and again, this
behavior is different from MS Windows bridging. Could anyone tell me
why?
How did you set up the bridge? Show us your interfaces file.
WT
--
To UNSUBSCRIBE
wlan0
tcpdump will show the ARP request message again and again, this
behavior is different from MS Windows bridging. Could anyone tell me
why?
Deephay
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubs
On Tuesday 09 December 2008, Micha Feigin <[EMAIL PROTECTED]> wrote
about 'the cost of ethernet bridging':
>I was thinking of using ethernet bridging to simplify naming and routing
> on my system. This system consists of four computers all interconnected.
> The questio
I was thinking of using ethernet bridging to simplify naming and routing on my
system. This system consists of four computers all interconnected. The question
is whether there is any hidden cost, as I need the cards to work at full
throughput (three ethernet cards). So, will this just give me the
Umarzuki Mochlis wrote:
> Other than sharing the same IP, say wireless interface and ethernet, what
> else? In case I missed something. Please share your experience :)
>
Are you asking how to bridge those interfaces? I don't fully understand
your question.
--
To UNSUBSCRIBE, email to [EMAIL
Other than sharing the same IP, say wireless interface and ethernet, what
else? In case I missed something. Please share your experience :)
--
Regards,
Umarzuki Mochlis
http://gameornot.net
Matt Price <[EMAIL PROTECTED]> wrote: On 12/31/06, Kevin Ross wrote:
>
>
> You got it half right. Turning on ip_forward on the server is only one
> piece. The other piece is to set the client's default gateway to point to
> your server, which is 192.168.0.1. You can set this via DHCP options,
On 12/31/06, Kevin Ross <[EMAIL PROTECTED]> wrote:
You got it half right. Turning on ip_forward on the server is only one
piece. The other piece is to set the client's default gateway to point to
your server, which is 192.168.0.1. You can set this via DHCP options, since
you have a DHCP serv
You got it half right. Turning on ip_forward on the server is only one piece.
The other piece is to set the client's default gateway to point to your server,
which is 192.168.0.1. You can set this via DHCP options, since you have a DHCP
server.
-- Kevin
On Sat, Dec 30, 2006 at 10:01:46AM -0500, Matt Price wrote:
> On 12/29/06, Andrew Sackville-West <[EMAIL PROTECTED]> wrote:
> >On Fri, Dec 29, 2006 at 04:42:49PM -0500, Matt Price wrote:
> >> From: Matt Price <[EMAIL PROTECTED]>
> >> To: TLUG <[EMAIL PROTECTED]>
> >> Subject: bridge
Marty wrote:
There is a
dedicated Debian package called guarddog which produces such a script. You
might want to take a look at its docs to get an idea of what's required.
Sorry, I meant guidedog, not guarddog.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe".
e's something messed up in the set up for the
desktop's networking. Howm ight I diagnose that?
Anyway thanks again,
Matt
You need several networking kernel drivers as modules or compiled into the
kernel, including drivers for iptables, packet routing, and bridging. You can
run t
On 12/29/06, Andrew Sackville-West <[EMAIL PROTECTED]> wrote:
On Fri, Dec 29, 2006 at 04:42:49PM -0500, Matt Price wrote:
> From: Matt Price <[EMAIL PROTECTED]>
> To: TLUG <[EMAIL PROTECTED]>
> Subject: bridge eth1 to eth0?
> Date: Fri, 29 Dec 2006 15:51:31 -0500
>
>
> hi,
Le samedi 30 décembre 2006 00:42, Andrew Sackville-West a écrit :
> On Sat, Dec 30, 2006 at 12:28:33AM +0100, Gilles Mocellin wrote:
> > Le samedi 30 décembre 2006 00:09, Andrew Sackville-West a écrit :
> > > On Fri, Dec 29, 2006 at 11:04:01PM +0100, Sven Arvidsson wrote:
> > > > On Fri, 2006-12-29
On Sat, Dec 30, 2006 at 12:28:33AM +0100, Gilles Mocellin wrote:
> Le samedi 30 décembre 2006 00:09, Andrew Sackville-West a écrit :
> > On Fri, Dec 29, 2006 at 11:04:01PM +0100, Sven Arvidsson wrote:
> > > On Fri, 2006-12-29 at 16:42 -0500, Matt Price wrote:
> [...]
> > > echo 1 > /proc/sys/net/ip
Le samedi 30 décembre 2006 00:09, Andrew Sackville-West a écrit :
> On Fri, Dec 29, 2006 at 11:04:01PM +0100, Sven Arvidsson wrote:
> > On Fri, 2006-12-29 at 16:42 -0500, Matt Price wrote:
[...]
> > echo 1 > /proc/sys/net/ipv4/ip_forward
> >
> > There might be a more permanent and Debian friendly w
e the eth1 traffic to bridge across to eth0
> > and thus access the whole internet? I guess it has something to do with
> > ip forwarding or ip masquarading or one of those very scary and arcane
> > pieces of dark magic.
[...]
>
> Bridging is done using the tools from the br
On Fri, Dec 29, 2006 at 04:42:49PM -0500, Matt Price wrote:
> From: Matt Price <[EMAIL PROTECTED]>
> To: TLUG <[EMAIL PROTECTED]>
> Subject: bridge eth1 to eth0?
> Date: Fri, 29 Dec 2006 15:51:31 -0500
>
>
> hi,
>
> for stupid reasons I need to install via netboot on a com
55.0
> network 192.168.0.0
>
> --
> I should maybe say that eth0 attaches to a cheap wireless router --
> simple but not very flexible. The router is then in turn attached
> through a cable modem to the local cable network.
>
> thanks and please let me k
From: Matt Price <[EMAIL PROTECTED]>
To: TLUG <[EMAIL PROTECTED]>
Subject:bridge eth1 to eth0?
Date: Fri, 29 Dec 2006 15:51:31 -0500
hi,
for stupid reasons I need to install via netboot on a compaq tablet
(hoping this will work, it's my last shot!). I have an ubuntu desktop
wit
1 - 100 of 123 matches
Mail list logo
