> On Feb 15, 2016, at 2:02 PM, Johnny Billquist <[email protected]> wrote:
>
> On 2016-02-15 19:53, Paul Koning wrote:
>>
>>> On Feb 15, 2016, at 1:48 PM, Hittner, David T (IS) <[email protected]>
>>> wrote:
>>>
>>> LAT runs fine over the (wired) Ethernet port.
>>> LAT doesn’t run over wireless Ethernet without major help from the wireless
>>> hardware or unless it’s tunneled over IP.
>>
>> I'm still baffled. Why doesn't it? 802.11 has the same MAC layer service
>> as Ethernet -- broadcast, multicast, unicast, 48 bit addresses, etc. What
>> specifically does LAT do that doesn't work on 802.11? Is it a standards
>> issue, or a case of defective implementations?
>
> Trying to recall what I might have read/understood from somewhere, the
> problem is that WiFi might look like ethernet, but there are some important
> differences. One of these is that the switch/router actually *knows* the MAC
> addresses that are connected, as in the card/controller identities. Which,
> unlike a normal ethernet, means that if you add a device with a different mac
> address to the interface, the router at the other end will not learn this,
> and will not forward packets to you the way you would expect it to work on an
> ethernet.
So you can't build a LAN bridge with a Wifi network-side interface? Really?
paul
_______________________________________________
Simh mailing list
[email protected]
http://mailman.trailing-edge.com/mailman/listinfo/simh
