Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Wed 18 Jul 2018, 12:42
All times are UTC - 4
 Forum index » House Training » Bugs ( Submit bugs )
Possible networking 'bug' in Upup Bionic Beaver 18.05?
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 1 of 1 [5 Posts]  
Author Message
Mike Walsh


Joined: 28 Jun 2014
Posts: 3907
Location: King's Lynn, UK.

PostPosted: Thu 10 May 2018, 05:14    Post subject:  Possible networking 'bug' in Upup Bionic Beaver 18.05?
Subject description: May be a 'bug', may not; just curious if anyone else has found this one.....
 

@ peebee/whoever:-

Normally, my Ethernet connection invariably comes up as interface 'eth0' or occasionally 'eth1' (Lucid springs to mind here). But I've discovered a strange difference in BB.

For some reason, my ethernet interface is reporting itself as 'enp3s3'..??? It configures, and connects fine.....but for the very first time, I cannot install WINE correctly. (It won't download/install the 'gecko' and 'mono' packages, needed for HTML rendering (gecko) and .NET framework emulation (mono)). Insists there's no connection to the server 'stream'.

Anybody else discovered this 'oddity'?


Mike. Wink

_________________
MY PUPPY PACKAGES | 'Thanks' are always appreciated!
--------------------------------------

Back to top
View user's profile Send private message Visit poster's website 
perdido


Joined: 09 Dec 2013
Posts: 842
Location: ¿Altair IV , Just north of Eeyore Junction.?

PostPosted: Thu 10 May 2018, 07:45    Post subject:  

Thats not a bug, its a feature Smile

http://www.ubuntugeek.com/network-interfaces-name-change-in-ubuntu-15-10-wily-werewolf.html

Some info in that link about inserting a UDEV rule to change the name.

I remember seeing a reference to the network name changes in the murga forum somewhere, with a fix. Don't know where though.
Edit:Mentioned here for radky's Dpup-Stretch 7.5
Quote:
Alpha-1 changelog: 20/Oct/2017
- Add /etc/udev/rules.d/80-net-name-slot.rules for conventional network nomenclature


.

Last edited by perdido on Thu 10 May 2018, 08:50; edited 1 time in total
Back to top
View user's profile Send private message 
p310don

Joined: 19 May 2009
Posts: 1205
Location: Brisbane, Australia

PostPosted: Thu 10 May 2018, 07:58    Post subject:  

Quote:
Thats not a bug, its a feature Smile


Seems like a solution to a problem that nobody had...
Back to top
View user's profile Send private message 
rcrsn51


Joined: 05 Sep 2006
Posts: 12206
Location: Stratford, Ontario

PostPosted: Thu 10 May 2018, 09:29    Post subject:  

p310don wrote:
Seems like a solution to a problem that nobody had...

Not so. These "cryptic but predictable" interface names are the equivalent of using UUIDs to identify drive partitions. They uniquely identify the device.

If you have a machine with multiple ethernet or wifi ports, there is no guarantee that they will initialize in the same order. So port #1 may be eth0 on one boot and eth1 on the next.

Using the cryptic names solves this problem.
Back to top
View user's profile Send private message 
Mike Walsh


Joined: 28 Jun 2014
Posts: 3907
Location: King's Lynn, UK.

PostPosted: Thu 10 May 2018, 11:12    Post subject:  

perdido wrote:
Thats not a bug, its a feature Smile

http://www.ubuntugeek.com/network-interfaces-name-change-in-ubuntu-15-10-wily-werewolf.html

Some info in that link about inserting a UDEV rule to change the name.

I remember seeing a reference to the network name changes in the murga forum somewhere, with a fix. Don't know where though.
Edit:Mentioned here for radky's Dpup-Stretch 7.5
Quote:
Alpha-1 changelog: 20/Oct/2017
- Add /etc/udev/rules.d/80-net-name-slot.rules for conventional network nomenclature


Mmm.....

Well, thanks for the link, perdido. That's something I was not aware of, I must admit. More systemd/udev-related stuff. Where will it end..?

rcrsn51 wrote:
Not so. These "cryptic but predictable" interface names are the equivalent of using UUIDs to identify drive partitions. They uniquely identify the device.

If you have a machine with multiple ethernet or wifi ports, there is no guarantee that they will initialize in the same order. So port #1 may be eth0 on one boot and eth1 on the next.

Using the cryptic names solves this problem.


Thanks for the clarification, Bill. Makes sense, I suppose..!

If that's the case, though, I have to assume that PhilB must have employed the above-mentioned 'fix' for Xenial, as the 'follow-up' to Wily. Because my Xenialpup has the 'traditional' interface nomenclature.....and there's definitely no problems installing WINE there.

I guess further disclosures will come to light; 'Bionic' is, after all, still pretty new.

Mike. Wink

_________________
MY PUPPY PACKAGES | 'Thanks' are always appreciated!
--------------------------------------

Back to top
View user's profile Send private message Visit poster's website 
Display posts from previous:   Sort by:   
Page 1 of 1 [5 Posts]  
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » House Training » Bugs ( Submit bugs )
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.0374s ][ Queries: 11 (0.0072s) ][ GZIP on ]