So what should I check to troubleshoot this further? The dummy0 interface is created and up:
[root@phabricator ~]# ifconfig
dummy0: flags=195<UP,BROADCAST,RUNNING,NOARP> mtu 1500
inet 192.168.5.1 netmask 255.255.255.0 broadcast 192.168.5.255
inet6 fe80::c4fa:9cff:fe49:2614 prefixlen 64 scopeid 0x20<link>
ether c6:fa:9c:49:26:14 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 3 bytes 210 (210.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
(others deleted)
The system’s been rebooted (more than once). The nic-info script, as already established, doesn’t need to be patched. But the interface doesn’t show in the web GUI:
Or is there a different “best practice” to accomplish this?
Edit: kind of frustrating is that I have another Neth server, with the same VPS host, where I’m pretty sure I followed identical instructions, and the dummy interface appears in the GUI. The nic-info scripts are identical (same md5sum) between the two, and as far as I can tell, the ifcfg-dummy0 files differ only in the assigned IP addresses.
Edit 2: Well, when the GUI fails, try the CLI. db networks set dummy0 ethernet ipaddr=whatever netmask=whatever role green && db networks setprop eth0 role red && signal-event interface-update. It works, and now dummy0 shows up in the GUI (both on the dashboard and on the Network page). Kind of scratching my head as to why, but… Attempted comparison between the working and the non-working system isn’t finding any differences. It might (but shouldn’t) be relevant to note that the working system started with Neth 7.4 and was upgraded to 7.5, while the non-working system started with 7.5.