Displaying 3 results from an estimated 3 matches for "enp10s0f1".
Did you mean:
enp130s0f1
2017 Apr 11
3
OT: systemd Poll
On Tue, Apr 11, 2017 at 08:09:01AM -0400, Pete Orrall wrote:
> > And *why* random NIC names? Quick, you've got servers from 5
> > manufacturers, of different ages... what's the NIC going to be called? Do
> > names like enp5s0 offer any convenience to *anyone* not a hardware
> > engineer?
>
> As someone else had stated, it's not related to SystemD but
>
2017 Apr 11
0
OT: systemd Poll
...hernet)
eno2: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 0c:c4:7a:c8:a5:4d txqueuelen 1000 (Ethernet)
Those two are my onboard nic, Intel - Scheme 1
enp10s0f0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 00:1b:21:94:72:37 txqueuelen 1000 (Ethernet)
enp10s0f1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 00:1b:21:94:72:36 txqueuelen 1000 (Ethernet)
enp9s0f0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 00:1b:21:94:72:35 txqueuelen 1000 (Ethernet)
enp9s0f1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500...
2017 Apr 11
1
OT: systemd Poll
...BROADCAST,MULTICAST> mtu 1500
> ether 0c:c4:7a:c8:a5:4d txqueuelen 1000 (Ethernet)
>
> Those two are my onboard nic, Intel - Scheme 1
>
> enp10s0f0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
> ether 00:1b:21:94:72:37 txqueuelen 1000 (Ethernet)
> enp10s0f1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
> ether 00:1b:21:94:72:36 txqueuelen 1000 (Ethernet)
> enp9s0f0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
> ether 00:1b:21:94:72:35 txqueuelen 1000 (Ethernet)
> enp9s0f1: flags=4099<UP,BROADCAST,MULTICA...