The etherfiles command is hidden, not shown by ip help.
10.11.3Example
mymachine> ip etherfiles
ether: //edd
flane: //lec1
atm: (no ethernet device)
10.12 files
10.12.1Syntax
files [full]
files <assoc>
10.12.2Description
Lists the files (associations) that other applications (or, internally, RIP) have opened on //ip. More detailed information on an association can be displayed by specifying the association number, or on all associations by specifying full.
The information for each association may include an interface name (ether or flane in the example below). This can be either the interface last used to send a packet on the association or, for a new association, the interface that is expected to be used for packets to the remote host. This interface can change over the lifetime of an association; in particular, for a UDP association not bound to a specific remote host it may change each time a packet is sent to a different destination. (In other cases it will normally change only as a result of routing changes.)
The files command is hidden, not shown by ip help.
10.12.3Example
mymachine> ip files
1: rw+ ether 192.168.2.1 TCP port telnet (23) Established to 192.168.2.2
port 1071 1 rx requests
2:rw+ ether <noaddr> UDP port snmp (161) 3 rx requests
3:rw+ <unset> <noaddr> UDP port tftp (69) 4 rx requests
4:rw+ <unset> <noaddr> UDP port router (520) 2 rx requests
5:w flane <noaddr> UDP port router (520)
6:rw+ <unset> <noaddr> UDP port 2050 4 rx requests
7:rw+ <unset> <noaddr> UDP port 2051 4 rx requests
8:rw+ <unset> <noaddr> UDP port 2052 4 rx requests
9:rw+ <unset> <noaddr> UDP port 2053 4 rx requests mymachine> ip files 3
3: rw+ <unset> <noaddr> UDP port tftp (69) 4 rx requests
