Bug #2158
closedSNMP bind needs to list all interfaces/VIPs
100%
Description
The SNMP GUI has a "bind to LAN interface" option but that is a bit ambiguous and not so useful in 2.x. It also doesn't help when trying to contact a CARP VIP over IPsec.
The option needs to be changed to a drop-down that lists all interfaces and CARP/Alias VIPs to allow a more precise bind.
Manually specifying a CARP VIP in the config has been confirmed to work.
JP Updated by Jim Pingle over 14 years ago
- Status changed from New to Feedback
- % Done changed from 0 to 100
Applied in changeset commit:c82b2c3f212e7c008146df624e0423d0f10770ab.
JP Updated by Jim Pingle over 14 years ago
Applied in changeset commit:18d4d360a3a5de5c80ab3940ce2cf80bee3859e6.
BM Updated by Bruce Mah over 14 years ago
I'm seeing a minor buglet in SNMP configuration that might be related to this bug.
On the Services -> SNMP page, the interface dropdown for the Bind Interface setting seems "stuck" on "Localhost". I wanted to set this to my LAN interface...if I select the LAN interface and click "Save" the change does seem to take effect on the back-end. However if I click off to a different page in the Web UI and come back to the SNMP page, the interface dropdown once again says "Localhost".
I'm running this code:
pfSense-2.1-DEVELOPMENT-1g-i386-nanobsd-upgrade-20120315-1352.img.gz
Bruce.
JP Updated by Jim Pingle over 14 years ago
- Status changed from Feedback to New
I'll set this back to new, there's probably a little logic error in re-selecting the right value on load.
JP Updated by Jim Pingle over 14 years ago
- Status changed from New to Feedback
Applied in changeset commit:3d594a3fba8a2e781f845d64102d06fb6dc4e0b7.
BM Updated by Bruce Mah over 14 years ago
I just tested this, and the dropdown appears to correctly populated now. Using this snapshot build:
pfSense-2.1-DEVELOPMENT-1g-i386-nanobsd-upgrade-20120319-1509.img.gz
Thanks for the fix!
CB Updated by Chris Buechler over 14 years ago
- Status changed from Feedback to Resolved