when setting up the mesh iface don't use the ssid option. it is not needed.
David Fulgham On Tue, Nov 22, 2011 at 7:51 PM, Yeoh Chun-Yeow <[email protected]>wrote: > Hi, Romulo > > Can you create only one mesh node in both your routers and see whether > they are able to communication before creating the AP mode for the same > radio. At least, we need to make sure the mesh nodes working first. > > Regards, > Chun-Yeow > > > On Wed, Nov 23, 2011 at 8:15 AM, romulo albuquerque > <[email protected]>wrote: > >> Hi Thomas, >> Today I have configured the 2 nodes in this way: >> >> 1- I have created 2 ifaces: one for ap mode and the other one for mesh >> mode, look: >> >> /etc/config/network >> [...] >> config 'interface' 'ap' >> option 'proto' 'static' >> option 'ipaddr' '192.168.2.1' >> option 'netmask' '255.255.255.0' >> >> config 'interface' 'mesh' >> option 'proto' 'static' >> option 'ipaddr' '10.0.0.1' >> option 'netmask' '255.255.255.0' >> >> /etc/config/wireless >> [...] >> config 'wifi-iface' 'mesh0' >> option 'device' 'radio0' >> option 'network' 'mesh' >> option 'mode' 'mesh' >> option 'mesh_id' 'mymesh' >> option 'ssid' 'mesh' >> >> config 'wifi-iface' >> option 'device' 'radio0' >> option 'network' 'ap' >> option 'mode' 'ap' >> option 'ssid' 'meshap' >> option 'encryption' 'none' >> >> 2- running ifconfig: >> >> mon.wlan0 Link encap:UNSPEC HWaddr >> D8-5D-4C-EB-84-3C-00-47-00-00-00-00-00-00-00-00 >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:12881 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:32 >> RX bytes:1820051 (1.7 MiB) TX bytes:0 (0.0 B) >> >> wlan0 Link encap:Ethernet HWaddr D8:5D:4C:EB:84:3C >> inet addr:192.168.2.1 Bcast:192.168.2.255 Mask:255.255.255.0 >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:3 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:32 >> RX bytes:0 (0.0 B) TX bytes:180 (180.0 B) >> >> wlan0-1 Link encap:Ethernet HWaddr DA:5D:4C:EB:84:3D >> inet addr:10.0.0.1 Bcast:10.0.0.255 Mask:255.255.255.0 >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:32 >> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) >> >> 3- running iw dev: >> >> phy#0 >> Interface mon.wlan0 >> ifindex 21 >> type monitor >> Interface wlan0-1 >> ifindex 20 >> type mesh point >> Interface wlan0 >> ifindex 19 >> type AP >> >> 4- running iw dev wlan0-1 station dump: it seems that the node stablish >> L2 connection with the other node (da:5d:4c:d4:fd:7d) >> >> Station da:5d:4c:d4:fd:7d (on wlan0-1) >> inactive time: 30 ms >> rx bytes: 12271 >> rx packets: 332 >> tx bytes: 205 >> >> tx packets: 3 >> tx retries: 0 >> tx failed: 0 >> signal: -41 dBm >> signal avg: -40 [-48, -42, -58] dBm >> >> tx bitrate: 1.0 MBit/s >> rx bitrate: 1.0 MBit/s >> mesh llid: 52474 >> mesh plid: 63532 >> mesh plink: ESTAB >> >> OBSERVATION: when I put 'ap' to the second wifi-iface and run station >> dump command the nodes don't stablish connection >> >> config 'wifi-iface' 'mesh0' >> [...] >> config 'wifi-iface' 'ap' >> [...] >> >> 5- running iw dev wlan0-1 mpath dump: nothing appear >> >> DEST ADDR NEXT HOP IFACE SN METRIC QLEN >> EXPTIME DTIM DRET FLAGS >> >> 6- running dmesg: >> >> Linux version 2.6.39.4 (romulo@romulo) (gcc version 4.5.4 20110808 >> (prerelease) (Linaro GCC 4.5-2011.08) ) #3 Fri Nov 18 20:23:22 BRT 2011 >> prom: fw_arg0=00000007, fw_arg1=a1f77fb0, fw_arg2=a1f78440, >> fw_arg3=00000008 >> MyLoader: sysp=ffffffff, boardp=f7ffefff, parts=ffffffdf >> bootconsole [early0] enabled >> CPU revision is: 00019374 (MIPS 24Kc) >> SoC: Atheros AR9132 rev 2 >> Clocks: CPU:400.000MHz, DDR:400.000MHz, AHB:200.000MHz, Ref:5.000MHz >> Determined physical RAM map: >> memory: 02000000 @ 00000000 (usable) >> Initrd not found or empty - disabling initrd >> Zone PFN ranges: >> Normal 0x00000000 -> 0x00002000 >> Movable zone start PFN for each node >> early_node_map[1] active PFN ranges >> 0: 0x00000000 -> 0x00002000 >> On node 0 totalpages: 8192 >> free_area_init_node: node 0, pgdat 802b89a0, node_mem_map 81000000 >> Normal zone: 64 pages used for memmap >> Normal zone: 0 pages reserved >> Normal zone: 8128 pages, LIFO batch:0 >> pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768 >> pcpu-alloc: [0] 0 >> Built 1 zonelists in Zone order, mobility grouping on. Total pages: 8128 >> Kernel command line: board=TL-WR1043ND console=ttyS0,115200 >> rootfstype=squashfs,jffs2 noinitrd >> PID hash table entries: 128 (order: -3, 512 bytes) >> Dentry cache hash table entries: 4096 (order: 2, 16384 bytes) >> Inode-cache hash table entries: 2048 (order: 1, 8192 bytes) >> Primary instruction cache 64kB, VIPT, 4-way, linesize 32 bytes. >> Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes >> Writing ErrCtl register=00000000 >> Readback ErrCtl register=00000000 >> Memory: 29364k/32768k available (2011k kernel code, 3404k reserved, 392k >> data, 180k init, 0k highmem) >> SLUB: Genslabs=9, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 >> NR_IRQS:80 >> Calibrating delay loop... 265.42 BogoMIPS (lpj=1327104) >> pid_max: default: 32768 minimum: 301 >> Mount-cache hash table entries: 512 >> NET: Registered protocol family 16 >> MIPS: machine is TP-LINK TL-WR1043ND >> bio: create slab <bio-0> at 0 >> Switching to clocksource MIPS >> NET: Registered protocol family 2 >> IP route cache hash table entries: 1024 (order: 0, 4096 bytes) >> TCP established hash table entries: 1024 (order: 1, 8192 bytes) >> TCP bind hash table entries: 1024 (order: 0, 4096 bytes) >> TCP: Hash tables configured (established 1024 bind 1024) >> TCP reno registered >> UDP hash table entries: 256 (order: 0, 4096 bytes) >> UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) >> NET: Registered protocol family 1 >> PCI: CLS 0 bytes, default 32 >> squashfs: version 4.0 (2009/01/31) Phillip Lougher >> JFFS2 version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) >> 2001-2006 Red Hat, Inc. >> msgmni has been set to 57 >> io scheduler noop registered >> io scheduler deadline registered (default) >> Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled >> serial8250.0: ttyS0 at MMIO 0x18020000 (irq = 11) is a 16550A >> console [ttyS0] enabled, bootconsole disabled >> Atheros AR71xx SPI Controller driver version 0.2.4 >> m25p80 spi0.0: found s25sl064a, expected m25p80 >> m25p80 spi0.0: s25sl064a (8192 Kbytes) >> spi0.0: searching for MyLoader partition table at offset 0x10000 >> spi0.0: searching for MyLoader partition table at offset 0x20000 >> spi0.0: searching for MyLoader partition table at offset 0x30000 >> spi0.0: searching for MyLoader partition table at offset 0x40000 >> spi0.0: no MyLoader partition table found >> Searching for RedBoot partition table in spi0.0 at offset 0x7e0000 >> Searching for RedBoot partition table in spi0.0 at offset 0x7f0000 >> No RedBoot partition table detected in spi0.0 >> spi0.0: no WRT160NL signature found >> Creating 5 MTD partitions on "spi0.0": >> 0x000000000000-0x000000020000 : "u-boot" >> 0x000000020000-0x000000160000 : "kernel" >> 0x000000160000-0x0000007f0000 : "rootfs" >> mtd: partition "rootfs" set to be root filesystem >> mtd: partition "rootfs_data" created automatically, ofs=420000, >> len=3D0000 >> 0x000000420000-0x0000007f0000 : "rootfs_data" >> 0x0000007f0000-0x000000800000 : "art" >> 0x000000020000-0x0000007f0000 : "firmware" >> Realtek RTL8366RB ethernet switch driver version 0.2.3 >> rtl8366rb rtl8366rb: using GPIO pins 18 (SDA) and 19 (SCK) >> rtl8366rb rtl8366rb: RTL5937 ver. 3 chip found >> rtl8366rb: probed >> eth0: Atheros AG71xx at 0xb9000000, irq 4 >> eth0: using fixed link parameters >> Atheros AR71xx hardware watchdog driver version 0.1.0 >> ar71xx-wdt: timeout=15 secs (max=21) >> TCP westwood registered >> NET: Registered protocol family 17 >> 802.1Q VLAN Support v1.8 Ben Greear <[email protected]> >> All bugs added by David S. Miller <[email protected]> >> VFS: Mounted root (squashfs filesystem) readonly on device 31:2. >> Freeing unused kernel memory: 180k freed >> input: gpio-keys-polled as /devices/platform/gpio-keys-polled/input/input0 >> Button Hotplug driver version 0.4.1 >> ar71xx: pll_reg 0xb8050014: 0x1a000000 >> eth0: link up (1000Mbps/Full duplex) >> Registered led device: tp-link:green:usb >> Registered led device: tp-link:green:system >> Registered led device: tp-link:green:qss >> Registered led device: tp-link:green:wlan >> JFFS2 notice: (405) jffs2_build_xattr_subsystem: complete building xattr >> subsystem, 20 of xdatum (0 unchecked, 19 orphan) and 28 of xref (0 dead, 19 >> orphan) found. >> eth0: link down >> Compat-wireless backport release: compat-wireless-2011-10-14 >> Backport based on wireless-testing.git master-2011-11-04 >> cfg80211: Calling CRDA to update world regulatory domain >> usbcore: registered new interface driver usbfs >> usbcore: registered new interface driver hub >> cfg80211: World regulatory domain updated: >> cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, >> max_eirp) >> cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) >> cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) >> cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) >> cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) >> cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) >> usbcore: registered new device driver usb >> ath: EEPROM regdomain: 0x0 >> ath: EEPROM indicates default country code should be used >> ath: doing EEPROM country->regdmn map search >> ath: country maps to regdmn code: 0x3a >> ath: Country alpha2 being used: US >> ath: Regpair used: 0x3a >> ieee80211 phy0: Selected rate control algorithm 'ath9k_rate_control' >> ieee80211 phy0: Atheros AR9100 MAC/BB Rev:7 AR2133 RF Rev:a2 >> mem=0xb80c0000, irq=2 >> cfg80211: Calling CRDA for country: US >> PPP generic driver version 2.4.2 >> cfg80211: Regulatory domain changed to country: US >> cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, >> max_eirp) >> cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm) >> cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm) >> cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) >> cfg80211: (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) >> cfg80211: (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) >> cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm) >> ip_tables: (C) 2000-2006 Netfilter Core Team >> NET: Registered protocol family 24 >> ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver >> ar71xx-ehci ar71xx-ehci: Atheros AR91xx built-in EHCI controller >> ar71xx-ehci ar71xx-ehci: new USB bus registered, assigned bus number 1 >> ar71xx-ehci ar71xx-ehci: irq 3, io mem 0x1b000000 >> ar71xx-ehci ar71xx-ehci: USB 2.0 started, EHCI 1.00 >> hub 1-0:1.0: USB hub found >> hub 1-0:1.0: 1 port detected >> nf_conntrack version 0.5.0 (461 buckets, 1844 max) >> xt_time: kernel timezone is -0000 >> ar71xx: pll_reg 0xb8050014: 0x1a000000 >> eth0: link up (1000Mbps/Full duplex) >> device eth0.1 entered promiscuous mode >> device eth0 entered promiscuous mode >> br-lan: port 1(eth0.1) entering forwarding state >> br-lan: port 1(eth0.1) entering forwarding state >> wlan0: Selected IBSS BSSID 9a:cc:17:b6:44:e4 based on configured SSID >> ar71xx-wdt: enabling watchdog timer >> wlan0: Selected IBSS BSSID 9a:cc:17:b6:44:e4 based on configured SSID >> wlan0: Selected IBSS BSSID 9a:cc:17:b6:44:e4 based on configured SSID >> wlan0: Trigger new scan to find an IBSS to join >> device wlan0 entered promiscuous mode >> device wlan0 left promiscuous mode >> device wlan0 entered promiscuous mode >> device wlan0 left promiscuous mode >> device wlan0 entered promiscuous mode >> device wlan0 left promiscuous mode >> device wlan0 entered promiscuous mode >> device wlan0 left promiscuous mode >> device wlan0 entered promiscuous mode >> device wlan0 left promiscuous mode >> device wlan0 entered promiscuous mode >> device wlan0 left promiscuous mode >> device wlan0 entered promiscuous mode >> device wlan0 left promiscuous mode >> device wlan0 entered promiscuous mode >> device wlan0 left promiscuous mode >> device wlan0 entered promiscuous mode >> device wlan0 left promiscuous mode >> device wlan0 entered promiscuous mode >> device wlan0 left promiscuous mode >> br-lan: port 1(eth0.1) entering forwarding state >> device eth0 left promiscuous mode >> device eth0.1 left promiscuous mode >> br-lan: port 1(eth0.1) entering disabled state >> device eth0.1 entered promiscuous mode >> device eth0 entered promiscuous mode >> br-lan: port 1(eth0.1) entering forwarding state >> br-lan: port 1(eth0.1) entering forwarding state >> br-lan: port 1(eth0.1) entering forwarding state >> device eth0 left promiscuous mode >> device eth0.1 left promiscuous mode >> br-lan: port 1(eth0.1) entering disabled state >> device eth0.1 entered promiscuous mode >> device eth0 entered promiscuous mode >> br-lan: port 1(eth0.1) entering forwarding state >> br-lan: port 1(eth0.1) entering forwarding state >> device wlan0 entered promiscuous mode >> device wlan0-1 entered promiscuous mode >> device wlan0 left promiscuous mode >> wlan: port 1(wlan0) entering disabled state >> device wlan0-1 left promiscuous mode >> wlan: port 2(wlan0-1) entering disabled state >> >> >> >> >> 2011/11/22 Thomas Pedersen <[email protected]> >> >>> Hi Romulo, >>> >>> On Mon, Nov 21, 2011 at 4:12 PM, romulo albuquerque <[email protected]> >>> wrote: >>> > 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 >>> >>> Reloading the module should not be necessary. Especially nohwcrypt=1 >>> since you're not (?) running a secure mesh. >>> >>> > 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 >>> >>> Can you provide the output of 'iw mesh0 mpath dump'? Does dmesg have >>> anything interesting to say? >>> >>> > I'm using ath9k driver and compat-wireless-2011-11-04.tar.bz2. >>> >>> Compat-wireless is created from wireless-testing HEAD, so there are no >>> guarantees about the stability or functionality of this kernel. You >>> can fetch the latest release as a compat-wireless build here; >>> http://o11s.org/files/compat-wireless-o11s-0.5.tar.bz2 >>> >>> > Have anyone had similar problem with ath9k + 802.11s in backfire from >>> trunk >>> > version? >>> > >>> >>> Hope we can get to the bottom of this, >>> Thomas >>> _______________________________________________ >>> 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 >> >> > > _______________________________________________ > Devel mailing list > [email protected] > http://open80211s.com/mailman/listinfo/devel > >
_______________________________________________ Devel mailing list [email protected] http://open80211s.com/mailman/listinfo/devel
