OpenVZ Forum


Home » General » Support » Child can ping parent but can't access internet
Child can ping parent but can't access internet [message #36402] Tue, 16 June 2009 08:11 Go to next message
PeterPetrelli is currently offline  PeterPetrelli
Messages: 1
Registered: June 2009
Junior Member
On my parent host I can properly access the internet; ping and visit websites. However, the child is able to ping the parent but it can't access the internet. Any idea's?

ifconfig output on the child:
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: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)

venet0    Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet addr:127.0.0.1  P-t-P:127.0.0.1  Bcast:0.0.0.0  Mask:255.255.255.255
          UP BROADCAST POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:58 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:2900 (2.8 KiB)

venet0:0  Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet addr:192.168.0.128  P-t-P:192.168.0.128  Bcast:192.168.0.128  Mask:255.255.255.255
          UP BROADCAST POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1



This is the ifconfig output on the parent:
[root@localhost ~]# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:03:FF:85:2A:01
          inet addr:192.168.1.2  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::203:ffff:fe85:2a01/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2631 errors:5 dropped:0 overruns:0 frame:0
          TX packets:2923 errors:1 dropped:0 overruns:1 carrier:1
          collisions:0 txqueuelen:1000
          RX bytes:365055 (356.4 KiB)  TX bytes:2238525 (2.1 MiB)
          Interrupt:11 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:62691 errors:0 dropped:0 overruns:0 frame:0
          TX packets:62691 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:5987491 (5.7 MiB)  TX bytes:5987491 (5.7 MiB)


Some kernel information on the parent host:
Linux localhost.localdomain 2.6.18-92.el5 #1 SMP Tue Jun 10 18:49:47 EDT 2008 i686 i686 i386 GNU/Linux


Ping result on parent host:
[root@localhost ~]# ping -c 3 google.nl
PING google.nl (74.125.77.104) 56(84) bytes of data.
64 bytes from ew-in-f104.google.com (74.125.77.104): icmp_seq=1 ttl=55 time=15.9 ms
64 bytes from ew-in-f104.google.com (74.125.77.104): icmp_seq=2 ttl=55 time=3.76 ms
64 bytes from ew-in-f104.google.com (74.125.77.104): icmp_seq=3 ttl=55 time=17.1 ms

--- google.nl ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 24399ms rtt min/avg/max/mdev = 3.764/12.283/17.186/6.047 ms



Re: Child can ping parent but can't access internet [message #36404 is a reply to message #36402] Tue, 16 June 2009 11:55 Go to previous messageGo to next message
kir is currently offline  kir
Messages: 1645
Registered: August 2005
Location: Moscow, Russia
Senior Member

Do you have IP forwarding enabled?

Kir Kolyshkin
http://static.openvz.org/userbars/openvz-developer.png
Re: Child can ping parent but can't access internet [message #36406 is a reply to message #36402] Tue, 16 June 2009 12:26 Go to previous message
maratrus is currently offline  maratrus
Messages: 1495
Registered: August 2007
Location: Moscow
Senior Member
Hello,

there are plenty of questions devoted this problem.
It's a good idea searching through the forum because there is a big chance that you will be able to find out the reason of your problem.
Please, reread our wiki article
http://wiki.openvz.org/Venet
Perhaps, sysctl parameters are not set properly.
ifconfig output from the HN looks strange because venet0 interface should be set up to work properly. Service 'vz' sets it up so you may restart 'vz' service.
'uname -a' output looks more strange because OpenVZ kernels are not the pure RHEL5 kernel to which probably the provided output indicates.
A very helpful utility is 'tcpdump'. Try to ping anything from inside the VE and at the same moment run tcpdump utility on venet0 and eth0 interfaces (inside Ve and on the HN).
Previous Topic: Need help creating a template from an ISO
Next Topic: Does OpenVZ 'support' PERC6 or SAS6?
Goto Forum:
  


Current Time: Tue Apr 23 01:19:05 GMT 2024

Total time taken to generate the page: 0.01248 seconds