Timolthy,

Address4 is the address of the host(s) behind the "Wireless Ethernet-Client". 
(WEC)

Although Address4 is NOT a "WiFi must" it is in the IEEE .11b specs.

Most early .11b WiFi certified APs such as Lucent AP500 AP1000, Cisco 340, etc 
did
not support address4 just up to address3 since WiFi was designed with a single 
mac
client in mind. (pcmcia/PCI)

This is the reason most WECs such as CB3, WET11, etc are forced to proxy arp the
macs of the hosts behind the client (address4) to the mac of the Ehternet 
Client.
(address3)

Drawback of the address3 WECs are:

Only 64 active macs on the arp table
Only TCP/IP passes through
All other traffic (such as PPPoE) passes via hacks on the IP stack or it 
doesn't pass.

e.g.
1. CB3 client can only pass 1 PPPoE request from the IP of the source host and 
the
mac of the CB3. Second PPPoE request will show up on the PPPoE server with the 
IP of
the new source but the same mac of the CB3 so it will be dropped by the PPPoE
server.

2. Exactely the opposite regarding HotSpot authentication. Once the first host
behind an address3 WEC authenticates to a HotSpot then all ohter hosts "are"
authenticated as well.

Thank you
-- 
Dimitri

http://www.vergina.net

> Hello,
>
> There is the MAC address 4 in the packet/frame, it's
> support to be AP1 (Source AP's MAC) but I never seen
> the Address 4 in the Airopeek sniffer. Did anyone of
> you have seen this Address 4?  Station 1 sends to
> Station 2.
>
> Station 1 ----- AP1 --|
>                       |_____
>                       |
> Station 2 ----- AP2 --|
>
> Thanks,
>
> Timolthy
>
>
>
>
>
> __________________________________
> Do you Yahoo!?
> Meet the all-new My Yahoo! - Try it today!
> http://my.yahoo.com
>
>
> _______________________________________________
> BAWUG's general wireless chat mailing list
> [unsubscribe] http://lists.bawug.org/mailman/listinfo/wireless
>


_______________________________________________
BAWUG's general wireless chat mailing list
[unsubscribe] http://lists.bawug.org/mailman/listinfo/wireless

Reply via email to