{"id":3341,"date":"2022-12-20T17:02:23","date_gmt":"2022-12-20T20:02:23","guid":{"rendered":"http:\/\/lode.uno\/linux-man\/index.php\/2022\/12\/20\/pppoe-relay-man8\/"},"modified":"2022-12-20T17:02:23","modified_gmt":"2022-12-20T20:02:23","slug":"pppoe-relay-man8","status":"publish","type":"post","link":"https:\/\/lode.uno\/linux-man\/2022\/12\/20\/pppoe-relay-man8\/","title":{"rendered":"PPPOE-RELAY (man8)"},"content":{"rendered":"

PPPOE-RELAY<\/h1>\n

NAME<\/a>
SYNOPSIS<\/a>
DESCRIPTION<\/a>
OPTIONS<\/a>
OPERATION<\/a>
EXAMPLE INVOCATIONS<\/a>
AUTHORS<\/a>
SEE ALSO<\/a> <\/p>\n

\n

NAME <\/a> <\/h2>\n

pppoe-relay \u2212 user-space PPPoE relay agent.<\/p>\n

SYNOPSIS <\/a> <\/h2>\n

pppoe-relay<\/b> [options<\/i>]<\/p>\n

DESCRIPTION <\/a> <\/h2>\n

pppoe-relay<\/b> is a user-space relay agent for PPPoE (Point-to-Point Protocol over Ethernet) for Linux. pppoe-relay<\/b> works in concert with the pppoe<\/b> client and pppoe-server<\/b> server. See the OPERATION section later in this manual for details on how pppoe-relay<\/b> works.<\/p>\n

OPTIONS <\/a> <\/h2>\n

\u2212S<\/b> interface<\/i><\/p>\n

Adds the Ethernet interface interface<\/i> to the list of interfaces managed by pppoe-relay<\/b>. Only PPPoE servers may be connected to this interface.<\/p>\n

\u2212C<\/b> interface<\/i><\/p>\n

Adds the Ethernet interface interface<\/i> to the list of interfaces managed by pppoe-relay<\/b>. Only PPPoE clients may be connected to this interface.<\/p>\n

\u2212B<\/b> interface<\/i><\/p>\n

Adds the Ethernet interface interface<\/i> to the list of interfaces managed by pppoe-relay<\/b>. Both PPPoE clients and servers may be connected to this interface.<\/p>\n\n\n
<\/td>\n\n

\u2212n<\/b> num<\/i><\/p>\n<\/td>\n

<\/td>\n\n

Allows at most num<\/i> concurrent PPPoE sessions. If not specified, the default is 5000. num<\/i> can range from 1 to 65534.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

\u2212i<\/b> timeout<\/i><\/p>\n

Specifies the session idle timeout. If both peers in a session are idle for more than timeout<\/i> seconds, the session is terminated. If timeout<\/i> is specified as zero, sessions will never be terminated because of idleness.<\/p>\n

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<\/i> is 600 seconds (10 minutes.)<\/p>\n\n\n\n
<\/td>\n\n

\u2212F<\/b><\/p>\n<\/td>\n

<\/td>\n\n

The \u2212F<\/b> option causes pppoe-relay<\/b> not<\/i> to fork into the background; instead, it remains in the foreground.<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

\u2212h<\/b><\/p>\n<\/td>\n

<\/td>\n\n

The \u2212h<\/b> option prints a brief usage message and exits.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

OPERATION <\/a> <\/h2>\n

pppoe-relay<\/b> listens for incoming PPPoE PADI frames on all interfaces specified with -B<\/b> or -C<\/b> options. When a PADI frame appears, pppoe-relay<\/b> adds a Relay-Session-ID tag and broadcasts the PADI on all interfaces specified with -B<\/b> or -S<\/b> options (except the interface on which the frame arrived.)<\/p>\n

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.<\/p>\n

When a PADS frame is received, pppoe-relay<\/b> enters the two peers\u2019 MAC addresses and session-ID\u2019s into a hash table. (The session-ID seen by the access concentrator may be different from that seen by the client; pppoe-relay<\/b> must renumber sessions to avoid the possibility of duplicate session-ID\u2019s.) Whenever either peer sends a session frame, pppoe-relay<\/b> looks up the session entry in the hash table and relays the frame to the correct peer.<\/p>\n

When a PADT frame is received, pppoe-relay<\/b> relays it to the peer and deletes the session entry from its hash table.<\/p>\n

If a client and server crash (or frames are lost), PADT frames may never be sent, and pppoe-relay<\/b>\u2019s hash table can fill up with stale sessions. 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<\/i> 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.<\/p>\n

EXAMPLE INVOCATIONS <\/a> <\/h2>\n

pppoe-relay -C eth0 -S eth1<\/p>\n

The example above relays frames between PPPoE clients on the eth0 network and PPPoE servers on the eth1 network.<\/p>\n

pppoe-relay -B eth0 -B eth1<\/p>\n

This example is a transparent relay — frames are relayed between any mix of clients and servers on the eth0 and eth1 networks.<\/p>\n

pppoe-relay -S eth0 -C eth1 -C eth2 -C eth3<\/p>\n

This example relays frames between servers on the eth0 network and clients on the eth1, eth2 and eth3 networks.<\/p>\n

AUTHORS <\/a> <\/h2>\n

pppoe-relay<\/b> was written by Dianne Skoll .<\/p>\n

The pppoe<\/b> home page is http:\/\/www.roaringpenguin.com\/pppoe\/<\/i>.<\/p>\n

SEE ALSO <\/a> <\/h2>\n

pppoe-start(8), pppoe-stop(8), pppoe-connect(8), pppd(8), pppoe.conf(5), pppoe(8), pppoe-setup(8), pppoe-status(8), pppoe-sniff(8), pppoe-server(8)<\/p>\n

\n","protected":false},"excerpt":{"rendered":"

pppoe-relay \u2212 user-space PPPoE relay agent. <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[5,52,4,469],"class_list":["post-3341","post","type-post","status-publish","format-standard","hentry","category-8-administracion-del-sistema","tag-5","tag-administracion","tag-man8","tag-pppoe-relay"],"gutentor_comment":0,"_links":{"self":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/3341","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/comments?post=3341"}],"version-history":[{"count":0,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/3341\/revisions"}],"wp:attachment":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/media?parent=3341"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/categories?post=3341"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/tags?post=3341"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}