Re: pf(4) drops valid IGMP/MLD messages

I've just seen that this has been fixed in 7.3, now I see that prune, graft, graft-ack messages are not blocked by PF Thanks a lot Il giorno gio 16 mar 2023 alle ore 16:45 Luca Di Gregorio ha scritto: > Ok, thanks a lot for the info > > Il giorno gio 16 mar 2023 alle 16:40 Theo

Re: pf(4) drops valid IGMP/MLD messages

Ok, thanks a lot for the info Il giorno gio 16 mar 2023 alle 16:40 Theo de Raadt ha scritto: > Luca Di Gregorio wrote: > > > do you think that the correction proposed by Alexandr could be done with > a > > syspatch, or in the next release? > > It does not meet

Re: pf(4) drops valid IGMP/MLD messages

Hi, do you think that the correction proposed by Alexandr could be done with a syspatch, or in the next release? Thanks, regards Il giorno sab 4 mar 2023 alle ore 06:34 Luca Di Gregorio ha scritto: > Hi, my modest opinions: > > > Instead of implementing more and more details of RF

Re: pf(4) drops valid IGMP/MLD messages

Hi, my modest opinions: > Instead of implementing more and more details of RFC, we should > discuss what the goal is. I'd like to have multicast routing working properly. Multicast routing with good network architecture allows people to save tons of resources on hosts, as well as saving a lot of

Re: pf(4) drops valid IGMP/MLD messages

Hi, just another bit of info about this issue. I've installed from github the newest version of mrouted on a Linux machine. Just like the built-in OpenBSD's version of mrouted, this github version sends DVMRP Prune messages with IP Destination Address = Unicast Address of the adjacent router, and

Re: Disabling MULTICAST flag on an interface. Force outgoing multicast traffic to a specific interface

Hi Philip, thanks 1) ok, I’ll take it into account for my configurations 2) adding the route for 224.0.0.0/4 to the specific interface works Thanks again Luca Il giorno mer 1 mar 2023 alle 22:47 Philip Guenther ha scritto: > On Wed, Mar 1, 2023 at 9:58 AM Luca Di Gregorio wrote: >

Disabling MULTICAST flag on an interface. Force outgoing multicast traffic to a specific interface

Hi, 1) does anyone know if there is a way to disable MULTICAST on a single interface? I don't see any option in ifconfig to do this. 2) Can outgoing multicast traffic be routed to a specific interface? I don't see any option in route. It seems that the first interface, by id, is chosen. Thanks,

Re: pf(4) drops valid IGMP/MLD messages

Hi Matthieu, DVMRP messages are sent with IGMP protocol. Some Multicast Control messages (Query, Report) have an IP Destination Address belonging to 224.0.0.0/4, with TTL=1. Other DVMRP multicast control messages (Prune, Graft, Graft-Ack) have an IP Destination Address = Unicast Address of the adj