Post-23.09 Update: igmpproxy Too many origins for route 239.255.255.250; replacing 192.168.60.3 with 192.168.60.7

Mission-Ghost

Since updating to 23.09 from 23.05.1 I've been seeing the following errors in Status/System Logs/System/Routing (without verbose logging):

Nov 26 09:00:14 	igmpproxy 	18011 	Too many origins for route 239.255.255.250; replacing 192.168.60.3 with 192.168.60.7
Nov 25 09:27:13 	igmpproxy 	18011 	Too many origins for route 239.255.255.250; replacing 192.168.20.10 with 192.168.60.4
Nov 24 08:44:45 	igmpproxy 	18011 	Too many origins for route 239.255.255.250; replacing 192.168.60.211 with 192.168.60.10
Nov 23 08:51:28 	igmpproxy 	18011 	Too many origins for route 239.255.255.250; replacing 192.168.50.136 with 192.168.60.6
Nov 22 09:28:42 	igmpproxy 	18011 	Too many origins for route 239.255.255.250; replacing 192.168.50.143 with 192.168.60.3

What changed to precipitate these messages in this version that wasn't there in the last version?

What does this mean?

I don't notice any functional issues on the network, still, should I do anything about it?

Thanks in advance!

stephenw10

I assume those IPs are multicast clients joining that group?

I'm unsure exactly what that does but I'd assume it's simply updating the table with whichever the last client to register was once there are more than 4.

It doesn't look like an error if it's expected that there might be more than 4.

Steve

Mission-Ghost

@stephenw10 presumably they're multicast clients given the route IP.

The .60s are games--a PS5 and/or a Nintendo switch. Don't know if they use multicast but it's reasonable to assume so. The .50s are entertainment devices, such as Roku boxes. The .20.10 is an HP printer with an Ethernet to WiFi device as it has no built-in WiFi. Maybe the printer notification is due to Bonjour.

What's strange to me is the message did not appeare under 23.05.1 or previous firmware revs. Maybe it's showing up now due to the Kea DHCP server...?

It would be valuable if error messages were cataloged with meanings, causes and responses. Very often they, nor the appropriate responses, aren't clear. Having to dig into the source code to try to discern what the meaning of the message is it a bit much.

Even so, thanks for digging into the source code for me. I guess I'll disregard as the new normal under 23.09.

stephenw10

I wouldn't expect Kea to make any difference there. It is indeed odd that it would only now start to report that. I did wonder if either the max value changed or the logging level but I couldn't see anything obvious indicating either.