Bridging-(How to test and verify that bridging is enabled)

[Adam Vande More]

Faizan ul haq Muhammad wrote:
>
>
>
>
> > Date: Mon, 2 Mar 2009 07:48:40 -0600
> > From: amvandemore at gmail.com
> > CC: freebsd-questions at freebsd.org
> > Subject: Re: Bridging-(How to test and verify that bridging is enabled)
> >
> > Faizan ul haq Muhammad wrote:
> > >
> > >
> > >
> > >
> > >
> > >
> > >> Date: Mon, 2 Mar 2009 16:35:33 +0700
> > >> From: on at cs.ait.ac.th
> > >> To: faizi62 at hotmail.com
> > >> CC: fbsd.questions at rachie.is-a-geek.net; 
> freebsd-questions at freebsd.org; fbsd1 at 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
> > >
> > I think ifconfig bridge0 should list member interfaces. Did you add 
> them?
>
> ifconfig bridge0 addm sk0 addm sk1 up
> ifconfig sk0 up
> ifconfig sk1 up
>
> this configuration exists in rc.conf
>
>   
if ifconfig doesn't print out something like this:

bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 
1500
        ether 4a:be:26:65:75:06
        id 00:00:00:00:00:00 priority 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
        member: sk0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>        
                ifmaxaddr 0 port 1 priority 128 path cost 2000000
        member: sk1 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 2 priority 128 path cost 200000

Then you need to add the member interfaces.