Extra IP routing problem?

[perlmonkee]

I purchased an additional IP for my VServer, and am having a problem putting it to use. Packets sent to my additional IP address get caught up in a host that seems to just juggle it for several bounces before the TTL of the packet is exceeded, then throws back an error. I've included a ping attempt for my non-working IP (from home), ifconfig information from the VServer, and a very interesting pair of traceroute outputs.

Is this a router problem? Or am I somehow doing something stupid?

Any help anyone is willing to offer would be greatly appreciated.

Example attempt to ping non working IP from home:
perlmonkee@kronos:~$ ping 207.210.74.252
PING 207.210.74.252 (207.210.74.252) 56(84) bytes of data.
From 72.9.242.247 icmp_seq=1 Time to live exceeded
From 72.9.242.247 icmp_seq=2 Time to live exceeded
From 72.9.242.247 icmp_seq=3 Time to live exceeded
From 72.9.242.247 icmp_seq=4 Time to live exceeded

ifconfig information on VServer:
eth0 Link encap:Ethernet HWaddr AA:00:00:43:95:E8
inet addr:207.210.77.242 Bcast:207.210.77.255 Mask:255.255.255.0
inet6 addr: fe80::a800:ff:fe43:95e8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:128168 errors:0 dropped:0 overruns:0 frame:0
TX packets:105029 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:22323498 (21.2 Mb) TX bytes:67147691 (64.0 Mb)

eth0:0 Link encap:Ethernet HWaddr AA:00:00:43:95:E8
inet addr:207.210.74.252 Bcast:207.210.74.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1



Traceroute to working (primary) IP:
traceroute to hubert.perlmonkee.com (207.210.77.242), 30 hops max, 38 byte packets
1 * * *
2 68.87.218.21 (68.87.218.21) 9.281 ms 8.738 ms 9.448 ms
3 68.87.216.49 (68.87.216.49) 13.630 ms 10.276 ms 9.138 ms
4 68.87.216.29 (68.87.216.29) 10.840 ms 14.877 ms 13.405 ms
5 12.119.199.25 (12.119.199.25) 26.535 ms 19.918 ms 11.975 ms
6 12.123.44.146 (12.123.44.146) 19.184 ms 14.349 ms 14.917 ms
7 12.123.44.177 (12.123.44.177) 12.585 ms 12.967 ms 11.610 ms
8 208.50.134.33 (208.50.134.33) 14.519 ms 13.804 ms 14.263 ms
9 so1-0-0-9953M.ar4.ATL1.gblx.net (67.17.68.234) 95.447 ms 96.500 ms 96.628 ms
10 206.41.25.230 (206.41.25.230) 92.063 ms 87.872 ms 87.843 ms
11 209.51.149.105 (209.51.149.105) 287.197 ms 211.992 ms 246.573 ms
12 gig0-1.l3-atl-1.gnax.net (209.51.131.6) 88.352 ms 90.415 ms 87.549 ms
13 209.51.131.102 (209.51.131.102) 89.071 ms 93.481 ms 97.344 ms
14 72.9.242.247 (72.9.242.247) 88.885 ms 88.237 ms 90.694 ms
15 hubert.perlmonkee.com (207.210.77.242) 92.323 ms 87.937 ms 88.431 ms


Crazy traceroute to additional (non-working) IP:
traceroute to 207.210.74.252 (207.210.74.252), 30 hops max, 38 byte packets
1 * * *
2 68.87.218.21 (68.87.218.21) 9.048 ms 9.183 ms 9.985 ms
3 68.87.216.49 (68.87.216.49) 11.179 ms 26.935 ms 9.398 ms
4 68.87.216.29 (68.87.216.29) 11.213 ms 8.691 ms 9.309 ms
5 12.119.199.29 (12.119.199.29) 13.098 ms 14.261 ms 13.217 ms
6 12.123.44.150 (12.123.44.150) 14.636 ms 15.459 ms 15.587 ms
7 ggr1-p3100.st6wa.ip.att.net (12.123.44.133) 12.970 ms 14.365 ms 14.153 ms
8 so0-2-0-622M.ar2.SEA1.gblx.net (208.51.243.37) 17.872 ms 18.180 ms 30.132 ms
9 so1-0-0-9953M.ar4.ATL1.gblx.net (67.17.68.234) 97.409 ms 96.504 ms 96.157 ms
10 206.41.25.230 (206.41.25.230) 87.665 ms 89.412 ms 90.173 ms
11 209.51.149.105 (209.51.149.105) 89.064 ms 88.013 ms 96.177 ms
12 gig0-1.l3-atl-1.gnax.net (209.51.131.6) 93.602 ms 87.320 ms 88.734 ms
13 209.51.131.102 (209.51.131.102) 88.875 ms 89.327 ms 89.343 ms
14 72.9.242.247 (72.9.242.247) 406.838 ms 89.100 ms 89.341 ms
15 72.9.242.247 (72.9.242.247) 89.599 ms 102.282 ms 88.937 ms
16 * 72.9.242.247 (72.9.242.247) 90.083 ms 88.486 ms
17 72.9.242.247 (72.9.242.247) 88.249 ms 87.880 ms 90.119 ms
18 72.9.242.247 (72.9.242.247) 88.474 ms 89.320 ms *
19 72.9.242.247 (72.9.242.247) 89.562 ms 88.109 ms *
20 72.9.242.247 (72.9.242.247) 89.855 ms 89.200 ms 89.963 ms
21 72.9.242.247 (72.9.242.247) 91.867 ms 88.869 ms 88.386 ms
22 * 72.9.242.247 (72.9.242.247) 89.210 ms 89.801 ms
23 72.9.242.247 (72.9.242.247) 106.410 ms 90.822 ms 88.551 ms
24 72.9.242.247 (72.9.242.247) 88.040 ms * 90.125 ms
25 72.9.242.247 (72.9.242.247) 87.722 ms 89.017 ms 89.217 ms
26 72.9.242.247 (72.9.242.247) 88.290 ms 89.160 ms *
27 72.9.242.247 (72.9.242.247) 89.226 ms 88.635 ms 88.493 ms
28 72.9.242.247 (72.9.242.247) 88.723 ms 88.835 ms 87.328 ms
29 * 72.9.242.247 (72.9.242.247) 89.491 ms 89.152 ms
30 72.9.242.247 (72.9.242.247) 88.216 ms 88.790 ms 89.112 ms

[matta]

Make sure you reboot your VM via Teknic so the proper route gets added on the host.

[perlmonkee]

Can you explain to me why this is the way it is?
What happens when my server is booted that makes your router start sending packets to it properly? Is there any way to trigger this without rebooting?
It's done, and working, I'm just curious.

[matta]

The IP needs to be routed through your vif (virtual network interface). Technically when an IP is added to your config we could have it find out which vif is yours and add the route manually, but for now a reboot needs to be done to add the routes.