2010/6/21 Adam Maas <[email protected]>: > > The IP stack routes based on IP not hardware addressing, it's running > at layer 3 and never sees the MAC address. Layer 1 & 2 are handles by > the hardware and the drivers respectively. Typically routing > implementations are by IP and associated network interface (eth0 et > al). The drivers and hardware get the traffic from the stack in > separate buffers based on physical interface, MAC addresses really > only have a function when the hardware/driver is listening to incoming > traffic on the interface.
OK I agree with that bit > Most Wifi setups are segmented from the wired LAN from the WAP, which > is usually the router for both the Wifi and Wired so it while it looks > like a bridged connection, it's actually two separate segments. It's > rare to have a WAP running in bridged mode since the WAP then has to > rebroadcast all the traffic on the wired segment which leads to > additional congestion. Generally you have the Wifi on the same subnet > but a different segment in smaller organizations and a completely > different subnet and routed segment for larger implementations. I wish. Most networks I encounter have an access point plugged into a port on the only switch, often despite the fact that they have a firewall with one or multiple free optional network ports you can route between and filter traffic and more often than not I find clients connected to the network twice, wired and wireless at the same time. When I point this out, the response usually is, it works so what are you making such a fuss about... It is nice to be talking to someone (you) who seems to know their stuff but it is a jungle out there... still, can you name a product? I've googled a fair bit and can't find one. TIA Ecke -- PDML Pentax-Discuss Mail List [email protected] http://pdml.net/mailman/listinfo/pdml_pdml.net to UNSUBSCRIBE from the PDML, please visit the link directly above and follow the directions.
