Re: [PATCH 0/6] Add support for interface binding
Bill Fenner via Net-snmp-coders <[email protected]>
| Newsgroups | gmane.network.net-snmp.devel |
|---|---|
| Message-ID | <CAF4SogbsZ_wkMd7A4LtoS-kLb=Er4haRP5d6S-EbafjJJtKYCQ@mail.gmail.com> |
On Fri, Jan 25, 2019 at 11:37 AM Magnus Fromreide <[email protected]> wrote: > On Sun, Oct 28, 2018 at 01:54:22PM -0700, Bart Van Assche wrote: > > Hello, > > > > As you may have noticed multiple people asked to add SO_BINDTODEVICE > support > > to Net-SNMP. This patch series adds such support by allowing to specify > the > > name of the network interface to bind a Net-SNMP endpoint to as > > "@<interface name>". An example: > > > > agent/snmpd -Mmibs -f -Lo -c .../snmpd.conf udp6:localhost@lo:1161 -r > > apps/snmpwalk -Mmibs -v2c -cpublic udp6:localhost:1161 .1 > > I have no real feeling one way or the other over the patch per se but I > am wondering if the clash with virtual interface names on linux (e.g. > lo:1) makes the choosen syntax problematic for the interface name > parser? > This syntax is obsolete. The supported mechanism is to use iproute2 to manage multiple addresses/prefixes per interface. Bill _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders