Connman_dmenu: netcfg(netctl) alternative!

recently I tried all network manager, but eventually settled down to connman.
interestingly, connman is such a powerful tool because it provides proper abstraction on top of wpa_supplicant.
Pro:
+ super lightweight (dmenu + connman)
+ faster scan and connection (vs netcfg) (this is around 1~2 secs while netcfg can take up to 15 secs)
+ automatically connection after first connection is made (wifi or ethernet)
+ supported wifi security: wep, wpa2 peap, wpa psk, none (these 4 are the most common)
+ 2014/1/14 add vpn pptp support (pptp is the most common one.)
Con:
- dmenu cannot support all configuration, but for most people we dont have complicated wifi configuration
This works nicely if you use i3 or some other random tiling wm.
install
https://aur.archlinux.org/packages/connman_dmenu-git/
Last edited by taylorchu (2014-01-16 05:17:36)

Here's the output you requested.
connmanctl> scan wifi
Scan completed
connmanctl> services
*A PAL2.0 { wifi_a088b45b697c_50414c322e30_managed_ieee8021x }
*A PAL3.0 { wifi_a088b45b697c_50414c332e30_managed_ieee8021x }
PAL Setup { wifi_a088b45b697c_50414c205365747570_managed_none }
Purdue Guest Network { wifi_a088b45b697c_507572647565204775657374204e6574776f726b_managed_none }
Purdue Guest Network { wifi_a088b45b697c_hidden_managed_ieee8021x }
attwifi { wifi_a088b45b697c_61747477696669_managed_none }
attwifi { wifi_a088b45b697c_hidden_managed_none }
NETGEAR38 { wifi_a088b45b697c_4e4554474541523338_managed_psk }
PFRPZD8923YOHP { wifi_a088b45b697c_504652505a4438393233594f4850_managed_ieee8021x }
default { wifi_a088b45b697c_64656661756c74_managed_none }
└➤ sudo connman_dmenu
cut: invalid byte, character or field list
Try 'cut --help' for more information.
cut: fields and positions are numbered from 1
Try 'cut --help' for more information.

Similar Messages

  • Netctl begin a pain with Uppsala University networks

    Hello!
    So I'm studying at Uppsala University and I'm fed up with bringing my mobile broadband with me each day to get internet access. Also, I have cancelled it so I will not have it for that much longer anyway.
    I have tried to set it up and it does not work. I believe this worked with netcfg, but since then I have migrated to netctl due to a new install on a new laptop.
    The school has two networks. One eduroam network which I can't access in any way, and an open one which you are supposed to log in on through the web browser. Then you will get access. I can't get either of them to work.
    In the case of eduroam, I get a message saying to check the systemctl journal something becuase the service failed, and I can't post this message right now because if I do I have to reboot to restore it to my current internet settings (because the interface/service fails to do anything after trying eduroam)
    In the case of the open network I fail to get redirected to the login window from the school's network when I'm trying to access a website. This used to work in netcfg, and it used to work on a Ubuntu install I once had. This stopped working when I migrated (I deleted all old profiles and made new ones in netctl.
    For the record, I am currently using netctl-auto to connect to known networks and whenever I am trying to disable netctl-auto I get a lot of problems all of a sudden.
    I wish you can help me, and I know that this post has no information for you to show what's wrong, BUT I want you to give me instructions now on what to do, so that I can save the results from those instructions and post them after a reboot (after restoring the internet after my failed attempt has failed), OR if you actually know the cause just tell me straight away. I highly doubt the second case but you never know, right?
    Anyway, I would be very grateful if anybody can assist me with this. Also, alternatives to netctl will be greatly concidered, if you have other solutions which does not include netctl.
    Thanks!
    Last edited by timelaw (2013-10-07 09:17:45)

    Trilby wrote:
    timelaw wrote:I fail to get redirected to the login window from the school's network when I'm trying to access a website.
    One of my university's networks is like this.  What page(s) do you try to go to?  About six months ago, this stopped working for me as well, unless I specifically typed int "google.com" for the url.  The network will redirect 'google.com' requests to the login page, but everything else will just show a connection errror.
    timelaw wrote:I know that this post has no information for you to show what's wrong, BUT I want you to give me instructions now on what to do...
    The best information comes from following the manual connection steps in the wireless page of the wiki.  Network management tools hide all the relevant information, so no actual troubleshooting can be done - and discussions that don't post the ouput of the manual steps degrade to random guess-and-check.
    So, first off usually I can access aftonbladet.se by instantly being redirected, I log in and I get thrown back to aftonbladet. This is one of the few websites that used to work like this, but this is mainly my Windows installation. On Arch it does not work at all.
    I used netctl as my network configuration software and I had the service netctl-auto on to automatically connect to wifis.
    Now, this used to work with netcfg so I don't understand why it stopped working, when they said there would be no difference between the two packages (netctl and netcfg)
    So, what I have decided to try is to go for networkmanager because it used to work on my ubuntu without issues, and I believe that is what they use as default?
    I am using Gnome 3 and NetworkManager right now and now I can't even access secure networks at all. I'm really pissed off at this because it makes me sit here and connect to the internet through my phone instead.
    The slow reply is due to being away during the weekend so I could not try fixing it since I was not at school.
    Also, the network tutorials does not help me with this. The Eduroam part makes my services crash and it doesn't say anything about this type of network (as far as I understood)
    I'm trying to understand how to use journalctl right now to understand what is going wrong but I can't seem to get anything useful out of that either.... I'm kind of losing my patience... I keep hitting more walls and without the internet access I can't figure it out so it takes forever to get back to the first square even sometimes.

  • [SOLVED] netctl not bringing up my network at boot

    I recently converted from netcfg to netctl and but my network is not coming up ever at boot time. Once the machine is booted I can bring it up manually using
    netcfg start ethernet-static
    It is obviously an static IP address and I copied the netctl sample script and then modified it. Here is my ethernet-static profile.
    Description='A basic static ethernet connection'
    Interface=enp2s0
    Connection=ethernet
    IP=static
    Address=('192.168.0.5/24')
    #Routes=('192.168.0.0/24 via 192.168.1.2')
    Gateway='192.168.0.1'
    DNS=('192.168.0.1')
    ## For IPv6 autoconfiguration
    #IP6=stateless
    ## For IPv6 static address configuration
    #IP6=static
    #Address6=('1234:5678:9abc:def::1/64' '1234:3456::123/96')
    #Routes6=('abcd::1234')
    #Gateway6='1234:0:123::abcd'
    The output of journalctl -d | grep net is the following
    un 14 08:40:03 kfrance-home kernel: Initializing cgroup subsys net_cls
    Jun 14 08:40:03 kfrance-home kernel: audit: initializing netlink socket (disabled)
    Jun 14 08:40:03 kfrance-home kernel: drop_monitor: Initializing network drop monitor service
    Jun 14 08:40:03 kfrance-home systemd[1]: Expecting device sys-subsystem-net-devices-enp2s0.device...
    Jun 14 08:40:03 kfrance-home kernel: r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
    Jun 14 08:40:03 kfrance-home kernel: microcode: Microcode Update Driver: v2.00 <[email protected]>, Peter Oruba
    Jun 14 08:40:03 kfrance-home systemd-udevd[171]: renamed network interface eth0 to enp3s0
    Jun 14 08:40:03 kfrance-home systemd-udevd[168]: renamed network interface eth0 to enp2s0
    Jun 14 08:40:07 kfrance-home network[253]: Starting network profile 'ethernet-static'...
    Jun 14 08:40:12 kfrance-home network[253]: No connection on interface 'enp2s0'
    Jun 14 08:40:12 kfrance-home network[253]: Failed to bring the network up for profile 'ethernet-static'
    Jun 14 08:40:12 kfrance-home systemd[1]: netctl@ethernet\x2dstatic.service: main process exited, code=exited, status=1/FAILURE
    Jun 14 08:40:12 kfrance-home systemd[1]: Failed to start A basic static ethernet connection.
    Jun 14 08:40:12 kfrance-home systemd[1]: Unit netctl@ethernet\x2dstatic.service entered failed state.
    Jun 14 08:47:53 kfrance-home sudo[1300]: kfrance : TTY=pts/1 ; PWD=/home/emily ; USER=root ; COMMAND=/usr/bin/netctl start ethernet-static
    Jun 14 08:47:53 kfrance-home systemd[1]: Starting A basic static ethernet connection...
    Jun 14 08:47:53 kfrance-home network[1307]: Starting network profile 'ethernet-static'...
    Jun 14 08:47:57 kfrance-home network[1307]: Started network profile 'ethernet-static'
    Jun 14 08:47:57 kfrance-home systemd[1]: Started A basic static ethernet connection.
    Nothing from netcfg, or any other network service, is leading to a conflict for configuring the network.
    systemctl list-units | grep net
    [email protected] loaded active exited A basic static ethernet connection
    network.target loaded active active Network
    I do have two ethernet ports but from what I can tell the naming of the two ports is consistent.
    netctl status shows that my ethernet-static profile is the only profile and is active.
    I know I could connect without using netctl but want to get this working. Any ideas?
    Last edited by kfrance (2013-06-15 04:12:06)

    I fixed the problem. I changed the device name of the ethernet device I wanted to use using an udev-rule, according to the notes on the Network Configuration wiki page, to make sure that it wasn't a naming conflict and that solved it.

  • Can't get `netctl start` to work with example eth0-dhcp profile

    So I recently decided to go ahead and install netctl. I had netcfg previously. First thing I did was disable my old systemd unit for netcfg after upgrading.
    Then I proceeded with using the example profile
    cp /etc/netctl/examples/ethernet-dhcp /etc/netctl/eth0-dhcp
    netctl start eth0-dhcp
    But then, instead of it working, I get an error. I decided to reboot to see if the new kernel would affect it. It didn't. This is the error I got:
    [earlz@EarlzWork ~]$ sudo netctl start eth0-dhcp
    Job for netctl@eth0\x2ddhcp.service failed. See 'systemctl status netctl@eth0\x2ddhcp.service' and 'journalctl -xn' for details.
    [earlz@EarlzWork ~]$ sudo journalctl -xn
    -- Logs begin at Fri 2012-11-09 08:25:27 EST, end at Thu 2013-05-09 12:01:20 EDT. --
    May 09 12:01:02 EarlzWork sudo[1251]: pam_unix(sudo:session): session opened for user root by (uid=0)
    May 09 12:01:02 EarlzWork systemd[1]: Starting Networking for netctl profile eth0-dhcp...
    -- Subject: Unit netctl@eth0\x2ddhcp.service has begun with start-up
    -- Defined-By: systemd
    -- Support: [url]http://lists.freedesktop.org/mailman/listinfo/systemd-devel[/url]
    -- Unit netctl@eth0\x2ddhcp.service has begun starting up.
    May 09 12:01:02 EarlzWork network[1258]: Starting network profile 'eth0-dhcp'...
    May 09 12:01:02 EarlzWork network[1258]: The interface of network profile 'eth0-dhcp' is already up
    May 09 12:01:02 EarlzWork systemd[1]: netctl@eth0\x2ddhcp.service: main process exited, code=exited, status=1/FAILURE
    May 09 12:01:02 EarlzWork systemd[1]: Failed to start Networking for netctl profile eth0-dhcp.
    -- Subject: Unit netctl@eth0\x2ddhcp.service has failed
    -- Defined-By: systemd
    -- Support: [url]http://lists.freedesktop.org/mailman/listinfo/systemd-devel[/url]
    -- Documentation: [url]http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba40df7e9d022f03d[/url]
    -- Unit netctl@eth0\x2ddhcp.service has failed.
    -- The result is failed.
    May 09 12:01:02 EarlzWork systemd[1]: Unit netctl@eth0\x2ddhcp.service entered failed state.
    May 09 12:01:02 EarlzWork sudo[1251]: pam_unix(sudo:session): session closed for user root
    May 09 12:01:20 EarlzWork sudo[1266]: earlz : TTY=pts/0 ; PWD=/home/earlz ; USER=root ; COMMAND=/usr/bin/journalctl -xn
    May 09 12:01:20 EarlzWork sudo[1266]: pam_unix(sudo:session): session opened for user root by (uid=0)
    [earlz@EarlzWork ~]$ systemctl status netctl@eth0\x2ddhcp.service
    [email protected] - Networking for netctl profile eth0x2ddhcp
    Loaded: loaded (/usr/lib/systemd/system/[email protected]; static)
    Active: inactive (dead)
    Docs: man:netctl.profile(5)
    Somehow, the service is loaded, but not active. The error message appears to just be that the interface is already up... which doesn't make sense. If I manually use `ifconfig eth0 down` before calling it, then I get
    May 09 12:10:12 EarlzWork kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
    May 09 12:10:17 EarlzWork network[1335]: No connection on interface 'eth0'
    May 09 12:10:17 EarlzWork dhclient[1299]: receive_packet failed on eth0: Network is down
    May 09 12:10:17 EarlzWork network[1335]: Failed to bring the network up for profile 'eth0-dhcp'
    May 09 12:10:17 EarlzWork systemd[1]: netctl@eth0\x2ddhcp.service: main process exited, code=exited, status=1/FAILURE
    May 09 12:10:17 EarlzWork systemd[1]: Failed to start Networking for netctl profile eth0-dhcp.
    If I then reenable eth0, then I still get the "is already up" message, despite neither dhclient nor dhcpcd being active. Also, at this point the interface does not have an IP address either.
    How do I fix this? Why does it constantly say the interface is already up?
    Edit:
    I temporarily "fixed" this by using ForceConnect=yes as indicated here: https://github.com/joukewitteveen/netctl/issues/11 However, I think using that is quite a hack, so maybe someone can solve what the underlying cause is
    Last edited by earlz (2013-05-09 16:21:28)

    hotvic wrote:
    First make sure that any dhcp client isn't running:
    % ps aux | egrep 'dhcpcd|dhclient'
    If any of these is running kill the.
    After, put interface in DOWN state:
    # ip link set down dev eth0
    then restart profile and verify if it start:
    # netctl restart eth0-dhcp
    This must work, but I don't know what's putting interface in UP state.
    I did this. neither dhcpcd or dhclient were running through any of this. Also, when I set the link down, then I got the error message "network not ready" discussed in the second error message in my post

  • Netctl problem - No connection on interface 'enp1s0'

    I'm trying to switch from netcfg to netctl.  Since the network won't come up, it would be difficult to post actual logs so I'm typing all this in.
    /etc/netctl/mynet looks like:
    Description='My net'
    Interface=enp1s0
    Connection=ethernet
    IP=static
    Address=('192.168.1.102/24')
    When I try to start it, I get from systemctl status [email protected]:
    ... network[1877]: Starting network profile 'mynet' ...
    ... network[1877]: No connection on interface 'enp1s0'
    and then some failed/exited messages.
    Sorry that's not much to go on, but perhaps someone can point me in the right direction.

    Heh, it just dawned on me that I could use the modem even if the network is down.  Just in case someone can see a typo I'm missing, here's the actual config without the commented lines:
    Description='My net'
    Interface=enp1s0
    Connection=ethernet
    IP=static
    Address=('192.168.1.102/24')
    #Routes=('192.168.0.0/24 via 192.168.1.2')
    Gateway='192.168.1.1'
    DNS=('192.168.1.1')
    Results of 'netctl start mynet ; systemctl status [email protected]:
    [email protected] - My net
    Loaded: loaded (/etc/systemd/system/[email protected]; enabled)
    Active: failed (Result: exit-codesder) since Tue 2013-07-02 23:33:03 EAT; 8min ago
    Docs: man:netctl.profile(5)
    Process: 6726 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)
    Jul 02 23:32:58 chanan002 network[6726]: Starting network profile 'mynet'...
    Jul 02 23:33:03 chanan002 network[6726]: No connection on interface 'enp1s0'
    Jul 02 23:33:03 chanan002 systemd[1]: [email protected]: main process exited, code=exited, status=1/FAILURE
    Jul 02 23:33:03 chanan002 systemd[1]: Failed to start My net.
    Jul 02 23:33:03 chanan002 systemd[1]: Unit [email protected] entered failed state.
    Finally, since the wiki mentions possible conflicts, here's the output from 'systemctl list-units'. Hopefully there's nothing confidential in there.
    UNIT LOAD ACTIVE SUB DESCRIPTION
    proc-sys...misc.automount loaded active waiting Arbitrary Executable File Formats File System Automount Point
    sys-devi...d-card0.device loaded active plugged 5 Series/3400 Series Chipset High Definition Audio
    sys-devi...-enp1s0.device loaded active plugged NetLink BCM57780 Gigabit Ethernet PCIe
    sys-devi...-wlp2s0.device loaded active plugged AR9485 Wireless Network Adapter
    sys-devi...\x2d1.2.device loaded active plugged MFC-7420
    sys-devi...ttyUSB0.device loaded active plugged E180v
    sys-devi...9u1u3i1.device loaded active plugged E180v
    sys-devi...ttyUSB1.device loaded active plugged E180v
    sys-devi...ttyUSB2.device loaded active plugged E180v
    sys-devi...ock-sr1.device loaded active plugged Mass_Storage
    sys-devi...ock-sdb.device loaded active plugged SD_Storage
    sys-devi...da-sda1.device loaded active plugged WDC_WD3200BPVT-22JJ5T0
    sys-devi...da-sda2.device loaded active plugged WDC_WD3200BPVT-22JJ5T0
    sys-devi...ock-sda.device loaded active plugged WDC_WD3200BPVT-22JJ5T0
    sys-devi...ock-sr0.device loaded active plugged HL-DT-ST_DVDRAM_GT51N
    sys-devi...y-ttyS0.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS0
    sys-devi...y-ttyS1.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS1
    sys-devi...y-ttyS2.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS2
    sys-devi...y-ttyS3.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS3
    sys-devi...et-ppp0.device loaded active plugged /sys/devices/virtual/net/ppp0
    sys-modu...onfigfs.device loaded active plugged /sys/module/configfs
    sys-subs...-enp1s0.device loaded active plugged NetLink BCM57780 Gigabit Ethernet PCIe
    sys-subs...es-ppp0.device loaded active plugged /sys/subsystem/net/devices/ppp0
    sys-subs...-wlp2s0.device loaded active plugged AR9485 Wireless Network Adapter
    sys-subs...9u1u3i1.device loaded active plugged E180v
    -.mount loaded active mounted /
    dev-hugepages.mount loaded active mounted Huge Pages File System
    dev-mqueue.mount loaded active mounted POSIX Message Queue File System
    sys-kernel-config.mount loaded active mounted Configuration File System
    sys-kernel-debug.mount loaded active mounted Debug File System
    tmp.mount loaded active mounted Temporary Directory
    cups.path loaded active running CUPS Printer Service Spool
    systemd-...d-console.path loaded active waiting Dispatch Password Requests to Console Directory Watch
    systemd-...word-wall.path loaded active waiting Forward Password Requests to Wall Directory Watch
    avahi-daemon.service loaded active running Avahi mDNS/DNS-SD Stack
    colord.service loaded active running Manage, Install and Generate Color Profiles
    cronie.service loaded active running Periodic Command Scheduler
    cups.service loaded active running CUPS Printing Service
    dbus.service loaded active running D-Bus System Message Bus
    dictd.service loaded active running Dictd Dictionary Server Daemon
    [email protected] loaded active running Getty on tty1
    iptables.service loaded active exited Packet Filtering Framework
    [email protected] loaded failed failed My net
    pacserve.service loaded activating auto-restart Pacserve
    systemd-journald.service loaded active running Journal Service
    systemd-logind.service loaded active running Login Service
    systemd-...s-load.service loaded active exited Load Kernel Modulessystemd-...unt-fs.service loaded active exited Remount Root and Kernel File Systems
    systemd-sysctl.service loaded active exited Apply Kernel Variables
    systemd-...-setup.service loaded active exited Recreate Volatile Files and Directories
    systemd-...rigger.service loaded active exited udev Coldplug all Devices
    systemd-udevd.service loaded active running udev Kernel Device Manager
    systemd-...e-utmp.service loaded active exited Update UTMP about System Reboot/Shutdown
    systemd-...ssions.service loaded active exited Permit User Sessions
    systemd-...-setup.service loaded active exited Setup Virtual Console
    avahi-daemon.socket loaded active listening Avahi mDNS/DNS-SD Stack Activation Socket
    cups.socket loaded active listening CUPS Printing Service Sockets
    dbus.socket loaded active running D-Bus System Message Bus Socket
    dmeventd.socket loaded active listening Device-mapper event daemon FIFOs
    lvmetad.socket loaded active listening LVM2 metadata daemon socket
    systemd-initctl.socket loaded active listening /dev/initctl Compatibility Named Pipe
    systemd-journald.socket loaded active running Journal Socket
    systemd-shutdownd.socket loaded active listening Delayed Shutdown Socket
    systemd-...control.socket loaded active listening udev Control Socket
    systemd-...-kernel.socket loaded active running udev Kernel Socket
    basic.target loaded active active Basic System
    cryptsetup.target loaded active active Encrypted Volumes
    getty.target loaded active active Login Prompts
    graphical.target loaded active active Graphical Interface
    local-fs-pre.target loaded active active Local File Systems (Pre)
    local-fs.target loaded active active Local File Systems
    multi-user.target loaded active active Multi-User System
    network.target loaded active active Network
    paths.target loaded active active Paths
    printer.target loaded active active Printer
    remote-fs.target loaded active active Remote File Systems
    sockets.target loaded active active Sockets
    sound.target loaded active active Sound Card
    swap.target loaded active active Swap
    sysinit.target loaded active active System Initialization
    timers.target loaded active active Timers
    systemd-...es-clean.timer loaded active waiting Daily Cleanup of Temporary Directories
    As you can see, it's late here and at my age, I turn into a pumpkin at midnight, so I'm off.  Any suggestions would be much appreciated.

  • [SOLVED] netctl transition not working for me

    Hi,
    Following the latest news I tried to switch from netcfg to netctl but can't get it to work..
    my netctl profile, similar to my netcfg one:
    Description='A simple WPA encrypted wireless connection using a static IP'
    Interface=wlan0
    Connection=wireless
    Security='wpa-config'
    WPAConfigFile='/etc/wpa_supplicant.conf'
    IP=static
    Address='192.168.0.5'
    Gateway='192.168.0.254'
    result:
    # netctl start wirelessHome
    Job for [email protected] failed. See 'systemctl status [email protected]' and 'journalctl -xn' for details.
    # journalctl -xn
    -- Logs begin at Sun 2012-11-11 12:36:25 CET, end at Fri 2013-04-12 21:54:20 CEST. --
    Apr 12 21:54:19 alainLaptop kernel: wlan0: associated
    Apr 12 21:54:19 alainLaptop kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    Apr 12 21:54:20 alainLaptop network[1373]: RTNETLINK answers: Network is unreachable
    Apr 12 21:54:20 alainLaptop network[1373]: Could not set gateway '192.168.0.254' on interface 'wlan0'
    Apr 12 21:54:20 alainLaptop kernel: wlan0: deauthenticating from 00:24:d4:51:48:98 by local choice (reason=3)
    Apr 12 21:54:20 alainLaptop kernel: cfg80211: Calling CRDA to update world regulatory domain
    Apr 12 21:54:20 alainLaptop network[1373]: Failed to bring the network up for profile 'wirelessHome'
    Apr 12 21:54:20 alainLaptop systemd[1]: [email protected]: main process exited, code=exited, status=1/FAILURE
    Apr 12 21:54:20 alainLaptop systemd[1]: Failed to start Networking for netctl profile wirelessHome.
    -- Subject: Unit [email protected] has failed
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba40df7e9d022f03d
    -- Unit [email protected] has failed.
    -- The result is failed.
    Apr 12 21:54:20 alainLaptop systemd[1]: Unit [email protected] entered failed state
    Any suggestion ?
    Last edited by Alain2 (2013-04-12 22:37:20)

    Good & no big deal, I have added a sentence for it in the wiki. The error message is not perfect but not too bad either in my view. It does point toward the gateway. Strange I find that the systemd journal references a documentation link that then leads to a 404 page which does not give much clue how to continue there. The feature with the message_ID itself is awesome, but I'm sure the too plain 404 template at freedesktop has a great hit count (not for netctl, but in general)..

  • Request for author in Beginners Guide/Wireless Netctl

    Since netctl has been in [core] for a while now and since netcfg has been depreciated, it's pretty poor that one of the most popular pages on our wiki is out-of-date.  I am asking for someone with knowledge of netctl/wireless to make an edit the section linked below updating it with proper instructions for netctl.  I would do it myself, but have not used netctl with a wireless profile; my workstation does not have wifi and my laptop is elsewhere at the moment.  I might take a stab at it based on the docs, but will want someone using a wireless profile to check what I write for accuracy.  Anyone using netctl with wireless and willing to edit this first?
    https://wiki.archlinux.org/index.php/Be … Wireless_2
    Last edited by graysky (2013-05-25 10:09:49)

    Sorry you didn't get an answer faster but you have to know this is a peer to peer forum. it is users helping other users so not always the quickest way. First off, can you change your ISP router to modem only mode? It is best that way as you will get conflicts such as what you are seeing when there are two routers in the same link. You are getting the ISP router when you enter 192.168.1.1 because that is its address on the LAN side. It appears that your router is getting set to a 10.x IP because of the setup. You have two routers trying to work with DHCP so that is also an issue. If you can change the ISP router to modem only mode then once it is up disconnect it from the router and do a factory reset on your router and make sure it has the IP of 192.168.1.1 and you will then be able to make any changes you need to. the default login is password of admin and leave the user blank.

  • [solved] "adsl.service" does not start with "netctl" sometimes

    I recently moved from "netcfg" to "netctl".
    Solution. I copied "/usr/lib/systemd/system/adsl.service" into a new service and added a line
    After=[email protected]
    under "[Unit]"

    It goes definitely against any logic.
    The service file looks good, but I've copied it to /usr/lib/systemd/system/bdsl.service. Same contents - and the new one launches succesfully.
    I've deleted the original ...adsl.service file, verified that it disappeared, copied it back from the new bdsl.service file, and it still does not launch.
    [EDIT]
    I've erased the drive, restored the system from a 1 week old backup, started it - everything worked. Then I'v updated the whole system, including the rp-pppoe package, and the adsl service is failing again.
    Downgrading solves the problem. Should I file a bug report?
    Last edited by scar (2013-06-01 10:14:41)

  • Netcfg laptop wireless - "DHCP ip lease attempt failed"??

    hey folks. just loaded arch onto a toshiba laptop. in the process of configuring wireless, i followed the netcfg config instructions in the wiki. It worked fine the first time, but when I rebooted every subsequent time i tried to connect I get the "DHCP IP lease attempt failed" error. IN my logs i get absolutely nothing helpful - just "wlan0: rebinding lease of 172.16.0.138" and "wlan0: timed out". Of course, when I had Windows XP on the laptop it had zero problems connecting to the network, and it makes no damn sense why I was able to connect intially but each time after that it times out. My router has no problems.
    I did a forum search and someone suggested that this was because of a "bug" and to delete the file "/var/lib/dhcpcd/dhcpcd-wlan0.lease" file. I did this, and was able to connect successfully. But this is not a solution; am I really supposed to delete the lease EVERY time I reconnect/reboot the machine? Doesn't make any sense at all.
    Can ANYONE please help on this? I can post whatever config file/log info you need. This seems like it should be a simple setup, but I've come to realize nothing's ever simple in the linux world.... btw my network uses WPA2. There wasn't anything in the wiki about WPA2 (must be really really old, huh?); could this be part of the problem?

    Alternatively, try adding
    PRE_UP=' [ -e /var/lib/dhcpcd/dhcpcd-wlan0.lease ] && rm /var/lib/dhcpcd/dhcpcd-wlan0.lease '
    to the profile with the problem.
    Edit: I misspelled "dhcpcd" in the code above.
    Last edited by alexandrite (2010-08-15 14:54:33)

  • [SOLVED} systemd, netcfg, interface aliases and race conditions

    Not using NetworkManager - base Arch Linux with standard netcfg
    The situation (coming from an old SysV-init guy who's pretty new to systemd):
    I have an application that has a dependency on a specific interface alias.  To be more specific:
    1) eth0 comes up as a DHCP interface (but the address is static on the DHCP server side) and assigns the base IP, which we'll call 192.168.1.2
    2) network.target is satisfied since the interface is up
       3a) netcfg POST_UP executes on the interface, assigning IP address 192.168.1.3 with label eth0:0 to eth0
       3b) The application service (with an After of network.target) starts, attempting to bind a port listener on address 192.168.1.3
    Therein lies the rub.  3a and 3b happen in parallel, creating a race condition.  If the alias happens to be assigned before the application starts, all is well.  If the application initializes before the alias, it dies an ugly death, failing to bind to a non-existent address.  It's a coin toss which one "wins".
    My solution thus far has been to add a ExecStartPre stanza to the application's service calling "/usr/bin/sleep 5", pretty much guaranteeing that the alias will be defined before the application's ExecStart.  This is so ugly and inelegant it's embarassing.
    Two questions:
    - Is there a cleaner way to approach this - perhaps some way to indicate to systemd that eth0:0 must exist prior to starting the application (along the lines of a mythical AfterInterface element ?  I'd considered creating a 0-byte file in /tmp in POST_UP and having my application service check for existence, but it seems that if it doesn't exist, systemd will just skip launching the service, not delay its launch.  I cannot create the alias as part of ExecStartPre for the application, since this interface alias is actually used by multiple applications/services.
    - Would migrating to netctl alleviate this at all (to be more specific, does netctl have a more coherent definition of interface aliasing than hand-creating them via POST_UP, and if so, are the aliases defined by netctl prior to satisfying network.target)?
    Thanks much for any insight,
    Rodney
    Last edited by rhester72 (2013-05-03 16:46:47)

    I can...but my understanding of why the AL wiki recommends assigning aliases in POST_UP is to ensure they are consistently assigned if the interface should be brought offline and back online.  I'm not sure if this is an issue in practice, however - since the same contention would exist on the simplest-possible construct (i.e. what happens to all the services that have network listeners if eth0 just goes away for a while and comes back?).
    Rodney

  • Issues configuring broadcom wl driver with netctl and wpa_supplicant

    After quite some hurdle, I managed to get the wireless working with a Broadcom 4322 with the wl driver working. But there are two minor issues which I'd like to ask the more experienced audience:
    With netctl, I need to manually interact with wpa_supplicant. This was not needed for the same setup on a different machine with a different driver. I'm fine with that, but when it comes to directing the wpa config to netctl, I had to make the config available as /etc/wpa_supplicant.conf because this is the default for netctl. But according to the man page for netctl, netctl offers the option to specify WPAConfigFile, which should be enabled when Security is set to wpa-config. So, I'd like to have the following config:
    /etc/netctl/myWirelessSetup:
    Interface=eth0
    Connection=wireless
    Security=wpa-config
    IP=dhcp
    ESSID=
    Key=
    WPAConfigFile=/etc/wpa_supplicant/myWPASupplicantSetup
    The reason I did it this way is because I ran into a dependency issue with netcfg when not having a wpa_supplicant config file.
    The other issue I have with the broadcom wl driver is that it forces the naming of the wireless device to be eth0, which I don't like. I tried to set it according to the Network wiki, but on boot udev reported a busy device, so I gave up on that.
    I'd appreciate if anybody can point me on what I'm doing wrong.

    yeah, I know it seems odd, but when you install broadcom-wl, it sets the interface to eth0. You'll find it in the wiki. I also know it's eth0 because that's the interface I use to connect to wifi at home.

  • Using the mkinitcpio net hook confuses netcfg

    Hello everybody.
    I am currently trying to build a headless Linux home server, and I decided to try out Arch.
    The server has an encrypted root file system by means of having a plain-text /boot 1st partition and having the / file system on a 2nd LUKS partition.
    For starters I used the mkinitcpio hooks "keymap keyboard encrypt", with the appropriate "cryptdevice=..." and "root=..." kernel parameters to make the server prompt me for the pass phrase in early user space, which works nicely.
    As this thing is supposed to become a headless system I then tried to set it up in a way that enables me to open an SSH connection into the early user space and supply the pass phrase from there, using dropbear_initrd_encrypt. And it works! This is great stuff.
    Unfortunately doing this broke the then-running server's network connection.
    I have a static IP address netcfg profile that is loaded from systemd on server start-up (systemctl enable netcfg; the profile is set in the "NETWORKS=..." variable in "/etc/conf.d/netcfg").
    The ethernet device is called "enp2s0".
    This worked flawlessly until I started using the "net" mkinitcpio hook to get a network connection in early user space for the remote unlocking.
    The net hook's corresponding kernel parameter looks like "ip=<ip>:::<netmask>:::none"
    When I use this hook, the system boots up without having the "enp2s0" ethernet device, causing netcfg to bail out.
    It does however gain the same network device as "eth0" instead, which is apparently how early user space calls it. This "eth0" ethernet device appears to retain the settings it has been set up with by the net hook.
    Unfortunately the net hook does not supply things like a default gateway or DNS servers, so while the server technically is reachable from the local network, it cannot access the internet, which it definitely needs to be able to do.
    After tracking this down I figured "Whatever. I can live with the ethernet device being called eth0."
    So I made a second identical netcfg profile, exchanging "enp2s0" for "eth0", and set the server to load that one instead when booting.
    That unfortunately did not work either, because netcfg is cautious and aborts when it is told to set up a network adapter that is already active in some way unknown to netcfg.
    What also didn't help was specifying the "enp2s0" ethernet device name in the "ip=..." kernel parameter for the net hook, because indeed the early user space only knows the device as "eth0".
    So for now I'm stumped. Anyone experienced this issue and managed to solve it?
    A solution might be another "disablenet" mkinitcpio hook that deconfigures the network adapters configured by "net", so that the renaming from "eth0" to "enp2s0" during boot, which I assume fails on account of "eth0" being active, works again.
    Thanks for any help,
    eomanis
    Edit: Changed "netctl" to "netcfg" in the thread subject
    Last edited by eomanis (2013-04-18 08:45:21)

    tomk wrote:You could try including the appropriate command to bring down your interface in your profile's PRE_UP field.
    Okay, I tried that.
    I put both netcfg profiles into the "NETWORKS=..." variable in "/etc/conf.d/netcfg", and added this to both of them:
    # Clear leftover state from mkinitcpio net hook
    PRE_UP="ip link set <device> down || true"
    where <device> is eth0 or enp2s0, respectively.
    After a reboot with remote decryption the server's network was down completely. Looks like the "ip link set ... down" command worked all right, but the rest didn't go as planned.
    Here's what systemctl says about that:
    [root@hserver autologin]# systemctl status netcfg
    netcfg.service - Netcfg multi-profile daemon
    Loaded: loaded (/usr/lib/systemd/system/netcfg.service; enabled)
    Active: failed (Result: exit-code) since Thu 2013-04-18 22:35:38 CEST; 26min ago
    Process: 340 ExecStart=/usr/bin/netcfg-daemon start (code=exited, status=1/FAILURE)
    Apr 18 22:35:35 hserver netcfg-daemon[340]: :: static_enp2s0 up Cannot find device "enp2s0"
    Apr 18 22:35:35 hserver netcfg-daemon[340]: Interface enp2s0 does not exist
    Apr 18 22:35:35 hserver netcfg-daemon[340]: [fail]
    Apr 18 22:35:38 hserver netcfg-daemon[340]: :: static_eth0 up RTNETLINK answers: File exists
    Apr 18 22:35:38 hserver netcfg-daemon[340]: Could not configure interface
    Apr 18 22:35:38 hserver netcfg-daemon[340]: [fail]
    Apr 18 22:35:38 hserver systemd[1]: netcfg.service: main process exited, code=exited, status=1/FAILURE
    Apr 18 22:35:38 hserver systemd[1]: Failed to start Netcfg multi-profile daemon.
    Apr 18 22:35:38 hserver systemd[1]: Unit netcfg.service entered failed state
    As before, device "enp2s0" is missing, but "eth0" doesn't come up either, even after being downed manually beforehand :-(
    Strangely enough, if I do "netcfg -u static_eth0" after that, eth0 does come up. What?!
    @falconindy: Applying a udev rule in early user space would require to make a custom initcpio hook, wouldn't it?
    In that case I'd rather try to figure out what the "net" hook does and undo it, seeing that I have to write a custom hook anyway and that "eth0" doesn't come up no matter what.
    Having an "enp2s0" ethernet device that doesn't come up either isn't going to do me much good ;-)
    Thanks for the suggestions,
    eomanis

  • Netctl - Per interface configuration?

    With netcfg, you were able to have configuration files which defined global settings for each network interface. Is there any equivalent capability on netctl?

    Use default interface . This will reset config of ur router without affecting other interfaces

  • [Solved/Bug]Hard time getting my wireless to work with netctl

    I'm wondering what is up. I have a very fresh (no WM yet) arch linux install on a laptop i intend to use at school, needless to say i can't use it there unless i got proper wireless.
    Would you suggest i just switch to wicd? (i'm more familiar with wicd, but as i recall i think i had this set up and working fine with netcfg once upon a time.)
    anyways i'll tell you what i've got.
    #ip link
    1: lo:...
    2: enp0s25:....
    3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT qlen 1000
    link/ether 00:27:10:a5:2b:28 brd ff:ff:ff:ff:ff:ff
    contents of /etc/netctl/profile
    Description='Description'
    Interface=wlp3s0
    Connection=wireless
    Security=wpa
    IP=dhcp
    ESSID='MySsid1'
    Key='My number-only WPA-PSK'
    i try to start the profile.
    #netctl start profile
    Job for [email protected] failed. See 'systemctl status [email protected]' and 'journalctl -xn' for details.
    #journalctl -xn
    .... Starting Networking for netctl profile profile....
    The interface of network profile 'profile' is already up
    [email protected]: main process exited, code=exited, status=1/FAILURE
    Failed to start Networking for netctl profile profile.
    The result is failed.
    Unit [email protected] entered failed state.
    i tried according to the wiki using
    #wifi-menu -o
    to automatically generate a profile to see if i was doing something wrong, but no profile was generated (at least not inside /etc/netctl/)
    The only 2 programs i've installed apart from the core that came with the pacstrap last night are 'dialog' (for wifi-menu) and wpa_supplicant (with no particular configuration). Am i missing a dependency or doing something wrong?
    Last edited by rabcor (2013-08-21 13:15:05)

    I'll be using both ethernet and wireless on this laptop at random pretty much, i'm now scratching my head over how i can make it use ethernet anytime it's connected but otherwise look for a wireless network.
    I'm not understanding how that bonding thing works, so i don't know if i can rely on it for that purpose or not.
    This would be no problem if the whole thing was better designed. I need 1 extra dependency (ifplugd) to be able to automate switching between ethernet profiles and another(wpa_actiond) to be able to do the same for wireless profiles, i don't want to start both of them because it would most likely have a heavy impact on my boot time. all i want it to do is choose between dhcp ethernet or two different wireless connections.
    i was kindof hoping i could trick netctl-ifplugd into runing netctl-auto if it fails.
    Last edited by rabcor (2013-08-21 13:56:47)

  • [Solved] Netctl - Cannot connect to wireless network

    Hi,
    since I replaced netcfg with netctl a week ago, it worked just fine. Today, however, i wanted to connect to a different wireless network and i couldn't make it work.
    Here's some information about how i connected to my home network (which worked fine):
    I changed the netcfg config files to match netctl syntax (as described in the wiki)
    I activated netctl-auto@wlan0
    The connection to the network was established almost immediately after (re)boot or resume after suspend
    First off: I double-checked the config file for the second network. Both syntax and SSID/passphrase are correct. Also, I don't have special characters in my network/profile names, the names in brackets are placeholders.
    Here's what happens after a fresh reboot (only the second network is in range of my pc, so it doesn't connect to my first - working - network):
    Netctl-auto is active and running, but seems to repeatedly lose connection to the second network:
    # systemctl status netctl-auto@wlan0
    [email protected] - Automatic wireless network connection using netctl profiles
    Loaded: loaded (/usr/lib/systemd/system/[email protected]; enabled)
    Active: active (running) since Fri 2013-05-17 00:28:03 CEST; 13min ago
    Docs: man:netctl.special(7)
    Process: 453 ExecStart=/usr/bin/netctl-auto start %I (code=exited, status=0/SUCCESS)
    CGroup: name=systemd:/system/[email protected]/[email protected]
    ├─480 wpa_supplicant -B -P /run/wpa_supplicant_wlan0.pid -i wlan0 -D nl80211,wext -c/run/network/wpa_supplicant_wlan0.conf -W
    └─483 wpa_actiond -p /run/wpa_supplicant -i wlan0 -P /run/network/wpa_actiond_wlan0.pid -a /usr/lib/network/auto.action
    May 17 00:41:40 <hostname> wpa_actiond[483]: Interface 'wlan0' reestablished connection to network '<network_2>'
    May 17 00:41:41 <hostname> wpa_actiond[483]: Interface 'wlan0' lost connection to network '<network_2>'
    May 17 00:41:48 <hostname> wpa_actiond[483]: Interface 'wlan0' reestablished connection to network '<network_2>'
    May 17 00:41:48 <hostname> wpa_actiond[483]: Interface 'wlan0' lost connection to network '<network_2>'
    May 17 00:41:51 <hostname> wpa_actiond[483]: Interface 'wlan0' reestablished connection to network '<network_2>'
    May 17 00:41:51 <hostname> wpa_actiond[483]: Interface 'wlan0' lost connection to network '<network_2>'
    May 17 00:41:54 <hostname> wpa_actiond[483]: Interface 'wlan0' reestablished connection to network '<network_2>'
    May 17 00:41:54 <hostname> wpa_actiond[483]: Interface 'wlan0' lost connection to network '<network_2>'
    May 17 00:41:58 <hostname> wpa_actiond[483]: Interface 'wlan0' reestablished connection to network '<network_2>'
    May 17 00:41:58 <hostname> wpa_actiond[483]: Interface 'wlan0' lost connection to network '<network_2>'
    # journalctl -xn
    -- Logs begin at Sat 2012-12-08 23:44:06 CET, end at Fri 2013-05-17 00:47:43 CEST. --
    May 17 00:47:33 <hostname> kernel: cfg80211: Calling CRDA to update world regulatory domain
    May 17 00:47:36 <hostname> kernel: wlan0: authenticate with <network_2 mac address>
    May 17 00:47:36 <hostname> kernel: wlan0: send auth to <network_2 mac address> (try 1/3)
    May 17 00:47:36 <hostname> kernel: wlan0: authenticated
    May 17 00:47:36 <hostname> kernel: wlan0: associate with <network_2 mac address> (try 1/3)
    May 17 00:47:36 <hostname> kernel: wlan0: RX AssocResp from <network_2 mac address> (capab=0x431 status=0 aid=3)
    May 17 00:47:36 <hostname> kernel: wlan0: associated
    May 17 00:47:36 <hostname> wpa_actiond[483]: Interface 'wlan0' reestablished connection to network '<network_2>'
    More interestingly, dmesg seems to provide a reason for this behaviour:
    # dmesg
    [ 1438.732242] wlan0: authenticate with <network_2 mac address>
    [ 1438.737594] wlan0: send auth to <network_2 mac address> (try 1/3)
    [ 1438.740384] wlan0: authenticated
    [ 1438.743113] wlan0: associate with <network_2 mac address> (try 1/3)
    [ 1438.747226] wlan0: RX AssocResp from <network_2 mac address> (capab=0x431 status=0 aid=3)
    [ 1438.767629] wlan0: associated
    [ 1438.837011] wlan0: AP <network_2 mac address> changed bandwidth, new config is 2412 MHz, width 1 (2412/0 MHz)
    [ 1438.837024] wlan0: AP <network_2 mac address> changed bandwidth in a way we can't support - disconnect
    [ 1438.896427] cfg80211: Calling CRDA to update world regulatory domain
    [ 1442.140427] wlan0: authenticate with <network_2 mac address>
    [ 1442.145282] wlan0: send auth to <network_2 mac address> (try 1/3)
    [ 1442.148090] wlan0: authenticated
    [ 1442.151674] wlan0: associate with <network_2 mac address> (try 1/3)
    [ 1442.155712] wlan0: RX AssocResp from <network_2 mac address> (capab=0x431 status=0 aid=3)
    [ 1442.175911] wlan0: associated
    [ 1442.214954] wlan0: AP <network_2 mac address> changed bandwidth, new config is 2412 MHz, width 1 (2412/0 MHz)
    [ 1442.214967] wlan0: AP <network_2 mac address> changed bandwidth in a way we can't support - disconnect
    [ 1442.258359] cfg80211: Calling CRDA to update world regulatory domain
    I'm pretty sure everything should theoretically work fine, because it worked before the netctl update. I was even connected to this network today until i had to reboot!
    Now here's what happens if I try to connect manually:
    # netctl start <network_2>
    Job for netctl@<network_2>.service failed. See 'systemctl status netctl@<network_2>.service' and 'journalctl -xn' for details.
    # systemctl status netctl@<network_2>.service
    netctl@<network_2>.service - Networking for netctl profile <network_2>
    Loaded: loaded (/usr/lib/systemd/system/[email protected]; static)
    Active: failed (Result: exit-code) since Fri 2013-05-17 00:58:40 CEST; 2min 36s ago
    Docs: man:netctl.profile(5)
    Process: 7368 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)
    May 17 00:58:40 <hostname> network[7368]: Starting network profile '<network_2>'...
    May 17 00:58:40 <hostname> network[7368]: The interface of network profile '<network_2>' is already up
    May 17 00:58:40 <hostname> systemd[1]: netctl@<network_2>.service: main process exited, code=exited, status=1/FAILURE
    May 17 00:58:40 <hostname> systemd[1]: Failed to start Networking for netctl profile <network_2>.
    May 17 00:58:40 <hostname> systemd[1]: Unit netctl@<network_2>.service entered failed state.
    After an # ip link set wlan0 down netctl still claims that its job failed:
    # netctl start <network_2>
    Job for netctl@<network_2>.service failed. See 'systemctl status netctl@<network_2>.service' and 'journalctl -xn' for details.
    This time, the DHCP lease attempt seems to be failing:
    # systemctl status netctl@<network_2>.service
    netctl@<network_2>.service - Networking for netctl profile <network_2>
    Loaded: loaded (/usr/lib/systemd/system/[email protected]; static)
    Active: failed (Result: exit-code) since Fri 2013-05-17 01:04:42 CEST; 1min 33s ago
    Docs: man:netctl.profile(5)
    Process: 8423 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)
    May 17 01:04:23 <hostname> systemd[1]: Starting Networking for netctl profile <network_2>...
    May 17 01:04:23 <hostname> network[8423]: Starting network profile '<network_2>'...
    May 17 01:04:31 <hostname> dhcpcd[8656]: version 5.6.8 starting
    May 17 01:04:31 <hostname> dhcpcd[8656]: wlan0: carrier lost
    May 17 01:04:31 <hostname> dhcpcd[8656]: wlan0: waiting for carrier
    May 17 01:04:41 <hostname> dhcpcd[8656]: timed out
    May 17 01:04:41 <hostname> network[8423]: DHCP IP lease attempt failed on interface 'wlan0'
    May 17 01:04:42 <hostname> systemd[1]: netctl@<network_2>.service: main process exited, code=exited, status=1/FAILURE
    May 17 01:04:42 <hostname> systemd[1]: Failed to start Networking for netctl profile <network_2>.
    May 17 01:04:42 <hostname> systemd[1]: Unit netctl@<network_2>.service entered failed state.
    I wasn't able to find out whether netctl needs a running dhcpcd or not, but after running a systemctl start dhcpcd.service, dmesg seems to give a little more information:
    # dmesg
    [ 2500.090650] wlan0: authenticate with <network_2 mac address>
    [ 2500.109377] wlan0: send auth to <network_2 mac address> (try 1/3)
    [ 2500.114053] wlan0: authenticated
    [ 2500.115817] wlan0: associate with <network_2 mac address> (try 1/3)
    [ 2500.121336] wlan0: RX AssocResp from <network_2 mac address> (capab=0x431 status=0 aid=3)
    [ 2500.147262] wlan0: associated
    [ 2500.303529] wlan0: AP <network_2 mac address> changed bandwidth, new config is 2412 MHz, width 1 (2412/0 MHz)
    [ 2500.303542] wlan0: AP <network_2 mac address> changed bandwidth in a way we can't support - disconnect
    [ 2500.327471] cfg80211: Calling CRDA to update world regulatory domain
    [ 2769.285673] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
    [ 2769.285908] iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
    [ 2769.488380] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
    Any pointers and solutions are greatly appreciated.
    Thanks,
    diiis
    Last edited by diiis (2013-05-23 16:45:47)

    @silverzhao I use a manual dhcpcd/wpa_supplicant way of setting up my wlan0 using http://git.r-36.net/conn and I have the same problem.
    I have to kill my wireless and restart after seeing a message like:
    May 20 10:12:33 x220 kernel: wlan0: AP a4:b1:e9:55:25:2f changed bandwidth, new config is 2462 MHz, width 2 (2452/0 MHz)

Maybe you are looking for

  • Multiple inheritance in remote interfaces for EJB 3.0 session beans on Webl

    Hi All, We started migration from EJB 2.1(WLS 8.1) to EJB 3.0(WLS 10.3.2) and identified few serious problems. One of them is related with multiple business interfaces inheritance. I wrote simple example that presents point of the problem. we have se

  • Need Advice on RMAN backup script

    Hi; Can any one advice if any error or guide to make RMAN backup proper : Backup Policy are: 1.     0 level backup 2.     current log file is arvhived before backing up 3.     backup whole database (datafiles) 4.     backup separate control file 5.  

  • How do you put Save as back in the File menu?

    I know under File the "save as" is gone. I also know that if you push the option key it will show up under the File menu until you take your finger off the option key. What I want to know is how can you get the "save as" back under the file menu with

  • Call & SMS logging on BES

    How to prevent call logs and SMS details from the Balckberry handheld getting Synchronised on to the corporate BES server? Is there a setting on handheld that can be configured to block this?

  • Problems running Solaris 10 GA x86 on a Compaq Presario R3200

    Dear all, I downloaded the DVD images for Solaris 10 x86, and tried to install it on my amd64-based laptop. 1) The first thing that happens is that sometimes at the start, the keyboard will not work when I am asked the kind of installation, or to pre