#1 2019-02-09 00:52:21

Bearded_Blunder

Dodging A Bullet

From: Seat: seat0; vc7

Registered: 2015-09-29

Posts: 1,146

[solved] Network acting weird Debian buster netinstall (standard only)

So suddenly when I install today Debian boots with broken networking:
Temporary failure in name resolution
I'm having to do

sudo ifdown <interface> && sudo ifup <interface>

after every boot for it to work.
OK I have a workaround & once I install the Lithium bunsen-meta-all package network-manager is likely to be sorting it anyway.

I'm just curious what might be going on. 
Previous installs to same VM "Just Work(TM)" (Recycling one rather than creating new VM)
I've made no config changes in VirtualBox, though it did update yesterday. Existing other installs are unaffected though.

Any ideas?  It's not a "big deal" or an important install, virtual machine stuff, just an annoying glitch that has me curious.
Never seen the basic ethernet stuff misbehave before.

[edit] Don't mind me, just ignore, seems to be a VirtualBox bug, works fine set to NAT only misbehaves set to "Bridged"
New issue to me, but clearly a result of the VirtualBox version bump since "Bridged" worked before. [/edit]

Last edited by Bearded_Blunder (2019-02-09 01:17:20)

---

Blessed is he who expecteth nothing, for he shall not be disappointed...
If there's an obscure or silly way to break it, but you don't know what.. Just ask me

ohnonot

...again

Registered: 2015-09-29

Posts: 5,592

Re: [solved] Network acting weird Debian buster netinstall (standard only)

Calling a change in behaviour a bug? hmmm...

anyhow:

broken networking:
Temporary failure in name resolution

it's important to understand that networking consists of several layers.
the message only relates to name resolution; that does not mean you're not connected to the internet, or that the whole networking is broken.

Bearded_Blunder

Dodging A Bullet

From: Seat: seat0; vc7

Registered: 2015-09-29

Posts: 1,146

Re: [solved] Network acting weird Debian buster netinstall (standard only)

I do realize that, in fact it was deeper than name resolution as I also couldn't ping my default gateway by IP
"destination network unreachable" if i recall correctly
My DG does normally respond to ping.
`ip a` reported the interface as up, but no ipv4 addressing in evidence.

Didn't post everything here, particularly not after divining the cause.
I'm sure I've left out more stuff.

---

Blessed is he who expecteth nothing, for he shall not be disappointed...
If there's an obscure or silly way to break it, but you don't know what.. Just ask me