I'd like to ask if anyone has any insight into locking down a specific network interface configuration. I am in a situation where I provide a computer to an end user with 2 NICs. One is for "my" use to talk with specific hardware and should not be modified. This also goes for the hostname as well. The second interface is for the end user's connection to the rest of the building/facility.
I currently go through the effort of nicknaming the interfaces and writing up a detailed guide for the user to follow, but they still manage to break things. I've tried using chattr to make some of the configuration files immutable, but the system-config-network pukes, as it tries to rewrite all of the configuration files, regardless of any modifications. I've also thought about writing an init script to replace the settings on boot or even writing a custom frontend application to modify only the settings they are supposed to. Neither of which are very appetizing, but both doable. It doesn't appear system-config-network has any command line options to just pop up the window of the interface, or it would be as simple as creating icons for them to use. I'm currently using SL4.1, but plan to migrate 5.x by the end of the year. Cheers, Mark -- Mr. Mark V. Stodola Digital Systems Engineer National Electrostatics Corp. P.O. Box 620310 Middleton, WI 53562-0310 USA Phone: (608) 831-7600 Fax: (608) 831-9591
