Date: Thu, 15 Feb 2024 15:48:09 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 277063] [ARP] ignores permanent entries after upgrade to 14.0 Message-ID: <bug-277063-7501-QpfHf1C0qQ@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-277063-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-277063-7501@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D277063 --- Comment #6 from Marek Zarychta <zarychtam@plan-b.pwste.edu.pl> --- Please let me put my two cents in.=20 I confirm this regression, but it's not 100% reproducible. I noticed two fa= cts after the upgrade from 13.2-STABLE to 14.0-STABLE: 1. Messages like "arp: 00:aa:bb:cc:dd:ee trying to modify permanent entry f= or w.x.y.z on vlanQ" disappeared from Syslog even though the net.link.ether.inet.log_arp_permanent_modify parameter is set to 1. 2. When traffic from an IP address protected by a static ARP entry is recei= ved from a spoofed host with the same IP address that violates this policy, the= ARP entry for that IP address looks a bit strange: ? (w.x.y.z) at aa:bb:cc:dd:00:11 on vlan2 expires in -1708011502 seconds [vlan], but when the bogus traffic stops, the entry looks as expected ? (w.x.y.z.) at aa:bb:cc:dd:00:11 on vlan2 permanent [vlan]. --=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-277063-7501-QpfHf1C0qQ>