kernel 2.6.32-53 - Brakes internet help

[hikari]

Good day.
I was wondering if anyone can lend a hand.
When switch to kernel 2.6.32-53 it seems my connection to the internet stops not sure why?
ie I can ping yahoo.com it resolves and times out. However I can ping and connect to machine on the local network including SSH backhand forth.
Now if I switch back to Kernel 2.6.24-16 everything works fine.

Am I missing something very basic here?

Thanks in advance..


Current status: 0 updates [-45].
vmserver:/home/thomasfraley# pveversion -v
pve-manager: 1.9-26 (pve-manager/1.9/6567)
running kernel: 2.6.24-8-pve
proxmox-ve-2.6.32: 1.9-53
pve-kernel-2.6.32-6-pve: 2.6.32-53
pve-kernel-2.6.24-8-pve: 2.6.24-16
qemu-server: 1.1-32
pve-firmware: 1.0-14
libpve-storage-perl: 1.0-19
vncterm: 0.9-2
vzctl: 3.0.29-3pve1
vzdump: 1.2-16
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.15.0-2
ksm-control-daemon: 1.0-6

 

[tom]

you run an very old kernel "running kernel: 2.6.24-8-pve" and not 2.6.32-53. you installed it but you booted the old one. make sure you reboot into the right kernel!

 

[hikari]

you run an very old kernel "running kernel: 2.6.24-8-pve" and not 2.6.32-53. you installed it but you booted the old one. make sure you reboot into the right kernel!

Tom Thanks for getting back to me so fast.

Yes I understand that I booted the old kernel thats the point. Other wise I can't reach the internet.

When I boot the new kernel I can NOT reach the ineternet this is what I was asking for help for.

any suggestions on what it could be?

 

[udo]

Tom Thanks for getting back to me so fast.

Yes I understand that I booted the old kernel thats the point. Other wise I can't reach the internet.

When I boot the new kernel I can NOT reach the ineternet this is what I was asking for help for.

any suggestions on what it could be?

Hi,
try to download this version: http://download.proxmox.com/debian/...4/pve-kernel-2.6.32-6-pve_2.6.32-47_amd64.deb
and install with dpkg -i
Perhaps you have than network.

Have you checked if your network-device are renumbering from udev?
Look with

ifconfig -a
dmesg | grep eth
cat [U]/etc/udev/rules.d/70-persistent-net.rules

Udo
[/U]

 

[hikari]

udo,

Here is the output. Thinks look fine to me

Linux vmserver 2.6.32-6-pve #1 SMP Thu Nov 24 06:35:39 CET 2011 x86_64


The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.


Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
You have new mail.
Last login: Fri Dec 16 10:55:23 2011 from office.homeip.net
thomas@vmserver:~$ su
Password: 
vmserver:/home/thomas# pveversion -v
pve-manager: 1.9-26 (pve-manager/1.9/6567)
running kernel: 2.6.32-6-pve
proxmox-ve-2.6.32: 1.9-53
pve-kernel-2.6.32-6-pve: 2.6.32-53
pve-kernel-2.6.24-8-pve: 2.6.24-16
qemu-server: 1.1-32
pve-firmware: 1.0-14
libpve-storage-perl: 1.0-19
vncterm: 0.9-2
vzctl: 3.0.29-3pve1
vzdump: 1.2-16
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.15.0-2
ksm-control-daemon: 1.0-6
vmserver:/home/thomas# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 40:XX:XX:XX:2d 
          inet addr:192.168.70.185  Bcast:192.168.70.255  Mask:255.255.255.0
          inet6 addr: fe80::XXXX:XXXX:XXXX:422d/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:438 errors:0 dropped:0 overruns:0 frame:0
          TX packets:361 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:64217 (62.7 KiB)  TX bytes:45569 (44.5 KiB)
          Interrupt:29 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:8 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:560 (560.0 B)  TX bytes:560 (560.0 B)


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 40:XX:XX:XX:2d  
          inet addr:192.168.70.185  Bcast:192.168.70.255  Mask:255.255.255.0
          inet6 addr: fe80::XXXX:XXXX:XXXX:422d/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:419 errors:0 dropped:0 overruns:0 frame:0
          TX packets:278 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:56441 (55.1 KiB)  TX bytes:31135 (30.4 KiB)


vmserver:/home/thomas# dmesg | grep eth
eth0: RTL8168d/8111d at 0xffffc90000c7e000, 40:XX:XX:XX:2d, XID 081000c0 IRQ 29
r8169 0000:03:00.0: eth0: link up
r8169 0000:03:00.0: eth0: link up
device eth0 entered promiscuous mode
vmbr0: port 1(eth0) entering forwarding state
eth0: no IPv6 routers present
eth0: no IPv6 routers present
vmserver:/home/thomas# cat /etc/udev/rules.d/70-persistent-net.rules
# This file was automatically generated by the /lib/udev/write_net_rules
# program run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single line.


# PCI device 0x10ec:0x8168 (r8169)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="40:XX:XX:XX:2d", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
vmserver:/home/thomas#

Example.
Trying to ping yahoo.com - It resolved and time out
Office.homeip.net is another local computer and works fine

vmserver:/home/thomas# ping yahoo.com
PING yahoo.com (209.191.122.70) 56(84) bytes of data.
^C
--- yahoo.com ping statistics ---
7 packets transmitted, 0 received, 100% packet loss, time 5999ms


vmserver:/home/thomas# ping office.homeip.net
PING office.homeip.net (192.168.70.190) 56(84) bytes of data.
64 bytes from office.homeip.net (192.168.70.190): icmp_seq=1 ttl=64 time=0.750 ms
64 bytes from office.homeip.net (192.168.70.190): icmp_seq=2 ttl=64 time=0.408 ms
64 bytes from office.homeip.net (192.168.70.190): icmp_seq=3 ttl=64 time=0.390 ms
^C
--- office.homeip.net ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 0.390/0.516/0.750/0.165 ms
vmserver:/home/thomas#

Not sure about the pve-kernel-2.6.32-6-pve_2.6.32-47_amd64.deb but will give it a try.

 

[udo]

Hi,
why do you have for eth0 and vmbr0 an ip-config?
normaly there is no ip on eth0 and all ip-configuration is on vmbr0 (address, netmask, default-gateway).
Only for some "hosting"-solution (not clean in my eyes) is this nessesary.

I guess that something wrong to reach the default gateway (internal works). Look with "ip route" and tcpdump.

Udo

 

[hikari]

Ok looking at the routing it could be something here - ( I thought routing would be left alone with the kernel update)

Ok here is network interface config

# network interface settings
auto lo
iface lo inet loopback


auto eth0
iface eth0 inet dhcp  


auto vmbr0
iface vmbr0 inet static
        address  192.168.70.185
        netmask  255.255.255.0
        gateway  192.168.70.1
        bridge_ports eth0
        bridge_stp off
        bridge_fd 0

Now looking at the route (router ip is 192.168.70.1 - untangle.homeip.net) seems the domain name is missing .net at the end this could be the issue

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.70.0    *               255.255.255.0   U     0      0        0 vmbr0
default         untangle.homeip 0.0.0.0         UG    0      0        0 vmbr0
vmserver:/home/thomasfraley#

However Ip route looks fine

ip route
192.168.70.0/24 dev vmbr0  proto kernel  scope link  src 192.168.70.185 
default via 192.168.70.1 dev vmbr0

tcpdump

vmserver:/home/thomas# tcpdump
tcpdump: WARNING: eth0: no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
13:37:01.716744 IP vmserver..ssh > MBP.homeip.net.55917: P 1423590649:1423590889(240) ack 1112112194 win 145 <nop,nop,timestamp 2587749 944866764>
13:37:01.717041 IP vmserver..42101 > untangle.homeip.net.domain: 43630+ PTR? 199.70.168.192.in-addr.arpa. (45)
13:37:01.717493 IP untangle.homeip.net.domain > vmserver..42101: 43630* 1/0/0 (73)
13:37:01.717653 IP vmserver..54923 > untangle.homeip.net.domain: 49740+ PTR? 1.70.168.192.in-addr.arpa. (43)
13:37:01.717699 IP vmserver..ssh > MBP.homeip.net.55917: P 240:432(192) ack 1 win 145 <nop,nop,timestamp 2587750 944866764>
13:37:01.717716 IP MBP.homeip.net.55917 > vmserver..ssh: . ack 240 win 33184 <nop,nop,timestamp 944866884 2587749>
13:37:01.717987 IP untangle.homeip.net.domain > vmserver..54923: 49740* 1/0/0 (76)

udo
thanks so much for lending a hand with this.

 

[hikari]

Thanks. managed to get it working.
Not sure exactly what did it but change eth0 to static and manually entered everything in and it worked.
Just strange because dhcp is setup on the older kernel.
My router is set up to give it a static IP via DHCP have not touched it.

Any how its working. thanks for your help again...

 

[udo]

Ok looking at the routing it could be something here - ( I thought routing would be left alone with the kernel update)

Ok here is network interface config

# network interface settings
auto lo
iface lo inet loopback


auto eth0
iface eth0 inet dhcp  


auto vmbr0
iface vmbr0 inet static
        address  192.168.70.185
        netmask  255.255.255.0
        gateway  192.168.70.1
        bridge_ports eth0
        bridge_stp off
        bridge_fd 0

...

Hi,
try "iface eth0 inet manual" instead of dhcp please.

And your tcp-dump show only traffic related to your ssh-session to the host.
Try directly from console (on one console an ping) "tcpdump -n -i vmbr0 | grep 192.168.70.185"

Udo

 

[udo]

fine - i will go sleep...