| There are two ways to configure a PPPoE interface: - Create a new PPPoE interface using the CLI and reference the intended parent interface, see Technical Tip: PPPoE-interface configuration for IPv4 and IPv6.
- Set PPPoE mode for a physical interface, see Technical Tip: PPPoE interface option not available from GUI.
When configuring a new PPPoE interface with using the first method above, the new PPPoE interface may not initialize correctly after creation.
Example PPPoE tunnel interface configuration: config system pppoe-interface edit "test_pppoe" set device "wan2" set username user123 set password password123 next end Diagnostics: The command 'diagnose netlink interface list <pppoe_interface_name>' does not list the interface:
diagnose netlink interface list test_pppoe The firewall still attempts to run PPPoE Discovery (PPPoED). If PPPoED is successful, this does not provide network connectivity and the following error can be seen on the PPPoE debugs:
Couldn't create new ppp unit: No such device or address
Refer to the article for PPPoE troubleshooting and debugs: Troubleshooting Tip: How to Troubleshoot PPPoE Disconnection Issues
There are two possible workarounds:
- Reboot the FortiGate. After the reboot, the interface can be successfully created on the kernel, and the following command will show output:
diagnose netlink interface list test_pppoe if=test_pppoe family=00 type=512 index=49 mtu=1492 link=0 master=0 ref=9 state=start present fw_flags=0 flags=up p2p run noarp multicast Qdisc=pfifo_fast stat: rxp=0 txp=0 rxb=0 txb=0 rxe=0 txe=0 rxd=0 txd=0 mc=0 collision=0 @ time=1758999611 re: rxl=0 rxo=0 rxc=0 rxf=0 rxfi=0 rxm=0 te: txa=0 txc=0 txfi=0 txh=0 txw=0 misc rxc=0 txc=0 input_type=0 state=3 arp_entry=0 refcnt=9
- Configure PPPoE mode on the interface as described in option 2. However, this is not possible for all firmware versions and interface types.
| 
