Help with 2 NICs and Virtualbox

From: Erik Hanson 
------------------------------------------------------
Hi all,

Two things:

1. I have a box running Crunchbang (essentially Debian 6.0.5) with 2 NICs.
When both NICs are up I have occasional network problem (hanging and
lagging). Bringing one NIC down resolves the problem. I've never bothered
to track down why this is. Maybe someone can enlighten me. I'd like this to
change because...

2. I'd like to bind that second NIC to Virtualbox's bridged networking
only. So that the host (crunchbang) only uses eth0, and the pfsense
firewall I have in vbox has it's external NIC tied to eth1 (internal NIC is
running on the internal intnet). Is there some knowledge someone can share
to do this? Point me in a direction, maybe?

Erik Hanson

=============================================================== From: Joe Freeman ------------------------------------------------------ would need to see ifconfig and netstat -rn output, but it's possible that both nics are on the same network and the ip stack isn't handling that well. I've seen this with lots of machines with NICs that aren't setup with some type of Link Agg on the ports.

=============================================================== From: Erik Hanson ------------------------------------------------------ Sure leprkhn@crunchie:~/downloads$ sudo ifconfig -a eth0 Link encap:Ethernet HWaddr 00:24:21:da:64:ad inet addr:192.168.0.187 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::224:21ff:feda:64ad/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:512905 errors:0 dropped:0 overruns:0 frame:0 TX packets:296173 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:676173919 (644.8 MiB) TX bytes:26763975 (25.5 MiB) Interrupt:45 Base address:0xa000 eth1 Link encap:Ethernet HWaddr 00:24:21:da:64:ac inet addr:192.168.0.189 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::224:21ff:feda:64ac/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1858411 errors:0 dropped:0 overruns:0 frame:0 TX packets:1188358 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1934499744 (1.8 GiB) TX bytes:129032171 (123.0 MiB) Interrupt:46 Base address:0xe000 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:21880985 errors:0 dropped:0 overruns:0 frame:0 TX packets:21880985 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:5008623466 (4.6 GiB) TX bytes:5008623466 (4.6 GiB) pan0 Link encap:Ethernet HWaddr 06:fa:04:ca:1b:f2 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:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) vboxnet0 Link encap:Ethernet HWaddr 0a:00:27:00:00:00 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) leprkhn@crunchie:~/downloads$ sudo netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 192.168.0.2 0.0.0.0 UG 0 0 0 eth0 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1

=============================================================== From: Randy Yates ------------------------------------------------------ This is a complete shot in the dark, but I had some Linux NIC issues with a certain version of the RealTek network drivers in at least one Debian-based distribution. This probably isn't your issue, but just for grins, what is the device?

=============================================================== From: Erik Hanson ------------------------------------------------------ Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03)

=============================================================== From: Erik Hanson ------------------------------------------------------ Both NICs are identical, onboard.

=============================================================== From: Randy Yates ------------------------------------------------------ The RTL8111/8169 drivers in the newer kernels is broke. Be forewarned about that. In order to fix it, I had to compile and force it to use the 8168 driver. So that's definitely not your problem. I've not messed the ipv6 much, but should those ipv6 addresses be the same on those two NICs?

=============================================================== From: Randy Yates ------------------------------------------------------ Scratch that last remark. I see my error. They are different. -- Google reads my email!