Joachim,

pimd is working as expected, however despite that there are two thing to notice:

• I have an enormous(!) amounts of alarms in the system log which is definitively not OK
• Perhaps OK, but in my eyes a bit strange is that pimctl shows a lot of interfaces as pim ionterfaces, where they are / should be disabled for pim!??

I did attache my pimd config file and a file with some data I did collect trying to understand these issues. It contains pimctl output and a wireshark trace.

Sincerely,

Louis

I notice the following alarms
<28>1 2022-11-17T20:54:13.978780+01:00 pfSense.lan pimd 61739 - - Timeout waiting for reply from routing socket for 169.254.0.1
<28>1 2022-11-17T20:54:54.935547+01:00 pfSense.lan pimd 61739 - - Timeout waiting for reply from routing socket for 169.254.0.1
<28>1 2022-11-17T20:55:22.174577+01:00 pfSense.lan pimd 61739 - - Timeout waiting for reply from routing socket for 10.60.142.62
<28>1 2022-11-17T20:56:14.808738+01:00 pfSense.lan pimd 61739 - - Timeout waiting for reply from routing socket for 169.254.0.1
<28>1 2022-11-17T20:56:54.159538+01:00 pfSense.lan pimd 61739 - - Timeout waiting for reply from routing socket for 169.254.0.1
<28>1 2022-11-17T20:57:14.637808+01:00 pfSense.lan pimd 61739 - - Timeout waiting for reply from routing socket for 169.254.0.1

Strange is that that "169.254..x.y" is of course a special range and why o why is pimd using that range !?
The other alarm is also strange since the 10.60.142.62 is perhaps a range used by my provide, but not mine

Strange!? All interfaces show in the pimd interface table
Probably OK, but not sure is the shown PIM interface table, the interface table shows nearly all interfaces, where I did define all interfaces of except (Default bind bind to none)

Used interfaces
lagg0.16 Up 192.168.1.1 1 30 0 192.168.1.1 (Normal PC-LAN that is where the hifi receivers are)
lagg0.26 Up 192.168.2.1 1 30 0 192.168.2.1 1 (PC-zone-2)
lagg1.11 Up 192.168.11.1 1 30 0 192.168.11.1 1 (PC-zone-3)
lagg0.13 Up 192.168.13.1 1 30 0 192.168.13.1 1 (IOT zone not yet used)
lagg1.14 Up 192.168.14.1 1 30 0 192.168.14.1 (redzone that is where the media player is (TWONKY)

em0.4 Up 10.236.170.200 1 30 0 10.236.170.200 1 (IP-TV not used, not enabled)

The media player is (TWONKY) is situated in the redzone on ip 192.168.14.15

pimd.conf.txt
pimd_issues_maybe.txt