Home » General » Support » [SOLVED] Routing problem in VE
| Re: Routing problem in VE [message #13077 is a reply to message #13068] |
Fri, 18 May 2007 14:37   |
 |
wilf
Messages: 30
Registered: January 2007
Location: UK
|
Member |
|
|
Hi Roman,
| Quote: |
I have couple questions for you:
Why you use default gw 192.0.2.1 at VE-LIVE? is it principled?
|
it's nothing to do with me - VE-LIVE:/etc/conf.d/net is created during vzctl start 201 by the function setup_network() in /etc/vz/disfiles/scripts/gentoo-add_ip.sh, which picks up FAKEGATEWAY=192.0.2.1 and FAKEGATEWAYNET=192.0.2.0 from /etc/vz/disfiles/scripts/functions.
| Quote: |
Could you please test VE-LIVE
with default gw 10.0.253.72
|
traceroute's output after change:-
BASE-INSTANCE ~ # vzctl enter 201
entered into VE 201
VE-LIVE / # route del -net 0.0.0.0
VE-LIVE / # route add 10.0.253.72/32 dev venet0
VE-LIVE / # route add default gw 10.0.253.72
VE-LIVE / # traceroute 10.1.4.191
traceroute to east (10.1.4.191), 30 hops max, 46 byte packets
1 10.0.253.72 (10.0.253.72) 0.072 ms 0.017 ms 0.012 ms
2 * * *
VE-LIVE / # traceroute 10.1.4.192
traceroute to 10.1.4.192 (10.1.4.192), 30 hops max, 46 byte packets
1 10.0.253.72 (10.0.253.72) 0.024 ms 0.014 ms 0.011 ms
2 * * *
3 *
VE-LIVE / # traceroute 10.1.1.191
traceroute to central (10.1.1.191), 30 hops max, 46 byte packets
1 10.0.253.72 (10.0.253.72) 0.041 ms 0.025 ms 0.011 ms
2 10.0.254.3 (10.0.254.3) 0.328 ms 0.349 ms 0.323 ms
3 central (10.1.1.191) 0.795 ms 0.776 ms 0.599 ms
VE-LIVE / # traceroute 10.1.1.192
traceroute to 10.1.1.192 (10.1.1.192), 30 hops max, 46 byte packets
1 10.0.253.72 (10.0.253.72) 0.028 ms 0.015 ms 0.012 ms
2 10.0.254.3 (10.0.254.3) 0.374 ms 0.340 ms 0.304 ms
3 10.1.1.192 (10.1.1.192) 0.681 ms 0.591 ms 0.629 ms
VE-LIVE / # traceroute 10.200.6.1
traceroute to 10.200.6.1 (10.200.6.1), 30 hops max, 46 byte packets
1 10.0.253.72 (10.0.253.72) 0.028 ms 0.020 ms 0.012 ms
2 10.0.254.3 (10.0.254.3) 0.663 ms 0.370 ms 0.325 ms
3 10.1.253.74 (10.1.253.74) 0.650 ms 0.513 ms 0.437 ms
4 * * *
VE-LIVE / # ping 10.200.6.1
PING 10.200.6.1 (10.200.6.1) 56(84) bytes of data.
64 bytes from 10.200.6.1: icmp_seq=1 ttl=252 time=0.868 ms
From 10.0.254.2: icmp_seq=2 Redirect Network(New nexthop: 10.0.254.3)
64 bytes from 10.200.6.1: icmp_seq=2 ttl=252 time=0.787 ms
--- 10.200.6.1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1000ms
rtt min/avg/max/mdev = 0.787/0.827/0.868/0.049 ms
VE-LIVE / # exit
logout
exited from VE 201 BASE-INSTANCE ~ # iptables -t nat -A POSTROUTING -j SNAT -s 10.0.253.133/32 --to-source 10.0.253.72
BASE-INSTANCE ~ # traceroute 10.1.4.191
traceroute to 10.1.4.191 (10.1.4.191), 30 hops max, 46 byte packets
1 10.0.254.2 (10.0.254.2) 0.237 ms 0.187 ms 0.186 ms
2 10.1.4.191 (10.1.4.191) 0.517 ms 0.455 ms 0.454 ms
BASE-INSTANCE ~ # traceroute 10.1.4.192
traceroute to 10.1.4.192 (10.1.4.192), 30 hops max, 46 byte packets
1 10.0.254.2 (10.0.254.2) 0.269 ms 0.189 ms 0.184 ms
2 10.1.4.192 (10.1.4.192) 0.564 ms 0.448 ms 0.445 ms
BASE-INSTANCE ~ # traceroute 10.1.1.191
traceroute to 10.1.1.191 (10.1.1.191), 30 hops max, 46 byte packets
1 10.0.254.2 (10.0.254.2) 0.311 ms 0.183 ms 0.172 ms
2 10.0.254.3 (10.0.254.3) 0.306 ms 0.275 ms 0.289 ms
3 10.1.1.191 (10.1.1.191) 0.721 ms 0.560 ms 0.502 ms
BASE-INSTANCE ~ # traceroute 10.1.1.192
traceroute to 10.1.1.192 (10.1.1.192), 30 hops max, 46 byte packets
1 10.0.254.2 (10.0.254.2) 0.365 ms 0.198 ms 0.195 ms
2 10.0.254.3 (10.0.254.3) 0.314 ms 0.294 ms 0.317 ms
3 10.1.1.192 (10.1.1.192) 0.644 ms 0.606 ms 0.517 ms
BASE-INSTANCE ~ # traceroute 10.200.6.1
traceroute to 10.200.6.1 (10.200.6.1), 30 hops max, 46 byte packets
1 10.0.254.2 (10.0.254.2) 0.390 ms 0.204 ms 0.183 ms
2 10.0.254.3 (10.0.254.3) 0.308 ms 0.291 ms 0.323 ms
3 10.1.253.74 (10.1.253.74) 0.651 ms 0.498 ms 0.480 ms
4 * * *
BASE-INSTANCE ~ # ping 10.200.6.1
PING 10.200.6.1 (10.200.6.1) 56(84) bytes of data.
64 bytes from 10.200.6.1: icmp_seq=1 ttl=253 time=0.877 ms
From 10.0.254.2: icmp_seq=2 Redirect Network(New nexthop: 10.0.254.3)
64 bytes from 10.200.6.1: icmp_seq=2 ttl=253 time=0.794 ms
--- 10.200.6.1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1000ms
rtt min/avg/max/mdev = 0.794/0.835/0.877/0.050 ms BASE-INSTANCE ~ # vzctl enter 201
entered into VE 201
VE-LIVE / #
VE-LIVE / # traceroute 10.1.4.191
traceroute to east (10.1.4.191), 30 hops max, 46 byte packets
1 10.0.253.72 (10.0.253.72) 0.032 ms 0.025 ms 0.011 ms
2 * * *
VE-LIVE / # traceroute 10.1.4.192
traceroute to 10.1.4.192 (10.1.4.192), 30 hops max, 46 byte packets
1 10.0.253.72 (10.0.253.72) 0.020 ms 0.024 ms 0.012 ms
2 * * *
VE-LIVE / # traceroute 10.1.1.191
traceroute to central (10.1.1.191), 30 hops max, 46 byte packets
1 10.0.253.72 (10.0.253.72) 0.036 ms 0.028 ms 0.012 ms
2 10.0.254.3 (10.0.254.3) 0.403 ms 0.274 ms 0.284 ms
3 central (10.1.1.191) 0.632 ms 0.500 ms 0.607 ms
VE-LIVE / # traceroute 10.1.1.192
traceroute to 10.1.1.192 (10.1.1.192), 30 hops max, 46 byte packets
1 10.0.253.72 (10.0.253.72) 0.018 ms 0.018 ms 0.011 ms
2 10.0.254.3 (10.0.254.3) 0.392 ms 0.355 ms 0.303 ms
3 10.1.1.192 (10.1.1.192) 0.652 ms 0.612 ms 0.529 ms
VE-LIVE / # traceroute 10.200.6.1
traceroute to 10.200.6.1 (10.200.6.1), 30 hops max, 46 byte packets
1 10.0.253.72 (10.0.253.72) 0.021 ms 0.016 ms 0.011 ms
2 10.0.254.3 (10.0.254.3) 0.393 ms 0.351 ms 0.341 ms
3 10.1.253.74 (10.1.253.74) 0.668 ms 0.484 ms 0.484 ms
4 * * *
VE-LIVE / # ping !$
ping 10.200.6.1
PING 10.200.6.1 (10.200.6.1) 56(84) bytes of data.
64 bytes from 10.200.6.1: icmp_seq=1 ttl=252 time=1.02 ms
64 bytes from 10.200.6.1: icmp_seq=2 ttl=252 time=0.750 ms
--- 10.200.6.1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 999ms
rtt min/avg/max/mdev = 0.750/0.887/1.025/0.140 ms
I hope that tells you something 
Best Regards, Paul.
|
|
|
|
 |
|
[SOLVED] Routing problem in VE
By: wilf on Wed, 16 May 2007 23:39 |
|
|
Re: Routing problem in VE
By: morik on Thu, 17 May 2007 11:16 |
|
|
Re: Routing problem in VE
By: wilf on Thu, 17 May 2007 11:27 |
|
|
Re: Routing problem in VE
By: morik on Thu, 17 May 2007 12:10 |
|
|
Re: Routing problem in VE
By: wilf on Thu, 17 May 2007 13:00 |
|
|
Re: Routing problem in VE
By: morik on Fri, 18 May 2007 08:19 |
|
|
Re: Routing problem in VE
By: wilf on Fri, 18 May 2007 10:52 |
|
|
Re: Routing problem in VE
By: morik on Fri, 18 May 2007 12:04 |
|
|
Re: Routing problem in VE
By: wilf on Fri, 18 May 2007 14:37 |
|
|
Re: Routing problem in VE
By: morik on Sat, 19 May 2007 07:11 |
|
|
Re: Routing problem in VE
By: wilf on Mon, 21 May 2007 10:23 |
Goto Forum:
Current Time: Fri Aug 29 22:59:29 GMT 2025
Total time taken to generate the page: 0.06046 seconds
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
