https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=292807
--- Comment #5 from Marek Zarychta <[email protected]> --- In the past, back in the days of FreeBSD 11 and possibly even 12, it was possible for a jail to communicate with the host when a service was running on the host and bound to the loopback interface at 127.0.0.1, provided that nothing inside the jail was listening on that port. AFAIR, this functionality never worked for IPv6. Nowadays, such communication is no longer possible even for IPv4, at least with the pf.ko module loaded. In order for a jail to access a service running on the host, the service must be bound to an address other than 127.0.0.1. I am not sure whether this should be considered a bug or even a regression. I am also not sure whether it is relevant in this context, but such functionality never existed for IPv6 anyway - in that case, an additional IPv6 address on the host’s loopback interface was always required for jail <=> host communication. This behaviour is somewhat consistent with other network operating systems, where components communicating within the same stack usually use addresses from the 127.0.0.0/8 range, but not 127.0.0.1 or ::1. -- You are receiving this mail because: You are the assignee for the bug.
