Yes, I like my VMs to have static IPs, so I did this

Now I get this:

I believe I have done nothing wrong, after all it's just 4 numbers - yes? How do I save that VM confconsole from its despair now?


I should probably add that this is the LXC 15.1 Turnkey VM and there is one container there (Observium), which I have created and nginx-proxied before doing the static IP change.

Was that too much for poor little confconsole?

The problem seems to be that there is no br0 network device (there is a natbr0).

Unfortunately, confconsole hangs hard upon invocation once it failed configuring nonexisting br0 device.

Needless to say, the user has no chance to tell confconsole to not look for br0. So you see the iceberg coming, but cannot avoid it. The consequences to that are well known.

Jeremy Davis's picture

Hmmm, yep, look like a Confconsole bug. I think your assessment is on the money.

At the very least, it should fail gracefully, although there isn't any good reason why it shouldn't "just work"...

Unfortunately, fixing this for v15.x is unlikely, but we should definitely have a closer look for v16.0.

Whilst it's a bit of a pain, you should be able to manually set a static IP via the /etc/network/interfaces file. I don't recall the exact syntax OTTOMH, but if you google, you should be able to find it. And when I get a chance to double check it myself, I'll post back.

Ok. While you are at it, please consider building something in like "confconsole reset" or so, to have at least some kind of last resort when the things hangs up itself on startup.


Maybe have some backup of the pristine initial config somewhere. While one loses settings, it may be better than to have to reinstall the machine and try again.

Add new comment