Date: Thu, 14 Mar 2024 10:07:43 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 277687] [regression] IPv4 link-level problem with ng(4) Message-ID: <bug-277687-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D277687 Bug ID: 277687 Summary: [regression] IPv4 link-level problem with ng(4) Product: Base System Version: 13.3-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: eugen@freebsd.org CC: melifaro@FreeBSD.org 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=3D88d1<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=3Dstable/13&id=3Dec4ae38566569bfac4e= 18e1fb2ce61fec1e2361b --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-277687-227>