bisdn/meta-switch

meta-switch's Issues

systemd: 99-enp.network ineffective due to systemd-conf's 80-wired.conf taking precedence

The switch from Yocto warrior to Yocto dunfell brought in a default wired config /lib/systemd/networkd/80-wired.network, which configures DHCP on all interfaces starting with eth and en.

Since 80 is lower number than 99, it matches first, and thus always takes precedence before our 99-enp.network, preventing any intended management interface config from being applied.

Installer: log rootfs being written

Writing the root file system takes longer than any other step during the installation, but in the log it is not present at all and to the casual observer it looks like the system hangs for (depending on the platform) up to 3 minutes after "Writing superblocks and filesystem accounting information: done".

Preserve /home directory across OS upgrades

It seems unlikely that a NOS user would want an operating system upgrade to blow away the content of /home for them. For instance, it can be a rather unpleasant surprise if the home directories of their additional users (already preserved in /etc/passwd etc.) are suddenly gone.

There is a risk that the combined size of /home becomes too big for our backup/restore procedure. Something to consider.

Dead symlink in /var/log/README

On boot, the file /var/log/README is created automatically by systemd as part of the 'legacy files'.

As we don't include systemd-doc, this symlink is broken.

The file causing this is tmpfiles.d/legacy.conf from the systemd repo.

This is an upstream issue, which has been patched in Yocto >4.2 openembedded/openembedded-core@18d46e1 however, this change may itself be a problem.
It isn't clear to me whether that would stop systemd creating log directories at runtime in /var/log, or if it is limited to install time.

Another approach I have seen is: openembedded/openembedded-core@ac4c9f5#diff-17f6e12c28058e9bcbaddfa8ea71f60a3e16ca4b5e9a08bc67947f3ad9f7b575 which disables the legacy files creation.

Have onie-bisdn-upgrade warn about file loss

When run without -d, onie-bisdn-upgrade offers this warning:

Upgrading BISDN Linux to install-source: <URL> using Client-IP-cfg: dhcp! Please confirm system reboot: [y/N]

The reboot should be rather obvious when installing a new operating system. However, upgrading BISDN Linux will preserve files only if they are listed in /var/lib/opkg/info/*.conffiles or /etc/default/{system,user}-backup.txt. [1]
This is what onie-bisdn-upgrade should warn about.

[1] https://docs.bisdn.de/getting_started/install_bisdn_linux.html#backup-filesfolders-across-installations

Better error message for onie-bisdn-upgrade as non-root

$ onie-bisdn-upgrade -y http://repo.bisdn.de/pub/onie/accton-as4610/onie-bisdn-accton-as4610-v4.8.2.bin enp0
Configuration file wrong or corrupted
$ cat /etc/fw_env.config
# MTD device name       Device offset   Env. size       Flash sector size
/dev/mtd2               0x00000000      0x00002000         0x00010000

This is a vanilla install from the 4.8.1 image.

port 50051 is open on data ports

The ofdpa-grpc server listens on port 50051, and this port is open on BOTH managment ports (named en**) and data ports (named port**).

This is a security issue, and port 50051 should be closed on all ports except managment ports.