Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #182617

Re: quasi-SOLVED: Re: no network after jessie -> stretch

From David Wright <deblis@lionunicorn.co.uk>
Newsgroups linux.debian.user
Subject Re: quasi-SOLVED: Re: no network after jessie -> stretch
Date 2017-06-25 02:50 +0200
Message-ID <tW3Ut-6nU-1@gated-at.bofh.it> (permalink)
References (1 earlier) <tViVz-2hN-5@gated-at.bofh.it> <tVnLz-5m7-1@gated-at.bofh.it> <tVxKW-3iL-23@gated-at.bofh.it> <tVy4h-3pQ-7@gated-at.bofh.it> <tVyQF-3VK-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Fri 23 Jun 2017 at 09:37:18 (-0600), D. R. Evans wrote:
> David Wright wrote on 06/23/2017 08:42 AM:
> 
> >> Can anyone provide suggestions as to how to remove this delay?
> > 
> > Did you miss https://lists.debian.org/debian-user/2017/06/msg00858.html
> > which gave one possibility? It also asked for two things, neither of
> > which were forthcoming. I can't find any explicit statement as to
> > how you start your network, so any responses have been based on
> > guesswork.
> > 
> 
> Sorry, I thought that my statement about just entering info during the first
> installation would supply the requested information. Here is a bit more
> detail, formatted as a response to
> <d06d3b16-9c47-5e1e-b747-4859bc5bec33@debian.org>:
> 
> > Please share more details about your network configuration.
> 
> I'm not sure what details are needed. I input the information once, long ago,
> telling debian to use DHCP on eth0. I have not touched anything
> network-related since then. If you have a specific question in mind, please
> let me know and I'll try to answer it.
> 
> > Do you use ifupdown to manage your interface, NetworkManager, something
> > else?
> 
> I have no idea. I boot the system, and it works. I know that sounds snide and
> like I'm being an idiot, but it's the truth: once I had input the information
> when first installing debian, it all just worked and I never had to know
> anything about what debian was doing under the hood. Whatever the default was
> prior to stretch, I assume that that's what I was using.
> 
> (The version of debian on the system has always been plain debian stable,
> whichever version was the official stable at the time.)

I'm not the person to help with NM, but in the absence of other
replies…

> > The error message above indicates, that you have network-manager
> > installed and since stretch NetworkManager-wait-online.service is
> > enabled by default (it wasn't in jessie).

this would suggest a cause. Do you need the network before your login
prompt appears or not? If not, it looks like systemd needs telling that.
I think this just came up in a contemporaneous thread here, but in a
disk-mounting context rather than networking.

> > Now, if you don't actually manage your interfaces with NetworkManager,
> > NetworkManager-wait-online.service might run into a timeout (of 30s).

You originally wrote "about 30 useless seconds". It is worth stating
whether that is a counted-down timeout period or just an estimate of
a period you have wait. (I'm assuming you've done nothing to increase
the flow of console messages when you boot.)

> >
> > The output nmcli might be helpful.
> >
> 
> Now that eth0 is working properly, I can provide the output from nmcli without
> having to type it all :-) :
> 
> ----
> 
> n7dr@shack:~/projects/drlog$ nmcli
> eth0: connected to Wired connection 1
>         "Realtek RTL-8100/8101L/8139 PCI Fast Ethernet Adapter"
>         ethernet (8139too), 00:13:D4:93:04:FB, hw, mtu 1500
>         ip4 default
>         inet4 192.168.0.50/24
>         inet6 fe80::e6ec:1d58:4ed2:9964/64
> 
> eth1: disconnected
>         "Winbond Electronics W89C940"
>         1 connection available
>         ethernet (ne2k-pci), 00:20:78:19:8E:AF, hw, mtu 1500

I have no idea whether the status of eth1 could have any bearing
because I don't know where one makes ones wishes known to NM,
not having used it.

> lo: unmanaged
>         loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536
> 
> DNS configuration:
>         servers: 192.168.0.1
>         interface: eth0

Cheers,
David.

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

no network after jessie -> stretch "D. R. Evans" <doc.evans@gmail.com> - 2017-06-21 18:00 +0200
  Re: no network after jessie -> stretch Gian Carlo <ingats@tin.it> - 2017-06-21 21:30 +0200
    Re: no network after jessie -> stretch Felix Miata <mrmazda@earthlink.net> - 2017-06-21 21:40 +0200
      Re: no network after jessie -> stretch "D. R. Evans" <doc.evans@gmail.com> - 2017-06-22 01:50 +0200
        Re: no network after jessie -> stretch Fungi4All <fungilife@protonmail.com> - 2017-06-22 03:00 +0200
    Re: no network after jessie -> stretch "D. R. Evans" <doc.evans@gmail.com> - 2017-06-21 22:30 +0200
      Re: no network after jessie -> stretch Felix Miata <mrmazda@earthlink.net> - 2017-06-21 22:40 +0200
        Re: no network after jessie -> stretch Jude DaShiell <jdashiel@panix.com> - 2017-06-22 04:50 +0200
  Re: no network after jessie -> stretch Michael Biebl <biebl@debian.org> - 2017-06-21 21:50 +0200
  quasi-SOLVED: Re: no network after jessie -> stretch "D. R. Evans" <doc.evans@gmail.com> - 2017-06-23 00:40 +0200
    Re: quasi-SOLVED: Re: no network after jessie -> stretch Fungi4All <fungilife@protonmail.com> - 2017-06-23 05:50 +0200
      Re: quasi-SOLVED: Re: no network after jessie -> stretch "D. R. Evans" <doc.evans@gmail.com> - 2017-06-23 16:30 +0200
        Re: quasi-SOLVED: Re: no network after jessie -> stretch David Wright <deblis@lionunicorn.co.uk> - 2017-06-23 16:50 +0200
          Re: quasi-SOLVED: Re: no network after jessie -> stretch "D. R. Evans" <doc.evans@gmail.com> - 2017-06-23 17:40 +0200
            Re: quasi-SOLVED: Re: no network after jessie -> stretch David Wright <deblis@lionunicorn.co.uk> - 2017-06-25 02:50 +0200
              Re: quasi-SOLVED: Re: no network after jessie -> stretch "D. R. Evans" <doc.evans@gmail.com> - 2017-06-26 19:10 +0200
                Re: quasi-SOLVED: Re: no network after jessie -> stretch Joe <joe@jretrading.com> - 2017-06-26 19:40 +0200
        Re: quasi-SOLVED: Re: no network after jessie -> stretch Henrique de Moraes Holschuh <hmh@debian.org> - 2017-06-23 17:00 +0200
        Re: quasi-SOLVED: Re: no network after jessie -> stretch Fungi4All <fungilife@protonmail.com> - 2017-06-23 23:40 +0200
          Re: quasi-SOLVED: Re: no network after jessie -> stretch SDA <marathon.durandal@gmail.com> - 2017-06-24 05:00 +0200

csiph-web