Hi Antonio, Ok, this is not a problem, I want to generate an unique image to run both in gateway and routers. I will deploy a wireless mesh network with a geteway beside an authentication server in the wired network. The gateway need to run wifidog daemon to redirect flow from the mesh network to the specific authentication server. Indeed it's not necessary to run wifidog in the MBSS, then I disable wfidog in the routers. But anyway, wifidog must not prevent L2 mesh to work, ok?
2011/11/22 Antonio Anselmi <[email protected]> > - Network --> Captative Portal --> <*> wifidog > > why? > in L2 mesh the captive portal should run outside the MBSS. > > Antonio > > 2011/11/22 romulo albuquerque <[email protected]> > >> Hi everybody, >> >> I have isntalled openwrt backfire buildroot from trunk version in TP-link >> TL-WR1043ND. >> First I followed the steps from http://o11s.org/trac/wiki/OpenWrtBuilding, >> but I had building problems with compat-wireless from >> http://o11s.org/files/compat-wireless-2.6-o11s-0.4.2.tar.bz2. So I gave >> up those steps and made my on 802.11s enabled image following these other >> steps: >> >> 1- installation: >> svn co svn://svn.openwrt.org/openwrt/trunk openwrt >> ./scripts/feeds update -a >> ./scripts/feeds install -a >> make menuconfig >> >> - Target System --> Atheros AR71xx/AR7240/AR913x/AR934x >> - Target Profile --> TP-LINK TL-WR1043ND v1 >> - Kernel Module --> Wireless Drivers --> <*> kmod-ath9k >> - Network --> Captative Portal --> <*> wifidog >> --> File Transfer --> <*> wget >> --> <*> iperf >> --> <*> tcpdump >> --> <*> traceroute >> >> 2- make V=99 >> 3- make kernel_menuconfig >> >> Networking suport --> wireless --> <M> cfg80211 - wireless configuration >> API >> --> <M> Generic IEEE 802.11 >> Networking Stack (mac80211) >> --> <*> Enable >> mac80211 mesh networking (pre-802.11s) support >> >> 4- make V=99 (Then the image was generated in bin/ar71xx) >> >> 5- I followed the recomended configuration to set up the mesh network: >> >> router 1 >> rmmod ath9k >> insmod /lib/modules/2.6.39.4/ath9k.ko nohwcrypt=1 >> iw dev wlan0 interface add mesh0 type mp >> iw dev mesh0 set channel 6 >> ifconfig mesh0 192.168.2.1/24 >> iw dev mesh0 mesh join mymesh >> >> router 2 >> rmmod ath9k >> insmod /lib/modules/2.6.39.4/ath9k.ko nohwcrypt=1 >> iw dev wlan0 interface add mesh0 type mp >> iw dev mesh0 set channel 6 >> ifconfig mesh0 192.168.2.2/24 >> iw dev mesh0 mesh join mymesh >> >> When I run: >> iw dev mesh0 station dump >> >> I can see this result: >> Station d8:5d:4c:d4:fd:7c (on mesh0) >> inactive time: 920 ms >> rx bytes: 25320 >> rx packets: 634 >> tx bytes: 223 >> tx packets: 3 >> tx retries: 0 >> tx failed: 0 >> signal: -52 dBm >> signal avg: -51 [-66, -53, -60] dBm >> tx bitrate: 1.0 MBit/s >> rx bitrate: 1.0 MBit/s >> mesh llid: 65475 >> mesh plid: 36832 >> mesh plink: ESTAB >> >> It seems that routers are establishing connection on layer 2, but when I >> try to ping they do not respond >> I'm using ath9k driver and compat-wireless-2011-11-04.tar.bz2. >> Have anyone had similar problem with ath9k + 802.11s in backfire from >> trunk version? >> >> Thanks for your attention. >> >> Regards. >> >> -- >> Rômulo Pinto de Albuquerque >> >> _______________________________________________ >> Devel mailing list >> [email protected] >> http://open80211s.com/mailman/listinfo/devel >> >> > > _______________________________________________ > Devel mailing list > [email protected] > http://open80211s.com/mailman/listinfo/devel > > -- Rômulo Pinto de Albuquerque
_______________________________________________ Devel mailing list [email protected] http://open80211s.com/mailman/listinfo/devel
