Table of Contents
Advertisement
When the option to force unnumbered PPPoE is selected, the client (that is to say
NetDefendOS) will not accept assignment of another IP address by the server.
•
The IP address specified, or possibly the address assigned by the PPPoE server when
unnumbered PPPoE is not forced, will serve as the IP address of the PPPoE client interface.
This will be used as the local IP address for traffic leaving the interface when the traffic is
originated or NATed by the NetDefend Firewall.
Note: PPPoE has a discovery protocol
To provide a point-to-point connection over Ethernet, each PPP session must learn the
Ethernet address of the remote peer, as well as establish a unique session identifier.
PPPoE includes a discovery protocol that provides this.
PPPoE cannot be used with HA
For reasons connected with the way IP addresses are shared in a NetDefendOS high availability
cluster, PPPoE will not operate correctly. It should therefore not be configured with HA.
Example 3.23. Configuring a PPPoE Client
This example shows how to configure a PPPoE client on the wan interface with traffic routed over
PPPoE.
CLI
gw-world:/> add Interface PPPoETunnel PPPoEClient
Web Interface
1.
Go to: Network > Interfaces and VPN > PPPoE > Add > PPPoE Tunnel
2.
Then enter:
•
Name: PPPoEClient
•
Physical Interface: wan
•
Remote Network: all-nets (as we will route all traffic into the tunnel)
•
Service Name: Service name provided by the service provider
•
Username: Username provided by the service provider
•
Password: Password provided by the service provider
•
Confirm Password: Retype the password
•
Under Authentication specify which authentication protocol to use
(the default settings will be used if not specified)
EthernetInterface=wan
Network=all-nets
Username=exampleuser
Password=examplepw
204
Chapter 3: Fundamentals
- Quick Links:
- User Manual
Hide quick links:
Advertisement
Table of Contents
Troubleshooting
