Hi
I have a centos stream 9 installation
I have set a firewall front and assigned a virtual public IP example 9.9.9.9 and fw ip 9.9.1.1
I have added a virtual internal LAN vswitch with ip example 10.0.0.10 and from there all routed to firewall as outgoing, there is no actual public IPv4
Routing all fine but displayed DA as server IP the firewall main IP 9.9.1.1 instead the virtual , for some reason that I cant understand
Please note here if perform curl api.ipify.org display virtual IP not fw IP correct
When I executed
cd /usr/local/directadmin/scripts
./ipswap.sh 9.9.1.1 9.9.9.9
messed up all the routing configuration, and I had to redo it from scratch.
Now its working as I want and displayed the virtual ip correct and not fw
My main concern is how to avoid any autorun and destroy all routes again as in panel displayed as server IP 9.9.9.9 and second IP 10.0.0.10 as has to be
In ifconfig the actual server IP display only the 10.0.0.10 and not displayed the fw virtual ip 9.9.9.9
Is there any possibility of doing that in an upgrade of DA to see different ip configuration and run any automate script to fix ?
As you know Hetzner cloud is <<bizzare>> a little bit and in internal routing how performed with vswitch as DHCP controlled by vswitch only
I have a centos stream 9 installation
I have set a firewall front and assigned a virtual public IP example 9.9.9.9 and fw ip 9.9.1.1
I have added a virtual internal LAN vswitch with ip example 10.0.0.10 and from there all routed to firewall as outgoing, there is no actual public IPv4
Routing all fine but displayed DA as server IP the firewall main IP 9.9.1.1 instead the virtual , for some reason that I cant understand
Please note here if perform curl api.ipify.org display virtual IP not fw IP correct
When I executed
cd /usr/local/directadmin/scripts
./ipswap.sh 9.9.1.1 9.9.9.9
messed up all the routing configuration, and I had to redo it from scratch.
Now its working as I want and displayed the virtual ip correct and not fw
My main concern is how to avoid any autorun and destroy all routes again as in panel displayed as server IP 9.9.9.9 and second IP 10.0.0.10 as has to be
In ifconfig the actual server IP display only the 10.0.0.10 and not displayed the fw virtual ip 9.9.9.9
Is there any possibility of doing that in an upgrade of DA to see different ip configuration and run any automate script to fix ?
As you know Hetzner cloud is <<bizzare>> a little bit and in internal routing how performed with vswitch as DHCP controlled by vswitch only
Last edited: