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

Groups > linux.debian.user > #182292 > unrolled thread

Stretch--no network interfaces

Back to article view | Back to linux.debian.user

Contents

  Stretch--no network interfaces pplaw <pplaw@pcisys.net> - 2017-06-18 20:00 +0200
    Re: Stretch--no network interfaces Teemu Likonen <tlikonen@iki.fi> - 2017-06-18 20:00 +0200
      Re: Stretch--no network interfaces pplaw <pplaw@pcisys.net> - 2017-06-18 20:50 +0200
        Re: Stretch--no network interfaces Christian Seiler <christian@iwakd.de> - 2017-06-18 21:00 +0200
          Re: Stretch--no network interfaces Brian <ad44@cityscape.co.uk> - 2017-06-18 21:30 +0200
            Re: Stretch--no network interfaces Christian Seiler <christian@iwakd.de> - 2017-06-18 21:40 +0200
              Re: Stretch--no network interfaces Brian <ad44@cityscape.co.uk> - 2017-06-18 21:50 +0200
                Re: Stretch--no network interfaces Nicolas George <george@nsup.org> - 2017-06-18 22:00 +0200
                  Re: Stretch--no network interfaces Brian <ad44@cityscape.co.uk> - 2017-06-18 22:30 +0200
                    Re: Stretch--no network interfaces Felix Miata <mrmazda@earthlink.net> - 2017-06-18 23:20 +0200
                      Re: Stretch--no network interfaces Brian <ad44@cityscape.co.uk> - 2017-06-19 00:20 +0200
            Re: Stretch--no network interfaces Fungi4All <fungilife@protonmail.com> - 2017-06-18 21:50 +0200
          Resolved [was Re: Stretch--no network interfaces] pplaw <pplaw@pcisys.net> - 2017-06-18 22:00 +0200
            Re: Resolved [was Re: Stretch--no network interfaces] Brian <ad44@cityscape.co.uk> - 2017-06-18 23:00 +0200
        Re: Stretch--no network interfaces Brian <ad44@cityscape.co.uk> - 2017-06-18 21:20 +0200
      Re: Stretch--no network interfaces pplaw <pplaw@pcisys.net> - 2017-06-18 22:00 +0200

#182292 — Stretch--no network interfaces

Hi,

I installed Stretch, but have no network interfaces:


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: wlp1s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 4c:bb:58:20:0b:cd brd ff:ff:ff:ff:ff:ff
3: enx687f74158a8a: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 68:7f:74:15:8a:8a brd ff:ff:ff:ff:ff:ff


How do get at least #3 back as a useable interface, something like eth0.

Thanks,

b.

[toc] | [next] | [standalone]

#182294

[Multipart message — attachments visible in raw view] — view raw

pplaw@pcisys.net [2017-06-18 11:43:24-06] wrote:

> 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: wlp1s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
>     link/ether 4c:bb:58:20:0b:cd brd ff:ff:ff:ff:ff:ff
> 3: enx687f74158a8a: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
>     link/ether 68:7f:74:15:8a:8a brd ff:ff:ff:ff:ff:ff
>
>
> How do get at least #3 back as a useable interface, something like eth0.

enx687f74158a8a is your network interface. It has a stable name that
will never change. Just configure your system to use that interface.
More info:

https://www.debian.org/releases/stretch/amd64/release-notes/ch-whats-new.en.html#new-interface-names

https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/

-- 
/// Teemu Likonen   - .-..   <https://keybase.io/tlikonen> //
// PGP: 4E10 55DC 84E9 DFF6 13D7 8557 719D 69D3 2453 9450 ///

[toc] | [prev] | [next] | [standalone]

#182298

On Sun, Jun 18, 2017 at 08:54:34PM +0300, Teemu Likonen wrote:
> pplaw@pcisys.net [2017-06-18 11:43:24-06] wrote:
> 

__deletia__

> > 2: wlp1s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
> >     link/ether 4c:bb:58:20:0b:cd brd ff:ff:ff:ff:ff:ff
> > 3: enx687f74158a8a: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
> >     link/ether 68:7f:74:15:8a:8a brd ff:ff:ff:ff:ff:ff
> >
> >
> > How do get at least #3 back as a useable interface, something like eth0.
> 
> enx687f74158a8a is your network interface. It has a stable name that
> will never change. Just configure your system to use that interface.
> More info:
> 
> https://www.debian.org/releases/stretch/amd64/release-notes/ch-whats-new.en.html#new-interface-names
> 
> https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
> 
> -- 
> /// Teemu Likonen   - .-..   <https://keybase.io/tlikonen> //
> // PGP: 4E10 55DC 84E9 DFF6 13D7 8557 719D 69D3 2453 9450 ///

Thanks for the info, which explains the situation, certainly the naming 
convention.

The network I'm on at the moment hands out DHCP addresses.  But, sometimes,
I'll hard-code the IP address for the computer (with ifconfig:  ifconfig 
(eth0--but in this case) enx687f74158a8a 10.x.x.x netmask 255.255.255.0;
route add default gw 10.x.x.x).  Since this is a new install of Stretch,
I haven't been able to download the ifconfig package; and if I type ifup
enx687f74158a8a (or for my wireless card, wlp1s0), I get:  "unknown in-
terface.

So, I'm in between a rock and a hard place (I can't configure the interface,
and I can't connect to a network to download the package that will let me
configure the interface).  In case it would be of value, here's my lspci:

  
00:00.0 Host bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register (rev 0e)
00:02.0 VGA compatible controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display (rev 0e)
00:13.0 IDE interface: Intel Corporation Atom Processor E3800 Series SATA IDE Controller (rev 0e)
00:14.0 USB controller: Intel Corporation Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI (rev 0e)
00:1a.0 Encryption controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine (rev 0e)
00:1b.0 Audio device: Intel Corporation Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller (rev 0e)
00:1c.0 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 1 (rev 0e)
00:1f.0 ISA bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Power Control Unit (rev 0e)
00:1f.3 SMBus: Intel Corporation Atom Processor E3800 Series SMBus Controller (rev 0e)
01:00.0 Network controller: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter (rev 01)


Any help is appreciated.

Thanks,

b.

[toc] | [prev] | [next] | [standalone]

#182299

On 06/18/2017 08:25 PM, pplaw wrote:
> The network I'm on at the moment hands out DHCP addresses.  But, sometimes,
> I'll hard-code the IP address for the computer (with ifconfig:  ifconfig 
> (eth0--but in this case) enx687f74158a8a 10.x.x.x netmask 255.255.255.0;
> route add default gw 10.x.x.x).  Since this is a new install of Stretch,
> I haven't been able to download the ifconfig package; and if I type ifup
> enx687f74158a8a (or for my wireless card, wlp1s0), I get:  "unknown in-
> terface.

In the Debian release notes there's a section about the fact that
ifconfig has been deprecated for well over a decade now, and is not
included in new installs anymore starting with Stretch:

https://www.debian.org/releases/stretch/amd64/release-notes/ch-information.en.html#iproute2

If you want to temporarily add an IP to a given interface, you can
use the 'ip' utility (this also works in older Debian versions):

ip link set $DEVICE up
ip addr add 10.x.x.x/24 dev $DEVICE
ip route add default via 10.x.x.y

The question why 'ifup' doesn't work in your case: 'ifup' is only
a tool that is used in conjunction with /etc/network/interfaces
(or /etc/network/interfaces.d/*). So in order for ifup to work,
you need to create an entry in /etc/network/interfaces for your
network interface, for example:

auto enx687f74158a8a
iface enx687f74158a8a inet static
   address 10.x.x.x/24
   gateway 10.x.x.y

And then you can do 'ifup enx687f74158a8a'. (And in that case
the interface will also be configured when the system is rebooted.)

(The 'ifup' part is also the same in older Debian versions.)

Regards,
Christian

[toc] | [prev] | [next] | [standalone]

#182302

On Sun 18 Jun 2017 at 20:54:46 +0200, Christian Seiler wrote:

> On 06/18/2017 08:25 PM, pplaw wrote:
> > The network I'm on at the moment hands out DHCP addresses.  But, sometimes,
> > I'll hard-code the IP address for the computer (with ifconfig:  ifconfig 
> > (eth0--but in this case) enx687f74158a8a 10.x.x.x netmask 255.255.255.0;
> > route add default gw 10.x.x.x).  Since this is a new install of Stretch,
> > I haven't been able to download the ifconfig package; and if I type ifup
> > enx687f74158a8a (or for my wireless card, wlp1s0), I get:  "unknown in-
> > terface.
> 
> In the Debian release notes there's a section about the fact that
> ifconfig has been deprecated for well over a decade now, and is not
> included in new installs anymore starting with Stretch:
> 
> https://www.debian.org/releases/stretch/amd64/release-notes/ch-information.en.html#iproute2

ifconfig isn't the problem. The OP installed Stretch; stretch doesn't
have ifconfig.
 
> If you want to temporarily add an IP to a given interface, you can
> use the 'ip' utility (this also works in older Debian versions):

[Good advice snipped]

Do you not find it disturbing that someone can install Debian and not
end up with a network connection? d-i is (generally) very good at doing
this. It is one of its many strong points.

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#182303

On 06/18/2017 09:22 PM, Brian wrote:
> On Sun 18 Jun 2017 at 20:54:46 +0200, Christian Seiler wrote:
> 
>> On 06/18/2017 08:25 PM, pplaw wrote:
>>> The network I'm on at the moment hands out DHCP addresses.  But, sometimes,
>>> I'll hard-code the IP address for the computer (with ifconfig:  ifconfig 
>>> (eth0--but in this case) enx687f74158a8a 10.x.x.x netmask 255.255.255.0;
>>> route add default gw 10.x.x.x).  Since this is a new install of Stretch,
>>> I haven't been able to download the ifconfig package; and if I type ifup
>>> enx687f74158a8a (or for my wireless card, wlp1s0), I get:  "unknown in-
>>> terface.
>>
>> In the Debian release notes there's a section about the fact that
>> ifconfig has been deprecated for well over a decade now, and is not
>> included in new installs anymore starting with Stretch:
>>
>> https://www.debian.org/releases/stretch/amd64/release-notes/ch-information.en.html#iproute2
> 
> ifconfig isn't the problem. The OP installed Stretch; stretch doesn't
> have ifconfig.

Stretch does have ifconfig, just not by default. And I mentioned that
because the OP mentioned it and I wanted to clarify this. Please read
again the part I quoted from the OP. ;-)

>> If you want to temporarily add an IP to a given interface, you can
>> use the 'ip' utility (this also works in older Debian versions):
> 
> [Good advice snipped]
> 
> Do you not find it disturbing that someone can install Debian and not
> end up with a network connection?

Well, that depends on further details here: was the network configured
at all during installation? If you use one of the DVDs, for example,
you don't need to configure the network in the installer to install
Debian onto the hard disk - but if you didn't configure it in the
installer, you'll have to configure it manually in the running system.

But sure, if you can show that network properly configured in
the installer fails to lead to a system with configured networking,
then please report a bug with details and steps to reproduce, so that
this can be fixed in 9.1.

Regards,
Christian

[toc] | [prev] | [next] | [standalone]

#182305

On Sun 18 Jun 2017 at 21:36:49 +0200, Christian Seiler wrote:

> On 06/18/2017 09:22 PM, Brian wrote:
> > On Sun 18 Jun 2017 at 20:54:46 +0200, Christian Seiler wrote:
> > 
> >> On 06/18/2017 08:25 PM, pplaw wrote:
> >>> The network I'm on at the moment hands out DHCP addresses.  But, sometimes,
> >>> I'll hard-code the IP address for the computer (with ifconfig:  ifconfig 
> >>> (eth0--but in this case) enx687f74158a8a 10.x.x.x netmask 255.255.255.0;
> >>> route add default gw 10.x.x.x).  Since this is a new install of Stretch,
> >>> I haven't been able to download the ifconfig package; and if I type ifup
> >>> enx687f74158a8a (or for my wireless card, wlp1s0), I get:  "unknown in-
> >>> terface.
> >>
> >> In the Debian release notes there's a section about the fact that
> >> ifconfig has been deprecated for well over a decade now, and is not
> >> included in new installs anymore starting with Stretch:
> >>
> >> https://www.debian.org/releases/stretch/amd64/release-notes/ch-information.en.html#iproute2
> > 
> > ifconfig isn't the problem. The OP installed Stretch; stretch doesn't
> > have ifconfig.
> 
> Stretch does have ifconfig, just not by default. And I mentioned that
> because the OP mentioned it and I wanted to clarify this. Please read
> again the part I quoted from the OP. ;-)

The Stretch d-i does not have ifconfig. (Is that the third time I have
said that?)
 
> >> If you want to temporarily add an IP to a given interface, you can
> >> use the 'ip' utility (this also works in older Debian versions):
> > 
> > [Good advice snipped]
> > 
> > Do you not find it disturbing that someone can install Debian and not
> > end up with a network connection?
> 
> Well, that depends on further details here: was the network configured
> at all during installation? If you use one of the DVDs, for example,
> you don't need to configure the network in the installer to install
> Debian onto the hard disk - but if you didn't configure it in the
> installer, you'll have to configure it manually in the running system.
> 
> But sure, if you can show that network properly configured in
> the installer fails to lead to a system with configured networking,
> then please report a bug with details and steps to reproduce, so that
> this can be fixed in 9.1.

Of course it depends on further details. Which is why they were
requested.

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#182308

[Multipart message — attachments visible in raw view] — view raw

Le decadi 30 prairial, an CCXXV, Brian a écrit :
> The Stretch d-i does not have ifconfig. (Is that the third time I have
> said that?)

Yes, that is about the third time you said it as an answer to a message
that was telling the same thing more accurately. Please stop, and next
time read the messages before replying.

Regards,

-- 
  Nicolas George

[toc] | [prev] | [next] | [standalone]

#182310

On Sun 18 Jun 2017 at 21:49:14 +0200, Nicolas George wrote:

> Le decadi 30 prairial, an CCXXV, Brian a écrit :
> > The Stretch d-i does not have ifconfig. (Is that the third time I have
> > said that?)
> 
> Yes, that is about the third time you said it as an answer to a message
> that was telling the same thing more accurately. Please stop, and next
> time read the messages before replying.

Your wish is my command.

Ifconfig has no bearing on anything, then. Glad you agree.

d-i not providing connectivity after the installation. Any thoughts on
that?

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#182316

Brian composed on 2017-06-18 21:19 (UTC+0100):

> d-i not providing connectivity after the installation. Any thoughts on
> that?
.
Installing over network always WFM. Also I provide net.ifnames=0 on installation
kernel cmdline so that my NICs configure as the human memorable eth0.
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

[toc] | [prev] | [next] | [standalone]

#182321

On Sun 18 Jun 2017 at 17:10:57 -0400, Felix Miata wrote:

> Brian composed on 2017-06-18 21:19 (UTC+0100):
> 
> > d-i not providing connectivity after the installation. Any thoughts on
> > that?
> .
> Installing over network always WFM. Also I provide net.ifnames=0 on installation
> kernel cmdline so that my NICs configure as the human memorable eth0.

I see. The OP came up against netcfg not understanding ifnames. That's
a bit of a downer for people relying on d-i.

[toc] | [prev] | [next] | [standalone]

#182304

[Multipart message — attachments visible in raw view] — view raw

From: ad44@cityscape.co.uk

@ Do you not find it disturbing that someone can install Debian and not
@ end up with a network connection? d-i is (generally) very good at doing
@ this. It is one of its many strong points.

The new installer iso seem twice the size of their predecessors, or did I see
something wrong?
From skimming through the release am I to understand that if one installs 8.8
and upgrades to stretch they will not have this problem/change unless they intent
to manually switch. Weird?
So when one reports a bug (network related) from now on, if they are just indicating
installation and architecture they must also specify the interface used

From release:
> This change does not apply to upgrades of jessie systems; the naming will continue to be enforced by /etc/udev/rules.d/70-persistent-net.rules. For more information, see /usr/share/doc/udev/README.Debian.gz or the [upstream documentation](https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/).

--
Brian.

[toc] | [prev] | [next] | [standalone]

#182307 — Resolved [was Re: Stretch--no network interfaces]

On Sun, Jun 18, 2017 at 08:54:46PM +0200, Christian Seiler wrote:
> On 06/18/2017 08:25 PM, pplaw wrote:
> > The network I'm on at the moment hands out DHCP addresses.  But, sometimes,
> > I'll hard-code the IP address for the computer (with ifconfig:  ifconfig 
> > (eth0--but in this case) enx687f74158a8a 10.x.x.x netmask 255.255.255.0;
> > route add default gw 10.x.x.x).  Since this is a new install of Stretch,
> > I haven't been able to download the ifconfig package; and if I type ifup
> > enx687f74158a8a (or for my wireless card, wlp1s0), I get:  "unknown in-
> > terface.
> 
> In the Debian release notes there's a section about the fact that
> ifconfig has been deprecated for well over a decade now, and is not
> included in new installs anymore starting with Stretch:
> 
> https://www.debian.org/releases/stretch/amd64/release-notes/ch-information.en.html#iproute2
> 
> If you want to temporarily add an IP to a given interface, you can
> use the 'ip' utility (this also works in older Debian versions):
> 
> ip link set $DEVICE up
> ip addr add 10.x.x.x/24 dev $DEVICE
> ip route add default via 10.x.x.y
> 
> The question why 'ifup' doesn't work in your case: 'ifup' is only
> a tool that is used in conjunction with /etc/network/interfaces
> (or /etc/network/interfaces.d/*). So in order for ifup to work,
> you need to create an entry in /etc/network/interfaces for your
> network interface, for example:
> 
> auto enx687f74158a8a
> iface enx687f74158a8a inet static
>    address 10.x.x.x/24
>    gateway 10.x.x.y
> 
> And then you can do 'ifup enx687f74158a8a'. (And in that case
> the interface will also be configured when the system is rebooted.)
> 
> (The 'ifup' part is also the same in older Debian versions.)
> 
> Regards,
> Christian

Interesting info, which;

1)
proves quite successful;

2)
shows I've been out of step for a long time; and

3)
deserves to be set in gold (see #1, id.).

Thank you, Christian!

b.   

[toc] | [prev] | [next] | [standalone]

#182313 — Re: Resolved [was Re: Stretch--no network interfaces]

On Sun 18 Jun 2017 at 13:51:52 -0600, pplaw wrote:

> On Sun, Jun 18, 2017 at 08:54:46PM +0200, Christian Seiler wrote:
> > On 06/18/2017 08:25 PM, pplaw wrote:
> > > The network I'm on at the moment hands out DHCP addresses.  But, sometimes,
> > > I'll hard-code the IP address for the computer (with ifconfig:  ifconfig 
> > > (eth0--but in this case) enx687f74158a8a 10.x.x.x netmask 255.255.255.0;
> > > route add default gw 10.x.x.x).  Since this is a new install of Stretch,
> > > I haven't been able to download the ifconfig package; and if I type ifup
> > > enx687f74158a8a (or for my wireless card, wlp1s0), I get:  "unknown in-
> > > terface.
> > 
> > In the Debian release notes there's a section about the fact that
> > ifconfig has been deprecated for well over a decade now, and is not
> > included in new installs anymore starting with Stretch:
> > 
> > https://www.debian.org/releases/stretch/amd64/release-notes/ch-information.en.html#iproute2
> > 
> > If you want to temporarily add an IP to a given interface, you can
> > use the 'ip' utility (this also works in older Debian versions):
> > 
> > ip link set $DEVICE up
> > ip addr add 10.x.x.x/24 dev $DEVICE
> > ip route add default via 10.x.x.y
> > 
> > The question why 'ifup' doesn't work in your case: 'ifup' is only
> > a tool that is used in conjunction with /etc/network/interfaces
> > (or /etc/network/interfaces.d/*). So in order for ifup to work,
> > you need to create an entry in /etc/network/interfaces for your
> > network interface, for example:
> > 
> > auto enx687f74158a8a
> > iface enx687f74158a8a inet static
> >    address 10.x.x.x/24
> >    gateway 10.x.x.y
> > 
> > And then you can do 'ifup enx687f74158a8a'. (And in that case
> > the interface will also be configured when the system is rebooted.)
> > 
> > (The 'ifup' part is also the same in older Debian versions.)
> > 
> > Regards,
> > Christian
> 
> Interesting info, which;
> 
> 1)
> proves quite successful;
> 
> 2)
> shows I've been out of step for a long time; and
> 
> 3)
> deserves to be set in gold (see #1, id.).
> 
> Thank you, Christian!

Excellent information, indeed. It rectifies the inability of d-i to set
up a simple network connection which is available at first boot. Netcfg
fails once again it seems.

But we will never know.

[toc] | [prev] | [next] | [standalone]

#182301

On Sun 18 Jun 2017 at 12:25:11 -0600, pplaw wrote:

> On Sun, Jun 18, 2017 at 08:54:34PM +0300, Teemu Likonen wrote:
> > pplaw@pcisys.net [2017-06-18 11:43:24-06] wrote:
> 
> __deletia__
> 
> > > 2: wlp1s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
> > >     link/ether 4c:bb:58:20:0b:cd brd ff:ff:ff:ff:ff:ff
> > > 3: enx687f74158a8a: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
> > >     link/ether 68:7f:74:15:8a:8a brd ff:ff:ff:ff:ff:ff
> > >
> > >
> > > How do get at least #3 back as a useable interface, something like eth0.
> > 
> > enx687f74158a8a is your network interface. It has a stable name that
> > will never change. Just configure your system to use that interface.
> > More info:
> > 
> > https://www.debian.org/releases/stretch/amd64/release-notes/ch-whats-new.en.html#new-interface-names
> > 
> > https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
> > 
> > -- 
> > /// Teemu Likonen   - .-..   <https://keybase.io/tlikonen> //
> > // PGP: 4E10 55DC 84E9 DFF6 13D7 8557 719D 69D3 2453 9450 ///
> 
> Thanks for the info, which explains the situation, certainly the naming 
> convention.

The naming convention enlightens you but it is not the problem.

> The network I'm on at the moment hands out DHCP addresses.  But, sometimes,
> I'll hard-code the IP address for the computer (with ifconfig:  ifconfig 
> (eth0--but in this case) enx687f74158a8a 10.x.x.x netmask 255.255.255.0;
> route add default gw 10.x.x.x).  Since this is a new install of Stretch,
> I haven't been able to download the ifconfig package; and if I type ifup
> enx687f74158a8a (or for my wireless card, wlp1s0), I get:  "unknown in-
> terface.

But you did not do this when you installed Stretch, did you?

ifconfig is in the net-tools package. d-i does not provide the package.

> So, I'm in between a rock and a hard place (I can't configure the interface,
> and I can't connect to a network to download the package that will let me
> configure the interface).  In case it would be of value, here's my lspci:

The interface is capable of being configured. You do not need ifconfig.

> 00:00.0 Host bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register (rev 0e)
> 00:02.0 VGA compatible controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display (rev 0e)
> 00:13.0 IDE interface: Intel Corporation Atom Processor E3800 Series SATA IDE Controller (rev 0e)
> 00:14.0 USB controller: Intel Corporation Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI (rev 0e)
> 00:1a.0 Encryption controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine (rev 0e)
> 00:1b.0 Audio device: Intel Corporation Atom Processor Z36xxx/Z37xxx Series High Definition Audio Controller (rev 0e)
> 00:1c.0 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 1 (rev 0e)
> 00:1f.0 ISA bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Power Control Unit (rev 0e)
> 00:1f.3 SMBus: Intel Corporation Atom Processor E3800 Series SMBus Controller (rev 0e)
> 01:00.0 Network controller: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter (rev 01)

The last line is the wireless interface. Where is the other interface?

Did you install over wireless or cabled ethernet?

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#182306

On Sun, Jun 18, 2017 at 08:54:34PM +0300, Teemu Likonen wrote:
> pplaw@pcisys.net [2017-06-18 11:43:24-06] wrote:
> 
> > 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: wlp1s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
> >     link/ether 4c:bb:58:20:0b:cd brd ff:ff:ff:ff:ff:ff
> > 3: enx687f74158a8a: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
> >     link/ether 68:7f:74:15:8a:8a brd ff:ff:ff:ff:ff:ff
> >
> >
> > How do get at least #3 back as a useable interface, something like eth0.
> 
> enx687f74158a8a is your network interface. It has a stable name that
> will never change. Just configure your system to use that interface.
> More info:
> 
> https://www.debian.org/releases/stretch/amd64/release-notes/ch-whats-new.en.html#new-interface-names
> 
> https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
> 
> -- 
> /// Teemu Likonen   - .-..   <https://keybase.io/tlikonen> //
> // PGP: 4E10 55DC 84E9 DFF6 13D7 8557 719D 69D3 2453 9450 ///

Thanks for the info, Teemu!

b.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web