aoe-interfaces(8) System Manager's Manual aoe-interfaces(8)NAME
aoe-interfaces - restrict aoe driver to specified network interfaces
SYNOPSIS
aoe-interfaces [dev1] [dev2 ...]
aoe-interfaces -c
DESCRIPTION
The aoe-interfaces command tells the aoe driver to ignore ATA over Ethernet (AoE) traffic on all but the specified network interfaces. It
is analogous to the aoe_iflist module load option.
If neither the aoe_iflist module load option nor the aoe-interfaces command are used, the aoe driver will use any network interface for AoE
traffic. Using aoe-interfaces to limit AoE to only trusted networks prevents the case where a rogue AoE target appears on a public net-
work, diverting data from the legitimate AoE target. Such an imposter target effectively corrupts the data on the legitimate target.
If the aoe driver is a module, then calling aoe-interfaces without arguments will display the current interfaces list. If it hasn't been
set then the output will be blank.
It's good to run the aoe-discover command after setting the AoE interfaces list.
OPTIONS -c The -c flag will clear the interface access list, permitting any interface to be used.
EXAMPLE
In this example, the root user on a host named nai loads the aoe module with only eth0 allowable for AoE traffic. After remembering that
shelf 7 is on eth3, this sysadmin uses aoe-interfaces to add eth3 to the list of allowable network interfaces and then calls aoe-discover
to ask the aoe driver to look for new AoE devices.
nai:~# modprobe aoe aoe_iflist="eth0"
nai:~# aoe-stat
e10.9 eth0 up
nai:~# aoe-interfaces eth0 eth3
nai:~# aoe-discover
nai:~# aoe-stat
e7.0 eth3 up
e7.1 eth3 up
e7.2 eth3 up
e7.3 eth3 up
e7.4 eth3 up
e7.5 eth3 up
e7.6 eth3 up
e7.7 eth3 up
e7.8 eth3 up
e7.9 eth3 up
e10.9 eth0 up
nai:~# aoe-interfaces
eth0 eth3
SEE ALSO aoe-discover(8), aoe-stat(8), aoetools(8).
AUTHOR
Ed L. Cashin (ecashin@coraid.com)
aoe-interfaces(8)
Check Out this Related Man Page
PPPOE-RELAY(8) System Manager's Manual PPPOE-RELAY(8)NAME
pppoe-relay - user-space PPPoE relay agent.
SYNOPSIS
pppoe-relay [options]
DESCRIPTION
pppoe-relay is a user-space relay agent for PPPoE (Point-to-Point Protocol over Ethernet) for Linux. pppoe-relay works in concert with the
pppoe client and pppoe-server server. See the OPERATION section later in this manual for details on how pppoe-relay works.
OPTIONS -S interface
Adds the Ethernet interface interface to the list of interfaces managed by pppoe-relay. Only PPPoE servers may be connected to this
interface.
-C interface
Adds the Ethernet interface interface to the list of interfaces managed by pppoe-relay. Only PPPoE clients may be connected to this
interface.
-B interface
Adds the Ethernet interface interface to the list of interfaces managed by pppoe-relay. Both PPPoE clients and servers may be con-
nected to this interface.
-n num Allows at most num concurrent PPPoE sessions. If not specified, the default is 5000. num can range from 1 to 65534.
-i timeout
Specifies the session idle timeout. If both peers in a session are idle for more than timeout seconds, the session is terminated.
If timeout is specified as zero, sessions will never be terminated because of idleness.
Note that the idle-session expiry routine is never run more frequently than every 30 seconds, so the timeout is approximate. The
default value for timeout is 600 seconds (10 minutes.)
-F The -F option causes pppoe-relay not to fork into the background; instead, it remains in the foreground.
-h The -h option prints a brief usage message and exits.
OPERATION
pppoe-relay listens for incoming PPPoE PADI frames on all interfaces specified with -B or -C options. When a PADI frame appears, pppoe-
relay adds a Relay-Session-ID tag and broadcasts the PADI on all interfaces specified with -B or -S options (except the interface on which
the frame arrived.)
Any PADO frames received are relayed back to the client which sent the PADI (assuming they contain valid Relay-Session-ID tags.) Likewise,
PADR frames from clients are relayed back to the matching access concentrator.
When a PADS frame is received, pppoe-relay enters the two peers' MAC addresses and session-ID's into a hash table. (The session-ID seen by
the access concentrator may be different from that seen by the client; pppoe-relay must renumber sessions to avoid the possibility of
duplicate session-ID's.) Whenever either peer sends a session frame, pppoe-relay looks up the session entry in the hash table and relays
the frame to the correct peer.
When a PADT frame is received, pppoe-relay relays it to the peer and deletes the session entry from its hash table.
If a client and server crash (or frames are lost), PADT frames may never be sent, and pppoe-relay's hash table can fill up with stale ses-
sions. Therefore, a session-cleaning routine runs periodically, and removes old sessions from the hash table. A session is considered
"old" if no traffic has been seen within timeout seconds. When a session is deleted because of a timeout, a PADT frame is sent to each
peer to make certain that they are aware the session has been killed.
EXAMPLE INVOCATIONS
pppoe-relay -C eth0 -S eth1
The example above relays frames between PPPoE clients on the eth0 network and PPPoE servers on the eth1 network.
pppoe-relay -B eth0 -B eth1
This example is a transparent relay -- frames are relayed between any mix of clients and servers on the eth0 and eth1 networks.
pppoe-relay -S eth0 -C eth1 -C eth2 -C eth3
This example relays frames between servers on the eth0 network and clients on the eth1, eth2 and eth3 networks.
AUTHORS
pppoe-relay was written by David F. Skoll <dfs@roaringpenguin.com>.
The pppoe home page is http://www.roaringpenguin.com/pppoe/.
SEE ALSO pppd(8), pppoe(8), pppoe-sniff(8), pppoe-relay(8), /usr/share/doc/pppoe/README.Debian.gz
4th Berkeley Distribution 26 January 2001 PPPOE-RELAY(8)