PPPoe - Connection Attempt Failed - Archer c60 v3

Hello All,

Background:

  1. Soo I have recently flashed my Archer C60 v3 router with Openwrt latest code.
  2. My router connects to a ISP modem and we use PPPoE for authentication and get access to the internet.
  3. I'm more into open source things hence flashed my router to get best out of this opnewrt.

Issue:
4. PPPoe - Connection Attempt Failed.
5. I have configured wan interface (eth1) (Physical router port WAN) with PPPoe with no luck and later switched to Lan interface(eth0) (Physical router port Lan4) still PPPoe throws error

Tshoot steps taken:

  1. Note that the Username/Passwords were already working moments ago on TP links Stock firmware so no issues here.
  2. Confirmed with ISP and rather than confirmation I know I will be able to use multiple devices/routers/laptops directly with wan link and PPPoe and it never fails and have done that many many times. ISP doesn't have any mac binding setup on their end.
  3. Following the community discussions I have still hardcoded the recent mac address last used on the device where PPPoe was working still somehow Openwrt dosen't like that.
  4. Kept default values, Configured some suggested values that I read on discussions still no luck.
  5. verified with ISP they don't use any tagging etc and we can use as many macs we want.
  6. Tshoot with ISP, ISP is ACT Fibernet. when I connect something like Openwrt or some other modem they see a mac and link up. All they care is linkup and nothing more than that so I am not getting any further support from them. Also the modem has other connections going to other houses and I have asked them to configure a spare port but still same result the Openwrt just throws PPPoe Error.
**Config Details:**

++ Attached screenshots of GUI..
![Capture1|690x317](upload://hBJdBujau6Aw82YOQGlJEmh6qxZ.jpeg)
![Capture2|690x315](upload://1NcHGvhwYDnGWcLYQKKCmWhYN9a.jpeg)
![Capture3|348x376](upload://bNZj12exFd7fWnwqEB6qILWoiiG.jpeg)
![Capture4|690x348](upload://bR5gaKxiRkNGr8aVXAGsrtY5iab.jpeg)


root@OpenWrt:~# ifconfig
br-lan    Link encap:Ethernet  HWaddr **** (Hashed)
          inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fd32:b317:e290::1/60 Scope:Global
          inet6 addr: fe80::b27b:25ff:fe72:ce90/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:12603 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12691 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1398238 (1.3 MiB)  TX bytes:5140522 (4.9 MiB)

eth0      Link encap:Ethernet  HWaddr **** (Hashed)
          inet6 addr: fe80::e6c3:2aff:fe23:bda0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:462 errors:0 dropped:348 overruns:0 frame:0
          TX packets:3040 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:43595 (42.5 KiB)  TX bytes:296844 (289.8 KiB)
          Interrupt:5

eth0.1    Link encap:Ethernet  HWaddr **** (Hashed)
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1859 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:232273 (226.8 KiB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:1521 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1521 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:133714 (130.5 KiB)  TX bytes:133714 (130.5 KiB)

wlan0     Link encap:Ethernet  HWaddr **** (Hashed)
          inet6 addr: fe80::437:60ff:fed3:d56/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:12621 errors:0 dropped:0 overruns:0 frame:0
          TX packets:13545 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1576178 (1.5 MiB)  TX bytes:5522406 (5.2 MiB)

===================

root@OpenWrt:/etc/config# cat network

config interface 'loopback'
        option device 'lo'
        option proto 'static'
        option ipaddr '127.0.0.1'
        option netmask '255.0.0.0'

config globals 'globals'
        option ula_prefix '****Hassed''

config interface 'wan'
        option proto 'pppoe'
        option username '****Hassed''
        option ipv6 'auto'
        option keepalive '2 5'
        option demand '0'
        option device 'eth0'
        option password '****Hassed''

config device
        option name 'br-lan'
        option type 'bridge'
        list ports 'eth0.1'

config interface 'lan'
        option device 'br-lan'
        option proto 'static'
        option ipaddr '192.168.1.1'
        option netmask '255.255.255.0'
        option ip6assign '60'

config switch
        option name 'switch0'
        option reset '1'
        option enable_vlan '1'

config switch_vlan
        option device 'switch0'
        option vlan '1'
        option ports '0 4 3 2 1'
        option vid '1'

config interface 'lansubnet'
        option proto 'static'
        option device 'br-lan'
        option ipaddr '192.168.1.2'
        option netmask '255.255.255.0'

config device
        option name 'eth0'
        option macaddr '****Hassed'

=================================
root@OpenWrt:/etc/ppp# cat options
#debug
logfile /dev/null
noipdefault
noaccomp
nopcomp
nocrtscts
lock
maxfail 0
root@OpenWrt:/etc/ppp#
root@OpenWrt:/etc/ppp#

==========================



**Logs:**

Wed Aug  9 08:49:24 2023 daemon.err insmod: module is already loaded - ppp_generic
Wed Aug  9 08:49:24 2023 daemon.err insmod: module is already loaded - pppox
Wed Aug  9 08:49:24 2023 daemon.err insmod: module is already loaded - pppoe
Wed Aug  9 08:49:25 2023 daemon.info pppd[5174]: Plugin pppoe.so loaded.
Wed Aug  9 08:49:25 2023 daemon.info pppd[5174]: PPPoE plugin from pppd 2.4.9
Wed Aug  9 08:49:25 2023 daemon.notice pppd[5174]: pppd 2.4.9 started by root, uid 0
Wed Aug  9 08:49:40 2023 daemon.warn pppd[5174]: Timeout waiting for PADO packets
Wed Aug  9 08:49:40 2023 daemon.err pppd[5174]: Unable to complete PPPoE Discovery
Wed Aug  9 08:49:40 2023 daemon.info pppd[5174]: Exit.
Wed Aug  9 08:49:40 2023 daemon.err insmod: module is already loaded - ppp_generic
Wed Aug  9 08:49:40 2023 daemon.err insmod: module is already loaded - pppox
Wed Aug  9 08:49:40 2023 daemon.err insmod: module is already loaded - pppoe
Wed Aug  9 08:49:40 2023 daemon.info pppd[5258]: Plugin pppoe.so loaded.
Wed Aug  9 08:49:40 2023 daemon.info pppd[5258]: PPPoE plugin from pppd 2.4.9
Wed Aug  9 08:49:40 2023 daemon.notice pppd[5258]: pppd 2.4.9 started by root, uid 0

====================

root@OpenWrt:~# ifstatus wan
{
        "up": false,
        "pending": true,
        "available": true,
        "autostart": true,
        "dynamic": false,
        "proto": "pppoe",
        "device": "eth0",
        "data": {

        },
        "errors": [
                {
                        "subsystem": "pppoe",
                        "code": "CONNECT_FAILED"
                }
        ]
}
root@OpenWrt:~#

======================================

Your config with eth0 cannot work unless you made some non-standard changes to the switch config. eth0 is connected to a switch... you can see that br-lan uses eth0.1 so you can either:

  • use eth1 as the interface (connected to the WAN port directly)
  • use br-lan as the interface (and connect the modem to any LAN Port)
  • use eth0.n (where n is a number greater than 1) and setup vlans in switch config accordingly

Replying to you since you have the magic bit, and that is vlans. I needed to set the PPPoE connection to use vlan 6 and then it worked for me. All depends on what your isp uses.

@zekica

No luck. Attached config for reference. Also, Kindly find points on initial thread under issues, Already tried eth1 hence moved to eth0 now back to eth1.

root@OpenWrt:/etc/config# cat network

config interface 'loopback'
        option device 'lo'
        option proto 'static'
        option ipaddr '127.0.0.1'
        option netmask '255.0.0.0'

config globals 'globals'
        option ula_prefix '**'

config interface 'wan'
        option device 'eth1'
        option proto 'pppoe'
        option username 'hashed'
        option password 'hashed'
        option ipv6 'auto'

config interface 'wan6'
        option device 'eth1'
        option proto 'dhcpv6'

config device
        option name 'br-lan'
        option type 'bridge'
        list ports 'eth0.1'

config interface 'lan'
        option device 'br-lan'
        option proto 'static'
        option ipaddr '192.168.1.1'
        option netmask '255.255.255.0'
        option ip6assign '60'

config switch
        option name 'switch0'
        option reset '1'
        option enable_vlan '1'

config switch_vlan
        option device 'switch0'
        option vlan '1'
        option ports '1 2 3 4 0t'

========================================

root@OpenWrt:/etc/config# ifstatus wan
{
        "up": false,
        "pending": true,
        "available": true,
        "autostart": true,
        "dynamic": false,
        "proto": "pppoe",
        "device": "eth1",
        "data": {

        },
        "errors": [
                {
                        "subsystem": "pppoe",
                        "code": "CONNECT_FAILED"
                }
        ]
}
root@OpenWrt:/etc/config#

@Bartvz
The logs are similar to as pasted earlier for pppoe

As mentioned earlier my ISB dosnt play vlan game. Strange thing is I hve this working on my other old routers with stock firmware even minuites ago. For some reason Openwrt dosen like pppoe.. Aahhhhh

PPPoE works completely fine on OpenWRT on two ISPs I use (both PPPoE on PON).

Can you type logread | grep pppd and see if there are any errors?
The output should look something like:

daemon.info pppd[6737]: Plugin pppoe.so loaded.
daemon.info pppd[6737]: PPPoE plugin from pppd 2.4.9
daemon.notice pppd[6737]: pppd 2.4.9 started by root, uid 0
daemon.info pppd[6737]: PPP session is 4113
daemon.warn pppd[6737]: Connected to xx:xx:xx:xx:xx:xx via interface eth6
kern.info kernel: [   31.066837] pppoe-wan2: renamed from ppp0
daemon.info pppd[6737]: Renamed interface ppp0 to pppoe-wan2
daemon.info pppd[6737]: Using interface pppoe-wan2
daemon.notice pppd[6737]: Connect: pppoe-wan2 <--> eth6
daemon.info pppd[6737]: Remote message: Login ok
daemon.notice pppd[6737]: PAP authentication succeeded
daemon.notice pppd[6737]: peer from calling number xx:xx:xx:xx:xx:xx authorized
daemon.notice pppd[6737]: local  IP address xxx.xxx.xxx.xxx
daemon.notice pppd[6737]: remote IP address xxx.xxx.xxx.xxx
daemon.notice pppd[6737]: primary   DNS address xxx.xxx.xxx.xxx
daemon.notice pppd[6737]: secondary DNS address xxx.xxx.xxx.xxx
daemon.notice netifd: Network device 'pppoe-wan2' link is up

Hey @zekica

I have the latest logs same as these ones.. I'll paste latest ones if you want. But its copy past as below ones even after setting eth1

Wed Aug  9 08:49:24 2023 daemon.err insmod: module is already loaded - ppp_generic
Wed Aug  9 08:49:24 2023 daemon.err insmod: module is already loaded - pppox
Wed Aug  9 08:49:24 2023 daemon.err insmod: module is already loaded - pppoe
Wed Aug  9 08:49:25 2023 daemon.info pppd[5174]: Plugin pppoe.so loaded.
Wed Aug  9 08:49:25 2023 daemon.info pppd[5174]: PPPoE plugin from pppd 2.4.9
Wed Aug  9 08:49:25 2023 daemon.notice pppd[5174]: pppd 2.4.9 started by root, uid 0
Wed Aug  9 08:49:40 2023 daemon.warn pppd[5174]: Timeout waiting for PADO packets
Wed Aug  9 08:49:40 2023 daemon.err pppd[5174]: Unable to complete PPPoE Discovery
Wed Aug  9 08:49:40 2023 daemon.info pppd[5174]: Exit.
Wed Aug  9 08:49:40 2023 daemon.err insmod: module is already loaded - ppp_generic
Wed Aug  9 08:49:40 2023 daemon.err insmod: module is already loaded - pppox
Wed Aug  9 08:49:40 2023 daemon.err insmod: module is already loaded - pppoe
Wed Aug  9 08:49:40 2023 daemon.info pppd[5258]: Plugin pppoe.so loaded.
Wed Aug  9 08:49:40 2023 daemon.info pppd[5258]: PPPoE plugin from pppd 2.4.9
Wed Aug  9 08:49:40 2023 daemon.notice pppd[5258]: pppd 2.4.9 started by root, uid 0

Timeout waiting for PADO packets means that your OpenWRT router doesn't see the PPPoE server at all.

Can you do ip link show dev eth1 and cat /sys/class/net/eth1/speed to see if your WAN interface is even connected to the modem. Also, make sure that eth1 is not part of any bridge.

Yea. @zekica That is really strange as this router was in working condition on stock firmware even today before I have flashed. Also I just tested my other routers / laptop as well just to double check.

But this Openwrt dont know whats happening.. Please help.

Attached screenshot. And yea this is not bridged.

Be aware that you (presumably) posted your PPPoE username/ password in public.

If you didn't change your config since the last time you posted in this thread, I'm still seeing issues with your VLAN setup.

  • please reset your OpenWrt configuration again.
  • only enter your PPPoE settings (use luci, don't copy'n'paste directly to the files), leave the switch/ VLAN and interface name (option device) settings alone(!)
  • configure wireless, if that helps you
  • don't do anything else and check what's happening first, before doing further customizations
2 Likes

Thanks @zekica @Bartvz @slh for your inputs.

Issue has been fixed. All config is the same, However I had ISP recheck their modem port and "half duplex" caught my attention, I had them change it to auto neg on their modem then booooom I'm part of internet now!!!. Woohooo...

One strange thing is stock firmware didn't had issue with half dup but Openwrt for some reason like a mischievous boy in the school said No Sir I don't do this assignment with half. I need a Full Dup or Auto Neg for assignment.

Thanks Everyone! All good Now. Happy to explore Openwrt!

2 Likes