[Prism54-devel] Re: Strange problem with wds in prism54

[Sergio Ammirata]

Hello Jean-Baptiste,

Your suggestion fixed the problem with strange mac addresses on the arp
table ... but I am afraid nothing else was fixed. Ping still does not work.

I think you are right, the TX path has problems. Here are some tests that
might shed some light:

In this test I have 3 radios, 2 prism54 and 1 hostap.

The first prism54 is bridged with the second prism54 and with a hostap
radio.
The second prism54 is only bridged with the first prism54.

Important info:
First prism54 device has mac 00-02-6f-22-9a-d7
Second prism54 device has mac 00-02-6f-21-1a-28
Hostap device has mac [00][04][e2][80][7d][42]
Spanning tree protocol (STP) is turned on in the hostap device and in the
second prism54 device.
I am logging all packets whether wds_find_device returns null or not ...
However I only see null ones.

These are the packets I see in the first prism54: 

Spanning Tree Protocol packets:

>From second prism54 radio:
wds_find_device
wds_find_device: WDS from mac 00-02-6f-22-9a-d7 not in current config,
returning NULL
[00][02][6f][22][9a][d7][01][80][c2][00][00][00][00][02][6f][21]

>From the hostap prism2.5 radio:
wds_find_device
wds_find_device: WDS from mac 01-80-c2-00-00-00 not in current config,
returning NULL
[01][80][c2][00][00][00][00][04][e2][80][7d][42][00][2e][42][42][03][00][00]
[00][00][00][00][0a][00][04][e2][80][7d][42][00][00][00][00][00][0a][00][04]
[e2][80][7d][42][80][02][00][00][3c][00][02][00][04][00][a5][a5][a5][a5][a5]
[a5][a5][a5]

The packet coming from the second prism54 does not seem to be well formed
when compared to the same STP packet that the hostap device sends.

Ping packets:

>From second prism54 radio:
wds_net_send_packet
wds_net_send_packet
wds_find_device
wds_find_device: WDS from mac 00-02-6f-22-9a-d7 not in current config,
returning NULL
[00][02][6f][22][9a][d7][ff][ff][ff][ff][ff][ff][00][02][6f][21]

>From the hostap prism2.5 radio:
wds_find_device
wds_find_device: WDS from mac ff-ff-ff-ff-ff-ff not in current config,
returning NULL
[ff][ff][ff][ff][ff][ff][00][04][e2][80][7d][42][08][06][00][01][08][00][06]
[04][00][01][00][04][e2][80][7d][42][c0][a8][0a][01][00][00][00][00][00][00]
[c0][a8][0a][02]
wds_net_send_packet
wds_net_send_packet

Again, the packet coming from the second prism54 does not seem to be well
formed when compared to the same ping packet that the hostap device sends.


These are the packet I see on the second prism54 device (they appear to be
related to STP):

wds_net_send_packet
wds_find_device
wds_find_device: WDS from mac 00-02-6f-21-1a-28 not in current config,
returning NULL
[00][02][6f][21][1a][28][01][80][c2][00][00][00][00][04][e2][80][7d][42]

When I initiate a ping from the first prism54 to the second prism54 device I
get:

wds_find_device
wds_find_device: WDS from mac 00-02-6f-21-1a-28 not in current config,
returning NULL
[00][02][6f][21][1a][28][ff][ff][ff][ff][ff][ff][00][02][6f][22]

When I initiate a ping from the hostap device towards the second prism54
device (going through the first prism54 device of course):

wds_find_device
wds_find_device: WDS from mac 00-02-6f-21-1a-28 not in current config,
returning NULL
[00][02][6f][21][1a][28][ff][ff][ff][ff][ff][ff][00][04][e2][80][7d][42]
wds_net_send_packet

Let me know what to do next,

Sergio