I've recently installed Windows Server 2016 as a VM within Proxmox. Everything is working well, other than the internet connection. Every which way I configure this, it still comes back as a unidentified network.
The drivers for the network portion are installed, and I know its a configuration issue with the network settings, but Im unsure where to go from here. Please let me know what information y'all would like me to provide!
Heyo! Which details about my setup? Hardware specifications? Install specifications?
Heres the output of my /etc/network/interfaces
Code:
# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage parts of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT read its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!
auto lo
iface lo inet loopback
iface eno1 inet manual
iface eno2 inet manual
auto vmbr0
iface vmbr0 inet static
address ***.**.**.**/24
gateway ***.**.**.***
bridge-ports eno1
bridge-stp off
bridge-fd 0
hwaddress **:**:**:**:**:**
iface vmbr0 inet6 static
address ****:****:**:****::/64
gateway ****:****:**:****FF:FF:FF:FF:FF
Additionally, here is how the network device is configured in Windows:
Heyo y'all!
I've managed to fix this issue on my lonesome. I'll explain what I've done so people having this issue in the future can reference it.
Since Kimsufi only offers you one IP per server, you must route your networking through iptables. I've followed this guide in regards to this, and it offers configuration for multiple VM's with very understandable steps.
When Proxmox 7 is installed via Kimsufi's panel, it comes preconfigured with the following /etc/networking/inferfaces:
YAML:
auto lo
iface lo inet loopback
iface eno1 inet manual
iface eno2 inet manual
auto vmbr0
iface vmbr0 inet static
address ***.**.**.**/24 #public IP address from Kimsufi
gateway ***.**.**.254 #default gateway IP for your cluster
bridge-ports eno1
bridge-stp off
bridge-fd 0
hwaddress **:**:**:**:**:**
The following section needs to be apppended under the already generated network configurations.
YAML:
# vmbr2
auto vmbr2
iface vmbr2 inet static
address 10.0.0.1
netmask 255.255.255.0
bridge_ports none
bridge_stp off
bridge_fd 0
post-up echo 1 > /proc/sys/net/ipv4/ip_forward
post-up echo 1 > /proc/sys/net/ipv4/conf/vmbr2/proxy_arp
post-up iptables -t nat -A POSTROUTING -s 10.0.0.0/24 -o vmbr0 -j MASQUERADE
post-down iptables -t nat -D POSTROUTING -s 10.0.0.0/24 -o vmbr0 -j MASQUERADE
#101 (for housekeeping purposes, keep this as your VM index) Windows Server Configuration
post-up iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 13389 -j DNAT --to 10.0.0.101:3389
post-down iptables -t nat -D PREROUTING -i vmbr0 -p tcp --dport 13389 -j DNAT --to 10.0.0.101:3389
Make sure you restart server or reload your networking configurations after this change has been made!
Now when you create your Windows VM instance, choose vmbr2 as your network bridge.
If you're having trouble with installing Windows as a VM, this guide can be helpful.
The only thing left you'll have to do is configure the Windows VM IPv4 Network Properties:
Heyo y'all!
I've managed to fix this issue on my lonesome. I'll explain what I've done so people having this issue in the future can reference it.
Since Kimsufi only offers you one IP per server, you must route your networking through iptables. I've followed this guide in regards to this, and it offers configuration for multiple VM's with very understandable steps.
When Proxmox 7 is installed via Kimsufi's panel, it comes preconfigured with the following /etc/networking/inferfaces:
YAML:
auto lo
iface lo inet loopback
iface eno1 inet manual
iface eno2 inet manual
auto vmbr0
iface vmbr0 inet static
address ***.**.**.**/24 #public IP address from Kimsufi
gateway ***.**.**.254 #default gateway IP for your cluster
bridge-ports eno1
bridge-stp off
bridge-fd 0
hwaddress **:**:**:**:**:**
The following section needs to be apppended under the already generated network configurations.
YAML:
# vmbr2
auto vmbr2
iface vmbr2 inet static
address 10.0.0.1
netmask 255.255.255.0
bridge_ports none
bridge_stp off
bridge_fd 0
post-up echo 1 > /proc/sys/net/ipv4/ip_forward
post-up echo 1 > /proc/sys/net/ipv4/conf/vmbr2/proxy_arp
post-up iptables -t nat -A POSTROUTING -s 10.0.0.0/24 -o vmbr0 -j MASQUERADE
post-down iptables -t nat -D POSTROUTING -s 10.0.0.0/24 -o vmbr0 -j MASQUERADE
#101 (for housekeeping purposes, keep this as your VM index) Windows Server Configuration
post-up iptables -t nat -A PREROUTING -i vmbr0 -p tcp --dport 13389 -j DNAT --to 10.0.0.101:3389
post-down iptables -t nat -D PREROUTING -i vmbr0 -p tcp --dport 13389 -j DNAT --to 10.0.0.101:3389
Make sure you restart server or reload your networking configurations after this change has been made!
Now when you create your Windows VM instance, choose vmbr2 as your network bridge.
If you're having trouble with installing Windows as a VM, this guide can be helpful.
The only thing left you'll have to do is configure the Windows VM IPv4 Network Properties:
I tried exactly like this but cannot RDP into my VM.. I also studied the linked guide (via Internet Archive/Wayback Machine) and cannot see an error on my side.. But the proxmox Firewall is not mentioned anywhere do I have to turn it on or off?
When I edit the second bridge via /etc/network/interfaces and do a "systemctl restart networking" I cannot RDP into my VM, then I have to attach the VM to another bridge and then back to the second bridge and it starts working! A VM restart does not help in this case.. At work I even rebooted the whole server without an effect but have to verify this, as I cannot reboot my homeserver at the moment..
Update:
This also seems to apply to the VMs connected to vmbr0, even if I don't modify this bridge.. Have to reassign the vms to the bridge to reach the VMs again..
