tabrisnet

above PR is merged

@Igor how often does netplan run? how possible might it be to sneak in a sed -i -e 's/PermanentMACAddress/MACAddress/' /run/systemd/network/* networkctl reload in my bootup sequence? will DHCP [on ethEXT1] or carrier up/down events break this?

https://forum.banana-pi.org/t/bpi-r4-eeprom/17836/13 suggests we should figure out how to give the info to uboot? or it already does generate it for us in one case? I can say I find eth0's local-mac-address in the running device tree, but the other two mac@ entries lack it. root@ratatosk:/boot# dtc /proc/device-tree 2>/dev/null |grep -PA 10 'mac@[0-9] ' mac@2 { phy-mode = "usxgmii"; compatible = "mediatek,eth-mac"; status = "okay"; pcs-handle = <0x3a 0x3b>; managed = "in-band-status"; phys = <0x3c>; reg = <0x02>; openwrt,netdev-name = "sfp-wan"; sfp = <0x3d>; }; -- mac@0 { phy-mode = "internal"; local-mac-address = [22 16 68 60 40 c2]; mac-address = [22 16 68 60 40 c2]; compatible = "mediatek,eth-mac"; status = "okay"; reg = <0x00>; phandle = <0x2c>; fixed-link { full-duplex; -- mac@1 { phy-mode = "usxgmii"; compatible = "mediatek,eth-mac"; status = "okay"; pcs-handle = <0x36 0x37>; managed = "in-band-status"; phys = <0x38>; reg = <0x01>; openwrt,netdev-name = "sfp-lan"; sfp = <0x39>; };

new Ubuntu/netplan bug: https://bugs.launchpad.net/netplan/+bug/2120999

https://github.com/canonical/netplan/pull/278 <-- related netplan PR

maybe not a strictly a systemd bug... but a netplan stupidity. root@ratatosk:~# ethtool --show-permaddr eth1 Permanent address: not set https://github.com/systemd/systemd/pull/14448/files <-- PR that created this systemd match feature

making a copy of the file from /run/, changing the YAML to use MAC, then diff root@ratatosk:~# netplan generate root@ratatosk:~# diff -purN /run/systemd/network/10-netplan-eth1.network /root/netplan-eth1-namematch.network --- /run/systemd/network/10-netplan-eth1.network 2025-08-19 20:10:54.900000038 +0000 +++ /root/netplan-eth1-namematch.network 2025-08-19 20:10:36.980000037 +0000 @@ -1,5 +1,5 @@ [Match] -PermanentMACAddress=6a:c9:72:53:13:d5 +Name=eth1 [Network] EmitLLDP=true feels like a systemD bug ☹️

Ok, so using the match name *does* work, still makes no sense. root@ratatosk:~# head /etc/netplan/20-ethLAN.yaml network: version: 2 renderer: networkd ethernets: eth1: match: #macaddress: '6a:c9:72:53:13:d5' name: eth1 #set-name: ethLAN addresses: [ "192.168.88.253/23" ] root@ratatosk:~# networkctl list IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 eth0 ether degraded unmanaged 3 eth1 ether routable configured 4 eth2 ether off unmanaged 5 wan dsa off unmanaged 6 lan1 dsa routable configured 7 lan2 dsa off unmanaged 8 lan3 dsa off unmanaged 8 links listed.

The eth0/lan1 MAC does change... the eth1/eth2 MACs do not change. I've checked over multiple reboot cycles. 3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 6a:c9:72:53:13:d5 brd ff:ff:ff:ff:ff:ff 4: eth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 32:b0:1b:6f:4e:e9 brd ff:ff:ff:ff:ff:ff root@ratatosk:~# uptime 20:05:19 up 5 min, 1 user, load average: 0.13, 0.39, 0.21 just rebooted, the MACs are stable 🐴 I could try reconfiguring the netplan config to use the name [like with lan1] instead of MAC... but that will of course mean I can't rename.

rules in /etc/udev/rules.d did *nothing*. tried with 00 prefix and 99 prefix. udevadm test-builtin net_setup_link didn't mention the filepath either. But I could make it do stuff with /etc/systemd/network/foo.link, which is what's current[ly not deleted yet from previous attempts]. Which makes it even weirder that it still won't rename at boot. Note that the problem is a lot less the renaming and more that networkd refuses to manage the interfaces, even if I give up on renaming,

BPI-R4, but that is probably the least of my problems. setting up netplan, like the docs say I have to. using networkd, or trying... renaming the eth1 interface to ethLAN, keeping lan1 as-is. networkctl always says that eth1 or ethLAN is unmanaged. Note that I'm using the ttyS0 serial console. root@ratatosk:~# networkctl list IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 eth0 ether degraded unmanaged 3 eth1 ether off unmanaged 4 eth2 ether off unmanaged 5 wan dsa off unmanaged 6 lan1 dsa routable configured 7 lan2 dsa off unmanaged 8 lan3 dsa off unmanaged root@ratatosk:~# netplan apply [ 141.017704] mtk_soc_eth 15100000.ethernet ethLAN: renamed from eth1 [ 141.068835] mtk_soc_eth 15100000.ethernet ethEXT1: renamed from eth2 root@ratatosk:~# networkctl list IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 eth0 ether degraded unmanaged 3 ethLAN ether off unmanaged 4 ethEXT1 ether off unmanaged 5 wan dsa off unmanaged 6 lan1 dsa routable configured 7 lan2 dsa off unmanaged 8 lan3 dsa off unmanaged Here's my config. Note that it does in fact rename the interfaces... albeit not at boot 😑 root@ratatosk:~# cat /etc/netplan/20-ethLAN.yaml network: version: 2 renderer: networkd ethernets: ethLAN: match: macaddress: '6a:c9:72:53:13:d5' #set-name: ethLAN #tried with and without this addresses: [ "192.168.88.253/23" ] emit-lldp: true dhcp4: false dhcp6: false #ignore-carrier: true nameservers: addresses: - 192.168.82.55 search: - tabris.net routes: #- to: 192.168.88.0/23 # metric: 10 # from: 192.168.88.253 # scope: link # type: local - to: "default" via: "192.168.88.254" root@ratatosk:~# cat /etc/netplan/11-lan1.yaml network: version: 2 renderer: networkd ethernets: lan1: match: name: "lan1" addresses: - "192.168.88.250/23" nameservers: addresses: - 192.168.82.55 search: - tabris.net # routes: # - to: "default" # via: "192.168.88.254" note that lan1 works! ethLAN, whether named eth1 or ethLAN... does not. I tried using renderer: NetworkManager It then tries to restart networkd & stop NetworkManager. but it can eventually work... but I have to sacrifice a rubber chicken [stupid manual steps like manually setting the interfaces up with ip link] each time, and they're starting to pile up. it will *not* work at boot no matter what I do.

https://github.com/armbian/build/pull/8517 appears to fix my SFP problems.

I moved the board back to my network core, and swapped the AQS SFP back to the WAN port. then inserted a Fiber SFP+ to the LAN port. by ip link set up dev eth2, I get the network switch to say there's link beat... but ethtool still says no tabris@ratatosk:~$ sudo ethtool eth1 Settings for eth1: Supported ports: [ FIBRE ] Supported link modes: 10000baseSR/Full Supported pause frame use: Symmetric Receive-only Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 10000baseSR/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Speed: Unknown! Duplex: Unknown! (255) Auto-negotiation: on Port: FIBRE PHYAD: 0 Transceiver: internal Current message level: 0x000000ff (255) drv probe link timer ifdown ifup rx_err tx_err Link detected: no tabris@ratatosk:~$ sudo ethtool -m eth1 Identifier : 0x03 (SFP) Extended identifier : 0x04 (GBIC/SFP defined by 2-wire interface ID) Connector : 0x07 (LC) Transceiver codes : 0x10 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 Transceiver type : 10G Ethernet: 10G Base-SR Encoding : 0x06 (64B/66B) BR, Nominal : 10300MBd Rate identifier : 0x00 (unspecified) Length (SMF,km) : 0km Length (SMF) : 0m Length (50um) : 80m Length (62.5um) : 30m Length (Copper) : 0m Length (OM3) : 300m Laser wavelength : 850nm Vendor name : SOURCEPHOTONICS Vendor OUI : 00:1f:22 Vendor PN : SFP-SR Vendor rev : 10 Option values : 0x00 0x1a Option : RX_LOS implemented Option : TX_FAULT implemented Option : TX_DISABLE implemented BR margin, max : 0% BR margin, min : 0% Vendor SN : 201712060269 Date code : 171206 Optical diagnostics support : Yes Laser bias current : 6.426 mA Laser output power : 0.4686 mW / -3.29 dBm Receiver signal average optical power : 0.7100 mW / -1.49 dBm Module temperature : 27.25 degrees C / 81.06 degrees F Module voltage : 3.3160 V Alarm/warning flags implemented : Yes Laser bias current high alarm : Off Laser bias current low alarm : Off Laser bias current high warning : Off Laser bias current low warning : Off Laser output power high alarm : Off Laser output power low alarm : Off Laser output power high warning : Off Laser output power low warning : Off Module temperature high alarm : Off Module temperature low alarm : Off Module temperature high warning : Off Module temperature low warning : Off Module voltage high alarm : Off Module voltage low alarm : Off Module voltage high warning : Off Module voltage low warning : Off Laser rx power high alarm : Off Laser rx power low alarm : Off Laser rx power high warning : Off Laser rx power low warning : Off Laser bias current high alarm threshold : 15.000 mA Laser bias current low alarm threshold : 1.000 mA Laser bias current high warning threshold : 13.000 mA Laser bias current low warning threshold : 2.000 mA Laser output power high alarm threshold : 1.1220 mW / 0.50 dBm Laser output power low alarm threshold : 0.1862 mW / -7.30 dBm Laser output power high warning threshold : 1.0000 mW / 0.00 dBm Laser output power low warning threshold : 0.2344 mW / -6.30 dBm Module temperature high alarm threshold : 80.00 degrees C / 176.00 degrees F Module temperature low alarm threshold : -10.00 degrees C / 14.00 degrees F Module temperature high warning threshold : 75.00 degrees C / 167.00 degrees F Module temperature low warning threshold : -5.00 degrees C / 23.00 degrees F Module voltage high alarm threshold : 3.5999 V Module voltage low alarm threshold : 3.0000 V Module voltage high warning threshold : 3.5000 V Module voltage low warning threshold : 3.0999 V Laser rx power high alarm threshold : 1.1220 mW / 0.50 dBm Laser rx power low alarm threshold : 0.0645 mW / -11.90 dBm Laser rx power high warning threshold : 1.0000 mW / 0.00 dBm Laser rx power low warning threshold : 0.0812 mW / -10.90 dBm tabris@ratatosk:~$ sudo dmesg |egrep 'sfp[12]' [ 7.656413] sfp sfp1: Host maximum power 3.0W [ 7.664987] sfp sfp2: Host maximum power 3.0W [ 7.973441] sfp sfp1: module AQUANTIA AQS-107-B0C2-CX rev 05 sn 174300000001458 dc 171024 [ 7.994274] sfp sfp2: module SOURCEPHOTONICS SFP-SR rev 10 sn 201712060269 dc 171206 [ 723.697583] sfp sfp1: no PHY detected Hopefully this somewhat more normal SFP+ is useful. it's a Macroreer 10GBASE-SR, for HP Procurve. tabris@ratatosk:~$ sudo i2cdump -y 4 0x50 No size specified (using byte-data access) 0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef 00: 03 04 07 10 00 00 00 00 00 00 00 06 67 00 00 00 ????.......?g... 10: 08 03 00 1e 53 4f 55 52 43 45 50 48 4f 54 4f 4e ??.?SOURCEPHOTON 20: 49 43 53 20 00 00 1f 22 53 46 50 2d 53 52 20 20 ICS ..?"SFP-SR 30: 20 20 20 20 20 20 20 20 31 30 20 20 03 52 00 8e 10 ?R.? 40: 00 1a 00 00 32 30 31 37 31 32 30 36 30 32 36 39 .?..201712060269 50: 20 20 20 20 31 37 31 32 30 36 20 20 68 f0 03 ca 171206 h??? 60: 48 50 a0 00 80 50 20 20 4a 39 31 35 30 41 20 31 HP?.?P J9150A 1 70: 39 39 30 2d 34 30 36 35 20 20 00 32 00 00 00 00 990-4065 .2.... 80: 10 31 f1 e3 d6 b5 28 11 23 15 b1 f6 cf 33 34 cc ?1????(?#????34? 90: 1f 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ??.............. a0: 00 00 48 50 20 50 72 6f 43 75 72 76 65 20 50 72 ..HP ProCurve Pr b0: 6f 70 72 69 65 74 61 72 79 20 74 72 61 64 65 20 oprietary trade c0: 73 65 63 72 65 74 20 2d 20 63 6f 70 79 69 6e 67 secret - copying d0: 20 69 73 20 70 72 6f 68 69 62 69 74 65 64 20 77 is prohibited w e0: 69 74 68 6f 75 74 20 70 65 72 6d 69 73 73 69 6f ithout permissio f0: 6e 2e 00 00 00 00 00 00 00 00 00 00 00 00 00 00 n............... tabris@ratatosk:~$ sudo i2cdump -y 4 0x51 No size specified (using byte-data access) 0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef 00: 50 00 f6 00 4b 00 fb 00 8c 9f 75 30 88 b8 79 17 P.?.K.?.??u0??y? 10: 1d 4c 01 f4 19 64 03 e8 2b d4 07 46 27 10 09 28 ?L???d??+??F'??( 20: 2b d4 02 85 27 10 03 2c 00 00 00 00 00 00 00 00 +???'??,........ 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 40: 00 00 00 00 3f 80 00 00 00 00 00 00 01 00 00 00 ....??......?... 50: 01 00 00 00 01 00 00 00 01 00 00 00 00 00 00 55 ?...?...?......U 60: 1b 46 81 71 0c 8d 12 6d 1b bc 00 00 00 00 00 00 ?F?q???m??...... 70: 00 00 00 00 00 00 00 00 00 00 40 00 00 00 00 00 ..........@..... 80: aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa ???????????????? 90: aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa ???????????????? a0: aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa ???????????????? b0: aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa ???????????????? c0: aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa ???????????????? d0: aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa ???????????????? e0: aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa aa ???????????????? f0: aa aa aa aa aa aa aa aa ff ff ff ff ff ff 49 2f ????????......I/

the Aquantia SFP root@ratatosk:~# i2cdetect -y 4 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: 50 51 -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: UU -- -- -- -- -- -- -- root@ratatosk:~# i2cdump -y 4 0x50 No size specified (using byte-data access) 0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef 00: 03 04 22 00 00 00 00 00 00 00 00 00 64 00 00 00 ??".........d... 10: 00 00 1e 00 41 51 55 41 4e 54 49 41 20 20 20 20 ..?.AQUANTIA 20: 20 20 20 20 1c 00 17 b6 41 51 53 2d 31 30 37 2d ?.??AQS-107- 30: 42 30 43 32 2d 43 58 20 30 35 20 20 00 00 00 33 B0C2-CX 05 ...3 40: 28 00 00 00 31 37 34 33 30 30 30 30 30 30 30 31 (...174300000001 50: 34 35 38 20 31 37 31 30 32 34 20 20 00 70 00 18 458 171024 .p.? 60: 03 04 01 60 4e 81 02 00 00 20 20 20 20 20 20 20 ???`N??.. 70: 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ c0: 7f 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ?............... d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ ethtool output root@ratatosk:~# ethtool eth1 Settings for eth1: Supported ports: [ TP ] Supported link modes: 10000baseT/Full Supported pause frame use: Symmetric Receive-only Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 10000baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Speed: Unknown! Duplex: Unknown! (255) Auto-negotiation: on Port: Twisted Pair PHYAD: 0 Transceiver: internal MDI-X: Unknown Current message level: 0x000000ff (255) drv probe link timer ifdown ifup rx_err tx_err Link detected: no root@ratatosk:~# ethtool -m eth1 Identifier : 0x03 (SFP) Extended identifier : 0x04 (GBIC/SFP defined by 2-wire interface ID) Connector : 0x22 (RJ45) Transceiver codes : 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x1c Transceiver type : Extended: 10Gbase-T Short Reach Encoding : 0x00 (unspecified) BR, Nominal : 10000MBd Rate identifier : 0x00 (unspecified) Length (SMF,km) : 0km Length (SMF) : 0m Length (50um) : 0m Length (62.5um) : 0m Length (Copper) : 30m Length (OM3) : 0m Laser wavelength : 0nm Vendor name : AQUANTIA Vendor OUI : 00:17:b6 Vendor PN : AQS-107-B0C2-CX Vendor rev : 05 Option values : 0x28 0x00 Option : Retimer or CDR implemented Option : Power level 3 requirement BR margin, max : 0% BR margin, min : 0% Vendor SN : 174300000001458 Date code : 171024 ethtool says no linkbeat, but the network switch it's connected to says it's up [but no traffic detected] I don't have the DAC plugged in right now, as the workstation i'm using doesn't have any SFP ports available.

I don't think I can take on such a role, but as I do have two of these boards, I can run tests and debug things within my knowledge level [and can run tests as requested]. My specific reason to not want to take on a maintainer role here is I don't know enough of the armbian process nor the board itself. Maybe I can work my way up to it. re tests... e.g. I have a few 10GbE SFP+ I can test: I have an FS.com DAC, an Aquantia [now Marvell] AQS-107-B0C2-CX [both the DAC & the AQS as posted above], and some other SFP+ as well. I haven't built my own linux kernels in a decade plus but I do know how to work with menuconfig et al. to @chainsx I do understand that this needs collaboration. I'm willing to work on it. I just don't know how much I know. I can, e.g., pull i2c data for the SFPs... but I don't know how to read the raw hex data. Point me at docs or forum posts, ask me questions or to do stuff... I'm also on github with the same username.