Difference between revisions of "Talk:Netctl"

From ArchWiki
Jump to: navigation, search
(netctl does not start at boot)
(netctl does not start at boot)
Line 13: Line 13:
 
:: I removed your entry to the wiki, your problem is not related to transition from netcfg. {{ic|network.service}} is user-created.<br> -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 10:41, 31 May 2013 (UTC)
 
:: I removed your entry to the wiki, your problem is not related to transition from netcfg. {{ic|network.service}} is user-created.<br> -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 10:41, 31 May 2013 (UTC)
 
:::{{ic|network.service}} is user created according to the Beginner's Guide and I believe that this simple instruction would serve many while not hurting anybody. [[User:Doru001|Doru001]] ([[User talk:Doru001|talk]]) 08:32, 1 June 2013 (UTC)
 
:::{{ic|network.service}} is user created according to the Beginner's Guide and I believe that this simple instruction would serve many while not hurting anybody. [[User:Doru001|Doru001]] ([[User talk:Doru001|talk]]) 08:32, 1 June 2013 (UTC)
 +
:::Maybe we should add a line saying that other network caring services like network.service and others should be disabled. How about this? [[User:Doru001|Doru001]] ([[User talk:Doru001|talk]]) 13:56, 1 June 2013 (UTC)

Revision as of 13:56, 1 June 2013

Passphrase in section 3.3

Passphrase in 3.3, what is it about? What is it protecting and how do I set it?
-- Doru001 (talk) 10:29, 27 May 2013 (UTC)

That section is talking about obfuscating the passphrase to connect to a wireless network. By default, netctl stores the passphrase to connect to a wireless network in plaintext. If a nefarious user is able to read the passphrase stored on your system, then they can connect to your wireless network. Obfuscating the passphrase just makes this more difficult to do. Section 3.3 explains how to obfuscate the passphrase.
-- Jstjohn (talk) 15:29, 27 May 2013 (UTC)
Thank you, now it is clear. Doru001 (talk) 06:30, 29 May 2013 (UTC)

netctl does not start at boot

I carefully followed the instructions on this page and on the Beginner's Guide to migrate from netcfg to netctl and, as I said here, netctl does not start at boot. Please tell me what is wrong and, if necessary, complete the instructions.--Doru001 (talk) 14:01, 30 May 2013 (UTC)

As a result of the above mentioned thread I added the entry about sudo systemctl disable network to the netcfg to netctl migration list. Please check and post here if that is wrong.--Doru001 (talk) 07:10, 31 May 2013 (UTC)
I removed your entry to the wiki, your problem is not related to transition from netcfg. network.service is user-created.
-- Lahwaacz (talk) 10:41, 31 May 2013 (UTC)
network.service is user created according to the Beginner's Guide and I believe that this simple instruction would serve many while not hurting anybody. Doru001 (talk) 08:32, 1 June 2013 (UTC)
Maybe we should add a line saying that other network caring services like network.service and others should be disabled. How about this? Doru001 (talk) 13:56, 1 June 2013 (UTC)