OpenWRT with Netcomm NF4V DSL: Timeout waiting for PADO packets; Unable to complete PPPoE Discovery

Forums › LAN (ethernet/Wifi/routers/Bluetooth) › OpenWRT with Netcomm NF4V DSL: Timeout waiting for PADO packets; Unable to complete PPPoE Discovery

dzh

50 posts

Geek

Trusted

#181284 8-Oct-2015 22:47

Hope I am in the right sub.

Configured Netcomm to work as a bridge as per instructions found here. Flashed TP-Link tl-wr841n to the latest stable OpenWRT 15.05.

In the system log I am getting:

Wed Oct 7 08:31:04 2015 daemon.notice netifd: Interface 'wan' is setting up now

Wed Oct 7 08:31:04 2015 daemon.info pppd[19295]: Plugin rp-pppoe.so loaded.

Wed Oct 7 08:31:04 2015 daemon.info pppd[19295]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7

Wed Oct 7 08:31:04 2015 daemon.notice pppd[19295]: pppd 2.4.7 started by root, uid 0

Wed Oct 7 08:31:19 2015 daemon.warn pppd[19295]: Timeout waiting for PADO packets

Wed Oct 7 08:31:19 2015 daemon.err pppd[19295]: Unable to complete PPPoE Discovery

Wed Oct 7 08:31:19 2015 daemon.info pppd[19295]: Exit.

Wed Oct 7 08:31:19 2015 daemon.notice netifd: Interface 'wan' is now down

Any suggestions what to check before I approach Orcon for advise?

Thank you.

michaelmurfy

meow
13230 posts

Uber Geek

Moderator

ID Verified

Trusted

Lifetime subscriber

#1402793 9-Oct-2015 00:09

Orcon use DHCP tagged on VLAN 10 - there is no other configuration (username / password) required.

Ensure you've enabled VLAN tagging on the WAN interface and set the WAN interface to grab an IP address via DHCP, should work from there.

Edit: If you're bridging because you have VDSL / ADSL I'd recommend just shoving your TP-Link router into a Dumb AP and using your main router as your DHCP server etc, you'll just need to disable DHCP on the TP-Link router and ensure it's IP address is one on your main routers range.

Michael Murphy | https://murfy.nz
Referral Links: Quic Broadband (use R122101E7CV7Q for free setup)

Are you happy with what you get from Geekzone? Please consider supporting us by subscribing.
Opinions are my own and not the views of my employer.

dzh

50 posts

Geek

Trusted

#1402794 9-Oct-2015 00:16

michaelmurfy: Orcon use DHCP tagged on VLAN 10 - there is no other configuration (username / password) required.

Ensure you've enabled VLAN tagging on the WAN interface and set the WAN interface to grab an IP address via DHCP, should work from there.

Edit: If you're bridging because you have VDSL / ADSL I'd recommend just shoving your TP-Link router into a Dumb AP and using your main router as your DHCP server etc, you'll just need to disable DHCP on the TP-Link router and ensure it's IP address is one on your main routers range.

I am bridging exactly because I do not want Netcomm to be as a main router. Thing is dropping packets randomly or spikes latency to seconds.

Will check about VLAN tagging. Does it apply to ADSL?

michaelmurfy

meow
13230 posts

Uber Geek

Moderator

ID Verified

Trusted

Lifetime subscriber

#1402795 9-Oct-2015 00:19

dzh:
michaelmurfy: Orcon use DHCP tagged on VLAN 10 - there is no other configuration (username / password) required.

Ensure you've enabled VLAN tagging on the WAN interface and set the WAN interface to grab an IP address via DHCP, should work from there.

Edit: If you're bridging because you have VDSL / ADSL I'd recommend just shoving your TP-Link router into a Dumb AP and using your main router as your DHCP server etc, you'll just need to disable DHCP on the TP-Link router and ensure it's IP address is one on your main routers range.

I am bridging exactly because I do not want Netcomm to be as a main router. Thing is dropping packets randomly or spikes latency to seconds.

Will check about VLAN tagging. Does it apply to ADSL?

Those Netcomm routers that are provided are actually rather good. Ensure you're not using it over WiFi as this will drop packets / spike latency instead use Ethernet and you shouldn't have any problems.

Since you're on ADSL it is a little different. I am personally not sure how to set it up via ADSL however I am sure somebody around here will. Just remember, using another router will mean you lose the phone service (if you're using that).

sbiddle

30853 posts

Uber Geek

Retired Mod

Trusted

Biddle Corp

Lifetime subscriber

#1402834 9-Oct-2015 08:11

The NF4V and NF8AC are IMHO two of the most stable devices in the market right now. If you're seeing issues I'm not sure the hardware if necessarily going to be the cause.

As you're on ADSL the most common cause of the two such issues is upstream saturation which is an incredibly common problem these days.

dzh

50 posts

Geek

Trusted

#1403204 9-Oct-2015 18:55

michaelmurfy:

Those Netcomm routers that are provided are actually rather good. Ensure you're not using it over WiFi as this will drop packets / spike latency instead use Ethernet and you shouldn't have any problems.

They are not that good if they drop packets