Hi;
Thank you for your quick respond.
Here is my bridge setting:
1. Bridge setup script:
#bin/sh
/sbin/ifconfig eth0 0.0.0.0
/sbin/ifconfig eth1 0.0.0.0
/usr/sbin/brctl addbr brg0
/usr/sbin/brctl addif brg0 eth0
/usr/sbin/brctl addif brg0 eth1
/usr/sbin/brctl sethello brg0 1
/usr/sbin/brctl setmaxage brg0 4
/usr/sbin/brctl stp brg0 off
/sbin/ifconfig brg0 0.0.0.0 up
During the system boot, I got the bridge messages like this:
..........
kmod: failed to exec /sbin/modprobe -s -k net-pf-10, errno = 2
device eth0 entered promiscuous mode
kmod: failed to exec /sbin/modprobe -s -k net-pf-10, errno = 2
device eth1 entered promiscuous mode
kmod: failed to exec /sbin/modprobe -s -k net-pf-10, errno = 2
kmod: failed to exec /sbin/modprobe -s -k net-pf-10, errno = 2
kmod: failed to exec /sbin/modprobe -s -k net-pf-10, errno = 2
brg0: port 2(eth1) entering learning state
brg0: port 1(eth0) entering learning state
brg0: port 2(eth1) entering forwarding state
brg0: topology change detected, propagating
brg0: port 1(eth0) entering forwarding state
brg0: topology change detected, propagating
.......
After the system is up, I manually assigned ip addr to the bridge device.
# ifconfig brg0 192.168.33.50 up
# ifconfig -a
brg0 Link encap:Ethernet HWaddr 00:BB:DE:AD:BE:EF
inet addr:192.168.33.50 Bcast:192.168.33.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:23 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1657 (1.6 kb) TX bytes:0 (0.0 b)
eth0 Link encap:Ethernet HWaddr 00:BB:DE:AD:BE:EF
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:14 errors:0 dropped:0 overruns:0 frame:0
TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:1439 (1.4 kb) TX bytes:540 (540.0 b)
Interrupt:3 Base address:0x1200
eth1 Link encap:Ethernet HWaddr 00:BB:DE:AD:BE:F0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:9 errors:0 dropped:0 overruns:0 frame:0
TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:540 (540.0 b) TX bytes:1439 (1.4 kb)
Interrupt:4 Base address:0x1300
I have 2 PC, one is connected to the eth0 side called PC0 (ip:192.168.33.1),
another connected to eth1 called PC1(ip:192.168.33.60)
I can ping from my system to the "brg0" and "PC0"
# ping 192.168.33.50
PING 192.168.33.50 (192.168.33.50): 56 data bytes
64 bytes from 192.168.33.50: icmp_seq=0 ttl=255 time=15.5 ms
64 bytes from 192.168.33.50: icmp_seq=1 ttl=255 time=1.2 ms
64 bytes from 192.168.33.50: icmp_seq=2 ttl=255 time=1.2 ms
64 bytes from 192.168.33.50: icmp_seq=3 ttl=255 time=1.2 ms
....
# ping 192.168.33.1
PING 192.168.33.1 (192.168.33.1): 56 data bytes
64 bytes from 192.168.33.1: icmp_seq=0 ttl=255 time=12.4 ms
64 bytes from 192.168.33.1: icmp_seq=1 ttl=255 time=1.3 ms
64 bytes from 192.168.33.1: icmp_seq=2 ttl=255 time=1.3 ms
64 bytes from 192.168.33.1: icmp_seq=3 ttl=255 time=1.3 ms
....
But ping failed from my system to "PC1"
# ping 192.168.33.60
PING 192.168.33.60 (192.168.33.60): 56 data bytes
--- 192.168.33.60 ping statistics ---
4 packets transmitted, 0 packets received, 100% packet loss
....
The tcpdump messages on PC1:
tcpdump: listening on eth0
14:48:11.835015 B arp who-has 192.168.33.60 tell 192.168.33.50
14:48:11.835015 > arp reply 192.168.33.60 (0:6:3f:0:0:d8) is-at
0:6:3f:0:0:d8 (0:bb:de:ad:be:ef)
14:48:12.835015 B arp who-has 192.168.33.60 tell 192.168.33.50
14:48:12.835015 > arp reply 192.168.33.60 (0:6:3f:0:0:d8) is-at
0:6:3f:0:0:d8 (0:bb:de:ad:be:ef)
....
Because I have not implemented the "tcpdump" app on my system yet.
I can only try on PC0 or PC1.
>From PC1 to ping PC0, the PC0's tcpdump messages:
14:53:24.900870 arp who-has pojen.home tell 192.168.33.60
14:53:24.900931 arp reply pojen-home is-at 0:60:97:c2:fb:76
14:53:25.894949 arp who-has pojen.home tell 192.168.33.60
14:53:25.894982 arp reply pojen-home is-at 0:60:97:c2:fb:76
....
>From PC0 to ping PC1, the PC1's tcpdump messages:
14:58:58.795015 B arp who-has 192.168.33.60 tell 192.168.33.1
14:58:58.795015 > arp reply 192.168.33.60 (0:6:3f:0:0:d8) is-at
0:6:3f:0:0:d8 (0:60:97:c2:fb:76)
14:58:59.795015 B arp who-has 192.168.33.60 tell 192.168.33.1
14:58:59.795015 > arp reply 192.168.33.60 (0:6:3f:0:0:d8) is-at
0:6:3f:0:0:d8 (0:60:97:c2:fb:76)
....
I need some document or any suggestions on where I can add debug code on
bridge or else
to trace the network packages go.
pojen
> Hi,
>
> more detailed traces would be welcome.
>
>
> cheers,
> Lennert
>
>
> On Thu, May 30, 2002 at 06:01:46PM -0700, pojen wrote:
>
> > Hi;
> > I have a project on MIPS embedded platform that using the 2.4.18 kernel.
> > There were two net devices on board and we wrote the device driver.
> > (The ethernet buildin CPU and eth0, eth1 share the same driver code)
> > Before I do the "nf-0.0.7 against 2.4.18" patch, everything went fine
> > including the firewall and NAT.
> > Here is the problem I hit:
> >
> > PC1------(eth1--brg0--eth0)-------PC0
> >
> > After the bridge patched and before I applied firewall,
> > if I bridged eth0, eth1 and then ping, I could catch packages from PC0
and PC1 by tcpdump.
> > But only the eth0 received the package replied from PC0.
> > The PC1 did reply but eth1 somehow did not know it.
> > If I only include ONE device on bridge, then not problem at all.
> >
> > It could be my network device driver problem. But how come only the eth1
got problem?
> > Any suggestions will appreciate.
> >
> > pojen
>
_______________________________________________
Bridge mailing list
[EMAIL PROTECTED]
http://www.math.leidenuniv.nl/mailman/listinfo/bridge
