> Date: Mon, 2 Mar 2009 16:35:33 +0700
> From: o...@cs.ait.ac.th
> To: faiz...@hotmail.com
> CC: fbsd.questi...@rachie.is-a-geek.net; freebsd-questions@freebsd.org; 
> fb...@a1poweruser.com
> Subject: Re: Bridging-(How to test and verify that bridging is enabled)
> 
> Hi,
> 
> > > Are you using properly crossed cables?
> > Isnt it enough check for the that two linux can ping each other..
> 
> Yes and no. You must used crossed Ethernet cable between your FreeBSD
> bridge and each of your Linux boxes.
Frankly i am not sure about the cables type but they works PC to PC 
connectivity. 
> As someone suggested, what is ifconfig saying on the FreeBSD box? You
> should see that both sk0 and sk1 have a status: active. Else it means
> you have a cable problem.

sk0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 
1500

options=b<RXCSUM, TXCSUM, VLAN_MTU
 ether 00:0a:5e:1a:69:25
 media: Ethernet autoselect (1000baseTX <full-duplex, flag0, flag1, flag2>)
 status: active

 

 

sk1: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 
1500

options=b<RXCSUM, TXCSUM, VLAN_MTU
 ether 00:0a:5e:1a:67:ee
 media: Ethernet autoselect (1000baseTX <full-duplex, flag0, flag1, flag2>)
 status: active

 

here is the ifconfig output for the bridge interface:

bridge0: flags=8943<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500

options=b<RXCSUM, TXCSUM, VLAN_MTU
 ether 0a:54:d7:7e:aa:66

inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255

id 00:00:00:00:00:00 priortiy 32768 hellotime 2 fwddelay 15

maxage 20 holdcnt 6 proto rstp maxaddr 100 timeout 1200

root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0



> 
> An example of ifconfig for a bridge (FreeBSD 4.xx):
> 
> fxp0: flags=89c3<UP,BROADCAST,RUNNING,NOARP,PROMISC,SIMPLEX,MULTICAST> mtu 
> 1500
> ether 00:07:e9:xx:xx:xx
> media: Ethernet autoselect (100baseTX <full-duplex>)
> status: active
> fxp1: flags=89c3<UP,BROADCAST,RUNNING,NOARP,PROMISC,SIMPLEX,MULTICAST> mtu 
> 1500
> ether 00:07:e9:yy:yy:yy
> media: Ethernet autoselect (100baseTX <full-duplex>)
> status: active
> 
> Once you make sure that both interfaces on your FreeBSD box are up and
> running, you can procced to the next step:
> 
> > > On the FreeBSD box=2C you can tcpdump(8) and see the packets moving:
> > > tcpdump -i sk0 and tcpdump -i sk1 and you will see the pick request
> > > and ping echo packets.
> > it says arp: who has 192.168.0.4 tell 192.168.0.5
> 
> You'd need to give more information about your connection; something
> like:
> 
> Linux 192.168.0.4 <---> sk0 FreeBSD sk1 <---> Linux 192.168.0.5
> 
> And you should also specify if ou where tcpdump'ing on interface sk0
> or sk1. Once your bridge is working, you will get the same thing for
> tcpdump on both interfaces.
ok here is the detail:

 

 Linux 192.168.0.5 <---> sk0 FreeBSD sk1 <---> Linux 192.168.0.4

ping from 192.168.0.5 to 192.168.0.4

tcpdump (on freeBSD) tcpdump -i sk0  RESULT arp: who has 192.168.0.4 tell 
192.168.0.5


ping from 192.168.0.4 to 192.168.0.5

tcpdump (on freeBSD) tcpdump -i sk1  RESULT arp: who has 192.168.0.5 tell 
192.168.0.4

tcpdump -i bridge0 gives nothing...
> Olivier


_________________________________________________________________
Windows Liveā„¢ Groups: Create an online spot for your favorite groups to meet.
http://windowslive.com/online/groups?ocid=TXT_TAGLM_WL_groups_032009_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Reply via email to