Pppd: CHAP authentication failed: invalid_mac

Installing and Using OpenWrt
1

Hello, I'm using OpenWRT v23.05.3 in a Proxmox VM and I can't connect with PPPoE, I keep getting "CHAP authentication failed: invalid_mac"

My Proxmox networking:

Screenshot from 2024-07-01 10-58-43
Screenshot from 2024-07-01 10-58-431453×134 14.2 KB

VM Networking

/etc/config/network: https://paste.centos.org/view/764ac03b

Log: https://paste.centos.org/view/0d51acdd.

I have already tried using my last routers MAC address with no luck, but I don't think it's that because I asked on discord and was mentioned https://en.m.wikipedia.org/wiki/Message_authentication_code

What should I do to troubleshoot?

2

boot openwrt on bare metal, get it to work there, then clone the config.

3

I don't know if it makes any difference, but I have already tried passing through my NIC to the VM (and I got the same error). Booting on bare metal is a bit of an inconvenience, but I'll try with a spare Raspberry Pi 4 I have.

4

The same thing happens on bare metal too! I ran pppoeconf on a Raspberry Pi 4 and got the same problem:

Jul 01 21:42:35 raspberrypi pppd[638]: PPP session is 21847
Jul 01 21:42:35 raspberrypi pppd[638]: Connected to xx:xx:xx:xx:xx:xx via interface eth0
Jul 01 21:42:35 raspberrypi pppd[638]: Using interface ppp0
Jul 01 21:42:35 raspberrypi pppd[638]: Connect: ppp0 <--> eth0
Jul 01 21:42:45 raspberrypi pppd[638]: CHAP authentication failed: invalid_mac
Jul 01 21:42:45 raspberrypi pppd[638]: CHAP authentication failed
Jul 01 21:42:45 raspberrypi pppd[638]: Connection terminated.

So it's definitely something weird with how my ISP handles things. A Tp-Link router from 2014 connects just fine (with minimal configuration) while both a Proxmox VM and a Raspberry Pi 4 get the same error :confused:

5

Okkk, so I found out that:
1- I'm an idiot
2- I'm definitely an idiot
3- I'm probably the stupidest person on this planet
4- The MAC address printed on the back of my old router is being used for LAN, while it uses the same MAC address incremented by 1 for WAN. So, using the WAN address fixed everything

6

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.