OpenVZ Forum: Support » VPS route prob

Home » General » Support » VPS route prob

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

VPS route prob [message #8436]

Mon, 20 November 2006 09:35

zwtint
Messages: 17
Registered: November 2006

Junior Member

Hello,

Im a newby in this topic and I have a problem with network configuration.

I cant reach my VPS from the "world"

init is running

ipv4 forward is on

root@server30444 [/vz/template/cache]# ip r l
83.170.73.235 dev eth0 scope link src 83.170.73.235
83.170.73.234 dev eth0 scope link src 83.170.73.234
83.170.73.232 dev venet0 scope link src 83.170.73.235
83.170.73.236 dev eth0 scope link src 83.170.73.236
83.170.73.128/26 dev eth0 proto kernel scope link src 83.170.73.143
83.170.73.0/24 dev eth0 proto kernel scope link src 83.170.73.232
169.254.0.0/16 dev eth0 scope link
default via 83.170.73.129 dev eth0
root@server30444 [/vz/template/cache]#

root@server30444 [/vz/template/cache]# ip a l
2: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
4: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:30:48:59:61:75 brd ff:ff:ff:ff:ff:ff
inet 83.170.73.143/26 brd 83.170.73.191 scope global eth0
inet 83.170.73.232/24 brd 83.170.73.255 scope global eth0:1
inet 83.170.73.233/24 brd 83.170.73.255 scope global secondary eth0:2
inet 83.170.73.234/24 brd 83.170.73.255 scope global secondary eth0:3
inet 83.170.73.235/24 brd 83.170.73.255 scope global secondary eth0:4
inet 83.170.73.236/24 brd 83.170.73.255 scope global secondary eth0:5
7: venet0: <BROADCAST,POINTOPOINT,NOARP,UP> mtu 1500 qdisc noqueue
link/void

the ip of the vps is 83.170.73.232

What should I modify to reach the vps outside the machine?

thank you

Report message to a moderator

Re: VPS route prob [message #8438 is a reply to message #8436]

Mon, 20 November 2006 09:54

Vasily Tarasov
Messages: 1345
Registered: January 2006

Senior Member

Hello,

What is in /proc/sys/net/ipv4/ip_forward file?

Thanks!

Report message to a moderator

Re: VPS route prob [message #8439 is a reply to message #8436]

Mon, 20 November 2006 10:03

zwtint
Messages: 17
Registered: November 2006

Junior Member

root@server30444 [/etc/vz]# cat /proc/sys/net/ipv4/ip_forward
1
root@server30444 [/etc/vz]#

Report message to a moderator

Re: VPS route prob [message #8441 is a reply to message #8439]

Mon, 20 November 2006 10:17

Vasily Tarasov
Messages: 1345
Registered: January 2006

Senior Member

Can you post output of
# ip r s 83.170.73.232
command on HN.

Also you say, that you can't reach VE from world. Can you ping VE from HN? Can you ping VE from your NET? Can VE ping HN, other servers?

Thanks.

Report message to a moderator

Re: VPS route prob [message #8442 is a reply to message #8436]

Mon, 20 November 2006 10:21

zwtint
Messages: 17
Registered: November 2006

Junior Member

root@server30444 [/etc/vz]# ip r s 83.170.73.232
83.170.73.232 dev venet0 scope link src 83.170.73.235
root@server30444 [/etc/vz]#

from VE:

-bash-3.00# ping google.com
ping: unknown host google.com
-bash-3.00# ping localhost
PING localhost.localdomain (127.0.0.1) 56(84) bytes of data.
64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=0 ttl=64 time=0.030 ms
64 bytes from localhost.localdomain (127.0.0.1): icmp_seq=1 ttl=64 time=0.023 ms

how can I try to ping VE from HN? Razz

When I enter 83.170.73.232 ip, its try to connect to HN, not to VE.

Report message to a moderator

Re: VPS route prob [message #8443 is a reply to message #8436]

Mon, 20 November 2006 10:23

zwtint
Messages: 17
Registered: November 2006

Junior Member

if I use the hostname of the HN for PING from VE, it says as for google.com

Report message to a moderator

Re: VPS route prob [message #8444 is a reply to message #8443]

Mon, 20 November 2006 10:29

Vasily Tarasov
Messages: 1345
Registered: January 2006

Senior Member

you can ping by name (google.com) only if nameserver for VE is set. Have you done it? (vzctl set <veid> --hostname your.dns.server)

Report message to a moderator

Re: VPS route prob [message #8445 is a reply to message #8436]

Mon, 20 November 2006 10:35

zwtint
Messages: 17
Registered: November 2006

Junior Member

-bash-3.00# ping 83.170.73.121
PING 83.170.73.121 (83.170.73.121) 56(84) bytes of data.

[1]+ Stopped ping 83.170.73.121
-bash-3.00# ping 83.170.73.141
PING 83.170.73.141 (83.170.73.141) 56(84) bytes of data.

[2]+ Stopped ping 83.170.73.141
-bash-3.00# ping 64.233.167.99
PING 64.233.167.99 (64.233.167.99) 56(84) bytes of data.

[3]+ Stopped ping 64.233.167.99
-bash-3.00#

ping not works, I waited for minutes, but nothing

Report message to a moderator

Re: VPS route prob [message #8446 is a reply to message #8445]

Mon, 20 November 2006 10:47

Vasily Tarasov
Messages: 1345
Registered: January 2006

Senior Member

Can you give an access to the node in question?

Report message to a moderator

Re: VPS route prob [message #8447 is a reply to message #8436]

Mon, 20 November 2006 10:49

zwtint
Messages: 17
Registered: November 2006

Junior Member

of course,

maybe can we talk any faster way? (msn,irc or smth)

Report message to a moderator

Re: VPS route prob [message #8448 is a reply to message #8447]

Mon, 20 November 2006 10:58

Vasily Tarasov
Messages: 1345
Registered: January 2006

Senior Member

Ok, then send me a PM with login, please.
My ICQ is available in contacts here at forum.

Report message to a moderator

Re: VPS route prob [message #8457 is a reply to message #8436]

Mon, 20 November 2006 12:36

cyborg
Messages: 1
Registered: November 2006

Junior Member

Hi
I have the same problem. As I understood the problem is that there is no default gw after VPS starts.

After some experements found that command "ip route add ..." which is used in "/etc/sysconfig/network-scripts/ifup-routes" isn't work.

-bash-3.1# ip route add 191.255.255.0/24 dev venet0 scope host
RTNETLINK answers: Operation not permitted

This is strange because command "route add" works fine.

I modify script ifup-routes to use this command and all start work.

But I think that there is other way to solve this problem. Smile

Report message to a moderator

Previous Topic:	SOLVED /proc pid number off-by-one? ... 2.6.18-028test003.1
Next Topic:	Services crashing inside of VE

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sat Apr 18 22:08:00 GMT 2026

Total time taken to generate the page: 0.51734 seconds