Hi, Shinoda It could be due to old ath9k chipset filtering issue (broadcast packet is filtered out, such as ARP request) as mentioned in: https://github.com/cozybit/open80211s/wiki/ath9kFilteringIssueFix
So modify as follow in ath9k/recv.c and see how: + if (sc->sc_ah->hw_version.macVersion == AR_SREV_VERSION_9160 || + sc->sc_ah->hw_version.macVersion == AR_SREV_VERSION_9100) I have run into the same problem on my AR54516 PCI card before. --- Chun-Yeow On Thu, Aug 30, 2012 at 5:39 AM, Thomas Pedersen <tho...@cozybit.com> wrote: > On Wed, Aug 29, 2012 at 5:21 AM, LEO Airwarosu Yoichi Shinoda > <shin...@jaist.ac.jp> wrote: >> >> With OpenWrt r33276 (compat-wireless-2012-07-13), >> Buffalo WZR-HP-G300NH (AR9132) does not start a mesh >> until an adjacent monitor interface is created and brought up. >> >> For example, let's consider a mesh interface mesh0. >> >> # iw phy0 interface add mesh0 type mp >> # iw mesh0 set channel 11 >> # iw mesh0 mesh join mymesh >> # ifconfig mesh0 up >> >> I need to issue following additional commands before >> the mesh is actually capable of seeing the interface, >> or the interface seeing the mesh. >> >> # iw phy0 interface add mon0 type monitor >> # ifconfig mon0 up >> >> Where do I start looking? > > Is the card even beaconing before the monitor interface comes up? Are > peering frames transmitted? What does station dump show before > starting mon0? A capture during this period would also be useful. > > Thomas > _______________________________________________ > Devel mailing list > de...@lists.open80211s.org > http://lists.open80211s.org/cgi-bin/mailman/listinfo/devel _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
