OpenWrt Forum Archive

Topic: WAN troubleshooting

The content of this topic has been archived on 27 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Hi,

At home I have an ADSL2+ modem which is connected to an old router running LibreCMC 1.3 (which I think it is just a Barrier Breaker, not sure).

Everything works fine, but the router's hardware is very limited and I cannot install some packages I need now. So I am trying to replace that old router.

The new router is a TP-Link WDR4300. The problem is that, after installing Openwrt and configuring everything -having my old router as a reference-, I get no WAN connectivity.

Once everything is properly started and plugged into the new router, I run the command "ifconfig -a" and I cannot see the pppoe-wan interface I could see in my old router.

In the logs of the new router, it complains about the MTU, but I think that setting is ok, that is how the ISP told me to configure it and it works fine in my old router.

Please find below the logs of the new router. Any suggestion is more than welcome...

Thank you!!

Wed May 10 20:20:51 2017 daemon.warn pppd[1574]: Timeout waiting for PADO packets
Wed May 10 20:20:51 2017 daemon.err pppd[1574]: Unable to complete PPPoE Discovery
Wed May 10 20:20:51 2017 daemon.info pppd[1574]: Exit.
Wed May 10 20:20:52 2017 daemon.notice netifd: Interface 'wan' is now down
Wed May 10 20:20:52 2017 daemon.notice netifd: Interface 'wan' is setting up now
Wed May 10 20:20:52 2017 daemon.info pppd[1594]: Plugin rp-pppoe.so loaded.
Wed May 10 20:20:52 2017 daemon.info pppd[1594]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
Wed May 10 20:20:52 2017 daemon.notice pppd[1594]: pppd 2.4.7 started by root, uid 0
Wed May 10 20:20:52 2017 daemon.err pppd[1594]: Interface eth0.20 has MTU of 1488 -- should be at least 1500.
Wed May 10 20:20:52 2017 daemon.err pppd[1594]: This may cause serious connection problems.
Wed May 10 20:21:07 2017 daemon.warn pppd[1594]: Timeout waiting for PADO packets
Wed May 10 20:21:07 2017 daemon.err pppd[1594]: Unable to complete PPPoE Discovery
Wed May 10 20:21:07 2017 daemon.info pppd[1594]: Exit.
Wed May 10 20:21:07 2017 daemon.notice netifd: Interface 'wan' is now down
Wed May 10 20:21:07 2017 daemon.notice netifd: Interface 'wan' is setting up now
Wed May 10 20:21:07 2017 daemon.info pppd[1615]: Plugin rp-pppoe.so loaded.
Wed May 10 20:21:07 2017 daemon.info pppd[1615]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
Wed May 10 20:21:07 2017 daemon.notice pppd[1615]: pppd 2.4.7 started by root, uid 0
Wed May 10 20:21:07 2017 daemon.err pppd[1615]: Interface eth0.20 has MTU of 1488 -- should be at least 1500.
Wed May 10 20:21:07 2017 daemon.err pppd[1615]: This may cause serious connection problems.

Find the WAN interface configuration from the OpenWRT config file /etc/config/network. Add a 'pppd_options' line with 'debug' value.

For example:

config interface 'wan'
    option proto 'pppoe'
    ... other settings ...
    option pppd_options 'debug'

This enables debug output in the pppd logs. It might provide more insight on why the connection attempt fails.

The WDR4300 does not have an ADSL interface... how are you connecting it?

Also, do you have any more details on how your ISP is providing the Internet access? Do they use VLAN encapsulation i.e. they specify that in VID X you use PPPoE -protocol with 'username' and 'password' and that this VLAN arrives to you over the ADSL line?

If this is the case, then you should also post your /etc/config/network details. It may just be a switch or VLAN configuration issue.

(Last edited by Antek on 9 Jun 2017, 09:23)

Thank you!!

I did everything you suggested and I was writing a very long post with all the information I got, but then I saw this new topic in the forum named 'No WAN connectivity' which let me see what the problem was. As you suggested it was indeed a switch or VLAN thing. In the switch I was not correctly tagging the WAN port with its VLAN.

Problem solved!!

Thanks again!

The discussion might have continued from here.