summaryrefslogtreecommitdiff
path: root/UPDATING
diff options
context:
space:
mode:
authorSteven Hartland <smh@FreeBSD.org>2017-03-31 00:41:54 +0000
committerSteven Hartland <smh@FreeBSD.org>2017-03-31 00:41:54 +0000
commit6ebc1b7b7d632e5c7ea58d93f15946a1403dc0cd (patch)
tree75278a69014844447b562c1e862c45c1e717ea6a /UPDATING
parent39b7ca4533a5cbdb182b0388955d4c7d37a74ab8 (diff)
downloadsrc-test-6ebc1b7b7d632e5c7ea58d93f15946a1403dc0cd.tar.gz
src-test-6ebc1b7b7d632e5c7ea58d93f15946a1403dc0cd.zip
Allow explicitly assigned IPv4 loopback address to be used in jails
If a jail has an explicitly assigned loopback address then allow it to be used instead of remapping requests for the loopback adddress to the first IPv4 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. A example of this is binding nginx to 127.0.0.1 and then running "service nginx upgrade" which before this change would cause nginx to fail. Also: * Correct the description of prison_check_ip4_locked to match the code. MFC after: 2 weeks Relnotes: Yes Sponsored by: Multiplay
Notes
Notes: svn path=/head/; revision=316313
Diffstat (limited to 'UPDATING')
-rw-r--r--UPDATING5
1 files changed, 5 insertions, 0 deletions
diff --git a/UPDATING b/UPDATING
index 1f5a7676e0813..529ea1f8da8e2 100644
--- a/UPDATING
+++ b/UPDATING
@@ -51,6 +51,11 @@ 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
+ use any explicitly assigned loopback address available in the jail
+ instead of using the first assigned IPv4 address of the jail.
+
20170329:
The ctl.ko module no longer implements the iSCSI target frontend:
cfiscsi.ko does instead.