Frustrating issue with Flint 2 + PPPOE

Technical Support for Routers
1

So I received my Flint 2 today and merrily went setting it up except hit a big brick wall with the very first step that is setting up PPPOE. I came across many topics that mentioned Flint 2 having PPPOE issues but I cannot figure out what is going on. My setup has been as under:

ISP ONT (in Bridge mode) > Flint 2

Previously using Linksys WRT1900AC in the same setup and all I've had to enter was simply the PPPOE Username/Password provided by my ISP and no fuss connection. In fact it still works on WRT1900AC but the same setting won't work on Flint 2. No MAC cloning or VLAN tagging ever required from ISP.

Network Config on WRT1900AC:

config device
	option name 'wan'
	option macaddr 'removed'

config interface 'wan'
	option device 'wan'
	option proto 'pppoe'
	option username 'removed'
	option password 'removed'
	option ipv6 '0'

Connection log on WRT1900AC:

Mon Jan 13 15:33:30 2025 daemon.info pppd[18723]: Plugin pppoe.so loaded.
Mon Jan 13 15:33:30 2025 daemon.info pppd[18723]: PPPoE plugin from pppd 2.4.9
Mon Jan 13 15:33:30 2025 daemon.notice pppd[18723]: pppd 2.4.9 started by root, uid 0
Mon Jan 13 15:33:30 2025 daemon.info pppd[18723]: PPP session is 5768
Mon Jan 13 15:33:30 2025 daemon.warn pppd[18723]: Connected to xx:xx:xx:xx:xx:a3 via interface wan
Mon Jan 13 15:33:30 2025 kern.info kernel: [ 9323.572089] pppoe-wan: renamed from ppp0
Mon Jan 13 15:33:30 2025 daemon.info pppd[18723]: Renamed interface ppp0 to pppoe-wan
Mon Jan 13 15:33:30 2025 daemon.info pppd[18723]: Using interface pppoe-wan
Mon Jan 13 15:33:30 2025 daemon.notice pppd[18723]: Connect: pppoe-wan <--> wan
Mon Jan 13 15:33:33 2025 daemon.notice pppd[18723]: PAP authentication succeeded
Mon Jan 13 15:33:33 2025 daemon.notice pppd[18723]: peer from calling number xx:xx:xx:xx:xx:xx authorized
Mon Jan 13 15:33:33 2025 daemon.notice pppd[18723]: local  IP address x.x.x.x
Mon Jan 13 15:33:33 2025 daemon.notice pppd[18723]: remote IP address x.x.x.x

Network Config on Flint 2:

config device
	option name 'eth1'
	option macaddr 'x:x:x:x:x:x'

config interface 'wan'
	option device 'eth1'
	option proto 'pppoe'
	option username 'removed'
	option password 'removed'
	option ipv6 '0'

Connection log on Flint 2:

Tue Dec  3 16:49:14 2024 daemon.info pppd[16908]: Plugin pppoe.so loaded.
Tue Dec  3 16:49:14 2024 daemon.info pppd[16908]: PPPoE plugin from pppd 2.5.1
Tue Dec  3 16:49:14 2024 daemon.notice pppd[16908]: pppd 2.5.1 started by root, uid 0
Tue Dec  3 16:49:14 2024 daemon.info pppd[16908]: PPP session is 5399
Tue Dec  3 16:49:14 2024 daemon.warn pppd[16908]: Connected to x:x:x:x:x:x via interface eth1
Tue Dec  3 16:49:14 2024 daemon.info pppd[16908]: Using interface pppoe-wan
Tue Dec  3 16:49:14 2024 daemon.notice pppd[16908]: Connect: pppoe-wan <--> eth1
Tue Dec  3 16:49:15 2024 daemon.err pppd[16908]: PAP authentication failed
Tue Dec  3 16:49:15 2024 daemon.notice pppd[16908]: Modem hangup
Tue Dec  3 16:49:15 2024 daemon.notice pppd[16908]: Connection terminated.
Tue Dec  3 16:49:15 2024 daemon.info pppd[16908]: Sent PADT
Tue Dec  3 16:49:15 2024 daemon.info pppd[16908]: Exit.

Under the Interface page, the error shown is one or the other:

Unknown error (NEGOTIATION_FAILED)
Unknown error (AUTH_TOPEER_FAILED)

I don't know what is wrong. I have tried various suggestions that came up through the topics here:

  1. Set VLAN to 0
  2. Enabled IPV6
  3. Went to latest 4.7.0
  4. Went back to 4.5.3 (which worked for a few)
  5. Went to latest stable build under OpenWRT (without Flint 2 skin on top, same issue)
  6. Currently on 4.7.0-op24 but no luck

PPPOE setup is very idiot proof and been doing it since the last 18 years but this has me pulling my hair out...

YELP! :cry:

2

I am currently following up on this issue via email. If I have any updates, I will reach out to you directly through email.

3

I don't understand what happened or changed but another few resets and it has started working. Nothing was changed in the equation.

4

It is possible the isp uses a lock mechanism, meaning if it detected a different mac address it locks down completely, because it doesn't want two isp routers connected.

There are two different types of those blocks, one can also block both routers for a certain grace period, or only the new router is blocked and mac cloning the mac address from the older can make you unblocked.

Or if you are patience wait until the mechanism has been lifted they're both temporary, but then if you place your old router back it can happen again :slight_smile:

1 Like