mirrors/haproxy
1
0
Fork 0
mirror of https://git.haproxy.org/git/haproxy.git/ synced 2025-09-20 21:31:28 +02:00
Code Issues Projects Releases Wiki Activity

DOC: Clarify IPv4 address / mask notation rules

Browse Source 
Adds some examples regarding shorthand IPv4 address notation which might
be confused with RFC 4632 CIDR notation, leading to different than
expected results.
This commit is contained in:
Daniel Schneller 2016-04-13 00:26:52 +02:00 committed by Willy Tarreau
parent 39cec29244
commit eba5634f2c
1 changed files with 15 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
doc/configuration.txt
View File

@ -11473,6 +11473,21 @@ at least ensure that they are present in /etc/hosts so that the configuration
does not depend on any random DNS match at the moment the configuration is
parsed.
The dotted IPv4 address notation is supported in both regular as well as the
abbreviated form with all-0-octets omitted:
+------------------+------------------+------------------+
| Example 1 | Example 2 | Example 3 |
+------------------+------------------+------------------+
| 192.168.0.1 | 10.0.0.12 | 127.0.0.1 |
| 192.168.1 | 10.12 | 127.1 |
| 192.168.0.1/22 | 10.0.0.12/8 | 127.0.0.1/8 |
| 192.168.1/22 | 10.12/8 | 127.1/8 |
+------------------+------------------+------------------+
Notice that this is different from RFC 4632 CIDR address notation in which
192.168.42/24 would be equivalent to 192.168.42.0/24.
IPv6 may be entered in their usual form, with or without a netmask appended.
Only bit counts are accepted for IPv6 netmasks. In order to avoid any risk of
trouble with randomly resolved IP addresses, host names are never allowed in