Debian 8 to Debian 9 to Debian 10

[mingmeng]

Excellent discussion for learning, is this relevant?:

Supported Debian virtual machines on Hyper-V

Learn about the Debian and Linux integration services and features included in each version and known issues and workarounds for each distribution.

docs.microsoft.com

Note4: The latest upstream kernel capabilities are only available by using the kernels available in the Debian Backports repository

 

[ASap]

During Debian 9 to 10 upgrade, while running: apt disc-upgrade -y

*** named.conf.options (Y/I/N/O/D/Z) [default=N] ? Y
Installing new version of config file /etc/bind/named.conf.options ...
Installing new version of config file /etc/network/if-down.d/bind9 ...
Installing new version of config file /etc/network/if-up.d/bind9 ...
Installing new version of config file /etc/ppp/ip-down.d/bind9 ...
Installing new version of config file /etc/ppp/ip-up.d/bind9 ...
bind9-pkcs11.service is a disabled or a static unit not running, not starting it.
bind9-resolvconf.service is a disabled or a static unit not running, not starting it.
insserv: warning: current start runlevel(s) (empty) of script `bind9' overrides LSB defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `bind9' overrides LSB defaults (0 1 6).
Processing triggers for libc-bin (2.28-10) ...
Processing triggers for systemd (241-7~deb10u7) ...
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for mime-support (3.62) ...

Rebooted the VM and here's post Debian 9 to 10 upgrade:
ip a

/usr/local/directadmin/scripts/startips

/etc/network/interfaces

(actual WAN address is hidden) net mask is 255.255.255.255.

dmesg

 

[mingmeng]

andych, getting beyond by ken but if it helps my ip a output on Debian 10:

$ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 00:11:22:33:44:55 brd ff:ff:ff:ff:ff:ff
inet 123.123.123.123/24 brd 123.123.123.123 scope global eth0
valid_lft forever preferred_lft forever
inet6 fefe::fefe:cccc:eeee:11bb/64 scope link
valid_lft forever preferred_lft forever

obviously some digits changed to protect the innocent

 

[kristian]

Rebooted the VM and here's post Debian 9 to 10 upgrade:
ip a
View attachment 4500

Your eth0 has not gotten any IP from DHCP?

/usr/local/directadmin/scripts/startips
View attachment 4501

This is your problem, at least in regards to startips. You do not have a default route. What is the output of /sbin/ip route show?

 

[ASap]

Your eth0 has not gotten any IP from DHCP?




This is your problem, at least in regards to startips. You do not have a default route. What is the output of /sbin/ip route show?

It's the eth0 interface that's missing, like gone gone.

 

[kristian]

It's the eth0 interface that's missing, like gone gone.

Your screenshot from the output of ip a clearly shows the eth0 interface, so obviously it's not "gone gone".

 

[ASap]

Your screenshot from the output of ip a clearly shows the eth0 interface, so obviously it's not "gone gone".

eth0 isn't getting a static DHCP IP address from the router.

 

[kristian]

Troubleshooting your router's DHCP functionality is far outside the scope of this forum.

 

[ASap]

Troubleshooting your router's DHCP functionality is far outside the scope of this forum.

The VM didn't even initiate DORA request.

 

[ASap]

Update:
I used netplan and it works for me.
On Debian 10 Buster now. Cheers.