From: Juergen Pfeiffer <j.pfeiffer@seskion.de>
To: bridge@lists.osdl.org
Subject: Re: [Bridge] Is bridgeing possible with kernel 2.6.10
Date: Thu, 27 Jul 2006 11:15:38 +0200 [thread overview]
Message-ID: <44C8843A.4010200@seskion.de> (raw)
In-Reply-To: <20060726101335.67406ee8@localhost>
[-- Attachment #1: Type: text/plain, Size: 5749 bytes --]
Stephen Hemminger schrieb:
>
> The bridge starts in the learning state doesn't forward until the
> forwarding delay (30 seconds) in expired. You need to be either patient
> or set the delay to a lower value.
>
>
Hi
Here is the trace of my test:
After the output of "now do pings!", i started to ping on computer
192.168.1.1 (MAC=00:50:fc:93:e0:9c), connected to eth1 of my bridge to
computer 192.168.1.33 (MAC=00:14:22:f2:5d:70), connected to eth0 of my
bridge.
=> No Responses! May it be a problem of my ethernet driver
(drivers/net/fec.c for Freescale ColdFire 5485) ??
*$ /mnt/mtd/startbridge*
+ ifconfig eth0 0.0.0.0 down
+ ifconfig eth1 0.0.0.0 down
+ brctl addbr br0
+ brctl stp br0 on
+ brctl addif br0 eth0
device eth0 entered promiscuous mode
+ brctl addif br0 eth1
device eth1 entered promiscuous mode
+ ifconfig eth0 0.0.0.0 up
+ ifconfig eth1 0.0.0.0 up
+ ifconfig br0 0.0.0.0 up
br0: port 2(eth1) entering listening state
br0: port 1(eth0) entering listening state
+ sleep 35
br0: port 2(eth1) entering learning state
br0: port 1(eth0) entering learning state
br0: topology change detected, propagating
br0: port 2(eth1) entering forwarding state
br0: topology change detected, propagating
br0: port 1(eth0) entering forwarding state
+ echo 'now do pings!'
now do pings!
+ sleep 10
+ brctl show
bridge name bridge id STP enabled interfaces
br0 8000.001122334450 yes eth0
eth1
+ brctl showmacs br0
port no mac addr is local? ageing timer
1 00:11:22:33:44:50 yes 0.00
2 00:11:22:33:44:51 yes 0.00
* 1 00:14:22:f2:5d:70 no 10.13*
2 00:40:05:41:12:8d no 4.52
* 2 00:50:fc:93:e0:9c no 0.38
* 2 00:c0:02:39:53:52 no 7.88
+ brctl showstp br0
br0
bridge id 8000.001122334450
designated root 8000.001122334450
root port 0 path cost 0
max age 20.00 bridge max
age 20.00
hello time 2.00 bridge hello
time 2.00
forward delay 15.00 b rbr0id:ge fporowarrdt d
el2ay(1
d a geeinng ttiemer i 3n00g.0 0
tihesllao btilmeer d s0.t61a t tecn
o imberr 0 : 0 .0p0
l rtotpo lo1gy( cehatnghe 0ti)me r e n19t.7e0 r
igcn tg8
_Cefldag s s tTOaPOtLOeGY
HANGE TOPOLOGY_CHANGE_DETECTED
eth0 (1)
port id 8001 state
forwarding
pdesignated root d80e00v.0i01c12e23 34e45t0 hpa1th closet
f 0
34rdeosimgniatsedc buriodgue s80 00m.0o01d12e23
h 45b0 rme0ss:ag e pagoe rtitme r 2 ( 0e.0t0
1de)si gneatnedt peorrt i80n01g fdoriwasrda
dbellaye tde
d
esignated cost 0 hold
timer 0.00
flags
eth1 (2)
port id 8002 state
forwardidne
v diescigena teed trohot0 8 00l0.e00f11t22 33p44r50o pmatih
scocstu s
d dmesoigdnaete
brbidrge0 8:00 0.p00o11r22t33 44150( meestsahge0 a)ge
teimnert n
ded esdiginastead bpolrte 8d00 2 s tfoarwtared
lay timer 0.00
designated cost 0 hold
timer 0.00
flags
+ ifconfig
br0 Link encap:Ethernet HWaddr 00:11:22:33:44:50
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:24 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:1499 (1.4 KiB) TX bytes:0 (0.0 B)
eth0 Link encap:Ethernet HWaddr 00:11:22:33:44:50
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
*RX packets:85* errors:0 dropped:0 overruns:0 frame:0
TX packets:229 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:7232 (7.0 KiB) TX bytes:26956 (26.3 KiB)
Interrupt:103 Base address:0x9000
eth1 Link encap:Ethernet HWaddr 00:11:22:33:44:51
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:946 errors:0 dropped:0 overruns:0 frame:0
TX packets:93 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:167451 (163.5 KiB) TX bytes:62a3 (6.1 KiB)
Interrupt:102 Base address:0x9800
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:268 (268.0 B) TX bytes:268 (268.0 B)
+ ifconfig br0 down
+ brctl delif br0 eth1
+ brctl delif br0 eth0
+ brctl delbr br0
+ ifconfig eth1 0.0.0.0 down
+ ifconfig eth0 0.0.0.0 down
*$
*
--
------------------------------------------------------------------------
Jürgen Pfeiffer
* _mailto:j.pfeiffer@seskion.de_
SesKion Softwareentwicklung und System Konzeption GmbH
( : +49-711-9905814
Karlsruher Str. 11/1
Fax: +49-711-9905827
D-70771 Leinfelden-Echterdingen
1 _http://www.seskion.de_
------------------------------------------------------------------------
[-- Attachment #2: Type: text/html, Size: 13834 bytes --]
next prev parent reply other threads:[~2006-07-27 9:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-26 14:44 [Bridge] Is bridgeing possible with kernel 2.6.10 Juergen Pfeiffer
2006-07-26 15:34 ` Stephen Hemminger
2006-07-26 16:26 ` Juergen Pfeiffer
2006-07-26 17:13 ` Stephen Hemminger
2006-07-27 9:15 ` Juergen Pfeiffer [this message]
2006-07-27 17:39 ` Stephen Hemminger
2006-07-28 19:17 ` Bart De Schuymer
2006-08-02 23:05 ` [Bridge] [uClinux-dev] " David McCullough
2006-08-14 15:52 ` [Bridge] " Juergen Pfeiffer
[not found] <1167297092.6795.17.camel@getafix.msbmicro.com>
2006-12-28 9:52 ` Juergen Pfeiffer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44C8843A.4010200@seskion.de \
--to=j.pfeiffer@seskion.de \
--cc=bridge@lists.osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox