On Wed, Aug 24, 2016 at 01:10:23PM -0400, Lennart Sorensen wrote: > Well certainly doing udevtrigger -n -v I see no ethernet devices (but > lots of other things). Looking in sysfs it is possible to dereive which > ethX belongs to which port based on the directory names, but that's > probably not the most convinient manner to deal with it.
OK, udev DOES work: # udevadm info -p /sys/class/net/eth0 P: /devices/platform/soc/soc:internal-regs/f1034000.ethernet/net/eth0 E: DEVPATH=/devices/platform/soc/soc:internal-regs/f1034000.ethernet/net/eth0 E: IFINDEX=2 E: INTERFACE=eth0 E: SUBSYSTEM=net # udevadm info -p /sys/class/net/eth1 P: /devices/platform/soc/soc:internal-regs/f1070000.ethernet/net/eth1 E: DEVPATH=/devices/platform/soc/soc:internal-regs/f1070000.ethernet/net/eth1 E: IFINDEX=3 E: INTERFACE=eth1 E: SUBSYSTEM=net So it isn't hopeless. -- Len Sorensen
