up vote 2 down vote favorite

The devices that used typically to be called eth0 now seem to be p3p1, p2p1, p1p1.

I presume the name means something, but have been unable to find out what.

I think it is not related in any way to W3C's P3P1.

share|improve this question
    
It's a result of predictable network interface names: freedesktop.org/wiki/Software/systemd/… – muru Dec 9 '14 at 11:50
    
it-stuff-i-needed.blogspot.fr/2014/07/… might also help your understanding. – Graham Dec 9 '14 at 11:53
    
Hm, OK, that seems kind of reasonable. Except that my p3p1 is definitely an on-motherboard Ethernet adaptor, which lspci gives as 05:00.0, which appears to differ from the explanation is the answer below. It would really help if the developers who make changes like that gave a hint nearby to find what and why. Ho Hum. Thanks all. – Gordon Dec 9 '14 at 12:53
    
My brain has just cried "tilt" with that. The solution to the problem of inconsistent names is to change the names to something completely different. I'd have thought a map of conventional names to their actual physical devices would have been more appropriate. Am I missing something? – Gordon Dec 9 '14 at 13:13
up vote 2 down vote

This is a network interfaces, and it is derived from:

Lan-On-Motherboard interfaces: em<port number> (ethernet-on-motherboard <1,2 ..>)

PCI add-in interfaces: p<slot number>p<port number>_<virtual function instance>
share|improve this answer
2  
Presumably there's a means to ascertain the numbers as above. The freedesktop page referenced above says "just by looking at lspci you can figure out what the interface is going to be called". Well, when they say "you", they seem not to be referring to me :-( – Gordon Dec 9 '14 at 15:11
    
Oh good grief.After an upgrade to 10.04.2 the Ethernet interface p3p1 has vanished, no others have appeared, no ethX has appeared lspci still shows the network device present. – Gordon Jun 12 '17 at 8:00
    
Ohhh. Upgrade to 16.04.02 not 10.04.2. There are also no enXXX devices appeared. Another issue I forgot. For some reason this PC seems not to run with any kernel more recent than 3.13.0-51, so that is the kernel I'm presently obliged to use. I did the upgrade because I hoped that might have been resolved. – Gordon Jun 12 '17 at 8:55
    
ifconfig -a shows an eth0 with a HWaddr. Maybe I have to unwind the changes to get to p3p1 and revert to eth0? Maddening! – Gordon Jun 12 '17 at 9:16

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.