How can I configure the SonicWall WAN / X1 Interface with PPPoE connection?

10/14/2021 1,016 People found this article helpful 116,730 Views

Download

Print

Share

• LinkedIn
• Twitter
• Facebook
• Email
• Copy URL The link has been copied to clipboard

Description

Configuring the SonicWall WAN interface (X1 by default) with PPPoE settings (Other WAN configuration: DHCP, Static IP, PPTP or L2TP)

Video Tutorial: Click here for the video tutorial of this topic.

Resolution

Resolution for SonicOS 7.X

This release includes significant user interface changes and many new features that are different from the SonicOS 6.5 and earlier firmware. The below resolution is for customers using SonicOS 7.X firmware.

1. Navigate to Network| System | Interfaces| X1 .
2. Click  Configure.
   
   
   
   
3. Under IP assignment, choose PPPoE from the drop down menu.
   NOTE: The X1 Interface MTU is 1500 by default.
4. Enter the User name and User password given by the ISP. 
5. At the bottom of the page, you can choose Obtain IP address automatically if the ISP is leasing out IP addresses, or you can manually specify the IP address by choosing Specify IP Address and entering the IP Address given by the ISP.
   
   
   
   
6. Either check Obtain DNS server address automatically or manually specify it by choosing Specify DNS servers.

Protocol tab (Displays the acquired IP address, subnet mask, gateway address, and DNS server addresses)

1. Click Protocol tab.
2. View the settings for the acquired IP address, subnet mask, gateway address, and DNS server addresses.
3. Inactivity Disconnect—Specify how long (in minutes) the SonicWall appliance waits before disconnecting from the Internet, and select the checkbox.
4. Strictly use LCP echo packets for server keep-alive—This checkbox is enabled when the client recognizes that the server relies on Link Control Protocol (LCP) echo requests for keeping the PPPoE connection alive.
5. Reconnect the PPPoE client if the server does not send traffic for __ minutes—Select this checkbox and enter the number of minutes to wait without traffic before the connection is ended. When enabled, the PPPoE client monitors traffic from the server on the tunnel and disconnects when no traffic is seen for the specified time period.
6. Click OK .
   
   
   
   

How to test the connectivity

1. Navigate to Device | Diagnostics. Choose Ping .
2. Ping your ISP’s Default Gateway or any IP that is pingable on the Internet (e.g. 4.2.2.2).
3. Also try to ping a website (eg: www.google.com) to ensure that the DNS resolution is working.
   
   

Resolution for SonicOS 6.5

This release includes significant user interface changes and many new features that are different from the SonicOS 6.2 and earlier firmware. The below resolution is for customers using SonicOS 6.5 firmware.

1. Navigate to Manage | System Setup | Network | X1 .
2. Click  Configure.
   
   
   
   
   
3. Under IP assignment, choose PPPoE from the drop down menu.
   
   

    NOTE: The X1 Interface MTU is 1500 by default.

4. Enter the User name and User password given by the ISP. 
5. At the bottom of the page, you can choose Obtain IP address automatically if the ISP is leasing out IP addresses, or you can manually specify the IP address by choosing Specify IP Address and entering the IP Address given by the ISP.
   
   
   
   
6. Either check Obtain DNS server address automatically or manually specify it by choosing Specify DNS servers.

Protocol tab (Displays the acquired IP address, subnet mask, gateway address, and DNS server addresses)

1. Click Protocol tab.
2. View the settings for the acquired IP address, subnet mask, gateway address, and DNS server addresses.
3. Inactivity Disconnect—Specify how long (in minutes) the SonicWall appliance waits before disconnecting from the Internet, and select the checkbox.
4. Strictly use LCP echo packets for server keep-alive—This checkbox is enabled when the client recognizes that the server relies on Link Control Protocol (LCP) echo requests for keeping the PPPoE connection alive.
5. Reconnect the PPPoE client if the server does not send traffic for __ minutes—Select this checkbox and enter the number of minutes to wait without traffic before the connection is ended. When enabled, the PPPoE client monitors traffic from the server on the tunnel and disconnects when no traffic is seen for the specified time period.
6. Click OK .
   
   
   
   
   

How to test the connectivity

1. On the SonicWall, Navigate to Investigate|System Diagnostics. Choose Ping in the  Diagnostic utility” drop down in the Sonic OS Standard and Enhanced firmware. (In 6.x firmware Click Tools | Diagnostics).
2. Ping your ISP’s Default Gateway or any IP that is pingable on the Internet (e.g. 4.2.2.2).
3. Also try to ping a website (eg: www.google.com) to ensure that the DNS resolution is working.
   
   
   
   
   

Troubleshooting

• Try doing power recycle of SonicWall and the modem. After 30 seconds plug in back the power cable of the modem first and after getting solid lights on the modem plug in back the power cable of SonicWall. 
• KBID 5387 - UTM: How to Optimize PPPoE MTU? 
• KBID 3895 - UTM: Troubleshooting PPPoE ISP Connectivity Issues
• KBID 3863 - TM: Troubleshooting a PPPoE Authentication Failure on SonicWall Firewall (UTM) Appliances
  
  
  
  

Resolution for SonicOS 6.2 and Below

The below resolution is for customers using SonicOS 6.2 and earlier firmware. For firewalls that are generation 6 and newer we suggest to upgrade to the latest general release of SonicOS 6.5 firmware.

PPPoE mode: Use this mode if your ISP is using a PPPoE connection. To configure this mode

1. Navigate to  Network | Interfaces tab. 
2. Click Configure for the WAN interface (X1 by default). 
3. Under IP assignment, choose PPPoE from the drop down menu.
   
   

   NOTE: The X1 Interface MTU is 1500 by default. 

4. Enter the User name and User password given by the ISP. 
5. At the bottom of the page, you can choose Obtain IP address automatically if the ISP is leasing out IP addresses, or you can manually specify the IP address by choosing Specify IP Address and entering the IP Address given by the ISP. 
   
   
   
   
6. Either check Obtain DNS server address automatically or manually specify it by choosing Specify DNS servers.

Protocol tab (Displays the acquired IP address, subnet mask, gateway address, and DNS server addresses)

1.  Click the Protocol tab.
2. View the settings for the acquired IP address, subnet mask, gateway address, and DNS server addresses.
3. Inactivity Disconnect—Specify how long (in minutes) the SonicWall appliance waits before disconnecting from the Internet, and select the checkbox.
4. Strictly use LCP echo packets for server keep-alive—This checkbox is enabled when the client recognizes that the server relies on Link Control Protocol (LCP) echo requests for keeping the PPPoE connection alive.
5. Reconnect the PPPoE client if the server does not send traffic for __ minutes—Select this checkbox and enter the number of minutes to wait without traffic before the connection is ended. When enabled, the PPPoE client monitors traffic from the server on the tunnel and disconnects when no traffic is seen for the specified time period.
6. Click OK.
   
   

How to test the connectivity

1. On the SonicWall, Click System | Diagnostics. Choose Ping in the “Diagnostic utility” drop down in the Sonic OS Standard and Enhanced firmware. (In 6.x firmware Click Tools | Diagnostics).
2. Ping your ISP’s Default Gateway or any IP that is pingable on the Internet (e.g. 4.2.2.2).
3. Also try to ping a website (eg: www.google.com) to ensure that the DNS resolution is working.
   
   
   
   
   

Troubleshooting

• Try doing power recycle of SonicWall and the modem. After 30 seconds plug in back the power cable of the modem first and after getting solid lights on the modem plug in back the power cable of SonicWall. 
• KBID 5387 - UTM: How to Optimize PPPoE MTU? 
• KBID 3895 - UTM: Troubleshooting PPPoE ISP Connectivity Issues
• KBID 3863 - TM: Troubleshooting a PPPoE Authentication Failure on SonicWall Firewall (UTM) Appliances

Related Articles

• Client VPN hanging at acquiring IP using SonicWall DHCP
• GVC stuck on acquiring IP for some users
• App Control fails by schema error when editing VPN category

Categories

• Firewalls > NSa Series > Networking
• Firewalls > NSv Series > Networking
• Firewalls > TZ Series > Networking