It does start at your router / dhcp… to endpoint which is your server. - my light for you would be if your ISP support ipv6, enable it on your dhcp/router/modem and pass thru and then enable this within virtualmin… recheck configuration to see if virtualmin can see ipv6 and if so, set your dns settings with it and I not see why you cannot be wrong with this setup.
Virtualmin doesn’t care how you configure your network. It’s completely out of scope for Virtualmin. You just may need to tell Virtualmin which IPs to use for what, if it can’t detect it correctly (or if it changes regularly). But, Virtualmin is not a tool for configuring your network, generally speaking.
Webmin has a Network Configuration module, which works with most of the commonly used network configuration systems on Linux (or, it did until relatively recently…these days, it doesn’t know about systemd-networkd, and has probably what I’d call beta support for netplan). You didn’t mention your distro/version, so I can’t even begin to guess what configuration tools you’re using.
I appreciate that a LOT. I do not WANT virtualmin to care how I configure my network.
I do want it to incorporate into my network however.
I think I’ve found some clues to what is strange for me. I’ll start at the end and go backwards:
My ens18 ethernet interface is active in network config, but is not listed in the boot time info??!! I have no idea how that happens. Perhaps a question missed during initial install?
When I tried to add it as a boot time interface, suddenly more became clear: in adding a new interface, I’m asked about obtaining the IP via DHCP etc.
I do not recall ever seeing that question before… and
Until I attempted to add this boot-time interface definition, the words “DHCP client” never showed up. In fact, it’s essentially invisible in the GUI and the documentation and all searches. (Suggestion: perhaps there should be a way to copy an “active” interface to the “boot” tab… and also to edit such things as whether an interface obtains its IP via DHCP? And also to hint at this in documentation?)
I’m about to reboot, which hopefully will result in a proper config of the interface. It would be nice if I could config it without reboot but that’s how the cookie crumbles.
(I’m on Debian 10 as you can see below) I see some related packages in a semi-installed (??) state, perhaps because no DHCP is/was connected to my interface?)
DHCP is NOT found in Bootup/Shutdown process-service list
DHCP IS found if I search under Installed Packages:
dnsmasq-base 2.80-1+deb10u1 A-E Small caching DNS proxy and DHCP/TFTP server
isc-dhcp-client 4.4.1-2+deb10u1 F-J DHCP client for automatically obtaining an IP address
isc-dhcp-common 4.4.1-2+deb10u1 F-J common manpages relevant to all of the isc-dhcp packages
All of these show up as: installation status: unknown; files: are present and ok
All of these have an “uninstall” button available, so presumably installed
OK. Time to reboot and see what happens!
Operating system Debian Linux 10 Webmin version 1.990 Usermin version 1.834 Virtualmin version 6.17-3 Authentic theme version 19.85.1
Kind of with Alma8x i did have to, sorry i changed some after then manual in a config file but don’t remember which one, then it worked.
But the not activated at boot, if done some in the GUI from Virtualmin also not knowing which one or that was a cause at all causes this. Because i only did see it later at a reboot.
I didn’t post it while thought it was a “problem” i was responsible for myself.
But have see this now 2 times here in Forum, so maybe a kind of howto / help here needed, of if someone finds out how to reproduce it.
For this in GUI “from Network discovery” and “iface ens18 inet6 manual” i think that was correct behaviour, while “from Network discovery” is not the same as DHCP , only if DHCP then is really enabled it works to see a adress. It was for IPV6 on manual