*SOLVED* How does OpenVZ pick traceroutes? [message #6802] |
Fri, 22 September 2006 19:48 |
dlzinc
Messages: 34 Registered: March 2006
|
Member |
|
|
Here's something interesting, how does OpenVZ pick what IP shows up in a traceroute from inside a VPS?
I have a server with the following setup:
eth0 = 192.168.0.1/255.255.255.0
lo = 127.0.0.1
lo:10 = 192.168.3.5/255.255.255.255
lo:11 = 172.21.1.1/255.255.255.255
router 192.168.0.254 (attached to eth0) is configured to route 192.168.3.0/24 and 172.21.1.0/29 to 192.168.0.1
arpsend is a symlink to /bin/true (another device "policies" arp announces for unknown ip addresses on eth0 that I haven't gotten removed yet) to avoid complaints, I know, not the best idea
everything works properly.
traceroutes from outside show 192.168.0.254, 192.168.0.1, then the VPS IP
traceroutes from a VPS show 192.168.3.5 then 192.168.0.254
I've tried adding a lo:9 (no difference)
I've tried having a VPS with only a 192.168.0.x IP (no change)
or only a 172.21.1.x IP (also no change)
So, out of pure curiosity.. how does OpenVZ decide which IP to show in a traceroute from a VPS in this case? It seems to pick it quite arbitrarily...
[Updated on: Fri, 29 September 2006 07:11] by Moderator Report message to a moderator
|
|
|
|