Networking Forums

Networking Forums > Computer Networking > Linux Networking > Installed New Ethernet Card. Now Software Bridge Doesn't Work.

Reply
Thread Tools Display Modes

Installed New Ethernet Card. Now Software Bridge Doesn't Work.

 
 
Gazza
Guest
Posts: n/a

 
      11-29-2003, 11:24 PM
Hi,

I have a 3-PC 10/100 Mb/s Ethernet home network, with all machines runing
Mandrake Linux 9.1. I have two NIC's in my main computer, PC 1. One is
installed in PCI slot 2, the other is in PCI slot 4. In linuxconf, I set
up their IP addresses and FQDN's (respectively) as:

192.168.1.1, bedroom.masterton.net (alias 'bedroom') and
192.168.2.1, bedroom.masterton2.net (alias 'bedroom2').

PC's 2 and 3 were set up with IP addresses and FQDN's (respectively) of:

192.168.1.2, lounge.masterton.net (alias 'lounge') and
192.168.2.2, kitchen.masterton2.net (alias 'kitchen2').

Because PC's 2 and 3 were on different sub-nets, it was difficult to access
one from the other (and vice versa). So, I set up bridging on PC 1 by
issuing the following commands:

brctl addbr br0
brctl addif br0 eth0
brctl addif br0 eth1
ifconfig eth0 0.0.0.0
ifconfig eth1 0.0.0.0
ifconfig br0 192.168.1.1

and changed PC 3 to 192.168.1.4/kitchen.masterton.net/kitchen. Everything
worked beautifully, so, I added the above brctl lines to the bottom of my
/etc/rc.d/rc.local file so that the bridge comes into play at the end of OS
loading. Works fine.

The problem started when I installed a third NIC in PC 1, in PCI slot 3.
This Ethernet card is connected to a cable modem and, in linuxconf, I set
it (eth2) to get it's IP address by selecting 'DHCP'. I re-booted and did
an ifconfig. It showed everyting as expected, except that eth2 did not
show an IP address, but, underneath, there was something referred to as
'eth2:9', which had an IP address I recognised as belonging to a pool of
IP's that my ISP uses. I could ping this dynamic address. So, everyting
was okay. However, I could no longer ping PC 3 (192.168.1.4). 192.168.1.1
was pingable and so was PC 2 (192.168.1.2). What's up?

Sorry about being so verbose, but I thought I'd better give as much info. as
possible.

Yours,
Gary Hayward.

 
Reply With Quote
 
 
 
 
David Efflandt
Guest
Posts: n/a

 
      11-30-2003, 03:54 AM
On Sun, 30 Nov 2003 00:24:48 +0000, Gazza <gazza@192.168.1.1> wrote:
> Hi,
>
> I have a 3-PC 10/100 Mb/s Ethernet home network, with all machines runing
> Mandrake Linux 9.1. I have two NIC's in my main computer, PC 1. One is
> installed in PCI slot 2, the other is in PCI slot 4. In linuxconf, I set
> up their IP addresses and FQDN's (respectively) as:
>
> 192.168.1.1, bedroom.masterton.net (alias 'bedroom') and
> 192.168.2.1, bedroom.masterton2.net (alias 'bedroom2').
>
> PC's 2 and 3 were set up with IP addresses and FQDN's (respectively) of:
>
> 192.168.1.2, lounge.masterton.net (alias 'lounge') and
> 192.168.2.2, kitchen.masterton2.net (alias 'kitchen2').
>
> Because PC's 2 and 3 were on different sub-nets, it was difficult to access
> one from the other (and vice versa).


Should not have been a problem if you had proper routing. Since you were
planning on setting up an internet connection, all you would have needed
was a default route on lounge using gw 192.168.1.1, and default route on
kitchen2 using gw 192.168.2.1. Of course you need ip_forward enabled on
PC 1.

> So, I set up bridging on PC 1 by issuing the following commands:
>
> brctl addbr br0
> brctl addif br0 eth0
> brctl addif br0 eth1
> ifconfig eth0 0.0.0.0
> ifconfig eth1 0.0.0.0
> ifconfig br0 192.168.1.1
>
> and changed PC 3 to 192.168.1.4/kitchen.masterton.net/kitchen. Everything
> worked beautifully, so, I added the above brctl lines to the bottom of my
> /etc/rc.d/rc.local file so that the bridge comes into play at the end of OS
> loading. Works fine.
>
> The problem started when I installed a third NIC in PC 1, in PCI slot 3.
> This Ethernet card is connected to a cable modem and, in linuxconf, I set
> it (eth2) to get it's IP address by selecting 'DHCP'. I re-booted and did
> an ifconfig. It showed everyting as expected, except that eth2 did not
> show an IP address, but, underneath, there was something referred to as
> 'eth2:9', which had an IP address I recognised as belonging to a pool of
> IP's that my ISP uses. I could ping this dynamic address. So, everyting
> was okay. However, I could no longer ping PC 3 (192.168.1.4). 192.168.1.1
> was pingable and so was PC 2 (192.168.1.2). What's up?


What did your routing look like? It may also depend upon how you
configure iptables. For communication between eth0 and eth1 networks, you
would need to insert a forward rule before any masq rules to allow your
local networks to communicate with each other. But I am not sure how all
that works with bridging (I have done proxy_arp, but not bridging).

--
David Efflandt - All spam ignored http://www.de-srv.com/
 
Reply With Quote
 
Gazza
Guest
Posts: n/a

 
      12-02-2003, 07:31 PM
David Efflandt wrote:

> On Sun, 30 Nov 2003 00:24:48 +0000, Gazza <gazza@192.168.1.1> wrote:
>> Hi,
>>
>> I have a 3-PC 10/100 Mb/s Ethernet home network, with all machines runing
>> Mandrake Linux 9.1. I have two NIC's in my main computer, PC 1. One is
>> installed in PCI slot 2, the other is in PCI slot 4. In linuxconf, I set
>> up their IP addresses and FQDN's (respectively) as:
>>
>> 192.168.1.1, bedroom.masterton.net (alias 'bedroom') and
>> 192.168.2.1, bedroom.masterton2.net (alias 'bedroom2').
>>
>> PC's 2 and 3 were set up with IP addresses and FQDN's (respectively) of:
>>
>> 192.168.1.2, lounge.masterton.net (alias 'lounge') and
>> 192.168.2.2, kitchen.masterton2.net (alias 'kitchen2').
>>
>> Because PC's 2 and 3 were on different sub-nets, it was difficult to
>> access one from the other (and vice versa).

>
> Should not have been a problem if you had proper routing. Since you were
> planning on setting up an internet connection, all you would have needed
> was a default route on lounge using gw 192.168.1.1, and default route on
> kitchen2 using gw 192.168.2.1. Of course you need ip_forward enabled on
> PC 1.

[snip]

Hi,

On PC 1 I have done the following:

* ifconfig'ed my bridge down;
* did a brctl delbr br0 [deleted bridge];
* commented out my bridging script in /etc/rc.d/rc.local;
* removed reference to eth2 in /etc/modules.conf;
* shut down;
* physically removed eth2 NIC;
* booted up;
* checked to see that eth0 and eth1 were 192.168.1.1 and 192.168.2.1
respectively [okay];
* entered the following into /etc/sysconfig/static-routes:
eth0 net 192.168.1.0 netmask 255.255.255.0 gw 192.168.1.1
eth1 net 192.168.2.0 netmask 255.255.255.0 gw 192.168.2.1

On PC 2 I did the following:

* checked to see that eth0 was 192.168.1.2 [okay];
* entered (on command line):
route add -net 192.168.2.0 netmask 255.255.255.0 gw 192.168.1.1

On PC 3 I did the following:

* changed IP address of eth0 to 192.168.2.2;
* entered (on command line):
route add -net 192.168.1.0 netmask 255.255.255.0 gw 192.168.2.1

On PC 1, I could ping 192.168.1.2 and 192.168.2.2.

On PC 2, I could ping 192.168.2.0, 192.168.2.1 and 192.168.2.255 _but not_
192.168.2.2 (PC 3).

On PC 3, I could ping 192.168.1.0, 192.168.1.1 and 192.168.1.255 _but not_
192.168.1.2 (PC 2).

How come I can't ping from PC 2 to PC 3 and vice versa? I used instructions
from the Internet to do this and it said I would be able to access machines
on one sub-net from machines on another. I can't! :-(

Please help me.

Yours,
Gary Hayward.

 
Reply With Quote
 
Gazza
Guest
Posts: n/a

 
      12-03-2003, 12:43 AM
Gazza wrote:

> David Efflandt wrote:
>
>> On Sun, 30 Nov 2003 00:24:48 +0000, Gazza <gazza@192.168.1.1> wrote:
>>> Hi,
>>>
>>> I have a 3-PC 10/100 Mb/s Ethernet home network, with all machines
>>> runing
>>> Mandrake Linux 9.1. I have two NIC's in my main computer, PC 1. One is
>>> installed in PCI slot 2, the other is in PCI slot 4. In linuxconf, I
>>> set up their IP addresses and FQDN's (respectively) as:
>>>
>>> 192.168.1.1, bedroom.masterton.net (alias 'bedroom') and
>>> 192.168.2.1, bedroom.masterton2.net (alias 'bedroom2').
>>>
>>> PC's 2 and 3 were set up with IP addresses and FQDN's (respectively) of:
>>>
>>> 192.168.1.2, lounge.masterton.net (alias 'lounge') and
>>> 192.168.2.2, kitchen.masterton2.net (alias 'kitchen2').
>>>
>>> Because PC's 2 and 3 were on different sub-nets, it was difficult to
>>> access one from the other (and vice versa).

>>
>> Should not have been a problem if you had proper routing. Since you were
>> planning on setting up an internet connection, all you would have needed
>> was a default route on lounge using gw 192.168.1.1, and default route on
>> kitchen2 using gw 192.168.2.1. Of course you need ip_forward enabled on
>> PC 1.

> [snip]
>
> Hi,
>
> On PC 1 I have done the following:
>
> * ifconfig'ed my bridge down;
> * did a brctl delbr br0 [deleted bridge];
> * commented out my bridging script in /etc/rc.d/rc.local;
> * removed reference to eth2 in /etc/modules.conf;
> * shut down;
> * physically removed eth2 NIC;
> * booted up;
> * checked to see that eth0 and eth1 were 192.168.1.1 and 192.168.2.1
> respectively [okay];
> * entered the following into /etc/sysconfig/static-routes:
> eth0 net 192.168.1.0 netmask 255.255.255.0 gw 192.168.1.1
> eth1 net 192.168.2.0 netmask 255.255.255.0 gw 192.168.2.1
>
> On PC 2 I did the following:
>
> * checked to see that eth0 was 192.168.1.2 [okay];
> * entered (on command line):
> route add -net 192.168.2.0 netmask 255.255.255.0 gw 192.168.1.1
>
> On PC 3 I did the following:
>
> * changed IP address of eth0 to 192.168.2.2;
> * entered (on command line):
> route add -net 192.168.1.0 netmask 255.255.255.0 gw 192.168.2.1
>
> On PC 1, I could ping 192.168.1.2 and 192.168.2.2.
>
> On PC 2, I could ping 192.168.2.0, 192.168.2.1 and 192.168.2.255 _but not_
> 192.168.2.2 (PC 3).
>
> On PC 3, I could ping 192.168.1.0, 192.168.1.1 and 192.168.1.255 _but not_
> 192.168.1.2 (PC 2).
>
> How come I can't ping from PC 2 to PC 3 and vice versa? I used
> instructions from the Internet to do this and it said I would be able to
> access machines
> on one sub-net from machines on another. I can't! :-(
>
> Please help me.
>
> Yours,
> Gary Hayward.


Hi,

Problem solved by a posting I noticed above mine! (I needed to re-boot the
router computer).

Yours,
Gary Hayward.

 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
acx100 wireless card doesn't work noSpam Linux Networking 0 01-21-2006 12:22 AM
WiFi doesn't work with LAN card in WINXP sp2 Eugene Wireless Networks 0 04-26-2005 01:42 AM
PCMCIA 100MBit Eth. Card doesn't work after update (Suse 8.2 -> 9.2) Jan Buckow Linux Networking 0 01-16-2005 06:47 PM
Computer doesn't recognize ethernet card trishconnelly@aol.com Windows Networking 2 10-26-2003 03:55 PM
GP Fault in internet explorer and AOL after I installed ethernet card Billy Hart Windows Networking 0 10-02-2003 06:53 PM



1 2 3 4 5 6 7 8 9 10 11