DNS wont work and cant ping but it works... [message #27389] |
Sat, 16 February 2008 09:55 |
|
Alright all my VEs have the same problem. Basically i can ping and trace from my HN:
[root@monster ~]# ping google.com
PING google.com (64.233.167.99) 56(84) bytes of data.
64 bytes from py-in-f99.google.com (64.233.167.99): icmp_seq=1 ttl=247 time=59.7 ms
--- google.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 59.754/59.754/59.754/0.000 ms
[root@monster ~]#
now as soon as i go into any VE it wont find it at all. the VE itself is working on the web: boxstr.com but the dns isnt working and i cannot ping any site except the HN itself.
when i reset the network using service network restart:
[root@glimpse /]# service network restart
Shutting down interface venet0: [ OK ]
Shutting down loopback interface: [ OK ]
Setting network parameters: net.ipv4.ip_forward = 0
net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.default.accept_source_route = 0
error: unknown error 1 setting key 'kernel.sysrq'
error: unknown error 1 setting key 'kernel.core_uses_pid'
[FAILED]
Bringing up loopback interface: [ OK ]
Bringing up interface venet0: [ OK ]
[root@glimpse /]#
and the HN
[root@monster ~]# service network restart
Shutting down interface eth0: [ OK ]
Shutting down interface venet0: Shutting down interface venet0:
[ OK ]
Shutting down loopback interface: [ OK ]
Disabling IPv4 packet forwarding: net.ipv4.ip_forward = 0
[ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface eth0: [ OK ]
Bringing up interface venet0: Bringing up interface venet0:
Configuring interface venet0:
net.ipv4.conf.venet0.send_redirects = 0
[ OK ]
[root@monster ~]#
any ideas? let me know if you need anything else im using centos 5 64 bit on the HN and centos4 64bit on VE and it does the same thing on 32bit VE as well.
|
|
|
|
Re: DNS wont work and cant ping but it works... [message #27402 is a reply to message #27395] |
Sat, 16 February 2008 22:00 |
|
Vasily Tarasov wrote on Sat, 16 February 2008 14:56 | According to the output of your network init script on HN, it disables IP forwarding:
[root@monster ~]# service network restart
Shutting down interface eth0: [ OK ]
Shutting down interface venet0: Shutting down interface venet0: [ OK ]
Shutting down loopback interface: [ OK ]
Disabling IPv4 packet forwarding: net.ipv4.ip_forward = 0
It explains why you can't ping external nodes.
You can turn IP forwarding on by (on HN)
# sysctl net.ipv4.ip_forward=1
To make this change permanent use /etc/sysctl.conf file.
HTH,
Vasily
|
hi, that still didnt fix it. anything else? and the reason why it shut down ip_forwarding is because it was restarting the network. =1 is in my config file not =0
[Updated on: Sat, 16 February 2008 22:01] Report message to a moderator
|
|
|
|
|
|
|
Re: DNS wont work and cant ping but it works... [message #27465 is a reply to message #27464] |
Mon, 18 February 2008 10:00 |
|
alright i can now ping it was a weird ip issue so thats resolved. now i am running lighttpd and i have fcgi proxy for php requests and now i cannot get a connection to 127.0.0.1:9000 at all. it says connection timed out so basically my site cannot serve any type of files at all. lighttpd works because it serves static content like images but it wont work at all... its weird.. any idea?
|
|
|
|
|
|