Difference between revisions of "Talk:Netctl"
(→Netctl does not start when the system at the other end of the connection is down) |
m (→Wrong headings: rm closed discussion) |
||
(15 intermediate revisions by 5 users not shown) | |||
Line 1: | Line 1: | ||
− | == | + | == Altering a currently enabled profile == |
− | |||
− | + | Concerning this note: | |
− | + | {{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) | ||
− | + | : From netctl(1): | |
− | + | :{{bc|<nowiki>reenable [PROFILE] | |
− | -- [[User: | + | 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) | ||
− | : | + | ::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) |
− | |||
− | :: | + | ::: 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) |
− | + | : 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) |
Revision as of 14:37, 18 August 2013
Altering a currently enabled profile
Concerning this 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 simplenetctl restart <profile>
too in case people don't usenetctl-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 tonetctl-auto
. Halosghost (talk) 12:32, 17 July 2013 (UTC)
- On the contrary, the
- 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)