Date: Thu, 21 Feb 2019 21:44:59 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 235927] FreeBSD does not reply to ICMP requests when assigned a Class-E address Message-ID: <bug-235927-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D235927 Bug ID: 235927 Summary: FreeBSD does not reply to ICMP requests when assigned a Class-E address Product: Base System Version: 12.0-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: logan@cyberstorm.mu Created attachment 202244 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D202244&action= =3Dedit FreeBSD icmp class-e fix Due to the shrinkage of the IPv4 space, some people are looking at using Class-E as a way to further expand the range of usable IPv4 addresses. In o= rder to make this happen, an audit is needed for FreeBSD to check for 240.0.0.0/4 assignment. When assigning a class-e ip to FreeBSD-12, it works except for ICMP. Example, when pinging the FreeBSD machine: ping 240.0.1.199 PING 240.0.1.199 (240.0.1.199) 56(84) bytes of data. ^C --- 240.0.1.199 ping statistics --- 6 packets transmitted, 0 received, 100% packet loss, time 5088ms However, SSH is accessible: nc -v 240.0.1.199 22 Connection to 240.0.1.199 22 port [tcp/ssh] succeeded! SSH-2.0-OpenSSH_7.8 FreeBSD-20180909 This attached patch removes the check for experimental/class-e range address and allows ICMP to work. ping 240.0.1.199 PING 240.0.1.199 (240.0.1.199) 56(84) bytes of data. 64 bytes from 240.0.1.199: icmp_seq=3D1 ttl=3D64 time=3D0.664 ms 64 bytes from 240.0.1.199: icmp_seq=3D2 ttl=3D64 time=3D0.860 ms 64 bytes from 240.0.1.199: icmp_seq=3D3 ttl=3D64 time=3D0.740 ms --=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-235927-227>