PIMD not working after upgrade to 2.9.0 CE
-
The upgrade from 2.8.1 CE to 2.9.0 CE seems to have gone mostly well. One immediate issue is that the PIMD service no longer starts after the upgrade.
It seems that the executable was upgraded for this release but not the service script /usr/local/etc/rc.d/pimd.sh. The scipt invokes PIMD with command line options -q and -c, which no longer exist. The -c option should now be --config=, and I simply commented out lines with -q.
Unfortunately, this script gets rewritten on reboot, so you need to make a copy of the modified script for the case of a reboot, or temporary disabling of PIMD through the webgui config.
Please fix this and I hope this post helps others in the meantime.
-
THIS seems related
-
pimd is simply broken in FreeBSD and the upstream maintainer is AWOL.
https://forum.netgate.com/topic/199686/unable-to-automatically-start-pimd/11
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=292003
https://redmine.pfsense.org/issues/16612 -
Btw, are you actually using the PIM protocol? Or are you just routing between local interfaces?
-
I am not using the pimd protocol but am simply routing multicast traffic.
I found your multicast bridge and mDNS bridge packages. It seems that the latter would be a replacement for the way I use pimd. Correct?
If correct, I am not clear whether when using mDNS bridge, I need to define firewall rules for passing multicast traffic in addition. This was needed for pimd.
Guidance appreciated. Thank you.
-
@revengineer said in PIMD not working after upgrade to 2.9.0 CE:
I am not using the pimd protocol but am simply routing multicast traffic.
I found your multicast bridge and mDNS bridge packages. It seems that the latter would be a replacement for the way I use pimd. Correct?
It depends upon the type of traffic you are routing. If you are routing mDNS messages (port 5353), then mDNS Bridge would be correct. If you are routing other kinds of generic multicast traffic, Multicast Bridge would the choice to handle that.
There is a post in the other thread that has some detail regarding this.
If you share more about the data, I can provide more guidance.
-
@dennypage Thank you so much here as well, and I read the response in the other thread. I set up pimd years ago based on a need that I no longer remember. For now, I set up the mDNS bridge, and I will have to wait and see if something broke. If so, I will try the mcast bridge , and may come back to the other thread for help. Thanks again!
-
@revengineer Welcome
-
For info I use PIMD to distribute Music across multiple VLAN's.
After some fixes, PIMD has been working here for many years. SInce I do not like to lose that function, it would certainly be a major reason not to upgrade.
-
@louis2 said in PIMD not working after upgrade to 2.9.0 CE:
For info I use PIMD to distribute Music across multiple VLAN's.
Are the sources and destinations of the music on VLANS attached to your firewall? If so, you aren't actually using the PIM protocol. If that is the case, then mcast-bridge would be a good choice to replace pimd.
-
@louis2 I do not know that delaying updates for this reason alone is wise. The pimd developer is AWOL, so availability of a fix at any time is uncertain and perhaps this may not ever be fixed. There are a significant number of security fixes in the new version. I have OpenVPN and Wireguard connections coming an, and I prefer to have respective security updates in place.
I have removed pimd and will go with mDNS bridge and mcast bridge instead.
Privacy Policy · Cookie Policy