Bug #14929
closed
``choparp`` service is not stopped after deleting Proxy ARP type Virtual IP addresses
0%
Description
After deleting a ProxyARP virtual IP, the choparp process is still running. To reproduce:
1. Create a new single address ProxyARP virtual IP and apply it. For this example, I created a virtual IP for 192.168.1.150/32.
2. Run ps aux | grep choparp which show the virtual IP is running as expected: root 65423 0.0 0.3 13392 3244 - S 20:28 0:00.00 /usr/local/sbin/choparp -p /var/run/choparp_em0.pid em0 auto 192.168.1.150/32
3. Delete the virtual IP and rerun ps aux | grep choparp. The process for the deleted virtual IP is still running: root 65423 0.0 0.3 13392 3244 - S 20:28 0:00.00 /usr/local/sbin/choparp -p /var/run/choparp_em0.pid em0 auto 192.168.1.150/32
This appears to happen because interface_proxyarp_configure() is called before deleting the virtual IP from configuration, which results in the choparp process being re-spawned.
Updated by Danilo Zrenjanin about 1 year ago
- Status changed from Pull Request Review to Confirmed
I can confirm this behavior on the:
23.05.1-RELEASE (amd64) built on Wed Jun 28 03:57:27 UTC 2023 FreeBSD 14.0-CURRENT
Updated by Jared Hendrickson about 1 year ago
Forgot to add link to PR in case it's needed: https://github.com/pfsense/pfsense/pull/4652
Updated by Danilo Zrenjanin about 1 year ago
I tested the patch, and I can confirm that it fixes the issue.
Updated by Jim Pingle about 1 year ago
- Subject changed from choparp process is not killed after deleting ProxyARP virtual IP to ``choparp`` service is not stopped after deleting Proxy ARP type Virtual IP addresses
- Target version set to 2.8.0
- Plus Target Version set to 24.03
Updated by Jim Pingle about 1 year ago
- Status changed from Confirmed to Pull Request Review
Updated by Marcos M about 1 year ago
- Status changed from Pull Request Review to Feedback
Applied in changeset 9e8a0841716c1f27698c2321816f92632d004d70.
Updated by Danilo Zrenjanin 12 months ago
- Status changed from Feedback to Resolved
I couldn't replicate the issue in 23.09.
I am marking this ticket as resolved.