В Wed, 22 Apr 2015 15:45:44 +0200
Roger Oberholtzer
We assemble systems where Ethernet devices are statically configured. They are initialized when the system boots, and the user does not have access via, say, KDE. They can only be modified by root, and typically in yast. We like this because any accidental change causes havoc.
I would like to add a USB network device to the mix. It will be a telephone that the system tethers to in order to access the outside world. In the best of worlds, it would automatically be configured via DHCP. But I do not see how to do this via the traditional static method. The device may not be connected when the system boots. And it may be a different telephone at any time. I do not know how to predict the device handle.
I am trying to see how to keep the static network configurations not under user control while allowing other ones to be dynamic and under user control. Or at least allow the USB device to get configured in a predictable fashion when it is connected.
Add udev rule run script that configures interface when it appears. You can take rule from 13.1 as example.
I had thought that a udev rule may also be a way to go. But I don't seem to get that to work as expected (surely my mistake somewhere).
If you explain what you have done and what does not work someone may be able to help.
Anyone have any suggestions about how to best accomplish this sort of thing?
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org