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

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

network trouble on stretch

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

Contents

  network trouble on stretch Glenn English <ghe2001@gmail.com> - 2017-09-03 22:20 +0200
    Re: network trouble on stretch Fungi4All <fungilife@protonmail.com> - 2017-09-04 00:30 +0200
      Re: network trouble on stretch Zenaan Harkness <zenaan@freedbms.net> - 2017-09-04 06:10 +0200
      Re: network trouble on stretch Ben Caradoc-Davies <ben@transient.nz> - 2017-09-04 07:40 +0200
    Re: network trouble on stretch Cindy-Sue Causey <butterflybytes@gmail.com> - 2017-09-04 05:10 +0200
    Re: network trouble on stretch Erik Christiansen <dvalin@internode.on.net> - 2017-09-04 10:10 +0200
      Re: network trouble on stretch Felix Miata <mrmazda@earthlink.net> - 2017-09-04 10:50 +0200
        Re: network trouble on stretch Erik Christiansen <dvalin@internode.on.net> - 2017-09-04 12:00 +0200
        Re: network trouble on stretch Fungi4All <fungilife@protonmail.com> - 2017-09-04 13:20 +0200
          Re: network trouble on stretch Felix Miata <mrmazda@earthlink.net> - 2017-09-04 14:30 +0200
            Re: network trouble on stretch Glenn English <ghe2001@gmail.com> - 2017-09-04 17:50 +0200

#186403 — network trouble on stretch

Working on a Dell 5414 laptop, Stretch.

The WiFi works, but the Ethernet doesn't, and I can't figure out why.

ip addr:

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: enp0s31f6: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN
group default qlen 1000
    link/ether 10:05:01:40:f4:43 brd ff:ff:ff:ff:ff:ff
3: wwp0s20f0u2i12: <BROADCAST,MULTICAST,NOARP> mtu 1500 qdisc noop
state DOWN group default qlen 1000
    link/ether 4e:8a:3a:22:b3:df brd ff:ff:ff:ff:ff:ff
4: wlp1s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group
default qlen 1000
    link/ether f4:8c:50:17:bc:0e brd ff:ff:ff:ff:ff:ff
5: enx10050149649d: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state
DOWN group default qlen 1000
    link/ether 10:05:01:49:64:9d brd ff:ff:ff:ff:ff:ff

/etc/network/interfaces:

# 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/*

# The loopback network interface
auto lo
iface lo inet loopback

auto wwp0s20f0u2i12
iface wwp0s20f0u2i12 inet static
    address 216.17.134.202/29
    gateway 216.17.134.201

First I tried with wicd, a network manager (the static def wasn't in interfaces)

It said the wired interface was up, and assigned the requested IP. It
wasn't checking after assignment to see if it worked. I turned that
on, and it never came back.

I removed the network monitor and added the static paragraph to the
interface file. ifup and ifdown worked, and ip addr said
wwp0s20f0u2i12 was up.

There are two Ethernet ports on this thing, and I tried both with no
success. I swapped out the Ethernet cable with the same result.

I replaced Stretch with Buster. It works. dhcp (Comcast) or static (my
T1). Using the interfaces file.

BTW. ifconfig fans, wait till you get to Buster -- no ifup or down.
Buster seems to boot using a commented out dhcp paragraph, though.
Running by hand, '/etc/init.d/network reload' loads the correct
config.

The 'man interfaces' on Stretch talks a lot about the ethn interfaces.
It does on Buster, too.

This is less than optimal.

What's going on here? This is Linux, not Winders; Debian, not Ubuntu;
stable, not Sid. This is what we're supposed to put on Internet
servers? They had time to make something as simple as this work while
it was testing. And to correct the man pages, too.

If they didn't have time, the release should have been postponed until
it was ready for prime time, IMHO.

I looked on the 'Net, asking why the interface names were changed. I
found a good reason: sometimes the ethn names aren't reliably
consistent. Fine, I say, you've figured how to make them consistent.
That's no reason to change the names from a meaningful 4 or 5 chars to
11, chosen by /dev/urandom.

Somebody's selling the Debian management a pile of bull excrement.

--
Glenn English

[toc] | [next] | [standalone]

#186407

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

> From: ghe2001@gmail.com
> To: debianUsers <debian-user@lists.debian.org>
>
> Working on a Dell 5414 laptop, Stretch.
>
> The WiFi works, but the Ethernet doesn"t, and I can"t figure out why.
>
> ip addr:
>
> 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: enp0s31f6: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN
> group default qlen 1000
> link/ether 10:05:01:40:f4:43 brd ff:ff:ff:ff:ff:ff
> 3: wwp0s20f0u2i12: <BROADCAST,MULTICAST,NOARP> mtu 1500 qdisc noop
> state DOWN group default qlen 1000
> link/ether 4e:8a:3a:22:b3:df brd ff:ff:ff:ff:ff:ff
> 4: wlp1s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group
> default qlen 1000
> link/ether f4:8c:50:17:bc:0e brd ff:ff:ff:ff:ff:ff
> 5: enx10050149649d: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state
> DOWN group default qlen 1000
> link/ether 10:05:01:49:64:9d brd ff:ff:ff:ff:ff:ff
>
> /etc/network/interfaces:
>
> # 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/*
>
> # The loopback network interface
> auto lo
> iface lo inet loopback
>
> auto wwp0s20f0u2i12
> iface wwp0s20f0u2i12 inet static
> address 216.17.134.202/29
> gateway 216.17.134.201
>
> First I tried with wicd, a network manager (the static def wasn"t in interfaces)
>
> It said the wired interface was up, and assigned the requested IP. It
> wasn"t checking after assignment to see if it worked. I turned that
> on, and it never came back.
>
> I removed the network monitor and added the static paragraph to the
> interface file. ifup and ifdown worked, and ip addr said
> wwp0s20f0u2i12 was up.
>
> There are two Ethernet ports on this thing, and I tried both with no
> success. I swapped out the Ethernet cable with the same result.
>
> I replaced Stretch with Buster. It works. dhcp (Comcast) or static (my
> T1). Using the interfaces file.
>
> BTW. ifconfig fans, wait till you get to Buster -- no ifup or down.
> Buster seems to boot using a commented out dhcp paragraph, though.
> Running by hand, "/etc/init.d/network reload" loads the correct
> config.
>
> The "man interfaces" on Stretch talks a lot about the ethn interfaces.
> It does on Buster, too.
>
> This is less than optimal.
>
> What"s going on here? This is Linux, not Winders; Debian, not Ubuntu;
> stable, not Sid. This is what we"re supposed to put on Internet
> servers? They had time to make something as simple as this work while
> it was testing. And to correct the man pages, too.
>
> If they didn"t have time, the release should have been postponed until
> it was ready for prime time, IMHO.
>
> I looked on the "Net, asking why the interface names were changed. I
> found a good reason: sometimes the ethn names aren"t reliably
> consistent. Fine, I say, you"ve figured how to make them consistent.
> That"s no reason to change the names from a meaningful 4 or 5 chars to
> 11, chosen by /dev/urandom.
>
> Somebody"s selling the Debian management a pile of bull excrement.

Before you get a long lecture on the merits of long unique names try this:

Edit your /etc/default/grub change GRUB_CMDLINE_LINUX=”” to :
GRUB_CMDLINE_LINUX="net.ifnames=0" If the biosdevname is installed you need to add :
GRUB_CMDLINE_LINUX="net.ifnames=0 biosdevname=0"
$ sudo update-grub
$ sudo reboot

Now check your /dev/interfaces, they should be eth0 and wlan0 and they will stay
this way.

> Glenn English

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

#186418

On Sun, Sep 03, 2017 at 06:27:12PM -0400, Fungi4All wrote:
> > From: ghe2001@gmail.com
> > The WiFi works, but the Ethernet doesn"t, and I can"t figure out why.
> > ip addr:
...

> Before you get a long lecture on the merits of long unique names try this:
> 
> Edit your /etc/default/grub change GRUB_CMDLINE_LINUX=”” to :
> GRUB_CMDLINE_LINUX="net.ifnames=0" If the biosdevname is installed you need to add :
> GRUB_CMDLINE_LINUX="net.ifnames=0 biosdevname=0"
> $ sudo update-grub
> $ sudo reboot
> 
> Now check your /dev/interfaces, they should be eth0 and wlan0 and they will stay
> this way.

VERY nice hint - jotted away for future :)

That should hopefully solve the OP's problem. If not, the next step I
would personally take is to:

1) determine which ifnames are which type

2) drop into a terminal and use ip (or ifconfig still?) to manually
   configure each eth dev, one by one, with a static address, and see
   if ping works from another host;
   if not work, then "ifconfig down" or "ip link set $DEVNAME down"
   and try the next one...

This way also means that specific commands are either failing or
succeeding - I know it's lower level, but can make debugging ones
problem a little easier from my oh-so-incredibly-humble experiences
:)

Good luck,

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

#186422

On 04/09/17 10:27, Fungi4All wrote:
> Before you get a long lecture on the merits of long unique names try this:
> Edit your /etc/default/grub change GRUB_CMDLINE_LINUX=”” to :
> GRUB_CMDLINE_LINUX="net.ifnames=0" If the biosdevname is installed you need to add :
> GRUB_CMDLINE_LINUX="net.ifnames=0 biosdevname=0"
> $ sudo update-grub
> $ sudo reboot
> Now check your /dev/interfaces, they should be eth0 and wlan0 and they will stay
> this way.

Thank you. I have wanted this for so long.

Kind regards,

-- 
Ben Caradoc-Davies <ben@transient.nz>
Director
Transient Software Limited <http://transient.nz/>
New Zealand

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

#186417

On 9/3/17, Glenn English <ghe2001@gmail.com> wrote:
> Working on a Dell 5414 laptop, Stretch.
>
> The WiFi works, but the Ethernet doesn't, and I can't figure out why.
>
> ip addr:
>
> 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: enp0s31f6: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN
> group default qlen 1000
>     link/ether 10:05:01:40:f4:43 brd ff:ff:ff:ff:ff:ff
> 3: wwp0s20f0u2i12: <BROADCAST,MULTICAST,NOARP> mtu 1500 qdisc noop
> state DOWN group default qlen 1000
>     link/ether 4e:8a:3a:22:b3:df brd ff:ff:ff:ff:ff:ff
> 4: wlp1s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group
> default qlen 1000
>     link/ether f4:8c:50:17:bc:0e brd ff:ff:ff:ff:ff:ff
> 5: enx10050149649d: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state
> DOWN group default qlen 1000
>     link/ether 10:05:01:49:64:9d brd ff:ff:ff:ff:ff:ff
>
> /etc/network/interfaces:
>
> # 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/*
>
> # The loopback network interface
> auto lo
> iface lo inet loopback
>
> auto wwp0s20f0u2i12
> iface wwp0s20f0u2i12 inet static
>     address 216.17.134.202/29
>     gateway 216.17.134.201
>
> First I tried with wicd, a network manager (the static def wasn't in
> interfaces)
>
> It said the wired interface was up, and assigned the requested IP. It
> wasn't checking after assignment to see if it worked. I turned that
> on, and it never came back.
>
> I removed the network monitor and added the static paragraph to the
> interface file. ifup and ifdown worked, and ip addr said
> wwp0s20f0u2i12 was up.
>
> There are two Ethernet ports on this thing, and I tried both with no
> success. I swapped out the Ethernet cable with the same result.
>
> I replaced Stretch with Buster. It works. dhcp (Comcast) or static (my
> T1). Using the interfaces file.
>
> BTW. ifconfig fans, wait till you get to Buster -- no ifup or down.
> Buster seems to boot using a commented out dhcp paragraph, though.
> Running by hand, '/etc/init.d/network reload' loads the correct
> config.
>
> The 'man interfaces' on Stretch talks a lot about the ethn interfaces.
> It does on Buster, too.
>
> This is less than optimal.
>
> What's going on here? This is Linux, not Winders; Debian, not Ubuntu;
> stable, not Sid. This is what we're supposed to put on Internet
> servers? They had time to make something as simple as this work while
> it was testing. And to correct the man pages, too.
>
> If they didn't have time, the release should have been postponed until
> it was ready for prime time, IMHO.
>
> I looked on the 'Net, asking why the interface names were changed. I
> found a good reason: sometimes the ethn names aren't reliably
> consistent. Fine, I say, you've figured how to make them consistent.
> That's no reason to change the names from a meaningful 4 or 5 chars to
> 11, chosen by /dev/urandom.
>
> Somebody's selling the Debian management a pile of bull excrement.


You mentioned wicd, but I'm not quite able to tell where you made your
change. My apologies if you have already done what I've written below.
I'm going to post anyway on that off chance that it might help someone
else.

I changed mine by clicking that drop down arrow on the right of *my*
wicd interface. This is one of those cases where the window default is
smaller sized so something important is buried behind a non-invasive,
i.e. cognitively almost invisible, drop down arrow.

There's a Preferences option buried there when that window is smaller.
Mine has Preferences, About, and Quit hiding under that arrow.

Under Preferences, there's a General Settings tab. At the top of that
is Network Interfaces for Wireless Interface and Wired Interface.
That's where I changed mine a while back, and it's been working.

DISCLAIMER is that my setup is extremely basic. When all those fancier
settings have to be made for multiple computer systems networking
together, my successful, quick fix setting there may have no effect at
all for that something fancier.

Cindy :)
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with duct tape *

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

#186426

On 03.09.17 20:09, Glenn English wrote:
> I looked on the 'Net, asking why the interface names were changed. I
> found a good reason: sometimes the ethn names aren't reliably
> consistent. Fine, I say, you've figured how to make them consistent.
> That's no reason to change the names from a meaningful 4 or 5 chars to
> 11, chosen by /dev/urandom.

Most eloquently put, and you speak for thousands.

> Somebody's selling the Debian management a pile of bull excrement.

Noo-oo, I firmly believe they're smoking it.

In addition to Fungi4All's solution, there's also ifrename (in package
of same name):

DESCRIPTION
 Ifrename is a tool allowing you to assign a consistent name to each of
 your network interfaces.

But Fungi4All's solution is so easy to use that I'm won over, and
have implemented it here.

Erik

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

#186428

Erik Christiansen composed on 2017-09-04 18:06 (UTC+1000):

> But Fungi4All's solution is so easy to use that I'm won over, and
> have implemented it here. 

I think I started putting net.ifnames=0 on the kernel command line close to 3
years ago. :-)

More than that it's been around:
<https://secure.freedesktop.org/cgit/www/commit/Software/systemd/PredictableNetworkInterfaceNames.mdwn?id=dc0a2bb633786a3705a20638314ec654065f1790>
-- 
"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]

#186429

On 04.09.17 04:42, Felix Miata wrote:
> Erik Christiansen composed on 2017-09-04 18:06 (UTC+1000):
> 
> > But Fungi4All's solution is so easy to use that I'm won over, and
> > have implemented it here. 
> 
> I think I started putting net.ifnames=0 on the kernel command line close to 3
> years ago. :-)
> 
> More than that it's been around:
> <https://secure.freedesktop.org/cgit/www/commit/Software/systemd/PredictableNetworkInterfaceNames.mdwn?id=dc0a2bb633786a3705a20638314ec654065f1790>

Crikey, there's a lot of very literal people on this list.
My courtesy to another poster on_this_thread does not logically preclude
the existence of xxx in other parts of the universe, present or past.

Get a life.

Erik

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

#186430

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

> From: mrmazda@earthlink.net
> To: debian-user@lists.debian.org
>
> Erik Christiansen composed on 2017-09-04 18:06 (UTC+1000):
>
>> But Fungi4All"s solution is so easy to use that I"m won over, and
>> have implemented it here.
>
> I think I started putting net.ifnames=0 on the kernel command line close to 3
> years ago. :-)

You mean on grub.cfg on the linux command line.  This is what the above mentioned procedure does
when grub updates.  If you don't place the modifier in etc/grub then it may vanish again, meaning you
will have to do it again.  The same with other modifiers of grub, like default # entry, background, timeout.

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

#186435

Fungi4All composed on 2017-09-04 07:16 (UTC-0400):

>> From: mrmazda@earthlink.net To: debian-user@lists.debian.org

>> Erik Christiansen composed on 2017-09-04 18:06 (UTC+1000):

>>> But Fungi4All"s solution is so easy to use that I"m won over, and have
>>> implemented it here.

>> I think I started putting net.ifnames=0 on the kernel command line close to
>> 3 years ago. :-)

> You mean on grub.cfg on the linux command line.  This is what the above
> mentioned procedure does when grub updates.  If you don't place the modifier
> in etc/grub then it may vanish again, meaning you will have to do it again.
> The same with other modifiers of grub, like default # entry, background,
> timeout.

I disregard what update scripts do.
menu.lst is moved to menu.lst.## and menu.00 copied back to menu.ls

title Debian 9 Stretch defkernel on sda26
    root (hd0,25)
    kernel /boot/vmlinuz showopts ro root=LABEL=26deb9 ipv6.disable=1
net.ifnames=0 noresume plymouth.enable=0 vga=791 video=1024x768@60
video=1440x900@60
    initrd /boot/initrd

-- 
"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]

#186439

Very sorry. I told you guys some horrible lies yesterday about Buster.

ifupdown is there.

route is back.

ifconfig is back.

Thanks much, Fungi4All, for the name fix, I haven't implemented it
yet, and I'm not sure I will because who knows what'll happen in the
next release. I'm going to try to live with the peculiar interface
names until the proper ones come back like the utilities did.

However:

The interface names are still broken, as is the man page.

The interface file with the Ethernet address that worked yesterday
doesn't seem to work this morning. Systemd claims the file is written
incorrectly (it isn't, according to the man page; and it worked
yesterday) Ifup doesn't like it either. I can bring up the interface
and assign it an address with ifconfig.

And I can fix (and see) the routing table with route.

--
Glenn English

[toc] | [prev] | [standalone]

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

csiph-web