Bug #105

Legacy 212.13.x.x IP addresses can still be configured by installer

Added by admin almost 12 years ago. Updated almost 12 years ago.

Status:Closed Start:2013-06-28
Priority:Normal Due date:
Assigned to:- % Done:

0%
Category:-
Target version:-
Votes: 0

Description

A customer, upon doing a net install of Ubuntu 12.04, received an /etc/network/interfaces file which had a 212.13.x.x IP address configured as a secondary address.

These addresses are no longer in use by BitFolk and are not routed to the VMs so are not usable in any case.

History

#1
Updated by admin almost 12 years ago

I suspect this will be to do with the customer's VM accessing the CGI script that generates the file from its IPv6 address rather than its IPv4 address, as that code path has been tested a lot less.

#2
Updated by admin almost 12 years ago

  • Status changed from New to Closed

It turns out that this was happening for everyone (well, everyone with an account old enough to have legacy IPs), ad it had just never been reported before. I've fixed it now.

Also available in: Atom PDF