My attempts at updating the man page formats really poorly in 80 columns:
At its simplest, the AGENT specification may consist of a host-
name, or an IPv4 address in the standard "dotted quad" notation.
In this case, communication will be attempted using UDP/IPv4 to
port 161 of the given host. Otherwise, the <transport-address>
part of the specification is parsed according to the following
table:
<transport-specifier> <transport-address> format
udp hostname[@interface[@names-
pace]][:port] or
IPv4-address[@interface[@names-
pace]][:port]
tcp hostname[@interface[@names-
pace]][:port] or
IPv4-address[@interface[@names-
pace]][:port]
unix pathname
ipx [network]:node[/port]
aal5pvc or pvc [interface.][VPI.]VCI
udp6 or udpv6 or udpipv6 hostname[@interface[@names-
pace]][:port] or
IPv6-address[@interface[@names-
pace]]:port or
'['IPv6-address']'[@inter-
face[@namespace]][:port]
tcp6 or tcpv6 or tcpipv6 hostname[@interface[@names-
pace]][:port] or
IPv6-address[@interface[@names-
pace]]:port or
'['IPv6-address']'[@inter-
face[@namespace]][:port]
...
udp:hostname identical to the previous specification.
The "udp:" is redundant here since
UDP/IPv4 is the default transport.
hostname@eth0:161 identical to the previous specification,
except that the communication is forced
to eth0 using the SO_BINDTODEVICE socket
option.
hostname@eth0@blue identical to the previous specification,
except that the communication occurs
using the eth0 interface inside the
namespace named "blue" (created, e.g.,
using ip netns add ).
...
If the platform supports binding to an interface using the
SO_BINDTODEVICE socket option, the optional @interface specifier
can be added to an IP address or host name.
If the platform supports network namespaces using the setns sys-
tem call, the optional @netns specifier can be added to an IP
address or host name. If an interface specification (see above)
is not required, two @ s are used, e.g., 127.0.0.1@@blue .
Perhaps I can fix the formatting of the first table by separating out the
"hostname or ip_ address" and "followed by optional @interface, @namespace,
:port"? Any suggestions?
Thanks,
Bill
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
