Bug #6749
closed
Still responds to ARP after removing one of several Virtual IP - choparp not reconfigured
0%
Description
At the start, there were four Virtual IPs defined in pfSense. I removed two of them through the GUI, yet the machine still responds to ARP requests for the removed IP addresses.
Looking in the process list, we see:
13494 v0- S 0:05.74 /usr/local/sbin/choparp em3 auto xx.xx.35.195/32 xx.xx.35.196/32 xx.xx.35.197/32 xx.xx.35.198/32
Which is wrong, because only .195 and .198 remain as Virtual IP in the pfSense GUI. The other two have been removed.
Updated by Oskar Berggren over 7 years ago
Actually, I found two more choparp processes:
root 22202 0.0 0.1 14604 2248 - S Tue04PM 0:05.67 /usr/local/sbin/choparp em3 auto xx.xx.35.195/32 xx.xx.35.196/32 xx.xx.35.198/32
root 51391 0.0 0.1 14604 2244 - S 7:58AM 0:00.75 /usr/local/sbin/choparp em3 auto xx.xx.35.195/32 xx.xx.35.198/32
So it seems that when a Virtual IP is removed, a new choparp with the correct configuration is launched, but it fails to kill the old one - in effect the old process continue to respond for the removed addres.
Updated by Chris Linstruth over 7 years ago
It does not look like the proper PID files are being created in /var/run. -p PIDFILE arguments are not being added to the choparp command line or, perhaps, the default location/PIDFILE in the choparp utility is incorrect. This results in created processes never being killed when changed.
Updated by
Updated by Jim Pingle over 4 years ago
- Status changed from New to Duplicate
Duplicated by #7379 but it has a proposed fix