Also, your laptop is connected to mesh gate via wired interface, am I right?
---- Chun-Yeow On Fri, Feb 8, 2013 at 5:13 PM, Yeoh Chun-Yeow <[email protected]> wrote: > Hi, Cedric > > Yes, I am using OpenWRT. Possible to send me the wireless and network > config file. > > Thanks > > --- > Chun-Yeow > > On Fri, Feb 8, 2013 at 5:04 PM, Cedric VONCKEN <[email protected]> > wrote: >> Hi Chun-Yeow, >> >> my mesh settings are : >> mesh_retry_timeout = 100 milliseconds >> mesh_confirm_timeout = 100 milliseconds >> mesh_holding_timeout = 100 milliseconds >> mesh_max_peer_links = 32 >> mesh_max_retries = 3 >> mesh_ttl = 31 >> mesh_element_ttl = 31 >> mesh_auto_open_plinks = 1 >> mesh_hwmp_max_preq_retries = 4 >> mesh_path_refresh_time = 1000 milliseconds >> mesh_min_discovery_timeout = 100 milliseconds >> mesh_hwmp_active_path_timeout = 5000 TUs >> mesh_hwmp_preq_min_interval = 10 TUs >> mesh_hwmp_net_diameter_traversal_time = 50 TUs >> mesh_hwmp_rootmode = 0 >> mesh_hwmp_rann_interval = 5000 TUs >> mesh_gate_announcements = 0 >> mesh_fwding = 1 >> mesh_sync_offset_max_neighor = 50 >> mesh_rssi_threshold = 0 dBm >> mesh_hwmp_active_path_to_root_timeout = 6000 TUs >> mesh_hwmp_root_interval = 5000 TUs >> mesh_hwmp_confirmation_interval = 2000 TUs >> >> The meshgate2 and Meshgate1 have the same settings. The wireless mesh >> interface and ethernet lan are bridged. The IP address 192.168.3.253 is on >> bridge (so this IP is not on mesh network). >> >> I can see the default only if I ping a device from DS to DS throught mesh >> network. >> >> To reproduce the defautl : >> Step 1 : Power ON meshGate2 (the mesh network is initialized by openwrt >> script). >> Step 2 : Power ON meshGate1 (the mesh network is initializd by openwrt >> script). >> Step 3 : On mesh gate1 I laucn " wifi down" to disable wirless settings >> Step 4 : I launch ping from LAPTOP_A to 192.168.3.253 under linux machine >> (with windows machine I add option -t) >> Step 5 : On meshGate1, I launch my mesh init script. >> >> If I repeat that, in 90% of case the ping have no reponse. >> >> On my first mail I have attached a wireless wireshark capture. >> >> If you use openwrt for your test, I can send the network and wireless >> configuration file. >> >> Thanks for your help. >> >> Regards >> >> Voncken Cedric >> >> -------- Message d'origine-------- >> De: [email protected] de la part de Yeoh Chun-Yeow >> Date: ven. 08/02/2013 02:36 >> À: Cedric VONCKEN >> Cc: Thomas Pedersen; open11s; [email protected] >> Objet : Re: Mesh regression >> >> Hi, Cedric >> >> Are you able to explain the step-by-step on how you set up your mesh? >> I am not able recreate the problem here. >> >>>>> If I run a ping from LAPTOP_A to MeshGate2 and on the same time, I >>>>> launch the following mesh initialization script >>>>> iw phy phy0 interface add wlan0 type mp >>>>> iw wlan0 set channel 36 >>>>> ifconfig wlan0 up >>>>> iw wlan0 mesh join cvtest >>>>> brctl addif br-lan wlan0 >> >> Also, in which node that you launch the mesh initialization script >> during your ping process from laptop A to MeshGate2? >> >> Beside, you mesh is setup without enabling the proactive tree-building >> mode on your MeshGate, am I right? >> >> Please advice. Thanks >> >> --- >> Chun-Yeow >> >> On Fri, Feb 8, 2013 at 8:49 AM, Yeoh Chun-Yeow <[email protected]> >> wrote: >>> Hi, Thomas >>> >>> Yes. I will take a look on this. >>> >>> Hi, Cedric >>> >>> Both the 2 mesh gates, only MeshGate1 has interface bridged to >>> Ethernet and MeshGate2 has "no" interface bridged to Ethernet, am I >>> right? >>> >>> --- >>> Chun-Yeow >>> >>> On Fri, Feb 8, 2013 at 4:02 AM, Thomas Pedersen <[email protected]> >>> wrote: >>>> + o11s-devel, Chun-Yeow >>>> >>>> For once I don't think this regression is my fault :) >>>> >>>> $ git log master-2012-06-08...master-2012-09-07 --oneline >>>> net/mac80211/mesh_hwmp.c >>>> 4bd4c2d mac80211: clean up mpath_move_to_queue() >>>> 2c53040 net: Fix (nearly-)kernel-doc comments for various functions >>>> bdcbd8e mac80211: clean up debugging >>>> 7ebfa46 mac80211: fix and improve mesh RANN processing >>>> 728b19e {nl,cfg,mac}80211: implement dot11MeshHWMPconfirmationInterval >>>> 3fbf4b7 mac80211: implement the proactive PREP generation >>>> a69cc44 mac80211: implement the proactive PREQ generation >>>> 35b3fe1 mac80211: Rename stainfo variable for the more common sta >>>> e3f5d16 mac80211: Remove unused variable >>>> >>>> Chun-Yeow, can you please take a look at the PREQ forwarding logic in >>>> the context of Cedric's problem? >>>> >>>> On Thu, Feb 7, 2013 at 8:29 AM, Cedric VONCKEN <[email protected]> >>>> wrote: >>>>> My test Platform is: >>>>> >>>>> LAPTOP_A ---------------- MeshGate 1 ---------------- MeshGate2 >>>>> 192.168.3.1 192.168.3.252 192.168.3.253 >>>>> 08:00:27:c1:bf:06 Wistron_aa:41:ed Wistron_aa:40:a8 >>>>> Acksysco_00:2d:ef >>>>> >>>>> The meshgate2 have a mesh interface and a lan interface bridged >>>>> together, and IP address is set on the bridge. >>>>> >>>>> If I run a ping from LAPTOP_A to MeshGate2 and on the same time, I >>>>> launch the following mesh initialization script >>>>> iw phy phy0 interface add wlan0 type mp >>>>> iw wlan0 set channel 36 >>>>> ifconfig wlan0 up >>>>> iw wlan0 mesh join cvtest >>>>> brctl addif br-lan wlan0 >>>>> >>>>> In this case, I get no response from the ping. >>>>> I spied the wireless with airpcap and wireshark: >>>>> A PREQ frame is sent from the mesh gate but the "sta target" >>>>> field is not set with the other mesh gate. In this frame, the "sta >>>>> target" field is set to the destination mac address (Acksysco_00:2d:ef). >>>>> >>>>> I don't have this default with compat-2012-06-14. >>>>> I have this default with compat-2013-01-07 and compat-2012-09-07 >>>>> >>>>> I attach a wireshark capture with the default. The frame #49 is PREQ >>>>> with field target sta address set to MAC address of LAPTOPB. >>>>> >>>>> Do not hesitate to request more information or new test, if necessary to >>>>> understand the default. >>>>> >>>>> Any help will appreciate. >>>>> Best regards. >>>>> >>>>> Voncken cedric >>>> >>>> >>>> >>>> -- >>>> Thomas >> -- >> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in >> the body of a message to [email protected] >> More majordomo info at http://vger.kernel.org/majordomo-info.html >> _______________________________________________ Devel mailing list [email protected] http://lists.open80211s.org/cgi-bin/mailman/listinfo/devel
