|
|
|
|
|
|
|
|
| Re: Network Problem [message #33852 is a reply to message #33851] |
Fri, 14 November 2008 19:31   |
pooyan
Messages: 3
Registered: November 2008
Location: Iran
|
Junior Member |
|
|
1.it is a valid address and I have this range from 83.147.250.1 to 83.147.250.255 expect 83.147.250.2 as the gateway and 83.147.250.16 as my DNS server and i have set 83.147.250.190 for my HN and it is working from outside and i control it by SSH.
2.yes it is able to ping 83.147.250.101 from inside of the HN.
ping 83.147.250.101
PING 83.147.250.101 (83.147.250.101) 56(84) bytes of data.
64 bytes from 83.147.250.101: icmp_seq=1 ttl=64 time=0.160 ms
64 bytes from 83.147.250.101: icmp_seq=2 ttl=64 time=0.111 ms
64 bytes from 83.147.250.101: icmp_seq=3 ttl=64 time=0.108 ms
64 bytes from 83.147.250.101: icmp_seq=4 ttl=64 time=0.109 ms
3.iptables -L
sudo iptables -L
[sudo] password for pooyan:
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
4.ping 83.147.250.101
Pinging 83.147.250.101 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 83.147.250.101:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
5.I don't know how to it 
6.From HN
----root@ubuntu:/home/pooyan# ip a l
1: lo: <LOOPBACK,UP,LOWER_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 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:17:9a:78:57:5e brd ff:ff:ff:ff:ff:ff
inet 83.147.250.190/23 brd 83.147.251.255 scope global eth0
inet6 fe80::217:9aff:fe78:575e/64 scope link
valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
link/ether 00:15:e9:82:69:10 brd ff:ff:ff:ff:ff:ff
4: venet0: <BROADCAST,POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue
link/void
----root@ubuntu:/home/pooyan# ip rule list
0: from all lookup local
32766: from all lookup main
32767: from all lookup default
----root@ubuntu:/home/pooyan# ip r l
192.168.2.1 dev venet0 scope link
83.147.250.101 dev venet0 scope link
83.147.250.0/23 dev eth0 proto kernel scope link src 83.147.250.190
default via 83.147.250.2 dev eth0 metric 100
From Ve It self
-----[root@ubuntu ~]# ip a l
1: lo: <LOOPBACK,UP,10000> 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 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: venet0: <BROADCAST,POINTOPOINT,NOARP,UP,10000> mtu 1500 qdisc noqueue
link/void
inet 127.0.0.1/32 scope host venet0
inet 192.168.2.1/32 brd 192.168.2.1 scope global venet0:0
inet 83.147.250.101/32 brd 83.147.250.101 scope global venet0:1
inet 192.168.2.2/32 brd 192.168.2.2 scope global venet0:2
-----[root@ubuntu ~]# ip rule list
0: from all lookup local
32766: from all lookup main
32767: from all lookup default
----ip r l
192.0.2.0/24 dev venet0 scope host
169.254.0.0/16 dev venet0 scope link
default via 192.0.2.1 dev venet0
|
|
|
|
| Re: Network Problem [message #33860 is a reply to message #33852] |
Mon, 17 November 2008 07:36 |
maratrus
Messages: 1495
Registered: August 2007
Location: Moscow
|
Senior Member |
|
|
Hello,
I have a suspicion what could it be.
You have set several ip addresses to your VE and when a packet goes out of your VE it has to have a source ip address and it is set as "192.168.2.1". Of course, internet becomes unreachable.
Why do you need 192.168.2.1 and 192.168.2.2 ip addresses inside your VE?
To avoid this situation try to explicitly add appropriate routes inside VE for example:
# ip r del default
# ip r add 192.168.2.0/24 dev venet0 src 192.168.2.1
# ip r add default dev venet0 src 83.147.250.101
It's just an example. You can change it accordingly your purposes.
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
