[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: An Ounce of Prevention



On Tue, 18 Jun 2019, Andy Smith wrote:

Possibly your network interface has changed name due to persistent naming? In any case, please can we see the contents of your /etc/network/interfaces file...

/etc/network/interfaces

-snip-
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

auto lo eth0
iface lo inet loopback

iface eth0 inet static
    address 192.168.1.40
    netmask 255.255.255.0
    gateway 192.168.1.1
    dns-nameserver 8.8.8.8
-snip-

*The dns-nameserver line is brandy-new today. I've used the rest of that, above, for years.)

and the output of:
$ ip link

-snip-
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
    link/ether 00:24:21:87:09:c2 brd ff:ff:ff:ff:ff:ff
3: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN mode DEFAULT group default qlen 100
link/none -snip

$ ip address show

-snip-
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
    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 mq state UP group default qlen 1000
    link/ether 00:24:21:87:09:c2 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.40/24 brd 192.168.1.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 2600:8805:8900:120:224:21ff:fe87:9c2/64 scope global mngtmpaddr dynamic
       valid_lft 83116sec preferred_lft 83116sec
    inet6 fe80::224:21ff:fe87:9c2/64 scope link
       valid_lft forever preferred_lft forever
3: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 100
    link/none
    inet 10.17.15.15/24 brd 10.17.15.255 scope global tun0
       valid_lft forever preferred_lft forever
    inet6 fc00::99:0:0:1:d/64 scope global
       valid_lft forever preferred_lft forever
    inet6 fe80::f2a5:610d:5659:9512/64 scope link flags 800
       valid_lft forever preferred_lft forever
-snip-

(The tun0 somehow survived some openvpn experimentation I was doing last night. I have no idea what that IP is. It survived my Jessie -> Stretch upgrade done this afternoon.)

Or do you generally have no networking until X starts and gives you
NetworkManager, etc?

No. I didn't mean to imply that the X failure was at all connected to my networking puzzles. I like to boot to a CLI and then type "startx". I don't even know where to go to find NetworkManager. Absolute systemd noobie here.

Thank you

--
These are not the droids you are looking for.


Reply to: