The IPv4 or IPv6 address ranges used by the applications can be configured freely as long as the IP address range is private. The EdgeOS checks the IP address field and displays a warning if it is not a valid private address range. The gateway is automatically assigned the first address in the range, that is, xxx.xxx.xxx.1. Note: the device does not check address collisions on the local network when there are IP networks already in use.

 

NOTICE
Avoiding changing the container runtime IP address range

As long as there is no IP address range conflict between the container runtime and the local network, it is highly recommended to keep the default settings and not to change the IP range of the container runtime.

 

Valid private IPv4 address ranges:

Class

IP range start

IP range end

Subnet mask (bits)

Class A

10.0.0.0

10.255.255.255

8

Class B

172.16.0.0

172.31.255.255

12

Class C

192.168.0.0

192.168.255.255

16

Valid private Ipv6 address ranges:

Address space

RFC 4193 block

Subnet mask (bits)

Unique local address (ULA)

fd00::/8

64