summaryrefslogtreecommitdiff
path: root/UPDATING
diff options
context:
space:
mode:
authorSteven Hartland <smh@FreeBSD.org>2017-03-31 09:10:05 +0000
committerSteven Hartland <smh@FreeBSD.org>2017-03-31 09:10:05 +0000
commit4d806fc663c9263b7d069c39d22e0d54958d0b2d (patch)
tree291fffa128f7ea58565ad4daed802a3b90dbf1ce /UPDATING
parent0642eac4377a9fcee365e2e532c2111f1b071f8f (diff)
downloadsrc-test2-4d806fc663c9263b7d069c39d22e0d54958d0b2d.tar.gz
src-test2-4d806fc663c9263b7d069c39d22e0d54958d0b2d.zip
Allow explicitly assigned IPv6 loopback address to be used in jails
If a jail has an explicitly assigned IPv6 loopback address then allow it to be used instead of remapping requests for the loopback adddress to the first IPv6 address assigned to the jail. This fixes issues where applications attempt to detect their bound port where they requested a loopback address, which was available, but instead the kernel remapped it to the jails first address. This is the same fix applied to IPv4 fix by: r316313 Also: * Correct the description of prison_check_ip6_locked to match the code. MFC after: 2 weeks Relnotes: Yes Sponsored by: Multiplay
Notes
Notes: svn path=/head/; revision=316328
Diffstat (limited to 'UPDATING')
-rw-r--r--UPDATING4
1 files changed, 2 insertions, 2 deletions
diff --git a/UPDATING b/UPDATING
index 529ea1f8da8e..a5f9048f6a6d 100644
--- a/UPDATING
+++ b/UPDATING
@@ -52,9 +52,9 @@ NOTE TO PEOPLE WHO THINK THAT FreeBSD 12.x IS SLOW:
****************************** SPECIAL WARNING: ******************************
20170331:
- Binds and sends to the IPv4 loopback address (127.0.0.1) will now
+ Binds and sends to the loopback addresses, IPv6 and IPv4, will now
use any explicitly assigned loopback address available in the jail
- instead of using the first assigned IPv4 address of the jail.
+ instead of using the first assigned address of the jail.
20170329:
The ctl.ko module no longer implements the iSCSI target frontend: