Re: [Madwifi-users] HELP Please - The Next Step (WDS Bridging)
Status: Beta
Brought to you by:
otaku
Menu
▾
▴
Re: [Madwifi-users] HELP Please - The Next Step (WDS Bridging)
|
From: Jon S. <jsc...@po...> - 2006-01-23 19:38:29
|
Also, I have one other question, does setting this up, does it need to write any files to the file system. Most of the system I am running on is a Read only filesystem. Not sure if that matters or not. Thanks On Mon, 2006-01-23 at 12:33 -0700, Jon Scottorn wrote: > On Sat, 2006-01-21 at 10:47 +0100, Jiri Fojtasek wrote: > > > Hello Jon > > > > I have found this glitches: > > > > You have not assigned a IP address to the bridge, you leaved a IP > > address on the interface whis is part of the bridge. Try this: > > > > brctl addbr br0 > > brctl addif br0 ath0 > > brctl addif br0 ath1 > > fconfig ath1 0.0.0.0 up > > fconfig ath0 0.0.0.0 up > > ifconfig br0 192.168.30.145 netmask 255.255.255.0 up > > route add default gw 192.168.30.1 > > > > ok, i have assigned an address to br0 but still can't access the > network. On the unit it is connecting to I run iwevent to see any > activity throught the wireless device and nothing is happening when my > wds device boots up. I can connect a laptop to the head unit and I > can see the wireless event show up registering the laptop but the WDS > unit says it is registered to the head unit but I don't see it show up > in the event list. The only time I get it to show up is if I break > the bridge and just connect the unit in station mode. > > > With this you get the ping from your box working. Another part that can > > break your bridging is ath0 sta pseudowds bridge. I recomending you use > > the real wds bridge instead of the sta pseudowds bridge so try this: > > > > wlanconfig ath0 create wlandev wifi0 wlanmode wds > > iwpriv ath0 wds_add 00:15:6D:10:23:CE (it seems as mac of you bridged ap) > > iwpriv ath0 wds 1 > > > > I have tried this way as well and it still doesn't work. > > > And at other side of the wds link create wds vap linked with your side > > (for wds_add use device mac address from ath0) > > > > All this have one problem, you must use patch i posed under ticket 312 > > whis fixing true wds bridge nonfunctionality .. > > > > I am running a svn checkout of trunk as of 1/20/2006, which from what > I can tell that patch is already implimented. > > > Jiri > > > > Here is my interfaces file to bring up br0 on the WDS unit: > I am trying it with one atheros card as the wan side and I have been > swapping out the lan side between an atheros card and a proxim card. > I just need it working so I am trying anything. > > iface br0 inet static > address 192.168.30.141 > netmask 255.255.255.0 > network 192.168.30.0 > broadcast 192.168.30.255 > gateway 192.168.30.1 > # pre-up wlanconfig ath1 create wlandev wifi1 wlanmode ap > pre-up wlanconfig ath0 create wlandev wifi0 wlanmode wds > # pre-up iwconfig ath1 essid "avalon" channel 4 > ## pre-up iwconfig ath1 txpower 400mW > iwpriv ath0 wds_add 00:15:6d:10:23:ce > pre-up iwpriv ath0 wds 1 > iwpriv ath0 wds_add 00:15:6d:10:23:ce > pre-up iwpriv ath0 wds 1 > # pre-up iwconfig ath0 essid avalon-backbone > pre-up iwconfig wlan0 essid avalon channel 4 > pre-up ifconfig ath0 0.0.0.0 up > # pre-up ifconfig ath1 0.0.0.0 up > pre-up ifconfig wlan0 0.0.0.0 up > pre-up brctl addbr br0 > pre-up brctl addif br0 ath0 > pre-up brctl addif br0 wlan0 > # post-down ifconfig ath1 0.0.0.0 down > post-down ifconfig ath0 0.0.0.0 down > post-down ifconfig wlan0 0.0.0.0 down > post-down brctl delif br0 ath0 > post-down brctl delif br0 wlan0 > post-down brctl delbr br0 > # post-down wlanconfig ath1 destroy > post-down wlanconfig ath0 destroy > > Here is my interfaces file for the head unit. > > iface br0 inet static > address 192.168.30.140 > netmask 255.255.255.0 > broadcast 192.168.30.255 > gateway 192.168.30.1 > # bridge_ports ath0 eth0 > pre-up wlanconfig ath0 create wlandev wifi0 wlanmode ap > # pre-up iwpriv ath0 wds 1 > pre-up iwconfig ath0 essid "avalon-backbone" channel 52 > pre-up ifconfig eth0 0.0.0.0 up > pre-up ifconfig ath0 0.0.0.0 up > pre-up brctl addbr br0 > pre-up brctl addif br0 eth0 > pre-up brctl addif br0 ath0 > post-down ifconfig ath0 0.0.0.0 down > post-down ifconfig eth0 0.0.0.0 down > post-down brctl delif br0 ath0 > post-down brctl delif br0 eth0 > post-down brctl delbr br0 > post-down wlanconfig ath0 destroy > > > If someone could please explain what I might be doing wrong here. I > am at my whits end. > > Thanks for all the help and advice in advance. > > Jon > > > Jon Scottorn wrote: > > > Ok, Thanks for all the responses, I have got my ath to eth bridge > > > working. I had to reset the box to get it to work for some reason. I > > > actually got a kernel panic when I tried changing some settings and > > > then after a reboot it all came up so I've rebooted a few times now > > > and it comes up everytime. > > > > > > Now my next step. I am now working on getting a wireless to wireless > > > bridge setup. I now want to connect a wireless bridge to the bridge I > > > just got working. > > > > > > For keeping things straight: > > > > > > bridge A is my head bridge that has the ath => eth bridge. > > > bridge B is my wireless client bridge that I want to be ath => ath bridge. > > > > > > Bridge A works good now and is accessing the Inet just fine. > > > > > > bridge b can connect to bridge a in station mode and can access the > > > Inet just fine which which is done by these commands > > > > > > pfars-uc-000db9009224:~# wlanconfig ath0 create wlandev wifi0 wlanmode sta > > > ath0 > > > pfars-uc-000db9009224:~# iwpriv ath0 wds 1 > > > pfars-uc-000db9009224:~# iwconfig ath0 essid "avalon-backbone" > > > pfars-uc-000db9009224:~# ifconfig ath0 192.168.30.145 netmask > > > 255.255.255.0 up > > > pfars-uc-000db9009224:~# route add default gw 192.168.30.1 > > > pfars-uc-000db9009224:~# wlanconfig ath0 list scan > > > SSID BSSID CHAN RATE S:N INT CAPS > > > avalon-back... 00:15:6d:10:23:ce 52 54M 56:0 100 Es WME ATH > > > > > > Now I can ping out. > > > > > > pfars-uc-000db9009224:~# ping google.com > > > PING google.com (72.14.207.99): 56 data bytes > > > 64 bytes from 72.14.207.99: icmp_seq=0 ttl=241 time=92.0 ms > > > 64 bytes from 72.14.207.99: icmp_seq=1 ttl=241 time=92.2 ms > > > 64 bytes from 72.14.207.99: icmp_seq=2 ttl=241 time=92.3 ms > > > 64 bytes from 72.14.207.99: icmp_seq=3 ttl=241 time=92.2 ms > > > 64 bytes from 72.14.207.99: icmp_seq=5 ttl=241 time=92.1 ms > > > > > > Now I create my other ath interface for my ap. > > > > > > pfars-uc-000db9009224:~# wlanconfig ath1 create wlandev wifi1 wlanmode ap > > > ath1 > > > pfars-uc-000db9009224:~# iwconfig ath1 essid "avalon" channel 4 > > > pfars-uc-000db9009224:~# ifconfig ath1 0.0.0.0 up > > > > > > Here is what iwconfig reports > > > > > > pfars-uc-000db9009224:~# iwconfig > > > eth0 no wireless extensions. > > > > > > lo no wireless extensions. > > > > > > wifi0 no wireless extensions. > > > > > > wifi1 no wireless extensions. > > > > > > ath0 IEEE 802.11a ESSID:"avalon-backbone" > > > Mode:Managed Frequency:5.26 GHz Access Point: > > > 00:15:6D:10:23:CE > > > Bit Rate:36 Mb/s Tx-Power:18 dBm Sensitivity=0/3 > > > Retry:off RTS thr:off Fragment thr:off > > > Encryption key:off > > > Power Management:off > > > Link Quality=65/94 Signal level=-30 dBm Noise level=-95 dBm > > > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 > > > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > > > > > > ath1 IEEE 802.11g ESSID:"avalon" > > > Mode:Master Frequency:2.427 GHz Access Point: > > > 00:15:6D:10:24:7A > > > Bit Rate:0 kb/s Tx-Power:16 dBm Sensitivity=0/3 > > > Retry:off RTS thr:off Fragment thr:off > > > Encryption key:off > > > Power Management:off > > > Link Quality=40/94 Signal level=-55 dBm Noise level=-95 dBm > > > Rx invalid nwid:3 Rx invalid crypt:0 Rx invalid frag:0 > > > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > > > > > > Now I try to create the bridge > > > > > > pfars-uc-000db9009224:~# brctl addbr br0 > > > pfars-uc-000db9009224:~# brctl addif br0 ath0 > > > device ath0 entered promiscuous mode > > > pfars-uc-000db9009224:~# brctl addif br0 ath1 > > > device ath1 entered promiscuous mode > > > > > > As soon as I do this I can no longer access anything, not even the > > > bridge A. > > > > > > If I delete the interfaces from br0 it starts working again. > > > > > > I have tried both setups from the wiki pages form > > > http://madwifi.org/wiki/UserDocs/WDSBridge > > > I can't seem to get either of them working. > > > > > > The only real difference between my setup and what they have on the > > > wiki is that I am using two wifi cards ie.. wifi0 and wifi1 > > > the examples only use wifi0 to create multiple interfaces. > > > > > > If anyone can help me figure out how to get WDS working this way it is > > > greatly appreciated. > > > > > > Thanks, > > > > > > Jon > > > > > > On Fri, 2006-01-20 at 19:09 -0500, Bob Beers wrote: > > >> > > >> > > >> On 1/20/06, *Bob Beers* <bob...@gm... > > >> <mailto:bob...@gm...>> wrote: > > >> > > >> > > >> > > >> On 1/20/06, *Jon Scottorn* <jsc...@po... > > >> <mailto:jsc...@po...>> wrote: > > >> > > >> On Sat, 2006-01-21 at 09:09 +1000, Aaron Daniels wrote: > > >>> Jon, > > >>> > > >>> > Here are my exact commands > > >>> > > > >>> > wlanconfig ath0 create wlandev wifi0 wlanmode ap > > >>> > iwconfig ath0 essid "test" > > >>> > > > >>> > > >>> You will also need to bring the interface up before it is visible. > > >>> ifconfig ath0 up > > >>> > > >>> > > >> Sorry, I forgot to put that in my last post, that is exactaly > > >> what I did. > > >>> Aaron > > >>> > > >> > > >> > > >> > > >> try putting the 'ifconfig ath0 up' in between the wlanconfig > > >> command and > > >> the iwconfig commands. > > >> > > >> -Bob > > >> > > >> > > >> > > >> BTW: here's what I mean by cut and paste from command line: > > >> > > >> -bash-3.00# /sbin/modprobe ath_pci > > >> -bash-3.00# wlanconfig wlan0 create wlandev wifi0 wlanmode ap > > >> wlan0 > > >> -bash-3.00# ifconfig wlan0 up > > >> -bash-3.00# iwconfig wlan0 essid bob > > >> -bash-3.00# iwconfig > > >> lo no wireless extensions. > > >> > > >> eth0 no wireless extensions. > > >> > > >> eth1 no wireless extensions. > > >> > > >> hdlc0 no wireless extensions. > > >> > > >> pvc0 no wireless extensions. > > >> > > >> wifi0 no wireless extensions. > > >> > > >> Warning: Driver for device wlan0 has been compiled with version 19 > > >> of Wireless Extension, while this program supports up to version 18. > > >> Some things may be broken... > > >> > > >> wlan0 IEEE 802.11g ESSID:"bob" > > >> Mode:Master Frequency:2.417 GHz Access Point: > > >> 00:11:95:F2:01:A4 > > >> Bit Rate:0 kb/s Tx-Power:18 dBm Sensitivity=0/3 > > >> Retry:off RTS thr:off Fragment thr:off > > >> Encryption key:off > > >> Power Management:off > > >> Link Quality=0/94 Signal level=-95 dBm Noise level=-95 dBm > > >> Rx invalid nwid:42 Rx invalid crypt:0 Rx invalid frag:0 > > >> Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > > >> > > >> -bash-3.00# > > >> > > >> > > >> Works for me :) > > >> > > >> > > > */Jon Scottorn/* > > > /Systems Administrator/ > > > /The Possibility Forge, Inc./ > > > /http://www.possibilityforge.com/ > > > /435.635.0591 x.1004/ > > > > > > > > > ------------------------------------------------------- > > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files > > for problems? Stop! Download the new AJAX search engine that makes > > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 > > _______________________________________________ > > Madwifi-users mailing list > > Mad...@li... > > https://lists.sourceforge.net/lists/listinfo/madwifi-users > > Jon Scottorn > Systems Administrator > The Possibility Forge, Inc. > http://www.possibilityforge.com > 435.635.0591 x.1004 Jon Scottorn Systems Administrator The Possibility Forge, Inc. http://www.possibilityforge.com 435.635.0591 x.1004 |