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

[Sergio Ammirata]

He is absolutely right. I have spanning tree protocol enabled on the hostap
AP.

I logged into the hostap AP and initiated a ping towards the prism54 AP
through the wireless interface (Hostap AP has a wireless ip of 192.168.10.1
on the br0 interface and prism54 AP has a wireless ip of 192.168.10.2 on the
br0 interface)

Ping 192.168.10.2 obviously still times out (same happens if I ping from my
laptop) .. But the interesting part is the packet received by the prism54 AP
when I ping from the hostap AP. Here it is:

wds_net_send_packet
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

[00][04][e2][80][7d][42] is the mac address of the hostap AP

Hope that helps,

Sergio

> -----Original Message-----
> From: Rainer Weikusat [mailto:rainer.weikusat at sncag.com]
> Sent: Saturday, April 09, 2005 7:15 PM
> To: Jean-Baptiste Note
> Cc: Sergio Ammirata; 'Jouni Malinen'; prism54-devel at prism54.org; 'Denis
> Vlasenko'
> Subject: Re: [Prism54-devel] Re: Strange problem with wds in prism54
> 
> Jean-Baptiste Note <jean-baptiste.note at wanadoo.fr> writes:
> >>
> [01][80][c2][00][00][00][00][04][e2][80][7d][42][00][2e][42][42][03][00][0
> 0]
> >>
> >> To my untrained eye, this looks like
> >> 1/ a prism54-specific header, 6 bytes
> >
> > The 01-80-c2 OUI is used in 802.3 for event notification, so it is
> > indeed some kind of "special case", and the MAC here is meaningless.
> > Time to check the standard, i guess, but if anyone understands
> > this...
> 
> It's an ethernet group address (link layer multicast) and used for
> spanning tree negotiation (according to various lists on the web).