Networking problem ( Server side )

M

Mahmoud Aljan

New Member
Sep 5, 2012
2
0
1
London, United Kingdom, United Kingdom
Hey guys,

I have been running proxmox now for over a year in production on two servers and it has been great. I would like to upgrade to the newest release but it seems like my two servers can not access any internet, the strange thing is that the underlying vms have access to internet and are spinning fantastically.

both servers have these as their network configuration :

eth0
ip : 192.168.1.x
gateway : 192.169.1.1
vmbr0
ip : 192.168.1.x
gateway : void
bridge : eth0

Please help ?

Thank you
 
Mahmoud Aljan said:
Hey guys,

I have been running proxmox now for over a year in production on two servers and it has been great. I would like to upgrade to the newest release but it seems like my two servers can not access any internet, the strange thing is that the underlying vms have access to internet and are spinning fantastically.

both servers have these as their network configuration :

eth0
ip : 192.168.1.x
gateway : 192.169.1.1
vmbr0
ip : 192.168.1.x
gateway : void
bridge : eth0

Please help ?

Thank you
Click to expand...
Hi,
first - your gateway aren't in the same subnet like the host (perhaps 192.168.1.1 work as gateway?).

second: why you use on eth0 also an ip-config? Normaly you do all ip-related things on vmbr0 and bind eth0 to this bridge (ok, not with hostingprovider which are do some special things for subnetting without vlans and so on).

Udo
 
Last edited:
Thanks Udo

Sorry but i had my ip typed wrong every thing is on the same subnet 192.168.1.x

Do you suggest that I bind eth0 to vmbr0 instead of bridging it ?

What would be a easy way to switch to a healthier network configuration without deleting vmbr0 since every vm is relying on it for network connectivity right now.

Thank you
 
Mahmoud Aljan said:
Thanks Udo

Sorry but i had my ip typed wrong every thing is on the same subnet 192.168.1.x

Do you suggest that I bind eth0 to vmbr0 instead of bridging it ?

What would be a easy way to switch to a healthier network configuration without deleting vmbr0 since every vm is relying on it for network connectivity right now.

Thank you
Click to expand...
Hi,
bridging is right - but you don't need an IP on eth0 for that. Like
Code: 
iface eth0 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.1.x
        netmask 255.255.255.0
        gateway 192.168.1.1
        bridge_ports eth0
        bridge_stp off
        bridge_fd 0
to find the issue use tcpdump - on one terminal do an "ping www.google.com" and on another terminal "tcpdump -i vmbr0".

You should not use an ssh-connection for that, because of many traffic.

Udo
 
You must log in or register to reply here.
Top Bottom