Re: bridging ath

2007-09-29 Thread Randy Bush
>> so it does not want to be an AP but it does want to bridge. > At the bottom of if_bridge(4): > "Only wireless interfaces in hostap mode can be bridged due to the > 802.11 framing format, bridging a wireless client is not supported yet." randy, rearchitecting __

Re: bridging ath

2007-09-29 Thread Andrew Thompson
On Fri, Sep 28, 2007 at 10:01:04PM -1000, Randy Bush wrote: > > I don't know what you're trying to do > > no surprise. i rarely do. :) > > > When you attach your wired nic to a bridge and and turn the bridge on > > the nic gets set in promiscuous mode. This is likely why you can > > ping the ot

Re: bridging ath

2007-09-29 Thread Randy Bush
> I don't know what you're trying to do no surprise. i rarely do. :) > When you attach your wired nic to a bridge and and turn the bridge on > the nic gets set in promiscuous mode. This is likely why you can > ping the other wireless station through the wired nic. To ping the > wireless statio

Re: bridging ath

2007-09-27 Thread Sam Leffler
Sam Leffler wrote: Randy Bush wrote: Be sure apbridge is enabled not running in hostap mode, not an access point You can only bridge a wireless card in hostap mode. Sorry, engage brain before opening mouth. I don't know what you're trying to do but you're looking in the wrong plac

Re: bridging ath

2007-09-27 Thread Randy Bush
> You can only bridge a wireless card in hostap mode. after your earlier comment, i tried that too :( it's not that i think i have not done something stupid. i just can't find it :) randy ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.o

Re: bridging ath

2007-09-27 Thread Sam Leffler
Randy Bush wrote: Be sure apbridge is enabled not running in hostap mode, not an access point You can only bridge a wireless card in hostap mode. Sam ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/fre

Re: bridging ath

2007-09-27 Thread Randy Bush
> Be sure apbridge is enabled not running in hostap mode, not an access point > you can use tcpdump to check traffic on each interface to isolate the issue. the ath interface 00:28:26.699253 IP dhcp1.psg.com > hawi0.psg.com: ICMP echo request, id 56334, seq 218, length 64 00:28:26.699295 IP ha

Re: bridging ath

2007-09-27 Thread Randy Bush
> device if_bridge > or > if_bridge_load="YES" in loader.conf is all that's needed. if_bridge.ko is automagically loaded, no extra charge > For testing purposes, you might want to disable the filtering > configuration with: > sysctl net.link.bridge.pfil_member=0 > sysctl net.link.bridge.pfil_brid

Re: bridging ath

2007-09-27 Thread Sam Leffler
Randy Bush wrote: Andrew Thompson wrote: On Wed, Sep 26, 2007 at 04:07:00PM -1000, Randy Bush wrote: current i386 thinkpad t41 ifconfig_lo0="inet 127.0.0.1/8" cloned_interfaces="bridge0" ifconfig_bridge0="inet 192.168.0.3/24 addm em0 addm ath0 up" ifconfig_em0="up" ifconfig_ath0="ssid

RE: bridging ath

2007-09-27 Thread Michael K. Smith - Adhost
> -Original Message- > From: Andrew Thompson [mailto:[EMAIL PROTECTED] > Sent: Thursday, September 27, 2007 4:22 PM > To: Randy Bush > Cc: Michael K. Smith - Adhost; FreeBSD Net > Subject: Re: bridging ath > > On Thu, Sep 27, 2007 at 01:19:42PM -1000, Randy Bush

Re: bridging ath

2007-09-27 Thread Andrew Thompson
On Thu, Sep 27, 2007 at 01:19:42PM -1000, Randy Bush wrote: > > Just to be sure... > > good questions, thanks for asking > > > net.inet.ip.forwarding=1 > > # sysctl net.inet.ip.forwarding > net.inet.ip.forwarding: 1 > > > net.link.ether.bridge.enable=1 > > net.link.ether.bridge.config=em0,ath0

Re: bridging ath

2007-09-27 Thread Randy Bush
> Just to be sure... good questions, thanks for asking > net.inet.ip.forwarding=1 # sysctl net.inet.ip.forwarding net.inet.ip.forwarding: 1 > net.link.ether.bridge.enable=1 > net.link.ether.bridge.config=em0,ath0 # sysctl net.link.ether.bridge.enable sysctl: unknown oid 'net.link.ether.bridge.

RE: bridging ath

2007-09-27 Thread Michael K. Smith - Adhost
> > Andrew Thompson wrote: > > On Wed, Sep 26, 2007 at 04:07:00PM -1000, Randy Bush wrote: > >> current i386 thinkpad t41 > >> > >> ifconfig_lo0="inet 127.0.0.1/8" > >> cloned_interfaces="bridge0" > >> ifconfig_bridge0="inet 192.168.0.3/24 addm em0 addm ath0 up" > >> ifconfig_em0="up" > >> ifconfi

Re: bridging ath

2007-09-27 Thread Randy Bush
Andrew Thompson wrote: > On Wed, Sep 26, 2007 at 04:07:00PM -1000, Randy Bush wrote: >> current i386 thinkpad t41 >> >> ifconfig_lo0="inet 127.0.0.1/8" >> cloned_interfaces="bridge0" >> ifconfig_bridge0="inet 192.168.0.3/24 addm em0 addm ath0 up" >> ifconfig_em0="up" >> ifconfig_ath0="ssid rgnet up

Re: bridging ath

2007-09-27 Thread Andrew Thompson
On Wed, Sep 26, 2007 at 04:07:00PM -1000, Randy Bush wrote: > current i386 thinkpad t41 > > ifconfig_lo0="inet 127.0.0.1/8" > cloned_interfaces="bridge0" > ifconfig_bridge0="inet 192.168.0.3/24 addm em0 addm ath0 up" > ifconfig_em0="up" > ifconfig_ath0="ssid rgnet up" > defaultrouter="192.168.0.1"

bridging ath

2007-09-26 Thread Randy Bush
current i386 thinkpad t41 ifconfig_lo0="inet 127.0.0.1/8" cloned_interfaces="bridge0" ifconfig_bridge0="inet 192.168.0.3/24 addm em0 addm ath0 up" ifconfig_em0="up" ifconfig_ath0="ssid rgnet up" defaultrouter="192.168.0.1" with ether plugged in, i can ping it. unplug ether and no ping over ath0.