strange problem with two NICs

tafkaz

Renowned Member
Dec 1, 2010
147
7
83
Geilenkirchen Germany
Hi,
first of all i want to say thank you, for this incredible piece of software that Proxmox VE is!

Now on to my problem:

I have two network cards in my server:
Code:
hwinfo --netcard
09: PCI 306.0: 0200 Ethernet controller
  [Created at pci.310]
  Unique ID: rBUF.49XPc+GN1h3
  Parent ID: qscc.ULOo3yhA66C
  SysFS ID: /devices/pci0000:00/0000:00:14.4/0000:03:06.0
  SysFS BusID: 0000:03:06.0
  Hardware Class: network
  Model: "Intel PRO/1000 GT Desktop Adapter"
  Vendor: pci 0x8086 "Intel Corporation"
  Device: pci 0x107c "82541PI Gigabit Ethernet Controller"
  SubVendor: pci 0x8086 "Intel Corporation"
  SubDevice: pci 0x1376 "PRO/1000 GT Desktop Adapter"
  Revision: 0x05
  Driver: "e1000"
  Driver Modules: "e1000"
  Device File: eth0
  Memory Range: 0xfdec0000-0xfdedffff (rw,non-prefetchable)
  Memory Range: 0xfdea0000-0xfdebffff (rw,non-prefetchable)
  I/O Ports: 0xcf00-0xcf3f (rw)
  Memory Range: 0xfdd00000-0xfdd1ffff (ro,prefetchable,disabled)
  IRQ: 20 (14612 events)
  HW Address: 00:1b:21:3e:ee:93
  Link detected: yes
  Module Alias: "pci:v00008086d0000107Csv00008086sd00001376bc02sc00i00"
  Driver Info #0:
    Driver Status: e1000 is active
    Driver Activation Cmd: "modprobe e1000"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #18 (PCI bridge)

10: PCI 200.0: 0200 Ethernet controller
  [Created at pci.310]
  Unique ID: JNkJ.1Z6M++B8ak4
  Parent ID: bSAa._Y7AlhwF+q8
  SysFS ID: /devices/pci0000:00/0000:00:0a.0/0000:02:00.0
  SysFS BusID: 0000:02:00.0
  Hardware Class: network
  Model: "Realtek RTL8111/8168B PCI Express Gigabit Ethernet controller"
  Vendor: pci 0x10ec "Realtek Semiconductor Co., Ltd."
  Device: pci 0x8168 "RTL8111/8168B PCI Express Gigabit Ethernet controller"
  SubVendor: pci 0x1458 "Giga-byte Technology"
  SubDevice: pci 0xe000
  Revision: 0x02
  Driver: "r8169"
  Driver Modules: "r8169"
  Device File: eth1
  I/O Ports: 0xde00-0xdeff (rw)
  Memory Range: 0xfdcff000-0xfdcfffff (rw,prefetchable)
  Memory Range: 0xfdce0000-0xfdceffff (rw,prefetchable)
  Memory Range: 0xfdc00000-0xfdc0ffff (ro,prefetchable,disabled)
  IRQ: 25 (1594 events)
  HW Address: 00:24:1d:df:17:ed
  Link detected: yes
  Module Alias: "pci:v000010ECd00008168sv00001458sd0000E000bc02sc00i00"
  Driver Info #0:
    Driver Status: r8169 is active
    Driver Activation Cmd: "modprobe r8169"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #29 (PCI bridge)


Now i want to use eth0 as vmbr0 and eth1 as vmbr1, so that different guests would use different ethernet cards.
I configured this in the GUI just like in your video, and now have this in my /etc/network/interfaces:

Code:
# network interface settings
auto lo
iface lo inet loopback

iface eth0 inet manual

iface eth1 inet manual

auto vmbr0
iface vmbr0 inet static
        address  10.0.0.180
        netmask  255.255.255.0
        gateway  10.0.0.1
        bridge_ports eth0
        bridge_stp off
        bridge_fd 0

auto vmbr1
iface vmbr1 inet static
        address  10.0.0.181
        netmask  255.255.255.0
        bridge_ports eth1
        bridge_stp off
        bridge_fd 0

which looks ok to me.

Now the problem howexer is that in reality the two vmbr-devices are still linked to eth0.
If i unplug the cable from eth1 i can still ping both ip-adresses.
If i unplug the cable from eth0 i can't ping any of those.

Am i doing something terribly wrong here or what is the matter?


Thank you very much for your help!

Sascha
 
Hi Dietmar,
thanks for your fast reply.
I am sorry to say, that this didn't help.
I configured vmbr1 as you said and restartetd the server.

Now i have:


Code:
# network interface settings
auto lo
iface lo inet loopback

iface eth0 inet manual

iface eth1 inet manual

auto vmbr0
iface vmbr0 inet static
        address  10.0.0.180
        netmask  255.255.255.0
        gateway  10.0.0.1
        bridge_ports eth0
        bridge_stp off
        bridge_fd 0

auto vmbr1
iface vmbr1 inet manual
        bridge_ports eth1
        bridge_stp off
        bridge_fd 0

ifconfig shows:

Code:
eth0      Link encap:Ethernet  Hardware Adresse 00:1b:21:3e:ee:93
          inet6-Adresse: fe80::21b:21ff:fe3e:ee93/64 Gültigkeitsbereich:Verbindung
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metrik:1
          RX packets:9962 errors:0 dropped:0 overruns:0 frame:0
          TX packets:13478 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:1000
          RX bytes:1388729 (1.3 MiB)  TX bytes:9392654 (8.9 MiB)

eth1      Link encap:Ethernet  Hardware Adresse 00:24:1d:df:17:ed
          inet6-Adresse: fe80::224:1dff:fedf:17ed/64 Gültigkeitsbereich:Verbindung
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metrik:1
          RX packets:1525 errors:0 dropped:0 overruns:0 frame:0
          TX packets:83 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:1000
          RX bytes:205170 (200.3 KiB)  TX bytes:15583 (15.2 KiB)
          Interrupt:25 Basisadresse:0x4000

lo        Link encap:Lokale Schleife
          inet Adresse:127.0.0.1  Maske:255.0.0.0
          inet6-Adresse: ::1/128 Gültigkeitsbereich:Maschine
          UP LOOPBACK RUNNING  MTU:16436  Metrik:1
          RX packets:3461 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3461 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:0
          RX bytes:1208321 (1.1 MiB)  TX bytes:1208321 (1.1 MiB)

tap102i0d0 Link encap:Ethernet  Hardware Adresse 06:65:09:4c:af:aa
          inet6-Adresse: fe80::465:9ff:fe4c:afaa/64 Gültigkeitsbereich:Verbindung
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metrik:1
          RX packets:2501 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2822 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:500
          RX bytes:1639647 (1.5 MiB)  TX bytes:351014 (342.7 KiB)

tap104i0d0 Link encap:Ethernet  Hardware Adresse 12:62:51:04:9d:6c
          inet6-Adresse: fe80::1062:51ff:fe04:9d6c/64 Gültigkeitsbereich:Verbindung
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metrik:1
          RX packets:267 errors:0 dropped:0 overruns:0 frame:0
          TX packets:860 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:500
          RX bytes:65440 (63.9 KiB)  TX bytes:147197 (143.7 KiB)

tap104i1d0 Link encap:Ethernet  Hardware Adresse 56:95:22:36:fc:43
          inet6-Adresse: fe80::5495:22ff:fe36:fc43/64 Gültigkeitsbereich:Verbindung
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metrik:1
          RX packets:70 errors:0 dropped:0 overruns:0 frame:0
          TX packets:794 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:500
          RX bytes:14601 (14.2 KiB)  TX bytes:90891 (88.7 KiB)

tap107i0d0 Link encap:Ethernet  Hardware Adresse 1a:40:e5:d8:0f:4c
          inet6-Adresse: fe80::1840:e5ff:fed8:f4c/64 Gültigkeitsbereich:Verbindung
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metrik:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1317 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:500
          RX bytes:0 (0.0 B)  TX bytes:166522 (162.6 KiB)

venet0    Link encap:UNSPEC  Hardware Adresse 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet6-Adresse: fe80::1/128 Gültigkeitsbereich:Verbindung
          UP BROADCAST PUNKTZUPUNKT RUNNING NOARP  MTU:1500  Metrik:1
          RX packets:3985 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3344 errors:0 dropped:3 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:0
          RX bytes:829483 (810.0 KiB)  TX bytes:443379 (432.9 KiB)

vmbr0     Link encap:Ethernet  Hardware Adresse 00:1b:21:3e:ee:93
          inet Adresse:10.0.0.180  Bcast:10.0.0.255  Maske:255.255.255.0
          inet6-Adresse: fe80::21b:21ff:fe3e:ee93/64 Gültigkeitsbereich:Verbindung
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metrik:1
          RX packets:8106 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7993 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:0
          RX bytes:880476 (859.8 KiB)  TX bytes:7514352 (7.1 MiB)

vmbr1     Link encap:Ethernet  Hardware Adresse 00:24:1d:df:17:ed
          inet6-Adresse: fe80::224:1dff:fedf:17ed/64 Gültigkeitsbereich:Verbindung
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metrik:1
          RX packets:1271 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenlänge:0
          RX bytes:115756 (113.0 KiB)  TX bytes:468 (468.0 B)

Now in the Options for the guestsystem i have configured:

Code:
[TABLE="class: normal"]
[TR="bgcolor: #EDEDED"]
[TD][IMG]https://192.168.13.180/images/tarrdown.png[/IMG][/TD]
[TD]rtl8139[/TD]
[TD]vmbr0[/TD]
[TD][/TD]
[TD]7A:08:25:81:9B:49[/TD]
[/TR]
 [TR="bgcolor: #FFFFFF"]
[TD][IMG]https://192.168.13.180/images/tarrdown.png[/IMG][/TD]
[TD]rtl8139[/TD]
[TD]vmbr1[/TD]
[TD][/TD]
[TD]B6:61:71:AC:01:AB[/TD]
[/TR]
[/TABLE]

It looks well in the guest:

Code:
ifconfig
eth0      Link encap:Ethernet  HWaddr 7A:08:25:81:9B:49
          inet addr:10.0.0.110  Bcast:10.0.0.255  Mask:255.255.255.0
          inet6 addr: fe80::7808:25ff:fe81:9b49/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:723 errors:0 dropped:0 overruns:0 frame:0
          TX packets:343 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:138091 (134.8 KiB)  TX bytes:85036 (83.0 KiB)
          Interrupt:10 Base address:0x4000

eth1      Link encap:Ethernet  HWaddr B6:61:71:AC:01:AB
          inet addr:10.0.0.38  Bcast:10.0.0.255  Mask:255.255.255.0
          inet6 addr: fe80::b461:71ff:feac:1ab/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:583 errors:0 dropped:0 overruns:0 frame:0
          TX packets:79 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:70255 (68.6 KiB)  TX bytes:16141 (15.7 KiB)
          Interrupt:11 Base address:0x6100

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



i can ping on both ip, but i still have the same problem:
with only the eth0 cable i still can still ping on both IPs, with only the eth1 cable connected, none of the IPs are pingable.

thanks for your help
Sascha
 
tried another Networkcard too...
to no avail!


This is really strange. I am sure that something is just misconfigured, only i can't find what...


Thanks for your answers
Sascha
 
Same network on two different network cards = invalid configuration for any OS. It should be so. Use bridge if you want to have addresses from the same network on more than one card.
 
Hi!
ups...really didn't know that...
What would be the best way to configure a bridged second NIC with proxmox?
I need two (or more) NICs in the samte 10.0.0.x network with different IPs but using the same gateway (10.0.0.1).
Then i would like to allocate the cards to specific guest systems.

thank you very much for your help
Sascha
 
bridge one of the machines with one physical interface, and another machine with another one. no idea if it can be done with proxmox, but the config should be possible.

if you think of it, you will understand why it is impossible to put addresses from the same network on two different interfaces. think of routing. the routing does not know, which addresses are reachable through one of the interfaces, and which through other - so it will reach everything through just one of the interfaces (you never know, which one). If you need the computer to use both interfaces, though, you can check bonding. it has some algorithms to help the computer choose, which one of the interfaces to use - but it will still shown as a single virtual interface to other programs and to routing procedure.
 

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!