Slow, intermittent connection, maybe due to RTL8111/8168B

[103]

Recently our company acquired new machines, we decided to use one for a new Proxmox node. I successfully installed Proxmox 2.1, updated via Debian and Proxmox repositories. But when I want to use Web administration there was no connection, I issued ping, but no response, it seems that that occurs when I enter Proxmox Web administration. I searched threads related with this issue in the forums but no luck, the machine uses Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06), I tried to install the driver provided by Realtek but no luck either. I think there's a problem with the NIC, Proxmox 2.1 uses r8169 driver, I've tried other solutions unsuccessfully. I'm thinking of using different PCI NICs, but I want to solve this first if possible.

 

[dietmar]

Is it possible to login via ssh?

 

[103]

Is it possible to login via ssh?

Well, right now I can't check that, I'm not at work, but I observed the problem with a constant ping and there were response but for a certain amount of time it stopped, then it responded again, as I wrote in the title of this thread, the connection is intermittent. As I said in the last post I could update everything at the beggining using aptitude, but network is failing constantly, so I suspect that ssh login would be impossible. Soon I will check if it is possible to login via ssh.

Thanks for your answers and for this great software.

 

[103]

Is it possible to login via ssh?

No, it it not possible to login via SSH, I don't know what to do, I've reinstalled Proxmox 2.1 three times, 2.0 once, but the problem persist.

Edit: sorry, I could login via ssh, I didn't notice that the node was not connetced to the network.

 

[mastens]

Hi,

I experienced same problem with using the r8169 module, with the same NIC... Download drivers from Realtek.com.tw http://www.realtek.com.tw/downloads...d=5&Level=5&Conn=4&DownTypeID=3&GetDown=false
LINUX driver for kernel 3.x and 2.6.x and 2.4.x... (8.031.00)

Remember to blacklist the r8169 module, on boot...

echo "blacklist r8169" >> /etc/modprobe.d/blacklist.conf

and include the new module in initrd:

echo "r8168" >> /etc/initramfs-tools/modules

Last rebuild your initrd

update-initramfs -v -u -k `uname -r`

Then, you can do an reboot,
login to the box, check network module with lsmod ... r8168 should be loaded.

I belive this will help you out.

Marius

 

[103]

Well, I tried to do that, but I couldn't compile the driver, I don't know why, I installed build-essential, but there was an error while executing autoruns.sh with exactly that driver, no idea.

 

[mastens]

Well, maybe it helps trying again, and copy-past the results here?

 

[103]

This is the entire output:

make: *** /lib/modules/2.6.32-12-pve/build: No such file or directory. Stop.
make[1]: *** [clean] Error 2
make: *** [clean] Error 2

So, I create (forcing, just givin a try) /lib/modules/2.6.32-12-pve/build

And appeared this new line:

make[2]: *** No rule to make target 'clean'. Stop

I have installed build-essential and pve-headers

 

[mastens]

100% sure you have pve-headers-2.6.32-12-pve installed?

/lib/modules/2.6.32-12-pve/build is normaly linked to /usr/src/linux-headers-2.6.32-12-pve

 

[udo]

Recently our company acquired new machines, we decided to use one for a new Proxmox node. I successfully installed Proxmox 2.1, updated via Debian and Proxmox repositories. But when I want to use Web administration there was no connection, I issued ping, but no response, it seems that that occurs when I enter Proxmox Web administration. I searched threads related with this issue in the forums but no luck, the machine uses Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06), I tried to install the driver provided by Realtek but no luck either. I think there's a problem with the NIC, Proxmox 2.1 uses r8169 driver, I've tried other solutions unsuccessfully. I'm thinking of using different PCI NICs, but I want to solve this first if possible.

Hi,
to see if the issue depends on the rtl-nic post the output of following commands from the pve-host

dmesg | grep eth
ifconfig -a
brctl show
lspci | grep -i ethernet | awk '{ print "lspci -vs"$1}' | xargs -r0 sh -c

Udo

 

[sumsum]

Hello
I used the following howto,for compiling a working driver : http://wiki.hetzner.de/index.php/Installation_des_r8168-Treibers
Maybe it will help you
regards
tom

 

[103]

100% sure you have pve-headers-2.6.32-12-pve installed?

/lib/modules/2.6.32-12-pve/build is normaly linked to /usr/src/linux-headers-2.6.32-12-pve

Completely sure! maybe a reinstalation would fix the problem, thanks for the tips.

 

[103]

The output of the commands, this is when the network works.

dmesg | grep eth

eth0: RTL8168b/8111b at 0xffffc9000037c000, e0:69:95:e6:48:a0, XID 0c900800 IRQ 26
device eth0 entered promiscuous mode
r8169 0000:04:00.0: eth0: link up
r8169 0000:04:00.0: eth0: link up
vmbr: port 1(eth0) entering forwarding state
eth0: no IPv6 routers present

ifconfig -a

eth0 Link encap:Ethernet HWaddr e0:69:95:e6:48:a0
inet6 addr: fe80::e269:95ff:fee6:48a0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:17276 errors:0 dropped:0 overruns:0 frame:0
TX packets:13470 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3629541 (3.4 MiB) TX bytes:3818198 (3.6 MiB)
Interrupt:26 Base address:0xc000

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:22700 errors:0 dropped:0 overruns:0 frame:0
TX packets:22700 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3750026 (3.5 MiB) TX bytes:3750026 (3.5 MiB)

tap100i0 Link encap:Ethernet HWaddr f6:36:24:13:6e:e8
inet6 addr: fe80::f436:24ff:fe13:6ee8/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:53 errors:0 dropped:0 overruns:0 frame:0
TX packets:398 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:6666 (6.5 KiB) TX bytes:43179 (42.1 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 e0:69:95:e6:48:a0
inet addr:192.168.0.111 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::e269:95ff:fee6:48a0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:17223 errors:0 dropped:0 overruns:0 frame:0
TX packets:13395 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3385074 (3.2 MiB) TX bytes:3810056 (3.6 MiB)

brctl show

bridge name bridge id STP enabled interfaces
vmbr0 8000.e06995e648a0 no eth0
tap100i0

lspci | grep -i ethernet | awk '{ print "lspci -vs"$1}' | xargs -r0 sh -c

04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06)
Subsystem: Device 1b0a:0122
Flags: bus master, fast devsel, latency 0, IRQ 26
I/O ports at e000
Memory at d0004000 (64-bit, prefetchable) [size=4K]
Memory at d0000000 (64-bit, prefetchable) [size=16K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Endpoint, MSI 01
Capabilities: [b0] MSI-X: Enable- Count=4 Masked-
Capabilities: [d0] Vital Product Data
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Virtual Channel
Capabilities: [160] Device Serial Number 09-00-00-00-68-4c-e0-00
Kernel driver in use: r8169

 

[mastens]

I'm 99% sure, the module is bugged, any output in /var/log/syslog ?

Do an apt-get remove pve-headers-2.6.32-12-pve
Then: apt-get install pve-headers-2.6.32-12-pve

Marius