Brume 2 - PPPOE Chap Error

Hello!

I have finally received my awaited BRUME 2, however the first few hours have not been the best! :expressionless:

I have FTTP (Fibre ONT modem) that currently connects to my existing Amplifi HD Mesh router. This has PPPOE already setup / working fine.

Now I would like to connect BRUME 2 as my main router [ONT MODEM → BRUME 2 → Amplifi HD Router (Bridge Mode)] however connecting to the PPPOE account has been hard work!

At this point i have the existing HD router turned off, and i have only connected the BRUME 2 to the ONT Modem.

  1. I have restarted the ONT multiple times, including Brume 2
  2. I have cloned the existing HD Router MAC and put onto the WAN ETH0 port for the BRUME 2 (NO difference in connection logs)
  3. lost all patience.
  4. The PPPOE account is exactly the same as the existing setup, if i reconnect my OLD router back into the ONT, internet works again (horray).

Logs outputed from BRUME 2 when attempting to setup PPPOE:

Fri Aug 11 08:57:10 2023 daemon.info pppd[7683]: Plugin rp-pppoe.so loaded.
Fri Aug 11 08:57:10 2023 daemon.info pppd[7683]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.8
Fri Aug 11 08:57:10 2023 daemon.notice pppd[7683]: pppd 2.4.8 started by root, uid 0
Fri Aug 11 08:57:10 2023 daemon.info pppd[7683]: PPP session is 635
Fri Aug 11 08:57:10 2023 daemon.warn pppd[7683]: Connected to d8:18:d3:9e:d6:ab via interface eth0
Fri Aug 11 08:57:10 2023 kern.info kernel: [ 48.267617] pppoe-wan: renamed from ppp0
Fri Aug 11 08:57:10 2023 daemon.info pppd[7683]: Renamed interface ppp0 to pppoe-wan
Fri Aug 11 08:57:10 2023 daemon.info pppd[7683]: Using interface pppoe-wan
Fri Aug 11 08:57:10 2023 daemon.notice pppd[7683]: Connect: pppoe-wan ↔ eth0
Fri Aug 11 08:57:11 2023 daemon.info pppd[7683]: CHAP authentication failed: Realm not found in wholesaler
Fri Aug 11 08:57:11 2023 daemon.err pppd[7683]: CHAP authentication failed
Fri Aug 11 08:57:12 2023 daemon.info avahi-daemon[3550]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::9683:c4ff:fe33:####.
Fri Aug 11 08:57:12 2023 daemon.info avahi-daemon[3550]: New relevant interface eth0.IPv6 for mDNS.
Fri Aug 11 08:57:12 2023 daemon.info avahi-daemon[3550]: Registering new address record for fe80::9683:c4ff:fe33:#### on eth0..
Fri Aug 11 08:57:17 2023 daemon.notice pppd[7683]: Connection terminated.
Fri Aug 11 08:57:17 2023 daemon.info pppd[7683]: Sent PADT
Fri Aug 11 08:57:18 2023 daemon.notice pppd[7683]: Modem hangup
Fri Aug 11 08:57:18 2023 daemon.info pppd[7683]: Exit.
Fri Aug 11 08:57:18 2023 daemon.notice netifd: Interface ‘wan’ is now down
Fri Aug 11 08:57:18 2023 kern.info kernel: [ 55.497205] mtk_soc_eth 15100000.ethernet eth0: Link is Down
Fri Aug 11 08:57:18 2023 daemon.info avahi-daemon[3550]: Interface eth0.IPv6 no longer relevant for mDNS.
Fri Aug 11 08:57:18 2023 daemon.info avahi-daemon[3550]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::9683:c4ff:fe33:####.
Fri Aug 11 08:57:18 2023 daemon.info avahi-daemon[3550]: Withdrawing address record for fe80::9683:c4ff:fe33:#### on eth0.
Fri Aug 11 08:57:18 2023 daemon.notice netifd: Interface ‘wan’ is disabled
Fri Aug 11 08:57:18 2023 kern.info kernel: [ 55.509815] mtk_soc_eth 15100000.ethernet eth0: configuring for fixed/2500base-x link mode
Fri Aug 11 08:57:18 2023 kern.info kernel: [ 55.518174] mtk_soc_eth 15100000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
Fri Aug 11 08:57:18 2023 kern.info kernel: [ 55.526926] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Fri Aug 11 08:57:18 2023 daemon.notice netifd: Interface ‘wan’ is enabled
Fri Aug 11 08:57:18 2023 daemon.notice netifd: Interface ‘wan’ is setting up now
Fri Aug 11 08:57:18 2023 daemon.err insmod: module is already loaded - slhc
Fri Aug 11 08:57:18 2023 daemon.err insmod: module is already loaded - ppp_generic
Fri Aug 11 08:57:18 2023 daemon.err insmod: module is already loaded - pppox
Fri Aug 11 08:57:18 2023 daemon.err insmod: module is already loaded - pppoe
Fri Aug 11 08:57:18 2023 daemon.info pppd[8277]: Plugin rp-pppoe.so loaded.
Fri Aug 11 08:57:18 2023 daemon.info pppd[8277]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.8
Fri Aug 11 08:57:18 2023 daemon.notice pppd[8277]: pppd 2.4.8 started by root, uid 0
Fri Aug 11 08:57:19 2023 daemon.info avahi-daemon[3550]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::9683:c4ff:fe33:####.
Fri Aug 11 08:57:19 2023 daemon.info avahi-daemon[3550]: New relevant interface eth0.IPv6 for mDNS.
Fri Aug 11 08:57:19 2023 daemon.info avahi-daemon[3550]: Registering new address record for fe80::9683:c4ff:fe33:#### on eth0.
.
Fri Aug 11 08:57:33 2023 daemon.warn pppd[8277]: Timeout waiting for PADO packets
Fri Aug 11 08:57:33 2023 daemon.err pppd[8277]: Unable to complete PPPoE Discovery
Fri Aug 11 08:57:33 2023 daemon.info pppd[8277]: Exit.

The main line pointing out to me is:

Fri Aug 11 08:57:11 2023 daemon.info pppd[7683]: CHAP authentication failed: Realm not found in wholesaler

However i cannot find much information about it, and to repeat myself the PPPOE Accout and PW is exactly the same as the existing router (That works!).

ie: username@broadband.vodaphone.co.uk

Am i missing anything here?

*DropIn GW in not something i am interested in.

Thanks in advance!!

system info (redacted)

uci show network
network.wan=interface
network.wan.force_link=‘0’
network.wan.ipv6=‘0’
network.wan.password=‘############’
network.wan.disabled=‘0’
network.wan.peerdns=‘1’
network.wan.proto=‘pppoe’
network.wan.device=‘eth0’
network.wan.username=‘username@broadband.vodaphone.co.uk’
network.wan.vlanid=‘0’

uci show system
system.@system[0]=system
system.@system[0].log_size=‘64’
system.@system[0].urandom_seed=‘0’
system.@system[0].hostname=‘GL-MT2500’
system.@system[0].compat_version=‘1.0’
system.@system[0].ttylogin=‘1’
system.@system[0].timezone=‘GMT0BST,M3.5.0/1,M10.5.0’
system.@system[0].zonename=‘Europe/London’
system.@system[0].log_proto=‘udp’
system.@system[0].conloglevel=‘8’
system.@system[0].cronloglevel=‘5’
system.ntp=timeserver

Br

Can you double and triple check you really really entered the same username and password?

Aha trust me i have 10x checked, phone ISP and ensured the account is not locked etc. Normally the chap auth error would be related to incorrect details so im not sure where to go next.

it would help if I spelled “vodafone” and not “vodaphone”… oh the embarrassment!

To be honest, that actually makes sense. Even though the field is username, in this case it actually contains 2 things. Username and realm in the form of [username]@[realm]. Therefore this error in spelling of “vodafone”, did not result in a username/password invalid, but in a “Realm not found” error.

For future people on the internet finding this and having this same error: Check whatever is behind the @ sign of the username field! That part is likely having a typo.