Difference between revisions of "Talk:Netctl"

From ArchWiki
Jump to: navigation, search
(Passphrase in section 3.3)
(Altering a currently enabled profile: reenable command readded)
(28 intermediate revisions by 7 users not shown)
Line 1: Line 1:
==Passphrase in section 3.3==
+
== Altering a currently enabled profile ==
Passphrase in 3.3, what is it about? What is it protecting and how do I set it? <br>
+
-- [[User:Doru001|Doru001]] ([[User talk: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.
+
Concerning this note:
:-- [[User:Jstjohn|Jstjohn]] ([[User talk:Jstjohn|talk]]) 15:29, 27 May 2013 (UTC)
+
{{Note|
 +
* If there is ever a need to alter a currently enabled profile, execute {{ic|netctl reenable <profile>}} to apply the changes.
 +
* ''interface'' is hardware minus, e.g netctl-auto@wlan0.service or netctl-auto@enp2s0.service
 +
}}
 +
I find the second line in this note confusing, and the first line may be unnecessary. I found myself having to reboot my system to get any wireless profile changes to take effect. Through trial and error, I finally figured out the command {{ic|systemctl restart netctl-auto@<interface>.service}} allows the changes to take effect without requiring a reboot. Further, it appears that the command {{ic|netctl reenable <profile>}} is not necessary to achieve these results; although, some profile modifications did require that I issue the {{ic|systemctl restart netctl-auto@<interface>.service}} command twice before my wireless Internet connection would come back up. Has anyone else observed this?
 +
[[User:Mc33|Mc33]] ([[User talk:Mc33|talk]]) 04:59, 17 July 2013 (UTC)
  
::Thank you, now it is clear. [[User:Doru001|Doru001]] ([[User talk:Doru001|talk]]) 06:30, 29 May 2013 (UTC)
+
: From netctl(1):
 +
:{{bc|<nowiki>reenable [PROFILE]
 +
    Reenable the systemd unit for the profile specified. This is effectively a combination of ‘disable’ and ‘enable’.</nowiki>}}
 +
: So I'd say the first line of the note is absolutely incorrect. I think your command {{ic|systemctl restart netctl-auto@<interface>.service}} should be listed instead, and we should probably add simple {{ic|netctl restart <profile>}} too in case people don't use {{ic|netctl-auto@.service}}. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 07:45, 17 July 2013 (UTC)
  
==netctl does not start at boot==
+
::On the contrary, the {{ic|reenable}} command is correct. But it applies to specific profiles, not to {{ic|netctl-auto}}. [[User:Halosghost|Halosghost]] ([[User talk:Halosghost|talk]]) 12:32, 17 July 2013 (UTC)
I carefully followed the instructions on this page and on the Beginner's Guide to migrate from netcfg to netctl and, as I said [https://bbs.archlinux.org/viewtopic.php?pid=1280118#p1280118 here], netctl does not start at boot. Please tell me what is wrong and, if necessary, complete the instructions.
+
 
 +
::: Right, it does not apply to {{ic|netctl-auto}}, my mistake... But my point is, that it does not manipulate currently running processes, it only deletes & re-creates some symlink. To actually apply changes to some profile, you need to {{ic|netctl restart <profile>}}. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 13:05, 17 July 2013 (UTC)
 +
 
 +
::::I've re-added the ''reenable'' command: [https://wiki.archlinux.org/index.php?title=Netctl&diff=275702&oldid=275546] -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 18:18, 15 September 2013 (UTC)
 +
 
 +
: Regarding the second line, I have absolutely no idea of what does ''interface is hardware minus'' mean... -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 07:45, 17 July 2013 (UTC)
 +
 
 +
:I've removed the note as it's not related to that section, it's confusing etc. If someone wants it, feel free to expand and clarify it and put it back. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 16:49, 25 July 2013 (UTC)
 +
 
 +
== My working eduroam config (with TimeoutDHCP and anonymous identity) ==
 +
 
 +
 
 +
Description='eduroam for <your username>'
 +
Interface=wlp2s0
 +
Connection=wireless
 +
Security=wpa-configsection
 +
TimeoutDHCP=60
 +
IP=dhcp
 +
WPAConfigSection=(
 +
        'ssid="eduroam"'
 +
        'proto=RSN'
 +
        'key_mgmt=WPA-EAP'
 +
        'pairwise=CCMP'
 +
        'auth_alg=OPEN'
 +
        'eap=TTLS'
 +
        'identity="<your username>@tu-chemnitz.de"'
 +
        'password="<your password>"'
 +
        'anonymous_identity="anonymous@tu-chemnitz.de"'
 +
        'priority=2'
 +
        'phase2="auth=PAP"'
 +
)
 +
 
 +
This /etc/netctl/eduroam works for me. Maybe someone should update the main article?! Thank you!
 +
 
 +
: I'd certainly not replace the current config in [[netctl#Eduroam]]. I have another, different config, but several people had trouble with connecting in Prague using my profile, so I think it's very specific. Perhaps separate page would be better, when there are more configs. But more information would be needed, the page can't be just set of different configs... -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 07:55, 14 August 2013 (UTC)
 +
 
 +
== What is the first command used to set up netctl? ==
 +
 
 +
"''Once you have created your profile, make an attempt to establish a connection using the newly created profile by running:''"
 +
    '''# netctl start profile'''
 +
 
 +
Shouldn't the command be enable? From the man page:
 +
 
 +
  start [PROFILE]
 +
          Start the network profile specified on the command line.
 +
 
 +
  enable [PROFILE]
 +
          Enable the systemd unit for the profile specified. This will create
 +
          a unit configuration file. If the file already exists, the command
 +
          fails. No other profiles than the one specified will be enabled.
 +
          Changes to the general options in a profile specification will not
 +
          propagate to the unit configuration file automatically. After such
 +
          changes, it is necessary to ‘reenable’ the profile.
 +
 
 +
[[User:Xtian|Xtian]] ([[User talk:Xtian|talk]]) 15:49, 15 September 2013 (UTC)
 +
 
 +
:The command is correct, you can start disabled profile. Disabled means just that it will not start automatically at boot. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 18:11, 15 September 2013 (UTC)

Revision as of 18:18, 15 September 2013

Altering a currently enabled profile

Concerning this note:

Note:
  • If there is ever a need to alter a currently enabled profile, execute netctl reenable <profile> to apply the changes.
  • interface is hardware minus, e.g netctl-auto@wlan0.service or netctl-auto@enp2s0.service

I find the second line in this note confusing, and the first line may be unnecessary. I found myself having to reboot my system to get any wireless profile changes to take effect. Through trial and error, I finally figured out the command systemctl restart netctl-auto@<interface>.service allows the changes to take effect without requiring a reboot. Further, it appears that the command netctl reenable <profile> is not necessary to achieve these results; although, some profile modifications did require that I issue the systemctl restart netctl-auto@<interface>.service command twice before my wireless Internet connection would come back up. Has anyone else observed this? Mc33 (talk) 04:59, 17 July 2013 (UTC)

From netctl(1):
reenable [PROFILE]
    Reenable the systemd unit for the profile specified. This is effectively a combination of ‘disable’ and ‘enable’.
So I'd say the first line of the note is absolutely incorrect. I think your command systemctl restart netctl-auto@<interface>.service should be listed instead, and we should probably add simple netctl restart <profile> too in case people don't use netctl-auto@.service. -- Lahwaacz (talk) 07:45, 17 July 2013 (UTC)
On the contrary, the reenable command is correct. But it applies to specific profiles, not to netctl-auto. Halosghost (talk) 12:32, 17 July 2013 (UTC)
Right, it does not apply to netctl-auto, my mistake... But my point is, that it does not manipulate currently running processes, it only deletes & re-creates some symlink. To actually apply changes to some profile, you need to netctl restart <profile>. -- Lahwaacz (talk) 13:05, 17 July 2013 (UTC)
I've re-added the reenable command: [1] -- Lahwaacz (talk) 18:18, 15 September 2013 (UTC)
Regarding the second line, I have absolutely no idea of what does interface is hardware minus mean... -- Lahwaacz (talk) 07:45, 17 July 2013 (UTC)
I've removed the note as it's not related to that section, it's confusing etc. If someone wants it, feel free to expand and clarify it and put it back. -- Lahwaacz (talk) 16:49, 25 July 2013 (UTC)

My working eduroam config (with TimeoutDHCP and anonymous identity)

Description='eduroam for <your username>'
Interface=wlp2s0
Connection=wireless
Security=wpa-configsection
TimeoutDHCP=60
IP=dhcp
WPAConfigSection=(
        'ssid="eduroam"'
        'proto=RSN'
        'key_mgmt=WPA-EAP'
        'pairwise=CCMP'
        'auth_alg=OPEN'
        'eap=TTLS'
        'identity="<your username>@tu-chemnitz.de"'
        'password="<your password>"'
        'anonymous_identity="anonymous@tu-chemnitz.de"'
        'priority=2'
        'phase2="auth=PAP"'
)

This /etc/netctl/eduroam works for me. Maybe someone should update the main article?! Thank you!

I'd certainly not replace the current config in netctl#Eduroam. I have another, different config, but several people had trouble with connecting in Prague using my profile, so I think it's very specific. Perhaps separate page would be better, when there are more configs. But more information would be needed, the page can't be just set of different configs... -- Lahwaacz (talk) 07:55, 14 August 2013 (UTC)

What is the first command used to set up netctl?

"Once you have created your profile, make an attempt to establish a connection using the newly created profile by running:"

   # netctl start profile

Shouldn't the command be enable? From the man page:

  start [PROFILE]
          Start the network profile specified on the command line.
  enable [PROFILE]
          Enable the systemd unit for the profile specified. This will create
          a unit configuration file. If the file already exists, the command
          fails. No other profiles than the one specified will be enabled.
          Changes to the general options in a profile specification will not
          propagate to the unit configuration file automatically. After such
          changes, it is necessary to ‘reenable’ the profile.

Xtian (talk) 15:49, 15 September 2013 (UTC)

The command is correct, you can start disabled profile. Disabled means just that it will not start automatically at boot. -- Lahwaacz (talk) 18:11, 15 September 2013 (UTC)