Can't connect my Archer through PPPoE

[WildEast]

Hello,
I have a VDSL modem from my ISP as well as Gargoyle 1.12.0 on my V5 Archer. I configured the modem to act as a bridge, while the Archer connects as PPPoE. However, Archer wouldn't retrieve the WAN IP not matter what. I checked the logs and found this:

Code: Select all

Mon Nov 16 18:13:53 2020 daemon.notice netifd: Interface 'wan' is setting up now
Mon Nov 16 18:13:53 2020 daemon.err insmod: module is already loaded - slhc
Mon Nov 16 18:13:53 2020 daemon.err insmod: module is already loaded - ppp_generic
Mon Nov 16 18:13:53 2020 daemon.err insmod: module is already loaded - pppox
Mon Nov 16 18:13:53 2020 daemon.err insmod: module is already loaded - pppoe
Mon Nov 16 18:13:53 2020 daemon .info pppd[25121]: Plugin rp-pppoe.s o loaded.
Mon Nov 16 18:13:53 2020 daemon .info pppd[25121]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
Mon Nov 16 18:13:53 2020 daemon.notice pppd[25121]: pppd 2.4.7 started by root, uid 0
Mon Nov 16 18:13:53 2020 daemon .info pppd[25121]: PPP session is 1
Mon Nov 16 18:13:53 2020 daemon.warn pppd[25121]: Connected to 84:26:2b:de:d4:d1 via interface eth0.2
Mon Nov 16 18:13:53 2020 kern.inf o kernel: [62297.569179] pppoe-wan: renamed from ppp0
Mon Nov 16 18:13:53 2020 daemon .info pppd[25121]: Using interface pppoe-wan
Mon Nov 16 18:13:53 2020 daemon.notice pppd[25121]: Connect: pppoe-wan <--> eth0.2
Mon Nov 16 18:14:23 2020 daemon.warn pppd[25121]: LCP: timeout sending Config-Requests
Mon Nov 16 18:14:23 2020 daemon.notice pppd[25121]: Connection terminated.
Mon Nov 16 18:14:23 2020 daemon .info pppd[25121]: Sent PADT
Mon Nov 16 18:14:23 2020 daemon.notice pppd[25121]: Modem hangup
Mon Nov 16 18:14:23 2020 daemon .info pppd[25121]: Exit.
Mon Nov 16 18:14:23 2020 daemon.notice netifd: Interface 'wan' is now down
Mon Nov 16 18:14:23 2020 daemon.notice netifd: Interface 'wan' is setting up now
Mon Nov 16 18:14:24 2020 daemon.err insmod: module is already loaded - slhc
Mon Nov 16 18:14:24 2020 daemon.err insmod: module is already loaded - ppp_generic
Mon Nov 16 18:14:24 2020 daemon.err insmod: module is already loaded - pppox
Mon Nov 16 18:14:24 2020 daemon.err insmod: module is already loaded - pppoe
Mon Nov 16 18:14:24 2020 daemon .info pppd[25241]: Plugin rp-pppoe.s o loaded.
Mon Nov 16 18:14:24 2020 daemon .info pppd[25241]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
Mon Nov 16 18:14:24 2020 daemon.notice pppd[25241]: pppd 2.4.7 started by root, uid 0
Mon Nov 16 18:14:24 2020 daemon .info pppd[25241]: PPP session is 1
Mon Nov 16 18:14:24 2020 daemon.warn pppd[25241]: Connected to 84:26:2b:de:d4:d1 via interface eth0.2
Mon Nov 16 18:14:24 2020 kern.inf o kernel: [62328.318768] pppoe-wan: renamed from ppp0
Mon Nov 16 18:14:24 2020 daemon .info pppd[25241]: Using interface pppoe-wan
Mon Nov 16 18:14:24 2020 daemon.notice pppd[25241]: Connect: pppoe-wan <--> eth0.2
Mon Nov 16 18:14:58 2020 daemon.warn pppd[25241]: LCP: timeout sending Config-Requests
Mon Nov 16 18:14:58 2020 daemon.notice pppd[25241]: Connection terminated.
Mon Nov 16 18:14:58 2020 daemon .info pppd[25241]: Sent PADT
Mon Nov 16 18:14:58 2020 daemon.notice pppd[25241]: Modem hangup
Mon Nov 16 18:14:58 2020 daemon .info pppd[25241]: Exit.
Mon Nov 16 18:14:58 2020 daemon.notice netifd: Interface 'wan' is now down

(For the above log, I've put some spacing in the daemon .info because the forums thought its a URL)

Apparently, I'm always getting "LCP: timeout sending Config-Requests" and I'm not really sure what that means. Any ideas?

[RomanHK]

Try this procedure first: viewtopic.php?p=56747#p56747

EDIT: Then you can try adding these additional commands to the /etc/ppp/options file:

Code: Select all

maxfail 0
passive

and lastly, you can try this step: viewtopic.php?p=56732#p56732

[WildEast]

Try this procedure first: viewtopic.php?p=56747#p56747

EDIT: Then you can try adding these additional commands to the /etc/ppp/options file:

Code: Select all

maxfail 0
passive

and lastly, you can try this step: viewtopic.php?p=56732#p56732

I've tried all the above. Setting everything mentioned (LCP failure, interval, maxfail, force link, removing modemaccess.sh) didn't change the outcome of the logs, only the "passive" command got the log stuck at "LCP: timeout sending Config-Requests" and nothing else happened afterwards.

I'm not sure if this info will be of help, but when my ISP modem is used to connect as PPPoE it retrieves the WAN IP in a relatively long time (around 5-7 mins). Are there any settings I should try in Gargoyle related to this?

[RomanHK]

Also check the correct setting of these values:
VPI (Virtual Path Identifier) and VCI (Virtual Circuit Identifier).

[RomanHK]

Try contacting your ISP, it is quite possible that your xDSL modem will not work in bridge mode even though it has this function - usually this is solved by uploading another firmware in the modem.

I also had these problems with the Zyxel modem (I don't remember the type anymore) and it was set up using the new firmware and via the CLI (not the GUI). There were frequent resynchronizations and then I went from xDSL to UPC.

I also hope this is not a problem in VLANs where some ISPs require it - the configuration is very complicated and would have to be done manually.

[RomanHK]

The only thing I can advise you is to turn on debug command in the /etc/ppp/options file - this will give you more information about the progress of the connection .

Code: Select all

debug

[Lantis]

Are you certain you need to use PPPoE in this configuration? Have you tried just DHCP?

[RomanHK]

Are you certain you need to use PPPoE in this configuration? Have you tried just DHCP?

To avoid double NAT, the modem switches to bridge mode and in most cases you get a public IP on the router on the WAN interface.

But YES, to perform double NAT I would see as the last functional option.

[Lantis]

I know how bridge mode works.
Some ISP modems have "bridge mode" but it is more of a "half bridge" where the modem still performs the pppoe negotiation and then directly exposes the WAN IP over DHCP.

It is how my modem/router is running and has been for 18 months