Hi,
I do a lot of testing on firewall deployment, and configurtions in a virtual environment.
23.1_6 does not have this issue, however, both 23.1.11_1 and 23.7 have this issue.
If I disable DHCPv6 on WAN interface, shutdown the firewall, export to OVF or OVA for import elsewhere, then import it, then change the LAN interface IP address, the LAN page is inaccessible.
Of note is that when changing LAN IP address it asks for DHCPv6 on WAN even though its disabled, it does not do this in 23.1_6.
Anyone knows of a solution/fix for this, tried many way to search but could not find.
Quote from: tryllz on August 08, 2023, 10:44:23 AM
then change the LAN interface IP address
Which? IPv6 or IPv4? By default, the LAN interface is tracking the WAN (it generates its IPv6 address based on the prefix the WAN acquires via DHCPv6). If you disable the DHCPv6 client, you should set the LAN to static IPv6 (or none).
Cheers
Maurice
I'm not using IPv6, so I disabled it completely.
IPv4 Is set as static, but once changed (in my case I'm changing it from 192.168.3.10 to 192.168.9.21) the LAN is inaccessible because WAN IPv6 (shows as disabled in the Web-UI) but remains enabled in the CLI.
When the firewall VM is rebooted and IPv4 address is attempted to change and it does not prompt for DHCPv6 LAN is accessible with the new IP address.
Boot fresh 23.7 VM, access Web GUI via 192.168.1.1, cancel wizard. Set LAN IPv6 configuration type to 'none', save. Set WAN IPv6 configuration type to 'none', save and apply. Shutdown VM.
Boot VM, access Web GUI via 192.168.1.1. Set LAN IPv4 address to 10.10.10.1/24, save. Adjust DHCPv4 server range to 10.10.10.100-10.10.10.199, save. Apply LAN address change. Release / renew DHCPv4 lease on client. Access Web GUI via 10.10.10.1.
Works fine. Anything significantly different in your workflow?