7 Nov
2011
7 Nov
'11
7:30 a.m.
This happened to me, when I added the new ip address with the wrong
subnet mask. Just double check you added the new ip with the correct
subnet mask, ie. a /21 instead of a /23 like the old IPs were on.
I haven't rebooted my VPS yet, but it is working on the new ips and
new default route.
root@ares:~# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
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
state UP qlen 1000
link/ether 00:16:5e:00:02:b3 brd ff:ff:ff:ff:ff:ff
inet 212.13.194.167/23 brd 212.13.195.255 scope global eth0
inet 85.119.82.167/21 scope global eth0
inet6 2001:ba8:1f1:f24c::2/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::216:5eff:fe00:2b3/64 scope link
valid_lft forever preferred_lft forever
root@ares:~# ip route
212.13.194.0/23 dev eth0 proto kernel scope link src 212.13.194.167
85.119.80.0/21 dev eth0 proto kernel scope link src 85.119.82.167
default via 85.119.80.1 dev eth0
default via 212.13.194.1 dev eth0 metric 100
On Sun, Nov 6, 2011 at 4:06 PM, S P <sundancecloud(a)gmail.com> wrote:
Hello All,
I'm following instructions on the wiki to move to a new IP 4 address.
# ip route change default via 85.119.80.1
RTNETLINK answers: No such file or directory
This is on Ubuntu Lucid.
Has anyone else seen this ... Can you recommend a solution?
Thanks,
Sandy
PS: It may have something to with adding modules to the kernel, but I can't
find a clear answer on google.
On Fri, Nov 4, 2011 at 6:18 PM, Andy Smith <andy(a)bitfolk.com> wrote:
Dear customer,
[ Apologies if you've received duplicate copies of this email;
we felt it was of sufficient importance to send direct to the
contacts for each account. ]
If you've been following our mailing lists you'll know that the time
has come where we need you to change the IP address(es) associated
with your VPS.
Basically:
- For each IP address on your VPS you need to enable a new address,
which has already been routed to you.
- You then need to reconfigure your services to use only the new IP
addresses.
- Finally you need to disable the old IP addresses.
Full information on what you need to do can be found here:
https://tools.bitfolk.com/wiki/Renumbering_for_customers
The next time you need to reboot your VPS you should take care to
instead shut it down and boot it again from your Xen Shell,
otherwise you will lose the routes to the new IP addresses that have
been added.
The old IP addresses will be disabled approximately *three months*
from now, so if you don't make these changes before then YOU WILL
EXPERIENCE A LOSS OF SERVICE.
Therefore if you have any questions please do not hesitate to ask,
preferably on our users list:
https://lists.bitfolk.com/mailman/listinfo/users
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
_______________________________________________
users mailing list
users(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/users
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEAREDAAYFAk60ZLIACgkQIJm2TL8VSQt8KgCbBZsQdCUV3jrx5o8m7p4jncZX
bOQAoMP9LqgvyOYI82BPdluSXvmeuRwK
=hE8N
-----END PGP SIGNATURE-----