Netctl profile works flawlessly unless called by netctl-auto

I have four wireless profiles in /etc/netctl and all of them work just fine when used manually, i.e. netctl enable <profile> or netctl start <profile>, but when I set up netctl-auto one of them keeps failing.
The three others are identical except for the SSID and the WPA key so I'm including just one of them here along with the one the keeps failing, but there's really nothing special here. The only difference is that the one that keeps failing has a hidden SSID.
One of the three which work:
Description='WiFi: AMPERSAND'
Interface=wlan0
Connection=wireless
Security=wpa
IP=dhcp
ESSID='ampersand'
# Prepend hexadecimal keys with \"
# If your key starts with ", write it as '""<key>"'
# See also: the section on special quoting rules in netctl.profile(5)
Key='0f20f8g0fg2'
# Uncomment this if your ssid is hidden
#Hidden=yes
The one that doesn't:
Description='WiFi: HANLUKIO'
Interface=wlan0
Connection=wireless
Security=wpa
IP=dhcp
ESSID='kjKJls83jpkskKkkUyasjqKAS'
# Prepend hexadecimal keys with \"
# If your key starts with ", write it as '""<key>"'
# See also: the section on special quoting rules in netctl.profile(5)
Key='CCyzJvIVljL9hsHSbhspPhs929c0hLssh38sPssofo382d8OS320dgSop3hfIGdi32GF'
# Uncomment this if your ssid is hidden
Hidden=yes
The wiki doesn't seem to mention anything specific concerning a hidden SSID and netctl-auto, and since all four work flawlessly when used manually, I'm out of ideas. I'll try setting $NETCTL_DEBUG on the next try and hopefully that will output something meaningful but that wont be till next week and I was curious if anyone knew off the bat what the issue might me.

As I understand man netctl.special, the netctl-auto does not honor the WPADriver parameters in the profiles, because it works on the interface level. Hence, the "Hidden=yes" is not parsed and the hidden ones are probably discarded.
You should be able to add the parameter "scan_ssid=1" (or "Hidden=yes" - not sure) to a hook for the interface in /etc/netctl/interfaces/
edit: wrong semantics striked; see below.
Last edited by Strike0 (2013-12-16 22:16:36)

Similar Messages

  • [SOLVED] netctl-auto not working, and I cannot remove netctl instance

    Hi, I installed Arch a few days ago, netctl-auto was working yesterday but today it's not.
    Note that
    netctl start
    works: I have a problem with netctl-auto only.
    $ ping -c 3 8.8.8.8
    connect: Network in unreachable
    I have created only one netctl profile so far, it's called wlp4s0-VM581389-2G (wlp4s0 is the name of my wireless interface)
    $ ls /etc/netctl
    examples hooks interfaces wlp4s0-VM581389-2G
    $ netctl list
    wlp4s0-VM581389-2G
    wpa_actiond is installed, and I have done
    systemctl enable [email protected]
    But for some reason I have some extra netctl@ instances that shouldn't be there. I am wondering if they could be the cause of netctl-auto not working properly:
    $ systemctl | grep netctl
    [email protected] loaded active running Automatic wireless network connection using netctl profiles
    ● netctl@my\x2dnetwork.service loaded failed failed Networking for netctl profile my-network
    ● netctl@wlp4s0\x2dVM581389\x2d2G.service loaded failed failed Networking for netctl profile wlp4s0-VM581389-2G
    system-netctl.slice loaded active active system-netctl.slice
    system-netctl\x2dauto.slice loaded active active system-netctl\x2dauto.slice
    - What are these bullet points at the beginning of these two lines?
    - Where do netctl@my\x2dnetwork.service and netctl@wlp4s0\x2dVM581389\x2d2G.service come from? They might be instances that I had enabled in the past.
    These instances are not enabled and they are inactive, but they are loaded!
    $ systemctl is-enabled netctl@my\x2dnetwork.service
    Failed to get unit file state for [email protected]: No such file or directory
    $ systemctl status netctl@my\x2dnetwork.service
    [email protected] - Networking for netctl profile myx2dnetwork
    Loaded: loaded (/usr/lib/systemd/system/[email protected]; static; vendor preset: disabled)
    Active: inactive (dead)
    Docs: man:netctl.profile(5)
    I have tried to get rid of them, but not managed:
    $ systemctl stop netctl@my\x2dnetwork.service
    $ systemctl disable netctl@my\x2dnetwork.service
    $ systemctl | grep netctl
    [email protected] loaded active running Automatic wireless network connection using netctl profiles
    netctl.service loaded active exited (Re)store the netctl profile state
    ● netctl@my\x2dnetwork.service loaded failed failed Networking for netctl profile my-network
    ● netctl@wlp4s0\x2dVM581389\x2d2G.service loaded failed failed Networking for netctl profile wlp4s0-VM581389-2G
    system-netctl.slice loaded active active system-netctl.slice
    system-netctl\x2dauto.slice loaded active active system-netctl\x2dauto.slice
    [user@mascip-toshiba ~]$ systemctl daemon-reload
    [user@mascip-toshiba ~]$ systemctl | grep netctl
    [email protected] loaded active running Automatic wireless network connection using netctl profiles
    netctl.service loaded active exited (Re)store the netctl profile state
    ● netctl@my\x2dnetwork.service loaded failed failed Networking for netctl profile my-network
    ● netctl@wlp4s0\x2dVM581389\x2d2G.service loaded failed failed Networking for netctl profile wlp4s0-VM581389-2G
    system-netctl.slice loaded active active system-netctl.slice
    system-netctl\x2dauto.slice loaded active active system-netctl\x2dauto.slice
    Also, I have tried to check with
    netctl-auto list
    , which gives an empty output. I am guessing that it's normal, because the netctl-auto instances are managed by systemd?
    Now, trying to understand what is happening to [email protected]: as seen before with systemctl | grep netctl, it is active and running.
    Then I do:
    $ journalctl -u [email protected]
    -- Reboot --
    Feb 10 17:34:23netctl-auto[270]: Included profile: 'wlp4s0-VM581389-2G'
    wpa_actiond[310]: Starting wpa_actiond session for interface 'wlp4s0'
    So, a wpa_actiond session was started, but I still cannot ping 8.8.8.8. Why?
    Investigating further:
    $ netctl status wlp4s0-VM581389-2G
    ● netctl@wlp4s0\x2dVM581389\x2d2G.service - Networking for netctl profile wlp4s0-VM581389-2G
    Loaded: loaded (/usr/lib/systemd/system/[email protected]; static; vendor preset: disabled)
    Active: failed (Result: exit-code) since Tue 2015-02-10 19:43:17 GMT; 3min 16s ago
    Docs: man:netctl.profile(5)
    Process: 274 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)
    Main PID: 274 (code=exited, status=1/FAILURE)
    Feb 10 19:43:15 mascip-toshiba network[274]: Failed to initialize control interface '/run/wpa_supplicant'.
    Feb 10 19:43:15 mascip-toshiba network[274]: You may have another wpa_supplicant process already running or the file was
    Feb 10 19:43:15 mascip-toshiba network[274]: left by an unclean termination of wpa_supplicant in which case you will need
    Feb 10 19:43:15 mascip-toshiba network[274]: to manually remove this file before starting wpa_supplicant again.
    Feb 10 19:43:17 mascip-toshiba network[274]: The WPA supplicant did not start for interface 'wlp4s0'
    Feb 10 19:43:17 mascip-toshiba network[274]: Failed to bring the network up for profile 'wlp4s0-VM581389-2G'
    Feb 10 19:43:17 mascip-toshiba systemd[1]: netctl@wlp4s0\x2dVM581389\x2d2G.service: main process exited, code=exited, status=1/FAILURE
    Feb 10 19:43:17 mascip-toshiba systemd[1]: Failed to start Networking for netctl profile wlp4s0-VM581389-2G.
    Feb 10 19:43:17 mascip-toshiba systemd[1]: Unit netctl@wlp4s0\x2dVM581389\x2d2G.service entered failed state.
    Feb 10 19:43:17 mascip-toshiba systemd[1]: netctl@wlp4s0\x2dVM581389\x2d2G.service failed.
    "You may have another wpa_supplicant process already running or the file was left by an unclean termination of wpa_supplicant in which case you will need to manually remove this file before starting wpa_supplicant again."
    What does this mean? Which file might have been left by an unclean termination? I tried to find this info in the wpa_supplicant documentation, and by searching on Google, but couldn't find anything.
    Now I am lost:
    - how do I get rid of these two undesired netctl instances?
    - where can I investigate next, to get netctl-auto@wlp4s0 to work?
    Any help greatly appreciated :-)
    Last edited by mascip (2015-02-13 11:15:38)

    What is the output of:
    ls -l /etc/systemd/system/multi-user.target.wants
    netctl-auto cannot be used with explicitly enabled profiles (ie, those for which you have used `netctl enable <profile>`).

  • [SOLVED]netctl-auto no longer working

    Can some kind person point me in the right direction to fix this? Seems to have stopped working after latest upgrade.  Manually netctl start works OK.  Haven't been able to find the solution in man pages or googling.
    [email protected] - Automatic wireless network connection using netctl profiles
    Loaded: loaded (/usr/lib/systemd/system/[email protected]; enabled)
    Active: failed (Result: exit-code) since Wed 2014-07-09 08:00:20 UTC; 1h 14min ago
    Docs: man:netctl.special(7)
    Process: 231 ExecStart=/usr/bin/netctl-auto start %I (code=exited, status=1/FAILURE)
    Jul 09 08:00:20 arch systemd[1]: Failed to start Automatic wireless network connection using netctl profiles.
    Jul 09 08:00:50 arch netctl-auto[231]: Included profile 'wlp16s0-Matviak'
    Jul 09 08:00:51 arch netctl-auto[231]: Included profile 'wlp16s0-WIRELESS'
    Jul 09 08:00:51 arch netctl-auto[231]: Successfully initialized wpa_supplicant
    Jul 09 08:00:51 arch netctl-auto[231]: ctrl_iface exists and seems to be in use - cannot override it
    Jul 09 08:00:51 arch netctl-auto[231]: Delete '/run/wpa_supplicant/wlp16s0' manually if it is not used anymore
    Jul 09 08:00:51 arch netctl-auto[231]: Failed to initialize control interface '/run/wpa_supplicant'.
    Jul 09 08:00:51 arch netctl-auto[231]: You may have another wpa_supplicant process already running or the file was
    Jul 09 08:00:51 arch netctl-auto[231]: left by an unclean termination of wpa_supplicant in which case you will need
    Jul 09 08:00:51 arch netctl-auto[231]: to manually remove this file before starting wpa_supplicant again.
    Last edited by hilltownboy (2014-08-02 12:41:03)

    journalctl -b | grep wlp16s0:
    ul 29 11:27:17 arch systemd-udevd[148]: renamed network interface wlan0 to wlp16s0
    Jul 29 11:27:28 arch kernel: IPv6: ADDRCONF(NETDEV_UP): wlp16s0: link is not ready
    Jul 29 11:27:28 arch kernel: IPv6: ADDRCONF(NETDEV_UP): wlp16s0: link is not ready
    Jul 29 11:27:19 arch dhcpcd[225]: wlp16s0: adding address fe80::ea40:c74b:8e70:d43a
    Jul 29 11:27:23 arch wpa_actiond[317]: Starting wpa_actiond session for interface 'wlp16s0'
    Jul 29 11:27:24 arch dhcpcd[230]: wlp16s0: waiting for carrier
    Jul 29 11:27:24 arch dhcpcd[230]: wlp16s0: carrier acquired
    Jul 29 11:27:25 arch dhcpcd[230]: wlp16s0: IAID e0:20:c5:69
    Jul 29 11:27:28 arch dhcpcd[230]: wlp16s0: carrier lost
    Jul 29 11:27:25 arch systemd[1]: netctl@wlp16s0\x2dWIRELESS.service: main process exited, code=exited, status=1/FAILURE
    Jul 29 11:27:25 arch systemd[1]: Unit netctl@wlp16s0\x2dWIRELESS.service entered failed state.
    Jul 29 11:27:28 arch network[222]: Starting network profile 'wlp16s0-WIRELESS'...
    Jul 29 11:27:28 arch network[222]: Delete '/run/wpa_supplicant/wlp16s0' manually if it is not used anymore
    Jul 29 11:27:28 arch network[222]: The WPA supplicant did not start for interface 'wlp16s0'
    Jul 29 11:27:28 arch network[222]: Failed to bring the network up for profile 'wlp16s0-WIRELESS'
    Jul 29 11:27:28 arch netctl-auto[223]: Included profile 'wlp16s0-Matviak'
    Jul 29 11:27:28 arch netctl-auto[223]: Included profile 'wlp16s0-WIRELESS'
    Jul 29 11:27:28 arch dhcpcd[230]: wlp16s0: soliciting a DHCP lease
    Jul 29 11:27:28 arch dhcpcd[230]: wlp16s0: if_sendrawpacket: Network is down
    Jul 29 11:27:28 arch dhcpcd[230]: wlp16s0: dhcp if_readrawpacket: Network is down
    Jul 29 11:31:21 arch dbus[227]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.7" (uid=1000 pid=605 comm="systemctl restart netctl-auto@wlp16s0 ") interface="org.freedesktop.systemd1.Manager" member="RestartUnit" error name="(unset)" requested_reply="0" destination="org.freedesktop.systemd1" (uid=0 pid=1 comm="/sbin/init ")
    Jul 29 11:31:22 arch dhcpcd[230]: wlp16s0: if_sendrawpacket: Network is down
    Jul 29 11:31:22 arch dhcpcd[230]: wlp16s0: dhcp if_readrawpacket: Network is down
    Jul 29 11:31:25 arch dhcpcd[230]: wlp16s0: if_sendrawpacket: Network is down
    Jul 29 11:31:25 arch dhcpcd[230]: wlp16s0: dhcp if_readrawpacket: Network is down
    Jul 29 11:31:29 arch dhcpcd[230]: wlp16s0: if_sendrawpacket: Network is down
    Jul 29 11:31:29 arch dhcpcd[230]: wlp16s0: dhcp if_readrawpacket: Network is down
    Jul 29 11:31:29 arch sudo[607]: norman : TTY=pts/1 ; PWD=/home/norman ; USER=root ; COMMAND=/usr/bin/systemctl restart netctl-auto@wlp16s0
    Jul 29 11:31:29 arch wpa_actiond[317]: Terminating wpa_actiond session for interface 'wlp16s0'
    Jul 29 11:31:33 arch dhcpcd[230]: wlp16s0: if_sendrawpacket: Network is down
    Jul 29 11:31:33 arch dhcpcd[230]: wlp16s0: dhcp if_readrawpacket: Network is down
    Jul 29 11:31:37 arch dhcpcd[230]: wlp16s0: if_sendrawpacket: Network is down
    Jul 29 11:31:37 arch dhcpcd[230]: wlp16s0: dhcp if_readrawpacket: Network is down
    Jul 29 11:31:41 arch netctl-auto[633]: Included profile 'wlp16s0-Matviak'
    Jul 29 11:31:41 arch netctl-auto[633]: Included profile 'wlp16s0-WIRELESS'
    Jul 29 11:31:41 arch dhcpcd[230]: wlp16s0: if_sendrawpacket: Network is down
    Jul 29 11:31:41 arch dhcpcd[230]: wlp16s0: dhcp if_readrawpacket: Network is down
    Jul 29 11:31:41 arch kernel: IPv6: ADDRCONF(NETDEV_UP): wlp16s0: link is not ready
    Jul 29 11:31:41 arch wpa_actiond[651]: Starting wpa_actiond session for interface 'wlp16s0'
    Jul 29 11:31:43 arch kernel: wlp16s0: authenticate with f8:1a:67:d3:6f:aa
    Jul 29 11:31:43 arch kernel: wlp16s0: send auth to f8:1a:67:d3:6f:aa (try 1/3)
    Jul 29 11:31:43 arch kernel: wlp16s0: authenticated
    Jul 29 11:31:43 arch kernel: wlp16s0: associate with f8:1a:67:d3:6f:aa (try 1/3)
    Jul 29 11:31:43 arch kernel: wlp16s0: RX AssocResp from f8:1a:67:d3:6f:aa (capab=0x421 status=0 aid=2)
    Jul 29 11:31:43 arch kernel: wlp16s0: associated
    Jul 29 11:31:43 arch kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp16s0: link becomes ready
    Jul 29 11:31:43 arch dhcpcd[230]: wlp16s0: carrier acquired
    Jul 29 11:31:43 arch wpa_actiond[651]: Interface 'wlp16s0' connected to network 'WIRELESS'
    Jul 29 11:31:43 arch dhcpcd[230]: wlp16s0: adding address fe80::ad30:b256:e3a3:dbd0
    Jul 29 11:31:43 arch dhcpcd[230]: wlp16s0: IAID e0:20:c5:69
    Jul 29 11:31:43 arch dhcpcd[230]: control command: dhcpcd -4 -q -t 30 -K -L wlp16s0
    Jul 29 11:31:43 arch dhcpcd[230]: wlp16s0: soliciting a DHCP lease
    Jul 29 11:31:43 arch dhcpcd[230]: wlp16s0: offered 192.168.0.100 from 192.168.0.1
    Jul 29 11:31:44 arch dhcpcd[230]: wlp16s0: soliciting an IPv6 router
    Jul 29 11:31:48 arch dhcpcd[230]: wlp16s0: leased 192.168.0.100 for 7200 seconds
    Jul 29 11:31:48 arch dhcpcd[230]: wlp16s0: adding route to 192.168.0.0/24
    Jul 29 11:31:48 arch dhcpcd[230]: wlp16s0: adding default route via 192.168.0.1
    Jul 29 11:31:56 arch dhcpcd[230]: wlp16s0: no IPv6 Routers available
    Blank line omits dozens of repeated "Network is down", etc.

  • HT204368 I recently upgraded from an iPhone 4s to an iPhone 5.  I have a Motorola HX550 Bluetooth Headset which worked flawlessly with the iPhone 4s.  However, since upgrading to the iPhone 5, I frequently lose audio when in the middle of a call.  I am no

    I recently upgraded from an iPhone 4s to an iPhone 5.  I have a Motorola HX550 Bluetooth Headset which worked flawlessly with the iPhone 4s.  However, since upgrading to the iPhone 5, I frequently lose audio when in the middle of a call.  I am not certain whether it is a full disconnect or just an audio loss.  The person on the other end reports still being able to hear me, however, I suppose they could hear me speaking over another source even if bluetooth disconnected. The loss of audio is always preceded by a quick shrill noise, so I can easily tell when it happens.  All I have to do to fix the problem is to select Audio Source on the call screen, temporarily switch audio back to the iPhone, and then switch back to the headset, and then it starts working again.
    Is is important to note that I am not the only one experiencing this issue:
    This is a link to someone using the Motorola H19txt headset experiencing the same issue
    https://forums.motorola.com/posts/94ac15ad7c
    If you go to the Plantronics website and look at the "Ratings and Reviews" on the Voyager Legend you will see the same issue reported:
    http://www.plantronics.com/us/product/voyager-legend (next paragraph is taken from the review since there is no direct link to the review.
    Really nice Headset unless you own an Iphone 5. I own several Plantronics headsets and have always loved the quality/ performance. This headset seems not to be compatible with the new Iphone 5. In the middle of a conversation it will lose all incoming audio. This leaves you trying to switch audio sources really fast in order not to lose your phone call. Ive tried 3 legend headsets and they all do the same thing. Hopefully this gets fixed soon because the headset is really nice
    Since this issue appears to affect multiple headsets from multiple vendors, I think it is fair to conclude that it is an issue with the iPhone5 bluetooth itself.
    I am posting this as a new discussion as I don't see any other posts specific to this iPhone 5 Bluetooth issue.  I would have reported this as a problem to Apple, but don't seem to be able to find a way to do this on the web.  Hopefully they are already aware, but if not, maybe they will see i here.

    here is an interesting thing: take the iphone and set lock screen to never. Now make an email with siri--be sure to activate her with call button. get to the body and get some text in there. then just stop talking. LOCK SCREEN APPEARS!!!!!! and of course you draft is gone.
    There does seem to be a work around for some--maybe all these issues. Don't use the call button--use the buttons on the phone.
    Siri seems to behave properly with scenerio above---sans call button. She does not go to lock.

  • Netctl-auto stoped working [Solved]

    After update yesterday, netctl-auto stoped working. Netctl start MyProfile works OK.
    Something I have missed during update?
    Last edited by torors (2013-11-17 21:09:09)

    I think another version of netctl has been pushed to the repos.  Maybe you should try updating again and see if your issues are resolved by the updated package.
    pacman -Qi netctl
    Name : netctl
    Version : 1.4-2
    <snip>
    Build Date : Sun 17 Nov 2013 01:37:39 AM PST
    Install Date : Sun 17 Nov 2013 08:56:25 AM PST
    <snip>

  • Netctl-auto@wlp3s0.service broken after wpa_supplicant upgrade

    A few hours ago, I upgraded from wpa_supplicant-2.3-1 to wpa_supplicant-2.4-1. Subsequently [email protected] stopped working. After I started it, it would be reported as "active (running)" but fail to connect to any WIFI network (I wouldn't get assigned a DHCP IP address):
    Apr 25 12:44:47 sauron wpa_actiond[6952]: Interface 'wlp3s0' connected to network 'Edward'
    Apr 25 12:44:47 sauron dhcpcd[6974]: DUID xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx
    Apr 25 12:44:47 sauron dhcpcd[6974]: wlp3s0: IAID xx:xx:xx:xx
    Apr 25 12:44:47 sauron dhcpcd[6974]: wlp3s0: rebinding lease of 192.168.1.20
    Apr 25 12:44:51 sauron dhcpcd[6974]: wlp3s0: leased 192.168.1.20 for 43200 seconds
    Apr 25 12:44:51 sauron dhcpcd[6974]: wlp3s0: adding route to 192.168.1.0/24
    Apr 25 12:44:51 sauron dhcpcd[6974]: wlp3s0: adding default route via 192.168.1.1
    12:55 ~$ journalctl -xe -u [email protected]
    Apr 25 12:36:28 sauron netctl-auto[5505]: Included profile 'wlp3s0-cz'
    Apr 25 12:36:28 sauron netctl-auto[5505]: Successfully initialized wpa_supplicant
    Apr 25 12:36:28 sauron netctl-auto[5505]: Could not read interface p2p-dev-wlp3s0 flags: No such device
    Apr 25 12:36:28 sauron systemd[1]: Started Automatic wireless network connection using netctl profiles.
    -- Subject: Unit [email protected] has finished start-up
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Unit [email protected] has finished starting up.
    Notice the "Could not read interface...". I downgraded back to 2.3-1 and the problem went away. Could this be a wpa_supplicant bug (new bug in 2.4-1) or netctl bug (incompatibility with the new wpa_supplicant)?
    There's nothing special about the profile files in /etc/netctl. In addition to the ones for wired network, I have a few files named like "wlp3s0-XXX" and they look like this (password crossed out):
    Connection=wireless
    Description='Edward'
    Interface=wlp3s0
    Security=wpa
    ESSID='Edward'
    Key='????'
    Hidden=yes
    IP=dhcp

    I'm having exactly the same problem.
    # wpa_supplicant -D wext -i wlp2s0 -c /tmp/wpap
    Successfully initialized wpa_supplicant
    ioctl[SIOCSIWENCODEEXT]: Invalid argument
    ioctl[SIOCSIWENCODEEXT]: Invalid argument
    ioctl[SIOCSIWSCAN]: Device or resource busy
    wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-1 retry=1
    ioctl[SIOCSIWSCAN]: Device or resource busy
    wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-1 retry=1
    ioctl[SIOCSIWSCAN]: Device or resource busy
    wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-1 retry=1
    ioctl[SIOCSIWSCAN]: Device or resource busy
    wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-1 retry=1
    wlp2s0: Trying to associate with 00:1e:e5:6d:83:6f (SSID='Driesen-Peeters' freq=2437 MHz)
    ioctl[SIOCSIWFREQ]: Device or resource busy
    wlp2s0: Association request to the driver failed
    wlp2s0: Authentication with 00:1e:e5:6d:83:6f timed out.
    ioctl[SIOCSIWMLME]: Transport endpoint is not connected
    ioctl[SIOCSIWAP]: Device or resource busy
    wlp2s0: CTRL-EVENT-DISCONNECTED bssid=00:1e:e5:6d:83:6f reason=3 locally_generated=1
    ioctl[SIOCSIWSCAN]: Device or resource busy
    wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-1 retry=1
    ioctl[SIOCSIWSCAN]: Device or resource busy
    wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-1 retry=1
    ^Cwlp2s0: CTRL-EVENT-TERMINATING
    # wpa_supplicant -D wext -i wlp2s0 -c /tmp/wpap
    Successfully initialized wpa_supplicant
    Could not read interface p2p-dev-wlp2s0 flags: No such device
    wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
    wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
    wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
    wlp2s0: SME: Trying to authenticate with 00:1e:e5:6d:83:6f (SSID='My-Network' freq=2437 MHz)
    wlp2s0: SME: Authentication request to the driver failed
    ^C
    nl80211: deinit ifname=p2p-dev-wlp2s0 disabled_11b_rates=0
    p2p-dev-wlp2s0: CTRL-EVENT-TERMINATING
    nl80211: deinit ifname=wlp2s0 disabled_11b_rates=0
    wlp2s0: CTRL-EVENT-TERMINATING
    This also break wifi-menu by the way, so the only option now is trying a manual wpa_supplicant connect. I should mention that this morning (after troubleshooting all night with no result) I managed to connect to my AP once (while begin connected via ethernet as well). After disconnecting the ethernet cable and trying again it failed again. I have not been able to reproduce this.
    Other possibly interesting information:
    # dmesg
    [ 734.004304] wlp2s0: authenticate with 00:1e:e5:6d:83:6f
    [ 734.004343] iwlwifi 0000:02:00.0: No available PHY context
    [ 734.004378] iwlwifi 0000:02:00.0: No available PHY context
    [ 737.496406] wlp2s0: authenticate with 00:1e:e5:6d:83:6f
    [ 737.496431] iwlwifi 0000:02:00.0: No available PHY context
    [ 741.388469] wlp2s0: authenticate with 00:1e:e5:6d:83:6f
    [ 741.388493] iwlwifi 0000:02:00.0: No available PHY context
    [ 963.953904] wlp2s0: authenticate with 00:1e:e5:6d:83:6f
    [ 963.956708] wlp2s0: send auth to 00:1e:e5:6d:83:6f (try 1/3)
    [ 963.958860] wlp2s0: authenticated
    [ 963.961363] wlp2s0: associate with 00:1e:e5:6d:83:6f (try 1/3)
    [ 963.964229] wlp2s0: RX AssocResp from 00:1e:e5:6d:83:6f (capab=0x411 status=0 aid=1)
    [ 963.965539] wlp2s0: associated
    [ 966.651095] wlp2s0: deauthenticating from 00:1e:e5:6d:83:6f by local choice (Reason: 3=DEAUTH_LEAVING)
    [ 966.655984] cfg80211: Calling CRDA to update world regulatory domain
    [ 966.659308] cfg80211: World regulatory domain updated:
    [ 966.659312] cfg80211: DFS Master region: unset
    [ 966.659313] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
    [ 966.659315] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
    [ 966.659317] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
    [ 966.659319] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
    [ 966.659321] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
    [ 966.659323] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
    [ 966.659324] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
    [ 966.659326] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
    [ 966.659327] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
    [ 1033.789418] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
    [ 1043.308740] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
    [ 1046.718632] wlp2s0: authenticate with 00:1e:e5:6d:83:6f
    [ 1046.718644] iwlwifi 0000:02:00.0: No available PHY context
    [ 1046.718654] iwlwifi 0000:02:00.0: No available PHY context
    [ 1050.109123] wlp2s0: authenticate with 00:1e:e5:6d:83:6f
    [ 1050.109147] iwlwifi 0000:02:00.0: No available PHY context
    [ 1072.258284] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
    [ 1075.694370] wlp2s0: authenticate with 00:1e:e5:6d:83:6f
    [ 1075.697180] wlp2s0: send auth to 00:1e:e5:6d:83:6f (try 1/3)
    [ 1076.003982] iwlwifi 0000:02:00.0: No association and the time event is over already...
    [ 1076.004017] wlp2s0: Connection to AP 00:1e:e5:6d:83:6f lost
    [ 1080.255382] wlp2s0: authenticated
    # pacman -Q wpa_supplicant
    wpa_supplicant 2.4-1
    # uname -r
    3.19.3-3-ARCH
    # lspci -v | grep Wireless -A 15
    02:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
    Subsystem: Intel Corporation Dual Band Wireless-AC 7265
    Flags: bus master, fast devsel, latency 0, IRQ 50
    Memory at f7000000 (64-bit, non-prefetchable) [size=8K]
    Capabilities: [c8] Power Management version 3
    Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
    Capabilities: [40] Express Endpoint, MSI 00
    Capabilities: [100] Advanced Error Reporting
    Capabilities: [140] Device Serial Number 60-57-18-ff-ff-4a-6a-8c
    Capabilities: [14c] Latency Tolerance Reporting
    Capabilities: [154] L1 PM Substates
    Kernel driver in use: iwlwifi
    Kernel modules: iwlwifi
    I'm on a Zenbook UX305, what are you guys on and could you post the output of those last three commands I posted?
    Cheers!

  • Netctl-auto and dropbox

    Hi, I've been reading the wiki. The only difference is my interface name is wlp2s0 instead of wlan0. So I went to /etc/netctl/interfaces and I created a new file called wlp2s0 with the contents
    ExecUpPost="su -c 'DISPLAY=:0 /usr/bin/dropboxd &' root || true"
    ExecDownPre="killall dropbox"
    However, this doesn't seem to do anything. I've disabled the "Start Dropbox on system startup" option, but everytime I restart, there's no dropbox icon in the dock like there normally is. What am I doing wrong?
    Internet roaming still seems to work, even after putting the computer to sleep.
    Last edited by boogerlad (2013-11-16 22:01:34)

    Wonderwoofy,
    I'm having a similar problem with my [email protected] connecting at startup. It loads fine but stays on connecting....... . I can stop and restart it using
    # systemctl stop/start dropbox@dmy
    and it works as expected. I can use the same method that boogerland describes in the first post and it works fine but I wanted to get it to work with systemd if possible. Any thoughts? Here's my [email protected]
    [Unit]
    Description=Dropbox
    After=local-fs.target network.target netctl-auto@wlan0 netctl-ifplugd@enp3s0
    Wants=netctl-auto@wlan0 netctl-ifplugd@enp3s0
    [Service]
    Type=simple
    Environment=DISPLAY=:0
    ExecStart=/home/dmy/.dropbox-dist/dropboxd
    ExecReload=/bin/kill -HUP $MAINPID
    KillMode=process
    Restart=always
    User=%I
    [Install]
    WantedBy=multi-user.target

  • Netctl-auto fails every second boot

    So, since about two oder three days ago, my netctl-auto fails every second boot and I can't even enable a profile manually.
    I already found this thread: https://bbs.archlinux.org/viewtopic.php?pid=1275755
    But I checked and don't have any failed units and dhcpcd is not running.
    I will do some further investigation and post it here. Any ideas for solutions are welcome
    Wolle

    I've been having the same problem as well, it boots up just fine then after a reboot netctl-auto fails which had been going on for me for the past 30 minutes without "fixing" itself.
    After I added the line:
    TimeoutDHCP=30
    to my profile then rebooted, it worked. It could be a fluke "fix" but worth a try. I *think* the reason it worked is that the default timeout is 10 seconds which might not be enough to establish a connection for some routers/network cards.
    EDIT: I did another boot to see if it was a fluke, and it was. I'm getting a little tired of netctl-auto... I'm going to just disable it and manually do a "netctl start <profile>" after I boot up.
    Last edited by DukeH (2013-07-16 19:07:58)

  • SAPRFC works great unless SAP is bounced

    'Everything is working fine unless SAP is taken off line. In which case the php.exe process cpu utilization jumps to 50% and is no longer listening for the RFC.
    Once SAP is back on line the php.exe process cpu time is still 50% and still no longer listening. Do I need an error trap, am I using something incorrectly, or is my code fundamentally flawed? Any help is appreciated.
    require_once( "api_tunnel.php" );
      $DEF_RFC_KWIKSHIP_API= array (
                      array (
                           "name"=>"MSGTOFS",
                           "type"=>"IMPORT",
                           "optional"=>"0",
                           "def"=> array (
                                array ("name"=>"","abap"=>"C","len"=>10000,"dec"=>0)
                      array (
                           "name"=>"MSGFROMFS",
                           "type"=>"EXPORT",
                           "optional"=>"0",
                           "def"=> array (
                                array ("name"=>"","abap"=>"C","len"=>10000,"dec"=>0)
    // Call script with: ./KWIKSHIP_rfc_connector.php -a KWIKSHIP_api -g hostname -x sapgw00 –t c:\
    $rfc = saprfc_server_accept ($argv);
    $fcl["KWIKSHIP_API"] = saprfc_function_define(0,"KWIKSHIP_API",$DEF_RFC_KWIKSHIP_API);
    // PHP server function
    while (true)
       $rc = saprfc_server_dispatch ($rfc, $fcl);
    function KWIKSHIP_api($fce) {
               $phpconnector_input_str = saprfc_server_import($fce,"MSGTOFS");
         $return_str = SendAPIMessage($phpconnector_input_str);
               saprfc_server_export ($fce,"MSGFROMFS",$return_str);
               return (true);
    //Attempt to run listener without ever closing the saprfc connection; Close RFC if necessary
    saprfc_close ($rfc);

    Hi,
    SAPRFC - works on - Windows Server 2003 (IIS x32) and on Apache WAMP -  PHP 5.2.8 - with - php_saprfc_528.dll.
    The crucial  thing is the c++ dll complilation. So you cannot use php_saprfc_530.dll for PHP 5.3.5 - it only works with
    PHP 5.3.0 and so on. Each php release needs its own c++ compilation for  the php_saprfc_xxx.dll.
    I already asked eduard.koucky at czech-tv.cz (the project leader) how to compile a php_saprfc_535.dll  together  with
    Visual Studio 2008 and saprfc_php5.sln?
    It seems to depend on the php dll build includes in the property sheets of the project in VS 2008:
    "..\Build\Php.Build\php-5.2.8";
    "..\Build\Php.Build\php-5.2.8\Zend";
    "..\Build\Php.Build\php-5.2.8\TSRM";
    "..\Build\Php.Build\php-5.2.8\main";
    "..\Build\Php.Build\php-5.2.8\win32";
    "C:\Program Files\Microsoft SDKs\Windows\v6.1\Include";
    ..\Build\RFCSDK.710.Win32\include;
    ..\Build\Php.Build\Win32\include
    You find existing versions of the php_saprfc_xxx.dlls here -> http://sourceforge.net/projects/saprfc/files/saprfc/ :
    4.3.0  -  4.3.2  -  4.3.8  -  4.3.10  -  4.4.0  -  4.4.1  -  4.4.9  -  5.0.0  -  5.0.3  -  5.0.4  -  5.1.1  -  5.2.8  -  5.3.0
    Best regards
    Axel Arnold Bangert - Herzogenrath 2011

  • Netctl-auto cannot connect after unblocking wifi

    Hello,
    I'm using netctl as a connection manager. Systemd automatically starts "netctl-auto@wlp1s0" and if I boot system with wifi unblocked (rfkill) it is working fine. But when I boot my system with wifi blocked (from previous session) and after boot I manually unblock it (using rfkill unblock wifi), it doesn't pick up network. And when I try "sudo netctl-auto swtich-to <network_name> it prints out:
    WPA association/authentication failed for interface 'wlp1s0'
    It also happens when I'm working without connection with blocked wifi (for saving the battery) and then I turn wifi on - it also doesn't pick up a network.
    I have to first do:
    systemctl restart netctl-auto@wlp1s0
    which blocks wifi (when I try rfkill list, I can see that this restart blocked it) and only if I immediately switch wifi on (also using rfkill), it connect as usual.
    Does anyone experience same issue? Is it normal behaviour? Thanks

    I think you are seeing a manifestation of this bug.
    Note that I wrote that report.
    Last edited by ewaller (2014-03-27 15:01:50)

  • Does the SIP Profile work for Symbian Belle?

    This is an interesting device, however besides having to have a seperate application for Wifi Hotspot, I am wondering if the so-called "application" for SIP VoIP calls, as per older handsets will in fact work or would it need upgrading.
    Hope someone can help.

    Hello,
    I had the same problem while testing Nokia 603 and it took a week to get the solution, so I'm happy to share my experience now...
    SIP profile works fine, but you still need to download a widget from Ovi Store in order to configure Internet telephony profile and activate VoIP calls. Unfortunately it seems that no VoIP provider has released own widgets, so you can't use Internet calls even if you setup SIP profile and registration to SIP server is ok. But there is a solution...
    You can download a little app from Nokia develeoper site, which enables hidden configuration and let you access to manual configuration of Internet telephony profile... same as it used to happen with older Nokia devices.
    After installing the app you can create a default Internet telephony profile associated to the SIP profile created before. After doing this, when you enter the contact list or oper the dialer, you can find a new menu option to call via Internet. Not easy, but it works!
    The app can be downloaded here...
    Carlo M. Strati
    ICT Consultant & Web Specialist
    Technology Journalist
    www.carlostrati.tel

  • Netctl-auto Is Not Observing Priority

    I have been using netctl with a single profile for the past few months without issue. My universities network offers a (much faster) WPA network in addition to a (more available) guest network. I am trying to configure netctl-auto to connect to these profiles using the Priority parameter in the profiles. I have set Priority=100 for WPA and Priority=75 for the guest network. Whenever I reboot my machine the guest network is selected and activated by netctl-auto even though the priority is set to use WPA.
    Would anyone have any insight as to why the priority is being ignored?

    I am having a similar issue, and would like to have a fix. I have 3 competing profiles, two guest networks and one eduroam. The first two profiles are simple, set up pretty much exactly as examples/wireless-open, and have Priority=1 and =2, respectively. The eduroam account contains a WPAConfigSection, and has Priority=3. Netctl-auto will not ahdere to these priorities. In order to start eduroam,  I need to “netctl-auto disable” both guest profiles.

  • Worked Flawlessly on 1st AND 2nd install!

    I don't get it?..The problems everyone is having??..I installed it initially on my Windows 2000 PC..worked fine..I just bought a new Gateway AMD 64 x2 4200 PC with XP..installed iTunes..hooked my 5th Gen iPod Video into the USB port..it recognized it..asked if I wanted to link to the library on the new PC..I said yes..& it works flawlessly on it now..Goes to show you..it's 99% the PCs with problems..not the 5 G iPod Videos..(unless of course I'm just...lucky?...)

    That's just it, though... "all these people having problems" are pretty much just the people that post on message boards about it. 99% of people don't have these problems, and therefore don't go searching the web for answers. I personally am just a tech geek that likes to help people fix stuff, but I never have any of these sorts of issues installing my software or connecting my iPod whatsoever.

  • Netctl-auto & netctl-ifplugd prefer wired?

    Hi,
    On my laptop running Arch Linux I've got both netctl-auto and netctl-ifplugd running. I have both ethernet and wireless set up in my house, and I'd like to have it set up so that it prefers wired over the wireless connection. So that if it's plugged in I can know for sure it is using the wired connection and not the wireless connection, and if I unplug it it should switch to wireless.
    There's a 'priority' variable but that only applies to wireless connections and so it has no effect on the wired profile. I've gone through the manpages for netctl-auto and ifplugd and gone through the relevant sections for netcl in the wiki multiple times but there doesn't seem to be anything on getting this kind of setup.
    So is there a way to have Arch prefer wired connections over wireless?

    https://wiki.archlinux.org/index.php/ne … s_failover

  • Hi Team, I wuold like to know if you have any app to make Firefox OS working with cisco Call Manager 10.5. Something like Cisco Jabber for Android or iOS.

    I'm interesting on buying a Firefox Smart Phone, but
    I would like to know if are any app to install on Firefox OS smart phone in order to work with cisco call manager 10.5.
    Something like Cisco Jabber for Android o iOS.
    Thanks,

    Hi Itech,
    If Cisco Jabber has a webapp, or mobile version of their website available, you should technically be able to access it through Firefox OS.
    You may also search Firefox Marketplace for an alternative solution:
    * [https://marketplace.firefox.com/]
    - Ralph

Maybe you are looking for