ethernetPPPoE

circle-info

PPPoE (Point-to-Point Protocol over Ethernet) is commonly used by ISPs for broadband connections. It provides authentication and session management over Ethernet.

In WinBox you can configure PPPoE in Interfaces -> PPPoE Client/Server, or you can use terminal with commands /interface pppoe-client and /interface pppoe-server

PPPoE can be used both as a client (connecting to ISP) and as a server (providing internet service).


PPPoE Client configuration

Basic PPPoE client setup

In WinBox go to Interfaces -> PPPoE Client and click +:

  • Name - Interface name (e.g., pppoe-out1)

  • Interface - Physical interface connected to ISP (ether1)

  • User - Username provided by ISP

  • Password - Password provided by ISP

  • Add Default Route - Yes (for internet connection)

  • Use Peer DNS - Yes (use ISP's DNS servers)

# Create basic PPPoE client
/interface pppoe-client add \
    name=pppoe-out1 \
    interface=ether1 \
    user="your_username" \
    password="your_password" \
    add-default-route=yes \
    use-peer-dns=yes \
    disabled=no \
    comment="Main ISP connection"

Advanced PPPoE client settings

PPPoE with VLAN (common ISP setup)

Many ISPs require VLAN tagging for PPPoE:


PPPoE Server configuration

Basic PPPoE server setup

Add PPPoE users

PPPoE server on specific interface


ISP-specific configurations

Common ISP PPPoE setups

Generic ISP with VLAN:

ISP with specific service name:

Dual-stack PPPoE (IPv4 + IPv6):


PPPoE monitoring and troubleshooting

Monitor PPPoE connection

PPPoE troubleshooting

Common PPPoE issues


PPPoE failover and load balancing

Dual PPPoE connections

PPPoE load balancing


PPPoE security considerations

Secure PPPoE server

Client security


Advanced PPPoE features

PPPoE with VPN integration

PPPoE bandwidth monitoring


chevron-rightShow complete PPPoE client setup with failoverhashtag

PPPoE performance optimization

Optimize for performance

Monitor performance

Best practices

PPPoE client best practices

  1. Use appropriate MTU - Set to 1492 or lower to avoid fragmentation

  2. Enable MSS clamping - Prevent TCP MSS issues

  3. Monitor connection - Use netwatch for failover

  4. Backup DNS - Don't rely solely on peer DNS

  5. Log events - Monitor PPPoE connection events

PPPoE server best practices

  1. Limit sessions - Prevent resource exhaustion

  2. Use rate limiting - Control bandwidth per user

  3. Strong authentication - Use MSCHAPv2 minimum

  4. Monitor usage - Track bandwidth and session count

  5. Regular maintenance - Clean up inactive sessions

Security recommendations

  1. Change default credentials - Use strong passwords

  2. Enable logging - Monitor authentication attempts

  3. Use VLANs - Isolate PPPoE traffic

  4. Implement monitoring - Watch for unusual activity

  5. Regular updates - Keep firmware current

Last updated

Was this helpful?