Hosed my site up all night after I rebooted after some routine maintenance. When was eth1 removed for our inside private NIC?

Now I've got to go through my IPTables and do a bunch of reconfiguring, a bit irritating to say the least .....

_________________

Where "Thought Crime" is commited
http://www.rejecttheherd.net

I discovered this a few days ago when setting up a new 'node. I should have posted here about it, I was just unclear on the what/why of it, other than that my setup script could no longer configure eth1

I submitted a ticket about it (because Profile settings said to use eth1, while the Network tab said eth0) and the response was that "We're actually phasing out the use of eth1 as it has a tendency to stop communicating under Xen."

Yeah it's totally borked up my IPTables, yes I'm a bit irritated

_________________


Where "Thought Crime" is commited

http://www.rejecttheherd.net

Some more information on that would be good.

Do we configure 192.168.whatever as an alias on eth0?

eth1 will be going away in the near future. If you are taking advantage of our private network you'll want to reconfigure your private IP as an alias on eth0.

Both the Network Tab and your Config Profile should reflect the change. Keep an eye out for an e-mail if you have a private IP on eth1.

-Tom

I put the private IP on eth0:0 (that's what the Network settings tab in the manager says to do). It looks really odd, and I haven't changed any firewall rules for it yet. I don't do anything production at Linode (yet).

So in Ubuntu/Debian, /etc/network/interfaces, I've got:

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
address <PUBLIC_IP>
netmask 255.255.255.0
gateway <GATEWAY>

auto eth0:0
iface eth0:0 inet static
address <PRIVATE_IP>
netmask 255.255.128.0

I only got as far as restarting the network and pinging that private IP...

Okay, it's already happened.



I did have a private IP on eth1, and I got no email?

No harm done as I caught it on a reboot, but... can we have a bit more attention paid towards announcing these sorts of changes?

I'm in Newark, and my eth1 is still there... for now

Why are you guys changing this? It's a PITA to have to change iptables, distcc, munin, etc.

Yeah I already bitched them out, someone screwed the pooch on the notifications. O'well we're all human and $h1t happens, I'll let them get by on this one since overall they really do rock.

_________________


Where "Thought Crime" is commited

http://www.rejecttheherd.net

Just to be clear: Notifications did not go out yet. eth1 was disabled on all Linodes that were not using it. We plan on sending notices out shortly and to give at least 2 weeks for the rest.

We apologize for the mistake -- for some reason, your Linode didn't appear to be responding at the time we created our list.

-Tom

No worries, I'm well over it, water under the bridge. You guy's do a great job overall and I've been and remain a happy plus loyal Linode customer

_________________


Where "Thought Crime" is commited

http://www.rejecttheherd.net

E-mail went out. It points us to this article, to which I just added Gentoo instructions.

(Article overlaps with this one BTW, but either should help get you reconfigured.)

A slightly off-topic feature request here:

We can swap public IP's between linodes using the control panel, which is really useful. It would be great if we could also swap private IP's using the control panel. A few weeks ago I added private IP's to two of my linodes, and I wondered for half an hour why it wasn't working before I realized that I had configured the IP's the other way around! (Those little numbers look so similar to each other...)