"30-enp1s0" = {
        matchConfig.Name = "enp1s0";
        # Allow baby jumbo frames to theoretically allow
        # PPP-encapsulated packets with 1500 Bytes payload
        # to pass through here.
        linkConfig.MTUBytes = "1512";
        address = [
          "192.168.1.2/24"
        ];
      };

      "30-enp1s0" = {
        matchConfig.Name = "enp1s0";
        # Allow baby jumbo frames to theoretically allow
        # PPP-encapsulated packets with 1500 Bytes payload
        # to pass through here.
        linkConfig.MTUBytes = "1512";
        address = [
          "192.168.1.2/24"
        ];
      };

the current state is that pppd succeeds and networkd considers the resulting device to have a carrier:

Dec 20 12:04:39 bpi-r4 pppd[2265]: Connect: ppp-wan <--> wan
Dec 20 12:04:39 bpi-r4 systemd-timesyncd[430]: Network configuration changed, trying to establish connection.
Dec 20 12:04:39 bpi-r4 systemd-networkd[471]: ppp-wan: Configuring with /etc/systemd/network/10-ppp-wan.network.
Dec 20 12:04:39 bpi-r4 systemd-networkd[471]: ppp-wan: Link UP
Dec 20 12:04:39 bpi-r4 systemd-networkd[471]: ppp-wan: Gained carrier

but it remains in the configuring state

19 ppp-wan ppp      carrier     configuring

and doesn't get any address

17: ppp-wan: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 3
    link/ppp

(that's after I manually networkctl up wan and with

  systemd.network.networks."10-ppp-wan" = {
    matchConfig.Name = "ppp-wan";
    networkConfig.KeepConfiguration = true;
    linkConfig.RequiredForOnline = "routable";
  };

for the created interface)

hello from another account, so im running ifstate to setup the network on my BPI-R4 and im running into a very weird, uh, bug? i genuinely don't know what's happening. When ifstate runs for the first time it does some processing and then eventually runs the following command:

/nix/store/gwx71g0s855x2ln1l17c720mh0rvvr3c-ethtool-6.14/bin/ethtool --change end2 autoneg off duplex full speed 1000

which fails with

netlink error: link settings update failed
netlink error: Invalid argument

which is weird, but then if i run ifstate again, it works, if i run that ethtool command in a shell, it works. It just doesnt work when ifstate is doing it during boot up. Is there some way to get more out of the kernel than "invalid argument"? because that is not descriptive enough

ah, progress:

Jun 13 16:08:26 hela kernel: sfp sfp1: Unable to ascertain link mode
Jun 13 16:08:26 hela kernel: mtk_soc_eth 15100000.ethernet end2: selection of interface failed, advertisement 0000000,00000000,00000000,00000000