Ben Evans - 2024-07-07

Hi, after some tweaking was able to setup mpd5 and much happier with cpu usage compared to pppd but have a minor issue.

When the pppoe interface is created with the ipv6cp option it assigns the ipv6 link-local address as fe80::1 instead of a eui-64 based on the physical interface's mac which I'd prefer as it's used by dhcpcd to negotiate a global address.

I'm aware you can run a script to change the address after the interface is up but feels more fragile and it appears to be possible to use an eui-64 since an opnsense user obtained one without meaning to: https://forum.opnsense.org/index.php?topic=26335.0 (but unfortunately didn't share their config).

The ipv6cp layer page states there aren't any options available and I haven't been able to find any other references to link-local addresses in the docs, is it possible it has something to do with the ISP which explains why some get ::1 assigned by default and others don't?

Ultimately doesn't matter that much and I can find a work around but thought I'd ask here and included my mpd.conf below, thanks!

~~~
default:

    create bundle static wan
    set bundle enable ipv6cp
    set iface name ppp0
    set iface route default
    set ipcp ranges 0.0.0.0/0 0.0.0.0/0

    create link static L1 pppoe
    set auth authname fakeusername
    set auth password correcthorsebatterystapler
    set link action bundle wan
    set link max-redial 0
    set link mtu 1500
    set link keep-alive 10 60
    set pppoe iface bge0
    set pppoe service ""
    set pppoe max-payload 1500
    open