Hi,
In the earlier days of BitFolk I only had a /25 allocation of IP
addresses. That is, 212.13.194.0 -> 212.13.194.127. Some time ago
this was expanded to the full /24, i.e. 212.13.194.0 ->
212.13.194.255, but a number of you will still have the old network
settings.
Having the old settings right now is harmless, but in the near future I
will have to start using IPs from .128 and above. If you have the
old settings then you won't be able to talk to hosts in that range.
Here are some instructions on how to change the settings. You
should be able to do this without losing any network connectivity.
These instructions are for Debian/Ubuntu, so Centos and Gentoo folks
you are on your own unfortunately, but this isn't complicated -- I
believe the only Debian-specific bit is step 4.
1. Make sure you have access to your xen console in case anything
goes wrong.
2. MAKE SURE YOU HAVE ACCESS TO YOUR XEN CONSOLE IN CASE ANYTHING
GOES WRONG. REALLY. LOG IN AND CHECK.
If you can't get into your xen console then please put in a
support ticket to support@???, and don't try to do the
rest until I've fixed it for you. :)
3. Check that you actually need to do this. An example of a VPS
that needs to make a change:
$ ip ro
212.13.194.0/25 dev eth0 proto kernel scope link src 212.13.194.75
default via 212.13.194.1 dev eth0
Note the /25.
An example of a VPS that does not need to make any change:
$ ip ro
212.13.194.0/24 dev eth0 proto kernel scope link src 212.13.194.83
default via 212.13.194.1 dev eth0
Note the /24.
4. Fix your config file, /etc/network/interfaces. Here's an example
of the content before it is fixed:
----[ /etc/network/interfaces ]--------------------------------------
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
address 212.13.194.75
netmask 255.255.255.128
gateway 212.13.194.1
----[ /etc/network/interfaces ]--------------------------------------
Here's an example after fixing:
----[ /etc/network/interfaces ]--------------------------------------
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
address 212.13.194.75
netmask 255.255.255.0
gateway 212.13.194.1
----[ /etc/network/interfaces ]--------------------------------------
The only line changed is the netmask.
You should change this config file ready for the next boot, but
it won't alter your current settings.
5. Find your current IP address:
$ ip -4 addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue
inet 127.0.0.1/8 scope host lo
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000
inet 212.13.194.75/25 scope global eth0
In this example my IP address is 212.13.194.75.
6. Add it with the correct settings:
$ ip addr add 212.13.194.75/24 dev eth0
That should complete without error.
7. Remove the old one:
$ ip addr del 212.13.194.75/25 dev eth0
That should complete without error.
8. Check that your routing table is now correct:
$ ip ro
212.13.194.0/24 dev eth0 proto kernel scope link src 212.13.194.75
default via 212.13.194.1 dev eth0
That's it. You should not lose connectivity at any point during
this procedure.
If you're already using the /24 setup (anyone set up probably in the
last year, but do check) then you don't need to do anything.
If you have your own netblock routed to you then you don't need to
do anything.
If you have multiple IPs then your interfaces file might look a bit
like this:
----[ /etc/network/interfaces ]--------------------------------------
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
address 212.13.194.75
netmask 255.255.255.128
gateway 212.13.194.1
auto eth0:1
iface eth0:1 inet static
address 212.13.194.116
netmask 255.255.255.255
----[ /etc/network/interfaces ]--------------------------------------
The netmask of aliased IPs (et0:1, eth0:2, ...) does not need to
change. IP aliases on the same network as another interface are
supposed to be 255.255.255.255 netmask.
I would estimate that it will be a couple of weeks before I start
allocating IPs from the top half, and even then it will only be
other customers that you can't reach unless you make this change. I
don't know how long it will be before I put some infrastructure on
one of those IPs. I'm not planning to chase people over this
however. :)
If you have any questions please feel free to mail me on or offlist
about it before you do anything.
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
Encrypted mail welcome - keyid 0x604DE5DB
