Guest Networking Unavailable

jmace

New Member
Feb 12, 2012
13
0
1
I have grown very fond of PM over the past couple months working with it in a testing environment. When I first installed it networking was working fine, however, I tried to create another bridge, on my eth1 nic, but ended up deleting it. After that, my bridged, vmbr0, network stopped connecting to the Internet. Besides not being able to get on to the Internet from many of my virtual machines, and my virtual machines cannot talk to each other on either bridged or NAT mode no matter which network adapter type I use (RealTec, Intel, or VirtIO).


Any help you could provide would be greatly appreciated.


My PM server is connected to a wireless extender with a static internal IP (192.168.1.99), Mask (255.255.255.0), Gateway and DNS (192.168.1.1). The extender is then connected to the base wireless router in DHCP mode IP (192.168.1.1), Mask (255.255.255.0), Gateway and DNS (192.168.1.1).


My /etc/network/interfaces file looks like this:
Code:
auto lo
iface lo inet loopback


auto eth0
iface eth0 inet manual


iface eth1 inet manual


auto vmbr0
iface vmbr0 inet static
        address  192.168.1.100
        netmask  255.255.255.0
        gateway  192.168.1.1
        bridge_ports eth0
        bridge_stp off
        bridge_fd 0


When I run a ifconfig, however, I get a couple of other "interfaces" that I don't quite understand as I have never set them. The output is as follows:
Code:
eth0      Link encap:Ethernet  HWaddr 00:e0:81:4d:b3:b6
          inet6 addr: fe80::2e0:81ff:fe4d:b3b6/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:151492 errors:0 dropped:0 overruns:0 frame:0
          TX packets:128819 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:21495071 (20.4 MiB)  TX bytes:70935019 (67.6 MiB)
          Interrupt:28 Base address:0x8000


lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:74638 errors:0 dropped:0 overruns:0 frame:0
          TX packets:74638 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:12732722 (12.1 MiB)  TX bytes:12732722 (12.1 MiB)


tap108i0  Link encap:Ethernet  HWaddr d6:e7:17:45:c2:f4
          inet6 addr: fe80::d4e7:17ff:fe45:c2f4/64 Scope:Link
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:196 errors:0 dropped:0 overruns:0 frame:0
          TX packets:32563 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500
          RX bytes:8448 (8.2 KiB)  TX bytes:2213992 (2.1 MiB)


venet0    Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00                                                                              -00
          inet6 addr: fe80::1/128 Scope:Link
          UP BROADCAST POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:3 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)


vmbr0     Link encap:Ethernet  HWaddr 00:e0:81:4d:b3:b6
          inet addr:192.168.1.100  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::2e0:81ff:fe4d:b3b6/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:151999 errors:0 dropped:0 overruns:0 frame:0
          TX packets:127357 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:19050824 (18.1 MiB)  TX bytes:68623372 (65.4 MiB)
 
I solved it!

It was a Windows issue, surprise surprise. When dropping and adding network adapters Windows didn't clear out the registry values for the old interface cards. Therefore, this is what I had to do:

Code:
1) Open a command window with elevated privileges (Start -> Right-click "Command Prompt", select [COLOR=#008000][B]"Run as Administrator"[/B][/COLOR]) <-- This is key #1


2) In the command window, execute the following commands:


[B]SET DEVMGR_SHOW_NONPRESENT_DEVICES=1[/B]


[B]START DEVMGMT.MSC[/B]


The second command starts the Device Manager. It MUST be started from the elevated-privilege command window for this procedure to work. <-- This is key #2


3) In Device Manager, click the VIEW menu item and select "Show hidden devices".


This should show any hidden devices. For network adapters, expand the network adapters node. Right-Click any device you wish to remove, and click Uninstall.

I hope this helps someone else.

I still don't get all of the extra "interfaces" after running the ifconfig command, so if someone knows or can shed some light on it I would be quite thankful.
 

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!