Talk:Netifrc

Additional section for finding network names
A section should be added on how to find out what the network interface names are, maybe to run dmesg | grep -i 'network interface'.


 * I added two methods for identifying interfaces. Don't forget to sign your messages on talk pages with your signature. --Maffblaster (talk) 18:36, 12 May 2015 (UTC)


 * Sorry, I am in doubt if having such section here was a good idea. These information about network interface names seem to be needed in several places, not only here. Especially since udev pushed its "predictable" crap, there are multiple threads on the forums with problems as people don't know about. Of course, most of that trouble is caused by using netifrc at all. But even without using netifrc, this knowledge about the network interface names could be needed, e.g. for setting a static IP address per interface without using the gui. I think a separate article Network interface in  might be a better place. There we could collect such information without bloating netifrc, wifi or other articles.


 * But, what about the "rc-update add net. default" stuff? This is very specific to netifrc and should be mentioned here, see Handbook:Parts/Networking/Introduction,.


 * Regarding "Use curly braces and commas to speed up the process when dealing with multiple interfaces:", why should using syntax instead of typing the path twice be specific for multiple interfaces? --Charles17 (talk) 06:13, 13 May 2015 (UTC)


 * The with curly braces was provided simply as a tip for users creating multiple interfaces in order to save them a bit of typing.. You can use either format; they are both visible in the Handbook. --Maffblaster (talk) 23:48, 17 April 2017 (UTC)

"DHCP is the default behavior ..."
Please regard this sentence given in the filebox Netifrc. Almost everybody can guess what it means. But, could it be reworded something like "The network configuration scripts will use dhcp by default to set up your interfaces. If you need to set up something more ..." and the example shown with some non-default configuration?

As the "behavior" is already default, the example presently shown is useless (even worse in the handbook). Putting dhcp or not doesn't change anything. So why not put a more useful example?

Another thing, regarding : Wasn't there something saying netifrc should work in some (or more) cases even without setting up the  file? If so, this might be mentioned in Netifrc before before saying "it is created by the system administrator ...".

--Charles17 (talk) 08:05, 28 July 2017 (UTC)