Search results

Thanks for the article I will try and follow that to set up NAT rather than routed config. Do I need to revert the settings back to the NIC or can I do that from the bridge I have acting as the NIC now?

No I got only one IP address with the server unfortunately. How do I set the NAT setup up in PVE?

I think it'a problem with the interface file in the container as there's nothing much in it: # UNCONFIGURED INTERFACES # remove the above line if you edit this file auto lo iface lo inet loopback auto eth0 iface eth0 inet dhcp #auto eth1 #iface eth1 inet dhcp That's what I get in the config...

When I create the container I leave the name as eth0 and use the vmbr0 bridge, I leave everything else as it is?

Have tried a couple of articles regarding container connections but cannot find a solution that works yet

That worked! Rebooted and it logged in fine, webUI also back up and showing the bridge active. Thanks a lot! Edit: Actually, too early, I still don't have any connection with any containers somehow? Also the network details from the network device have changed to the bridge (IP, Subnet, Gatway...

this is after a clean install of PVE on Debian 9, no bridge create or nothing yet auto lo iface lo inet loopback iface lo inet6 loopback auto enp5s0 iface enp5s0 inet static address xxx.xxx.xxx.180 netmask 255.255.255.192 gateway xxx.xxx.xxx.129 # route xxx.xxx.xxx.128/26 via...

Ok, no problem what configuration do you need?

I only installed it and created a bridge that was it, put in the bridge ports of the network device, but when I reboot the server to implement the changes I can't get back into the server. I can only get in on the rescue kvm?

Hello, Little new to PVE to bear with me..... I installed Debian 9 minimal on my server then installed Proxmox on top of it, when I make a bridge in PVE it does not show as active. If I then either reboot the node to implement changes or copy the interfaces.new file to replace the interfaces...