Setup guide

time (i.e. 2 * keepalive-timeout), not responding client is proclaimed disconnected.
one-session-per-host (yes | no; default: no) - allow only one session per host (determined by MAC
address). If a host will try to establish a new session, the old one will be closed
default-profile (name; default: default) - default profile to use
Notes
The default keepalive-timeout value of 10 is OK in most cases. If you set it to 0, the router will not
disconnect clients until they log out or router is restarted. To resolve this problem, the
one-session-per-host property can be used.
Security issue: do not assign an IP address to the interface you will be receiving the PPPoE
requests on.
Example
To add PPPoE server on ether1 interface providing ex service and allowing only one connection
per host:
[admin@Wandy] interface pppoe-server server> add interface=ether1 \
\... service-name=ex one-session-per-host=yes
[admin@Wandy] interface pppoe-server server> print
Flags: X - disabled
0 X service-name="ex" interface=ether1 mtu=1480 mru=1480
authentication=mschap2,mschap,chap,pap keepalive-timeout=10
one-session-per-host=yes default-profile=default
[admin@Wandy] interface pppoe-server server>
PPPoE Server Users
interface pppoe-server
Property Description
name (name) - interface name
service-name (name) - name of the service the user is connected to
remote-address (MAC address) - MAC address of the connected client
user (name) - the name of the connected user
encoding (text) - encryption and encoding (if asymmetric, separated with '/') being used in this
connection
uptime - shows how long the client is connected
Example
To view the currently connected users:
[admin@Wandy] interface pppoe-server> print
Flags: R - running
# NAME SERVICE REMOTE-ADDRESS USER ENCO... UPTIME
0 R <pppoe-ex> ex 00:C0:CA:16:16:A5 ex 12s
[admin@Wandy] interface pppoe-server>
To disconnect the user ex:
[admin@Wandy] interface pppoe-server> remove [find user=ex]
[admin@Wandy] interface pppoe-server> print
[admin@Wandy] interface pppoe-server>