Last Modified: Nov 25, 2025
Affected Product(s):
F5OS F5OS-C, Install/Upgrade
Known Affected Versions:
F5OS-C 1.8.0, F5OS-C 1.8.1, F5OS-C 1.8.2
Opened: Jul 30, 2025 Severity: 1-Blocking
When using a non-default internal chassis network range, a VELOS system controller may keep using 100.64.10.0/16 for the IP range for the docker0 network.
Some internal containers running on the system controller will continue to be addressed in 100.64.0.0/16 (RFC6598 address space) rather than the RFC1918 space configured.
This can occur when performing an RMA replacement, or a clean install of a controller via PXE or USB drive.
1. Log into the system controller as root 2. Edit /etc/sysconfig/docker and update the "--bip" parameter in the OPTIONS line. This can be done automatically by running the following commands from a root shell: source /etc/sysconfig/chassis_network_active.txt prefix=${network_prefix:-"100.65"} chassis_id=${chassis_id:-1} first_octet=${network_prefix%%.*} second_octet=${network_prefix##*.} (( second_octet=second_octet - chassis_id )) sed -i.bak -E "s@--bip[ =][0-9]*\.[0-9]*\.@--bip=${first_octet}.${second_octet}.@g" /etc/sysconfig/docker Or all on one line: ( source /etc/sysconfig/chassis_network_active.txt; prefix=${network_prefix:-"100.65"}; chassis_id=${chassis_id:-1}; first_octet=${network_prefix%%.*}; second_octet=${network_prefix##*.}; (( second_octet=second_octet - chassis_id )); sed -i.bak -E "s@--bip[ =][0-9]*\.[0-9]*\.@--bip=${first_octet}.${second_octet}.@g" /etc/sysconfig/docker ) 3. Reboot the system controller.
None