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


Groups > linux.debian.user > #162399

Re: Question: eth0 vs enp1s0 (second try)

From Hans <hans.ullrich@loop.de>
Newsgroups linux.debian.user
Subject Re: Question: eth0 vs enp1s0 (second try)
Date 2015-12-31 19:10 +0100
Message-ID <qLPPJ-7P9-21@gated-at.bofh.it> (permalink)
References <qL7lE-49U-19@gated-at.bofh.it> <qLqHE-8io-7@gated-at.bofh.it> <qLNkS-68I-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


Hi Brian,
> Is there no sign of any discovered interfaces for the Aspire in the
> output of dmesg?
> 
I get this: 

dmesg | grep eth0 
[    2.201866] forcedeth 0000:00:0a.0: ifname eth0, PHY OUI 0x732 @ 1, addr 
1c:75:08:2c:84:f8
[   36.198523] forcedeth 0000:00:0a.0 eth0: MSI enabled
[   36.198795] forcedeth 0000:00:0a.0 eth0: no link during initialization
[   36.199147] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   75.435837] forcedeth 0000:00:0a.0 eth0: link down



> dmesg or journalctl have no indication that eth0 on the EEEPC is renamed?
> 
> [...]


> I think you mean "net.ifnames=0".
> 

Yey, of course, it was just a typo. :)

> What do 'ls /sys/class/net' and 'ip link' give without this addition?

I get:

ls /sys/class/net/

enp1s0  Io  wlan0


Brian, I believe, for now I will stay with the net.ifnames=0 solution. I 
checjed, if I want to use enp1s0, I haved to edit a lot of configuration files 
from eth0 to enp1s0. This is rather annoying, as any update of a package will 
force me to that again and again.

As long the developers won't find a solution, which will fit both options, I 
will stay at eth0. When debian changed completely to enp1s0 (and this includes 
all the configurations, too), I can easyly remove the net.ifnames option and 
return to enp1s0.

I believe, the different outrputs are just becaus the EEEPC is newer and got a 
newer hardware and a more talking BIOS.

Thank you for all the help, the explanation is not as easy as I though, but 
the solution is.

So let this problem be solved for now.

Thank you (and all the other friends who helped here) very much indeed.

I wish you and your family a very happy new year and much joy of hacking.

Thanks again, and best regards

Hans 

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


Thread

Question: eth0 vs enp1s0 Hans <hans.ullrich@loop.de> - 2015-12-29 19:40 +0100
  Re: Question: eth0 vs enp1s0 Felix Miata <mrmazda@earthlink.net> - 2015-12-29 19:50 +0100
  Re: Question: eth0 vs enp1s0 Brian <ad44@cityscape.co.uk> - 2015-12-29 20:20 +0100
    Re: Question: eth0 vs enp1s0 Hans <hans.ullrich@loop.de> - 2015-12-29 21:00 +0100
      Re: Question: eth0 vs enp1s0 Brian <ad44@cityscape.co.uk> - 2015-12-29 22:30 +0100
      Re: Question: eth0 vs enp1s0 Felix Miata <mrmazda@earthlink.net> - 2015-12-29 22:40 +0100
      Re: Question: eth0 vs enp1s0 Jörg-Volker Peetz <jvpeetz@web.de> - 2015-12-30 13:00 +0100
        Re: Question: eth0 vs enp1s0 Hans <hans.ullrich@loop.de> - 2015-12-30 15:40 +0100
          Re: Question: eth0 vs enp1s0 Chris Bannister <cbannister@slingshot.co.nz> - 2015-12-30 16:00 +0100
            Re: Question: eth0 vs enp1s0 Hans <hans.ullrich@loop.de> - 2015-12-30 16:20 +0100
        Re: Question: eth0 vs enp1s0 (second try) Hans <hans.ullrich@loop.de> - 2015-12-30 16:20 +0100
          Re: Question: eth0 vs enp1s0 (second try) Brian <ad44@cityscape.co.uk> - 2015-12-31 16:30 +0100
            Re: Question: eth0 vs enp1s0 (second try) Hans <hans.ullrich@loop.de> - 2015-12-31 19:10 +0100
              Re: Question: eth0 vs enp1s0 (second try) Brian <ad44@cityscape.co.uk> - 2016-01-01 13:10 +0100
                Re: Question: eth0 vs enp1s0 (second try) Vincent Lefevre <vincent@vinc17.net> - 2016-01-01 17:30 +0100
                Re: Question: eth0 vs enp1s0 (second try) Brian <ad44@cityscape.co.uk> - 2016-01-02 17:30 +0100
                Re: Question: eth0 vs enp1s0 (second try) Vincent Lefevre <vincent@vinc17.net> - 2016-01-06 14:00 +0100
                Re: Question: eth0 vs enp1s0 (second try) Brian <ad44@cityscape.co.uk> - 2016-01-06 15:00 +0100
                Re: Question: eth0 vs enp1s0 (second try) Vincent Lefevre <vincent@vinc17.net> - 2016-01-07 03:00 +0100
                Re: Question: eth0 vs enp1s0 (second try) Rick Thomas <rbthomas@pobox.com> - 2016-01-07 07:20 +0100
                Re: Question: eth0 vs enp1s0 (second try) Vincent Lefevre <vincent@vinc17.net> - 2016-01-07 10:50 +0100
                Re: Question: eth0 vs enp1s0 (second try) Brian <ad44@cityscape.co.uk> - 2016-01-07 14:20 +0100
                Re: Question: eth0 vs enp1s0 (second try) Brian <ad44@cityscape.co.uk> - 2016-01-07 19:50 +0100
                Re: Question: eth0 vs enp1s0 (second try) Vincent Lefevre <vincent@vinc17.net> - 2016-01-08 02:40 +0100
                Re: Question: eth0 vs enp1s0 (second try) Brian <ad44@cityscape.co.uk> - 2016-01-08 13:10 +0100
          MAC address and security (was: Question: eth0 vs enp1s0 (second try)) Vincent Lefevre <vincent@vinc17.net> - 2015-12-31 16:50 +0100
            Re: MAC address and security Christian Seiler <christian@iwakd.de> - 2015-12-31 23:20 +0100
  Re: Question: eth0 vs enp1s0 Charlie Kravetz <cjk@teamcharliesangels.com> - 2015-12-29 20:20 +0100
  Re: Question: eth0 vs enp1s0 Michael Biebl <biebl@debian.org> - 2015-12-31 22:20 +0100
    Re: Question: eth0 vs enp1s0 Hans <hans.ullrich@loop.de> - 2015-12-31 22:30 +0100
    Re: Question: eth0 vs enp1s0 Brian <ad44@cityscape.co.uk> - 2016-01-02 17:30 +0100

csiph-web