Date: Fri, 20 Dec 2024 18:43:33 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 283450] ARP problem Message-ID: <bug-283450-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D283450 Bug ID: 283450 Summary: ARP problem Product: Base System Version: 14.2-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: dym@afalina.od.ua Upgrade from 13.4 to 14.2/ Before: # uname -a FreeBSD vpn 13.4-RELEASE-p2 FreeBSD 13.4-RELEASE-p2 3f40d5821 VPN amd64 After: # uname -a FreeBSD vpn 14.2-RELEASE FreeBSD 14.2-RELEASE c8918d6c7 VPN amd64 There was a problem with the mpd5 VPN server: VPN clients can connect and access the VPN server, but cannot access the internal network behind that server. tcpdump shows that only arp requests appear on the VPN server. If I add directive route /32 to the client on the internal machine, access = to the specific internal machine appears. When connecting the client, an error appears in mpd.log: mpd5 system: command "/usr/sbin/arp" returned 256 And from other links I see that it's not mpd5 that's the problem. The following line in the mpd5 config does not work: set iface enable proxy-arp Fresh install FreeBSD 14.2 and fresh install mpd5 lead to the same result. I found this thread: https://forums.freebsd.org/threads/mpd5-vpn-server-clients-cannot-access-se= rvers-lan-usr-sbin-arp-returned-256.94795/ It's certainly an option, but it's a stubby. --=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-283450-227>