I run into a similar scenario as noahsark1126. In my case, the USB subsystem can have its power be turned off and later on turned on.
]]>Isn't just removing the cable the right thing to do? By unplugging the USB-Ethernet adapter you are removing a chunk of networking hardware. The journal indicates that vital state information for eth0 has disappeared which bears this out. I wouldn't expect netctl to perform exactly as netcfg did and perhaps netcfg's previous behaviour was more due to luck than design.
I suppose you are right, but I cannot leave the adapter plugged in all the time. Maybe the better solution is to use acpid / udev to start netctl-ifplugd when the interface is detected.
]]>Now, if I only remove the ethernet cable but leave the NIC plugged, then the interface deconfigures and ifplugd continues running.
But if I remove the USB NIC from the computer, ifplugd stops completely. So next time I plug it in, nothing happens. Here are the relevant lines from the journal:
ifplugd[1044]: Link beat lost.
ifplugd[1044]: Executing '/etc/ifplugd/netctl.action eth0 down'.
ifplugd[1044]: client: Stopping network profile 'wired'...
ifplugd[1044]: client: /usr/lib/network/network: line 17: /sys/class/net/eth0/flags: No such file or directory
ifplugd[1044]: client: Stopped network profile 'wired'
ifplugd[1044]: Program executed successfully.
ifplugd[1044]: Exiting.
This used to work fine with net-auto-wired in netcfg.
]]>