linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Mesh addressing issue
@ 2012-08-14 16:25 Cedric VONCKEN
  2012-08-14 19:13 ` Thomas Pedersen
  0 siblings, 1 reply; 4+ messages in thread
From: Cedric VONCKEN @ 2012-08-14 16:25 UTC (permalink / raw)
  To: linux-wireless

                Dear all, 

I think I found an issue in mesh addressing. 
I used the compat-2012-06-14.

My network topology for the test is :
-----------------      -------------------   Wired LAN       -----------------
|MP1              |   |MP2                   |------------------| Computer      |
|192.168.4.1|    |192.168.4.253|                            |192.168.4.90 |
-----------------     -------------------                               ---------------

The MP1 is not bridged with any wired interface (The ip address is set directly on WLAN0 interface)
The MP2 is bridged with eth0 to offer link with a wired network (My computer is connected with the wired network).

If I try to ping from Computer to MP1.
      The ICMP request sent on WiFi (from MP2 to MP1) is a broadcast frame using a strange address format (3 address in 802.11 header + 1 address in mesh extension) . 
      The ICMP reply sent on wifi (from MP1 to MP2) is unicast frame using 6 addresses format.

Why the ICMP request is sent with address 1 set to broadcast (It was not the case for older compat-2011-08-25)?

If in MP1 I move the WLAN0 to a bridge with brctl (with no other interface), ICMP request are still sent with broadcast,
But 
 If I change the mac address of bridge interface, the ICMP request is now sent in unicast  format (using the 6 addresses formats) !

Best regards

Cedric Voncken 


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Mesh addressing issue
  2012-08-14 16:25 Mesh addressing issue Cedric VONCKEN
@ 2012-08-14 19:13 ` Thomas Pedersen
  2012-08-16  9:26   ` voncken
  0 siblings, 1 reply; 4+ messages in thread
From: Thomas Pedersen @ 2012-08-14 19:13 UTC (permalink / raw)
  To: Cedric VONCKEN; +Cc: linux-wireless

Hi Cedric,

On Tue, Aug 14, 2012 at 9:25 AM, Cedric VONCKEN
<cedric.voncken@acksys.fr> wrote:
> I think I found an issue in mesh addressing.
> I used the compat-2012-06-14.
>
> My network topology for the test is :
> -----------------      -------------------   Wired LAN       -----------------
> |MP1              |   |MP2                   |------------------| Computer      |
> |192.168.4.1|    |192.168.4.253|                            |192.168.4.90 |
> -----------------     -------------------                               ---------------
>
> The MP1 is not bridged with any wired interface (The ip address is set directly on WLAN0 interface)
> The MP2 is bridged with eth0 to offer link with a wired network (My computer is connected with the wired network).
>
> If I try to ping from Computer to MP1.
>       The ICMP request sent on WiFi (from MP2 to MP1) is a broadcast frame using a strange address format (3 address in 802.11 header + 1 address in mesh extension) .
>       The ICMP reply sent on wifi (from MP1 to MP2) is unicast frame using 6 addresses format.
>
> Why the ICMP request is sent with address 1 set to broadcast (It was not the case for older compat-2011-08-25)?
>
> If in MP1 I move the WLAN0 to a bridge with brctl (with no other interface), ICMP request are still sent with broadcast,
> But
>  If I change the mac address of bridge interface, the ICMP request is now sent in unicast  format (using the 6 addresses formats) !

Based on the information you've provided, none of this immediately
sounds wrong. Can you please link to a capture file we can
investigate?

Thanks,
Thomas

^ permalink raw reply	[flat|nested] 4+ messages in thread

* RE: Mesh addressing issue
  2012-08-14 19:13 ` Thomas Pedersen
@ 2012-08-16  9:26   ` voncken
  2012-08-17  5:03     ` Thomas Pedersen
  0 siblings, 1 reply; 4+ messages in thread
From: voncken @ 2012-08-16  9:26 UTC (permalink / raw)
  To: 'Thomas Pedersen'; +Cc: linux-wireless

[-- Attachment #1: Type: text/plain, Size: 2577 bytes --]


	Dear Thomas, 

	Please find in atachment 3 file capture.
	Computer.pcap : This capture show the ICMP request sent by the
computer. The MAC address destination is unicast.
	Mp2_to_mp1.pcap : this capture show the ICMP request (frame 33)
from MP2 to MP1 in mesh network.  The MAC address destination is broadcast
	Mp1.pcap : this capture show the ICMP request message received on
MP1 WLAN0 interface. The MAC address destination is broadcast

	Thanks for your help.

-----Message d'origine-----
De : linux-wireless-owner@vger.kernel.org
[mailto:linux-wireless-owner@vger.kernel.org] De la part de Thomas Pedersen
Envoyé : mardi 14 août 2012 21:13
À : Cedric VONCKEN
Cc : linux-wireless@vger.kernel.org
Objet : Re: Mesh addressing issue

Hi Cedric,

On Tue, Aug 14, 2012 at 9:25 AM, Cedric VONCKEN <cedric.voncken@acksys.fr>
wrote:
> I think I found an issue in mesh addressing.
> I used the compat-2012-06-14.
>
> My network topology for the test is :
> -----------------      -------------------   Wired LAN
-----------------
> |MP1              |   |MP2                   |------------------| Computer
|
> |192.168.4.1|    |192.168.4.253|                            |192.168.4.90
|
> -----------------     -------------------
---------------
>
> The MP1 is not bridged with any wired interface (The ip address is set 
> directly on WLAN0 interface) The MP2 is bridged with eth0 to offer link
with a wired network (My computer is connected with the wired network).
>
> If I try to ping from Computer to MP1.
>       The ICMP request sent on WiFi (from MP2 to MP1) is a broadcast frame
using a strange address format (3 address in 802.11 header + 1 address in
mesh extension) .
>       The ICMP reply sent on wifi (from MP1 to MP2) is unicast frame using
6 addresses format.
>
> Why the ICMP request is sent with address 1 set to broadcast (It was not
the case for older compat-2011-08-25)?
>
> If in MP1 I move the WLAN0 to a bridge with brctl (with no other 
> interface), ICMP request are still sent with broadcast, But  If I 
> change the mac address of bridge interface, the ICMP request is now sent
in unicast  format (using the 6 addresses formats) !

Based on the information you've provided, none of this immediately sounds
wrong. Can you please link to a capture file we can investigate?

Thanks,
Thomas
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@vger.kernel.org More majordomo info at
http://vger.kernel.org/majordomo-info.html

[-- Attachment #2: mp1.pcap --]
[-- Type: application/octet-stream, Size: 370 bytes --]

[-- Attachment #3: mp2_to_mp1.pcapng --]
[-- Type: application/octet-stream, Size: 6688 bytes --]

[-- Attachment #4: computer.pcap --]
[-- Type: application/octet-stream, Size: 386 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Mesh addressing issue
  2012-08-16  9:26   ` voncken
@ 2012-08-17  5:03     ` Thomas Pedersen
  0 siblings, 0 replies; 4+ messages in thread
From: Thomas Pedersen @ 2012-08-17  5:03 UTC (permalink / raw)
  To: voncken; +Cc: linux-wireless

On Thu, Aug 16, 2012 at 2:26 AM, voncken <cedric.voncken@acksys.fr> wrote:
>         Computer.pcap : This capture show the ICMP request sent by the
> computer. The MAC address destination is unicast.
>         Mp2_to_mp1.pcap : this capture show the ICMP request (frame 33)
> from MP2 to MP1 in mesh network.  The MAC address destination is broadcast

This is clearly wrong, thanks for reporting. Expect a patch fixing this shortly.

Thomas

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2012-08-17  5:04 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-08-14 16:25 Mesh addressing issue Cedric VONCKEN
2012-08-14 19:13 ` Thomas Pedersen
2012-08-16  9:26   ` voncken
2012-08-17  5:03     ` Thomas Pedersen

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).