Please assist with setting up networking on a Windows Guest

G

greavette

Renowned Member
Apr 13, 2012
163
9
83
Hello,

I have Proxmox 2.1 installed and connect to a Powerconnect 5548 switch. I've setup 4 vland's on this switch. I have 6 nics on my server and have plugged in the cables to the appropriate ports on my switch (as per my vlan setup).

Here is a screenshot of my Proxmox network setup:

VMProxmoxSetup.jpg

What should be my guest network properties if I was to use vmbr3 for my Guest O/S (Windows 7). I've tried this configuration but it is not working:

GuestNicProperties.jpg

Here is a screenshot of the networking I added to the Guest VM from Proxmox. Do I add in a vlan tag or not?

ProxmoxNetworkDevice.jpg

Thank you.
 
Wow Udo...you sure are helpful. ;)

I thought I didn't need vlan tagging. So I can take that off my nic config for my vm in proxmox...but what are the network settings in the VM itself? I have bought paid support on our server, but I wouldn't think paid support covers weekend work...I would wait until Monday, but I'm really hoping to get my guest network working while no one is in the office.

Thank you.
 
Last edited:
Hi,
I don't unserstand right. You have remove the vlan-tagging in the VM-network-config (on the pve-side)? And your guest are not able to use the network?
Perhaps the firewall of the windos-vm?
If you ping from the VM to the pve-host (ping 192.168.4.17) do you get answers? Do you see anything if you look on the pvehost with
Code: 
tcpdump -i vmbr3 host 192.168.4.18
Please post the config of the VM (cat /etc/pve/qemu-server/VMID.conf - e.g. 100.conf).

Udo
 
Hmmm, your comment has got me to thinking Udo. So if I don't assign an IP to eth1 (vmbr3 from my picture in my original post), I could then assign an IP to my guest from within my guest as follows:

GuestNicProperties2.jpg

I had thought I needed to assign an IP to the vmbr. It would seem I misunderstood how to set this up.

So if I don't assign an IP to vmbr3...I can select vmbr3 for more than one VM and within each VM assign it's own IP (as per my vland). Is this correct?

Thank you.
 
greavette said:
Hmmm, your comment has got me to thinking Udo. So if I don't assign an IP to eth1 (vmbr3 from my picture in my original post), I could then assign an IP to my guest from within my guest as follows:

View attachment 1149

I had thought I needed to assign an IP to the vmbr. It would seem I misunderstood how to set this up.

So if I don't assign an IP to vmbr3...I can select vmbr3 for more than one VM and within each VM assign it's own IP (as per my vland). Is this correct?

Thank you.
Click to expand...
Hi,
it's looks that there was an misunderstanding:
An bridge is like a simple network-hub - all devices which are connected to an bridge are connected together.
If you define vmbr3 for network 3 (BTW. you can name the vmbr also different, like vmbr250 if you use vlan250 or you have the network 192.168.250/24) you can support this network to many VMs.
An bridge-interface on the host don't need an IP (except vmbr0) - it's enough if the VMs use IPs of this network. E.G. if you have an /29-network you won't loose an extra IP for the pve-host. It's only nessecary if the pve-host (gui) must be accessible from this network and the normal routing wouldn't success. And the eth-interface don't need an IP!! Except on special hosting-setups.


Udo
 
Thank you for the reply and explanation. Would the same be true for bonded nics (802.3ad)? I create a bonded nic and assign the ethx nics to it. I wouldn't give my new bonded nic an IP, but within my VM I would set a static IP. Correct?

Would I need to tag the bonded nic so that I may have a bigger pipe (2 nics therefore 2GB pipe)?

Thank you,
 
greavette said:
Thank you for the reply and explanation. Would the same be true for bonded nics (802.3ad)? I create a bonded nic and assign the ethx nics to it. I wouldn't give my new bonded nic an IP, but within my VM I would set a static IP. Correct?
Click to expand...
Yes,
but I recommend first to create the network config without bonds - and if all is working create the bonds - otherwise you must look on different places where the issue is if something don't work.
Would I need to tag the bonded nic so that I may have a bigger pipe (2 nics therefore 2GB pipe)?

Thank you,
Click to expand...
depends on your mode for the bond. Use the search function, there are some post about this (I don't have experiences with bonds - I simply use 10GB Nics ;) ).

Udo
 
Nice...10GB nics would be great! I'm probably fine with just 1GB nics where I isolate one nic for my important database VM within it's own Vland anyway. Good advice...I will continue ensuring that my network config without bonds work well for me.

Thank you Udo.

By the way...is there a way to make a post as solved? I don't like leaving posts open if my problem has been solved.

Thank you.
 
greavette said:
Nice...10GB nics would be great! I'm probably fine with just 1GB nics where I isolate one nic for my important database VM within it's own Vland anyway. Good advice...I will continue ensuring that my network config without bonds work well for me.

Thank you Udo.

By the way...is there a way to make a post as solved? I don't like leaving posts open if my problem has been solved.
Click to expand...
edit post (the first) -> go advance -> change the title to start with [solved] (not tried yet - i'm more answer to threads...)
 
Thank you...before I close this post, I'd like to ask a further question though that may be related to this setup we've been discussing.

So I have a vlan4 setup on my switch that is assigned to vmbr3 (you are right...I should make these names match up...I will make the necessary changes).

With your assistance, I now have network access from within my network on my VM where the gateway is my switch (192.168.1.8). But my internet access is from my office router (192.168.1.1). From within my VM I have no internet access. I try and ping 192.168.1.1 and can't (requests times out).

Would this be a setting problem with Proxmox or do you think it's a problem with how I setup my vlan on my switch?

Thanks.
 
greavette said:
Thank you...before I close this post, I'd like to ask a further question though that may be related to this setup we've been discussing.

So I have a vlan4 setup on my switch that is assigned to vmbr3 (you are right...I should make these names match up...I will make the necessary changes).

With your assistance, I now have network access from within my network on my VM where the gateway is my switch (192.168.1.8). But my internet access is from my office router (192.168.1.1). From within my VM I have no internet access. I try and ping 192.168.1.1 and can't (requests times out).

Would this be a setting problem with Proxmox or do you think it's a problem with how I setup my vlan on my switch?

Thanks.
Click to expand...
Hi,
you must post a little bit more info...
If I remember right, your VM are in the network 192.168.4/24 - so the gateway can't be in a different net (192.168.1.8)!
If you are in the same network, you must be able to ping all destinations on this network except an firewall protect that - if you can ping the switch, but not the router, the issue can't be on the pve-node.

In your config the switch must have as default router 192.168.1.1?! Otherwise you must define as default router the office-router and use the switch only for static routes (like 192.168.3/24,192.168.4/24).

Sometimes people have issues with internet access but the routes are fine, only dns isn't working....

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