seanadams;262463 Wrote: 
> I am looking at our bridging implementation, and it is designed to
> forward to all ports in the event of a unicast packet whose MAC is not
> in its table. It is not clear to me if this is our problem or if
> something else is going on, so I am hesitant to open a bug without
> knowing any specifics.
> 
> It would be helpful to know whether the access point is actually
> sending the packet out to the wireless lan in the first place. To test
> that, put a wireless PC on it and run ethereal. I am not sure but I
> think you can monitor unicast traffic to other hosts that way without
> any special setup - you probably would need to disable encryption.

I was so happy getting the thing to work, that I thought of not doing
any further investigations. But, as you seem to be concerned, I took my
laptop and started testing.

Based on my non-scientific approach, it seems that the access point
(ADSL-modem w/ WLAN) is the one to blame! So, I'd say that there is no
need dig further on SB3's bridging implementation.

As I had windump already installed, I used it on two machines, other
being on the LAN and the other on WLAN. On ADSL modem I had two IP
addresses with static ARP, the other with the real one and the other
with MAC broadcast. Then I changed several times the IP address where
the modem should forward the WOL-packet coming from dslreports.com. Not
a single packet appeared on the WLAN with the real MAC address, but when
I changed the address to the broadcast MAC, they were nicely printed out
on the screen of the laptop on WLAN. All packets of course were received
by the PC on LAN.

I will make a note for the tech guys at ADSL modem manufacturer.

Best regards,
Mika


-- 
hau
------------------------------------------------------------------------
hau's Profile: http://forums.slimdevices.com/member.php?userid=4495
View this thread: http://forums.slimdevices.com/showthread.php?t=31850

_______________________________________________
discuss mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/discuss

Reply via email to