NICs - how does it work?

vanDivX

New Member
Jun 24, 2010
29
0
1
Hi there, I have installed v2.1 on my Dell T310 server and it comes with two ethernet ports on board.

Because I intend to experiment with running VM as firewall gateway which I believe should have its own physical ethernet ports to use (and minimum for this are two dedicated ports - one for WAN and the other LAN), I installed additional dual port NIC for that purpose.

Actually I have couple such dual port NICs (because I wasn't sure I would be able to install the one I bought initially which was maybe too new and there might not be drivers for it in the Proxmox install...) and I decided to put both of them inside the server for the Proxmox install procedure in the hope it would install them automatically (because later on if I decided to add the second one I might not be able to do it due to my rather limited Linux skills).

To me it looks as if both NICs installed OK during the Proxmox installation without me having to inject drivers during install procedure, or at least I think they did install - that's why I am here. How can you tell they did really install properly?

And how does one go about injecting drivers during Proxmox install or how does one install them after Proxmox is installed?

I am trying to sort this out before I start populating the server with VMs because now is the time to figure it all out and perhaps abandon a NIC if it turns up unusable with Proxmox.
---------------------------------------------------------

Now in the web interface if I go to Proxmox - Network tab I see there eth0, eth1 etc... untill eth5, plus vmbr0 (which has assigned the IP for web access). That's six physical ports which looks right - dual ports inbuilt on the server board plus two added dual port NICs, for total of the six physical ports, or eht0 to eth5.

So far so good. But then I click on 'Create VM' button and just to get to selecting the NICs I go through the wizard selecting win7 or Linux VM, accept default offerings and when I get to Network tab I look what is available there and I don't see my two NICs as choices. What I see there in the drop down menu on right is Realtec RTL8139, Intel E1000 and VirtIO (paravirtualized) for the total of these three choices.

Now I expected to see six choices, for the six physical ethernet ports plus that paravitualized VirtIO which I believe is some virtual Proxmox system networking interface. Or the three choices plus two MAC choices for each in the drop down menu below the NIC choice. But the MAC choice is greyed out.

I don't know what kind of onboard chipset I have, it might be that Realtec RTL8139 and even the Intel E1000 might be correct identification of the one NIC I have installed in addition but where is the second port for each? The MAC drop down menu just below the NIC choice is not active but greyed out. And where is that second dual port NIC I installed?


The two dual port NICs I have added to the server are both Intel Dual Gigabyte port NICs

Intel E1G42ET Blk

Intel PRO/1000 PT EXP1940PT


I can only think they didn't install after all and the ethx entries are just dummy nonfunctional pointers or what indicating that the cards are there but need to have drivers installed...


Also in the Proxmox Network tab I made all entries ethx autostart but that didn't change anything (of course I restarted the server). In previous install (I have reinstalled now many times) I tried assigning IPs to those ethx entries but when I do that and want to apply changes by rebooting, the server does reboot but I loose web access forever (don't know how to correct it from CLI) and have to make new install again. BTW I am not messing with editing eth0 or vmbr0. Also the ethx Edit menu won't allow me to assign gateway, it rejects it...

Perhaps those NIC ports would start working as they should if I had their ports plugged into a switch? I do all this testing with unconnected NIC ports (that is except the first onboard that has Proxmox LAN IP and through which I access the server from browser).
 
Last edited:

vanDivX

New Member
Jun 24, 2010
29
0
1
I've just found out that MAC one can input when making new Vmachine and I suppose that can be found out somehow.

I've just experimented with adding some interface, forgot its name or type which was offered by default, I put in IP, mask, it told me I can't use my gateway, I tried different gateway IP, still told I can't use it (go figure) and I then rebooted and bingo, no web access no more, going to reinstall, today second time already. What a dirge this is turning up.
Wonder if only experts get helped here. I've done just about what I can on my own.
 

udo

Famous Member
Apr 22, 2009
5,936
185
93
Ahrensburg; Germany
I've just found out that MAC one can input when making new Vmachine and I suppose that can be found out somehow.

I've just experimented with adding some interface, forgot its name or type which was offered by default, I put in IP, mask, it told me I can't use my gateway, I tried different gateway IP, still told I can't use it (go figure) and I then rebooted and bingo, no web access no more, going to reinstall, today second time already. What a dirge this is turning up.
Wonder if only experts get helped here. I've done just about what I can on my own.
Hi,
perhaps your nic-ordering changed?
Take a look in /etc/udev/rules.d/70-persistent-net.rules
Perhaps you can post the output of following commands:
Code:
cat /etc/udev/rules.d/70-persistent-net.rules
cat /etc/network/interfaces
ls /etc/network/interfaces*
ifconfig -a
dmesg | grep eth
Udo
 

vanDivX

New Member
Jun 24, 2010
29
0
1
I have been reading up to ten pages back on the forum here and already looked at the '70-persistent-net.rules' file and ran the 'dmesg | grep eth' command and it looks like both NICs have installed properly.

I suppose I do something one is not supposed to do. Perhaps I am not supposed to edit eth(x) lines in Network tab (and assign IPs to them) but create vmbr(x) and then associate it with one of the eth(x) entries... and vhen making new VM the Realtec and E1000 are not NICs but 'models' or emulations of NICs to use (like for win7 should be used E1000 type I think), right? One should create vmbr(#) in Network tab first and it is then available when making new VM as choice. I thought there would be selection of those eth(#) to use but there is not, one must use those vmbr(#) (is that short for Virtual Machine BRidge #)
Also now that I know MAC numbers of the NICs I can at least tell which is which.

I also read about testing Proxmox in VMWare, I think I am going to do my destructive trials in there from now on. ;)
Except that playing with NIC configuration has to be done on the server.

Thanks so much for replying, I noted those CLI commands down on paper for future use. Already have a small collection.

Also these are data from a fresh install (not messed up with my perhaps misguided experiments) which I just apt-get updated and upgraded, with both dual NICs inside server.

Code:
root@proxmox:~# cat /etc/udev/rules.d/70-persistent-net.rules
  # PCI device 0x14e4:0x163b (bnx2)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="a4:ba:db:2c:b9:4c", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

# PCI device 0x8086:0x10c9 (igb)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1b:21:5d:5d:91", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth5"

# PCI device 0x8086:0x10c9 (igb)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1b:21:5d:5d:90", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"

# PCI device 0x8086:0x105e (e1000e)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1f:29:5f:ab:42", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth3"

# PCI device 0x8086:0x105e (e1000e)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1f:29:5f:ab:43", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth4"

# PCI device 0x14e4:0x163b (bnx2)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="a4:ba:db:2c:b9:4b", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"


Code:
root@proxmox:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

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



Code:
root@proxmox:~# ls /etc/network/interfaces*
/etc/network/interfaces


Code:
root@proxmox:~# ifconfig -a
eth0      Link encap:Ethernet  HWaddr a4:ba:db:2c:b9:4b
          inet6 addr: fe80::a6ba:dbff:fe2c:b94b/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1479 errors:0 dropped:0 overruns:0 frame:0
          TX packets:526 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:234273 (228.7 KiB)  TX bytes:62512 (61.0 KiB)
          Interrupt:16 Memory:d8000000-d8012800

eth1      Link encap:Ethernet  HWaddr a4:ba:db:2c:b9:4c
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:17 Memory:da000000-da012800

eth2      Link encap:Ethernet  HWaddr 00:1b:21:5d:5d:90
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

eth3      Link encap:Ethernet  HWaddr 00:1f:29:5f:ab:42
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:16 Memory:dd380000-dd3a0000

eth4      Link encap:Ethernet  HWaddr 00:1f:29:5f:ab:43
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:17 Memory:dd3c0000-dd3e0000

eth5      Link encap:Ethernet  HWaddr 00:1b:21:5d:5d:91
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

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:70 errors:0 dropped:0 overruns:0 frame:0
          TX packets:70 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:11096 (10.8 KiB)  TX bytes:11096 (10.8 KiB)

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 a4:ba:db:2c:b9:4b
          inet addr:192.168.1.2  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::a6ba:dbff:fe2c:b94b/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1273 errors:0 dropped:0 overruns:0 frame:0
          TX packets:401 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:183502 (179.2 KiB)  TX bytes:46610 (45.5 KiB)


Code:
root@proxmox:~# dmesg | grep eth
bnx2 0000:02:00.0: eth0: Broadcom NetXtreme II BCM5716 1000Base-T (C0) PCI Express found at mem d8000000, IRQ 16, node addr a4:ba:db:2c:b9:4b
bnx2 0000:02:00.1: eth1: Broadcom NetXtreme II BCM5716 1000Base-T (C0) PCI Express found at mem da000000, IRQ 17, node addr a4:ba:db:2c:b9:4c
e1000e 0000:05:00.0: eth2: (PCI Express:2.5GT/s:Width x4) 00:1f:29:5f:ab:42
e1000e 0000:05:00.0: eth2: Intel(R) PRO/1000 Network Connection
e1000e 0000:05:00.0: eth2: MAC: 1, PHY: 4, PBA No: D51930-004
igb 0000:04:00.0: eth3: (PCIe:2.5GT/s:Width x4
igb 0000:04:00.0: eth3: MAC: 00:1b:21:5d:5d:90
igb 0000:04:00.0: eth3: PBA No: E43709-003
e1000e 0000:05:00.1: eth4: (PCI Express:2.5GT/s:Width x4) 00:1f:29:5f:ab:43
e1000e 0000:05:00.1: eth4: Intel(R) PRO/1000 Network Connection
e1000e 0000:05:00.1: eth4: MAC: 1, PHY: 4, PBA No: D51930-004
igb 0000:04:00.1: eth5: (PCIe:2.5GT/s:Width x4
igb 0000:04:00.1: eth5: MAC: 00:1b:21:5d:5d:91
igb 0000:04:00.1: eth5: PBA No: E43709-003
ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PMI0._GHL] (Node ffff88023f0aff60), AE_AML_BUFFER_LIMIT
ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PMI0._PMC] (Node ffff88023f0af420), AE_AML_BUFFER_LIMIT
udev[465]: renamed network interface eth2 to eth2-eth3
udev[459]: renamed network interface eth3 to eth2
udev[465]: renamed network interface eth2-eth3 to eth3
device eth0 entered promiscuous mode
bnx2 0000:02:00.0: eth0: using MSIX
ADDRCONF(NETDEV_UP): eth0: link is not ready
bnx2 0000:02:00.0: eth0: NIC Copper Link is Up, 1000 Mbps full duplex, receive & transmit flow control ON
vmbr0: port 1(eth0) entering forwarding state
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
eth0: no IPv6 routers present
 
Last edited:

udo

Famous Member
Apr 22, 2009
5,936
185
93
Ahrensburg; Germany
I have been reading up to ten pages back on the forum here and already looked at the '70-persistent-net.rules' file and ran the 'dmesg | grep eth' command and it looks like both NICs have installed properly.

I suppose I do something one is not supposed to do. Perhaps I am not supposed to edit eth(x) lines in Network tab (and assign IPs to them) but create vmbr(x) and then associate it with one of the eth(x) entries... and vhen making new VM the Realtec and E1000 are not NICs but 'models' or emulations of NICs to use (like for win7 should be used E1000 type I think), right? One should create vmbr(#) in Network tab first and it is then available when making new VM as choice. I thought there would be selection of those eth(#) to use but there is not, one must use those vmbr(#) (is that short for Virtual Machine BRidge #)
Also now that I know MAC numbers of the NICs I can at least tell which is which.

I also read about testing Proxmox in VMWare, I think I am going to do my destructive trials in there from now on. ;)
Except that playing with NIC configuration has to be done on the server.

Thanks so much for replying, I noted those CLI commands down on paper for future use. Already have a small collection.

Also these are data from a fresh install (not messed up with my perhaps misguided experiments) which I just apt-get updated and upgraded, with both dual NICs inside server.

Code:
root@proxmox:~# cat /etc/udev/rules.d/70-persistent-net.rules
  # PCI device 0x14e4:0x163b (bnx2)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="a4:ba:db:2c:b9:4c", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

# PCI device 0x8086:0x10c9 (igb)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1b:21:5d:5d:91", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth5"

# PCI device 0x8086:0x10c9 (igb)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1b:21:5d:5d:90", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"

# PCI device 0x8086:0x105e (e1000e)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1f:29:5f:ab:42", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth3"

# PCI device 0x8086:0x105e (e1000e)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1f:29:5f:ab:43", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth4"

# PCI device 0x14e4:0x163b (bnx2)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="a4:ba:db:2c:b9:4b", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"


Code:
root@proxmox:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

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



Code:
root@proxmox:~# ls /etc/network/interfaces*
/etc/network/interfaces


Code:
root@proxmox:~# ifconfig -a
eth0      Link encap:Ethernet  HWaddr a4:ba:db:2c:b9:4b
          inet6 addr: fe80::a6ba:dbff:fe2c:b94b/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1479 errors:0 dropped:0 overruns:0 frame:0
          TX packets:526 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:234273 (228.7 KiB)  TX bytes:62512 (61.0 KiB)
          Interrupt:16 Memory:d8000000-d8012800

eth1      Link encap:Ethernet  HWaddr a4:ba:db:2c:b9:4c
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:17 Memory:da000000-da012800

eth2      Link encap:Ethernet  HWaddr 00:1b:21:5d:5d:90
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

eth3      Link encap:Ethernet  HWaddr 00:1f:29:5f:ab:42
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:16 Memory:dd380000-dd3a0000

eth4      Link encap:Ethernet  HWaddr 00:1f:29:5f:ab:43
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:17 Memory:dd3c0000-dd3e0000

eth5      Link encap:Ethernet  HWaddr 00:1b:21:5d:5d:91
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

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:70 errors:0 dropped:0 overruns:0 frame:0
          TX packets:70 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:11096 (10.8 KiB)  TX bytes:11096 (10.8 KiB)

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 a4:ba:db:2c:b9:4b
          inet addr:192.168.1.2  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::a6ba:dbff:fe2c:b94b/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1273 errors:0 dropped:0 overruns:0 frame:0
          TX packets:401 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:183502 (179.2 KiB)  TX bytes:46610 (45.5 KiB)


Code:
root@proxmox:~# dmesg | grep eth
bnx2 0000:02:00.0: eth0: Broadcom NetXtreme II BCM5716 1000Base-T (C0) PCI Express found at mem d8000000, IRQ 16, node addr a4:ba:db:2c:b9:4b
bnx2 0000:02:00.1: eth1: Broadcom NetXtreme II BCM5716 1000Base-T (C0) PCI Express found at mem da000000, IRQ 17, node addr a4:ba:db:2c:b9:4c
e1000e 0000:05:00.0: eth2: (PCI Express:2.5GT/s:Width x4) 00:1f:29:5f:ab:42
e1000e 0000:05:00.0: eth2: Intel(R) PRO/1000 Network Connection
e1000e 0000:05:00.0: eth2: MAC: 1, PHY: 4, PBA No: D51930-004
igb 0000:04:00.0: eth3: (PCIe:2.5GT/s:Width x4
igb 0000:04:00.0: eth3: MAC: 00:1b:21:5d:5d:90
igb 0000:04:00.0: eth3: PBA No: E43709-003
e1000e 0000:05:00.1: eth4: (PCI Express:2.5GT/s:Width x4) 00:1f:29:5f:ab:43
e1000e 0000:05:00.1: eth4: Intel(R) PRO/1000 Network Connection
e1000e 0000:05:00.1: eth4: MAC: 1, PHY: 4, PBA No: D51930-004
igb 0000:04:00.1: eth5: (PCIe:2.5GT/s:Width x4
igb 0000:04:00.1: eth5: MAC: 00:1b:21:5d:5d:91
igb 0000:04:00.1: eth5: PBA No: E43709-003
ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PMI0._GHL] (Node ffff88023f0aff60), AE_AML_BUFFER_LIMIT
ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PMI0._PMC] (Node ffff88023f0af420), AE_AML_BUFFER_LIMIT
udev[465]: renamed network interface eth2 to eth2-eth3
udev[459]: renamed network interface eth3 to eth2
udev[465]: renamed network interface eth2-eth3 to eth3
device eth0 entered promiscuous mode
bnx2 0000:02:00.0: eth0: using MSIX
ADDRCONF(NETDEV_UP): eth0: link is not ready
bnx2 0000:02:00.0: eth0: NIC Copper Link is Up, 1000 Mbps full duplex, receive & transmit flow control ON
vmbr0: port 1(eth0) entering forwarding state
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
eth0: no IPv6 routers present
Hi,
this looks all ok. You use at this time only eth0 (bridged to vmbr0).

If you wan't to use another NIC for another network simply create an new bridge (like vmbr1, or vmbr10 or vmbr222 like you want) with the right NIC bridged to. BTW. you need for this nic only an IP if the host must be accessible on this IP.
You can also do bonding and vlan-tagging and so on - the normal linux networking stuff.

The NICs of a VM are virtualize (this is one big effort of virtualization, no hardware dependencies) and has nathing to do with the driver of the real NIC.
Use virtio for linux (and perhaps windows) and e1000 (bsd need rtl...).


Udo
 

vanDivX

New Member
Jun 24, 2010
29
0
1
Thanks for info, I'll try to read up on it. As you say, it is the 'normal linux networking stuff'. For me it is difficult to tell what is specific to proxmox (virtual environment as such) and what is generic linux, probably most of it is just plain linux.

My plans for the server is to install ClearOS VM (Firewall, LAN Gateway) and have it use two physical eth ports (WAN & LAN). Once that is working I would install Asterisk PBX (PIAF) and something to serve my webpages to public.

I will have to read up around here what people say about installing firewall gateway on proxmox, it seems many do that. Critical for that is handling the assignment of physical eth ports. I suppose one can edit directly eth entries just for some such use as this. And for other normal use one uses vmbr virtual bridge, which can be many to single eth physical port. But that's how I think it works, it might work quite differently as it may turn up. :)
 

udo

Famous Member
Apr 22, 2009
5,936
185
93
Ahrensburg; Germany
Thanks for info, I'll try to read up on it. As you say, it is the 'normal linux networking stuff'. For me it is difficult to tell what is specific to proxmox (virtual environment as such) and what is generic linux, probably most of it is just plain linux.

My plans for the server is to install ClearOS VM (Firewall, LAN Gateway) and have it use two physical eth ports (WAN & LAN). Once that is working I would install Asterisk PBX (PIAF) and something to serve my webpages to public.

I will have to read up around here what people say about installing firewall gateway on proxmox, it seems many do that. Critical for that is handling the assignment of physical eth ports. I suppose one can edit directly eth entries just for some such use as this. And for other normal use one uses vmbr virtual bridge, which can be many to single eth physical port. But that's how I think it works, it might work quite differently as it may turn up. :)
Hi,
simply define another bridge whitout IP for your WAN (I assume, that your LAN is the same network where the pve-host stay) like vmbr1 with brigded eth1 (or what else free NIC you have).
Then you can create an VM with two nics - one in LAN (vmbr0) ond one in WAN (vmbr1). That's all.

Udo
 

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 your own in 60 seconds.

Buy now!