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 <yeohchunyeow@xxxxxxxxx> 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 <thomas@xxxxxxxxxxx> 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 <cedric.voncken@xxxxxxxxx> 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 majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
