Hi all,
I have been using a BBB with a Debian Testing system for some time but
now I've run into a problem.
When I connect the BBB via the USB cable to my linux system (running
Debian Testing) the USB networkng device no longer comes up as ethX,
but instead comes up as:
enx9059af57444e: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN
group default qlen 1000
link/ether 90:59:af:57:44:4e brd ff:ff:ff:ff:ff:ff
and doesn't get assigned the normal 192.168.7.1 IP address.
I have no idea what changed. The kernel is 3.16.0-4-amd64 for Debian.
Clues?
Erik
Hi all,
I have been using a BBB with a Debian Testing system for some time but
now I’ve run into a problem.
When I connect the BBB via the USB cable to my linux system (running
Debian Testing) the USB networkng device no longer comes up as ethX,
but instead comes up as:
enx9059af57444e: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN
group default qlen 1000
link/ether 90:59:af:57:44:4e brd ff:ff:ff:ff:ff:ff
and doesn’t get assigned the normal 192.168.7.1 IP address.
I have no idea what changed. The kernel is 3.16.0-4-amd64 for Debian.
Clues?
It’s something with systemd 222 transition in debian stretch. Ran into it too last week, no ideas yet…
Robert Nelson wrote:
It's something with systemd 222 transition in debian stretch. Ran into it
too last week, no ideas yet...
This explains it all:
PredictableNetworkInterfaceNames
I created a custom udev rule as explained in that article.
Cheers,
Erik