So I'm puzzled.  Why would IS-IS not work?  If multicast semantics are implemented correctly (i.e., the multicast messages are delivered to all stations other than the sender), it should all just work.  Multicast is no different from broadcast, and of course broadcast works.

Is this just a case of some badly designed access points that don't understand how LANs work?  FWIW, I have once or twice turned on PyDECnet on a Wifi link.  Of course that doesn't work because of the HIORD stuff, but the multicast definitely do get delivered, I get adjacency up and all that.

        paul

> On Nov 6, 2022, at 6:24 PM, Johnny Billquist <bqt@softjar.se> wrote:
>
> I think all APs do multicasts over WiFi as unicasts to every client. WiFi could, I guess, in theory do true multicasting, but since it's all acknowledged at the radio level, and encryption and what not, WiFi do it all by unicasts. But that is basically hidden away, and usually works fine.
>
> Much worse is that with DECnet you want to change the MAC address, which WiFi gets really messed up with, and it usually do not work well at all. And that especially gets messed up when in combination with the multicasting.
>
> I didn't know that IS-IS had problems over WiFi. I learned something new today. Cool. Thanks.
>
>  Johnny
>
>
> On 2022-11-07 00:17, Peter Lothberg wrote:
>> If you are to do native DECnet over WIFI, note that Ethernet multicast
>> is a problem for WIFI and some AP's turns them in to unicasts to every client..
>> (This is the same problem as running IS-IS in your home network...)
>> -P
>> ----- Original Message -----
>>> From: "Paul Koning" <paulkoning@comcast.net>
>>> To: "The Hobbyist DECnet mailing list" <hecnet@lists.dfupdate.se>
>>> Sent: Sunday, November 6, 2022 4:35:25 PM
>>> Subject: [HECnet] Re: Ad-hoc connection to hecnet?
>>> Indeed, for Phase IV and IV-plus.  Fixed (obscurely) in IV-prime, and in Phase
>>> V.
>>>
>>> Some day I should implement IV-prime in PyDECnet.  It's not all that hard.
>>>
>>> If you just want to use WiFi to run IP based tunnel type protocols, there is no
>>> issue.  And if the router you're going to doesn't restrict the remote IP
>>> address for its traffic (in PyDECnet, you can only do that for TCP based
>>> protocols: Multinet and DDCMP) then you should be able to do "ad-hoc"
>>> connections just fine.
>>>
>>>     paul
>>>
>>>
>>> _______________________________________________
>>> HECnet mailing list -- hecnet@lists.dfupdate.se
>>> To unsubscribe send an email to hecnet-leave@lists.dfupdate.se
>> _______________________________________________
>> HECnet mailing list -- hecnet@lists.dfupdate.se
>> To unsubscribe send an email to hecnet-leave@lists.dfupdate.se
>
> --
> Johnny Billquist                  || "I'm on a bus
>                                  ||  on a psychedelic trip
> email: bqt@softjar.se             ||  Reading murder books
> pdp is alive!                     ||  tryin' to stay hip" - B. Idol
> _______________________________________________
> HECnet mailing list -- hecnet@lists.dfupdate.se
> To unsubscribe send an email to hecnet-leave@lists.dfupdate.se

_______________________________________________
HECnet mailing list -- hecnet@lists.dfupdate.se
To unsubscribe send an email to hecnet-leave@lists.dfupdate.se