Since upgrade from early 13.2-STABLE to 13.3-STABLE/amd64 the following regression affects my mpd5/L2TP client installation using verified mpd5 configuration: after successfull L2TP connection ifconfig ng0 shows: ng0: flags=88d1<UP,POINTOPOINT,RUNNING,NOARP,SIMPLEX,MULTICAST> metric 0 mtu 576 inet 0.0.0.0 --> 255.255.255.255 netmask 0xff000000 inet 192.168.71.82 --> 192.168.71.81 netmask 0xffffffff Note extra "inet 0.0.0.0" line that does not appear with FreeBSD 13.2. This is not cosmetic problem as it somehow corrupts routing lookup results in some cases. A work-around: "ifconfig ng0 0.0.0.0/8 -alias" added to up-script of mpd5. This command fixes routing lookups. The problem may be related to the following MFC: https://cgit.freebsd.org/src/commit/?h=stable/13&id=ec4ae38566569bfac4e18e1fb2ce61fec1e2361b
The system is a virtual machine that has in /etc/rc.conf: ifconfig_DEFAULT="SYNCDHCP" This was intended to work with em0 or vtnet0 or any other supported kind of emulated NIC. Unfortunately, in stable/13 this setting messes with non-broadcast interfaces, too. This is already fixed in recent branches AFAIR. I've just replaced ifconfig_DEFAULT="SYNCDHCP" with multiple lines in 13.3: ifconfig_em0="SYNCDHCP" ifconfig_vtnet0="SYNCDHCP" ...