2.5.1: new VM install, a few UI glitches and bugs?
-
I'm in the process of setting up two VMs in proxmox that will be configured as a CARP cluster eventually. While setting both up with a new(!) 2.5.1 ISO and doing the general setup I was quite confused to find a few webUI glitches(?) and bugs that I didn't notice before:
-
I have multiWAN with two AVM boxes up front. Those FritzBoxes are a cable and a DSL line. Both VMs have them as upstream gateways configured exactly the same. That's fine.
Both have static IP4s (.11/.12) in both transfer networks and get an IP6 via DHCP6 as those ISPs only have dynamic prefixes. That works, too, both VMs get both DHCP6 IPs and gateways.
BUT: although both VMs have the cable box selected as default IP4 AND IP6 gateway, the GW list above shows the "globe" icon (for default GW) behind the correct IP4 GW but the wrong(!) IP6 GW. Look here:
That is the same behavior on both VMs. I checked both via console and SSH, the default GW is indeed the WAN_VF_DHCP6 (routing table clearly shows that) but the icon is displayed behind the wrong v6 gateway and irritates me when looking things over.
-
Although both VMs were set up from the same ISO and the exact same steps were taken in configuring them, both show a different screen in "System / General Setup". The first VM is missing the dropdown boxes behind the DNS IP and DNS Name form fields, the second one has them on display. The config.xml on both boxes has the necessary XML entries in place:
VM 1:
VM2:
Especially the second bug is nagging me, as I don't understand how that could have happened and why one VM doesn't show the gateway dropdowns while the other does.
Any clues?
Cheers
\jens -
-
-
Something in the RA process must be triggering it to take the other gateway as default. That is somewhat moot though since you can't use DHCP/dynamic interfaces with HA if that's your ultimate goal. There isn't a way to make that work as-is, so you may have to forego IPv6 if you want these in HA or find a way to make it work static.
-
The gateway drop-down only shows up if it detects multi-WAN (e.g. multiple interfaces have gateways). If it doesn't show, then the only available gateway must be on a single interface. For static IPv4 perhaps you forgot to select the gateway on Interfaces > WAN for example.
-
-
@jimp said in 2.5.1: new VM install, a few UI glitches and bugs?:
- Something in the RA process must be triggering it to take the other gateway as default. That is somewhat moot though since you can't use DHCP/dynamic interfaces with HA if that's your ultimate goal. There isn't a way to make that work as-is, so you may have to forego IPv6 if you want these in HA or find a way to make it work static.
I don't exactly plan to utilize them in a HA style setup (not the v6 part). But I find it strange, that it shows the 2nd IP6 as default with the globe, the system itself, the default route and everything (even a ping6, traceroute6 etc.) all default to the 1st WAN IP6 and are going out the WAN IF. So it seems that it's a displaying issue rather then RA or do I miss something?
- The gateway drop-down only shows up if it detects multi-WAN (e.g. multiple interfaces have gateways). If it doesn't show, then the only available gateway must be on a single interface. For static IPv4 perhaps you forgot to select the gateway on Interfaces > WAN for example.
Interestingly you were right. I set up both WANs with their Gateways and configured the upstream. At some point one VM seems to have dropped it. I can see that in the config history but not why it happened. I reconfigured the WAN with missing gateway and the dropdown now shows as it should be. Weird though, that it was in (even shown in the config.xml) but somehow was dropped by something.