View source for Renumbering out of 212.13.194.0/23

==Background==
BitFolk currently operates out of an IP address range assigned from its single upstream transit provider, [http://www.jump.net.uk/ Jump Networks]. This assignment has gradually grown from <tt>212.13.198.0/27</tt>, through a renumbering into <tt>212.13.194.0/24</tt> and then expanded to <tt>212.13.194.0/23</tt>.

The time is now long overdue for BitFolk to be using its own IP address allocation. This allows for independence from one transit/colo provider, as well as to make use of additional transit. BitFolk has been allocated [http://apps.db.ripe.net/whois/lookup/ripe/inetnum/85.119.80.0-85.119.87.255.html <tt>85.119.80.0/21</tt>] by [http://ripe.net/ RIPE] and is now in the process of renumbering into this space.

==Phase I: customer-facing infrastructure==
In general all infrastructure is going to renumber into <tt>85.119.80.0/23</tt> rather than being inter-mingled throughout the range with customer IPs.

===Currently in progress===
All complete.

===Completed===
If you're still using old IPs for these then you can expect that to stop working at any time.

We're not listing the things that are always used by host name (like web sites) and/or not customer-facing (e.g. spamd backend nodes).

====All dom0 (host) machines====

====All resolvers====

====NTP servers====
* [http://lists.bitfolk.com/lurker/message/20110911.044100.9a55e70c.en.html Announcement]
* Old IPs:
** 212.13.195.3
** 212.13.195.4
* New IPs:
** 85.119.80.232
** 85.119.80.233
* Typical places for customers to reference these IPs:
** <tt>restrict</tt> ACLs in '''/etc/ntp.conf'''
** Possibly firewall config
* Old IPs withdrawn from service: 2011-10-12

====Authoritative DNS server a.authns.bitfolk.com====
* [http://lists.bitfolk.com/lurker/message/20110917.204502.9b3ad0db.en.html Announcement]
* Old IP:
** 212.13.194.70
* New IP:
** 85.119.80.222
* Typical places for customers to reference these IPs:
** Firewall and ACLs for zone transfers (likely)
** Zone files if you've gone out of your way to create your own nameserver records
** Registrars if you've created nameservers with these IPs
* Old IP withdrawn from service: 2011-10-23

====Spamd service IP====
* [http://lists.bitfolk.com/lurker/message/20110918.151112.c20cadaf.en.html Announcement]
* Old IP:
** 212.13.194.5
* New IP:
** 85.119.80.248
* Typical places for customers to reference these IPs:
** Mail server config
** Possibly firewall
* Old IP withdrawn from service: 2011-10-29

====Entropy service IP====
* [http://lists.bitfolk.com/lurker/message/20111002.103608.3442f6fd.en.html Announcement]
* Old IP:
** 212.13.194.102
* New IP:
** 85.119.80.215 (but please use the host name '''entropy.lon.bitfolk.com''')
* Typical places for customers to reference these IPs:
** '''/etc/default/ekeyd-egd-linux'''
** Possibly firewall
* Old IP withdrawn from service: 2011-11-02

==Phase II: customers==
This phase began on Friday 4th November 2011. Please see our detailed article on [[renumbering for customers]].

Briefly:

# All customers have been routed one IPv4 address in the new range for each IPv4 address they have in the old range:
#* <tt>212.13.194.''x''</tt> → <tt>85.119.82.''x''</tt>
#* <tt>212.13.195.''y''</tt> → <tt>85.119.83.''y''</tt>
# An email announcement was sent out that this has happened, and to advise customers to switch to using only the new range as soon as possible.
# ''If you're lucky'', BitFolk will monitor traffic to see who is still receiving traffic to the old range of IP addresses and send them a periodic auto-whine email.
# The old range of IP addresses will cease to be routed on or after Monday 6th February 2012.

==What about IPv6?==
We will also be renumbering all IPv6 as well but consider it too much to cover at once, so it will be done later. In particular, customer prefixes are likely to go from /64 to /56 or /48.