VMS not getting internet

jasonrx8

New Member
Oct 15, 2023
4
1
3
HI

hoping someone can assist , i have followed the install guide , and looked through all the documents but can not find the answer ,

i have PROMOX setup on a dedicated server , i have installed windows 10 ,
i have setup a bridge interface ,
the host can ping the windows box , 192.168.55.5
the VM can ping the host , 192.168.55.1
but i can not get internet on the VM
here are my config network files
-----------------------------------------------------
/etc/network/interfaces
auto lo
iface lo inet loopback

iface ens3 inet manual

auto vmbr0
iface vmbr0 inet static
address 103.1.184.184/24
gateway 103.1.184.1
bridge-ports ens3
bridge-stp off
bridge-fd 0

auto vmbr1
iface vmbr1 inet static
address 192.168.55.1/24
bridge-ports none
bridge-stp off
bridge-fd 0

--------------------------------------------------
ip a

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
link/ether 00:16:3e:e4:2d:02 brd ff:ff:ff:ff:ff:ff
altname enp0s3
3: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 00:16:3e:e4:2d:02 brd ff:ff:ff:ff:ff:ff
inet 103.1.184.184/24 scope global vmbr0
valid_lft forever preferred_lft forever
inet6 fe80::216:3eff:fee4:2d02/64 scope link
valid_lft forever preferred_lft forever
9: tap100i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr1 state UNKNOWN group default qlen 1000
link/ether 5a:e5:11:a4:66:59 brd ff:ff:ff:ff:ff:ff
16: vmbr1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 86:b2:a5:07:a2:2e brd ff:ff:ff:ff:ff:ff
inet 192.168.55.1/24 scope global vmbr1
valid_lft forever preferred_lft forever
inet6 fe80::6844:4aff:fe69:3b1d/64 scope link
valid_lft forever preferred_lft forever


--------------------------------------------------------------------------------
host details

1697330764079.png

VM network details
1697330802352.png

VM network setup

1697330824670.png

ping from VM to Host
1697330863427.png

Ping from host to VM

1697330896998.png


VM trying to ping google 8.8.8.8

1697330934969.png

Host pinging google 8.8.8.8

1697330966572.png



at present , all the firewalls are off ,

but still not working ,

any help would be very much appreciated
 

Attachments

  • 1697330728134.png
    1697330728134.png
    24.6 KB · Views: 1
Someone (read: an active piece of software) needs to translate that RFC1918 address of your choice (192.168.x.x/16) into a worldwide routeable address. Usually this is the main task of a router. You do not have one, so nobody does this - yet. The common term is Network-Address-Translation = NAT. If hiding a complete network with this approach it is often called "masquerading".

Please read https://pve.proxmox.com/wiki/Network_Configuration#sysadmin_network_masquerading

Best regards - and good luck!
 
HI

i did that about a hour after this post and it still has not fixed it

auto lo
iface lo inet loopback

iface ens3 inet manual

auto vmbr0
iface vmbr0 inet static
address 103.1.184.184/24
gateway 103.1.184.1
bridge-ports ens3
bridge-stp off
bridge-fd 0

auto vmbr1
iface vmbr1 inet static
address 192.168.55.1/24
bridge-ports none
bridge-stp off
bridge-fd 0

post-up echo 1 > /proc/sys/net/ipv4/ip_forward
post-up iptables -t nat -A POSTROUTING -s '192.168.55.0/24' -o eno1 -j MASQUERADE
post-down iptables -t nat -D POSTROUTING -s '192.168.55.0/24' -o eno1 -j MASQUERADE
 
As I am not using this type of configuration I can only guess: you do not have an "eno1" and "ens3" has no IP-address, your bridge vmbr0 has it. (And that is fine.) So in my personal understanding you should output the natted packages there: post-up iptables -t nat -A POSTROUTING -s '192.168.55.0/24' -o vmbr0 -j MASQUERADE.

Again: may be wrong. Just try this and if it fails try "ens3"...

PS: for multi-line content of a configuration file: please use [CODE]...[/CODE] - tags as it is much easier to read.
 
i have a bunch of public IPS i wanted to use and spent days trying to get those going with no luck ,
ive confirmed they work on another server , but when i set them up with PROXMOX same result im getting now , so i thought i would go back to basics
, i would have thought out of the box with the config it applies it would work , but it did not
i used the provided ISO
 
Udob , thankyou for that , that got me internet going , now ill switch to my public IPS and see if that works , thanks again
 
  • Like
Reactions: UdoB

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!