[SOLVED] Cannot connect wifi

Hi all.
i am newibe on arch linux.
i read too much but still i cant connect wifi.
it shows wifi networks but when i click them, it says cannoct connect..
my hardware is:
02:00.0 Network controller: Intel Corporation Centrino Wireless-N 130 (rev 34)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06)
i installed r8168 module and blacklisted 8169 module but not worked. after that i cannot connect weired network too.
Last edited by chataluck (2013-02-11 22:17:20)

@ewaller thnx for reply
output:
i am trying to connect agritux
but it is not important. because i cannot connect any essid
it says cannot activated
wlp2s0 Scan completed :
Cell 01 - Address: 18:28:61:1F:5B:1C
Channel:6
Frequency:2.437 GHz (Channel 6)
Quality=70/70 Signal level=-32 dBm
Encryption key:on
ESSID:"agritux"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s
Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s
Mode:Master
Extra:tsf=00000013938b7c16
Extra: Last beacon: 40ms ago
IE: Unknown: 000761677269747578
IE: Unknown: 010882848B962430486C
IE: Unknown: 030106
IE: Unknown: 2A0104
IE: Unknown: 2F0104
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
IE: Unknown: 32040C121860
IE: Unknown: DD09001018020100000000
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
Cell 02 - Address: 18:28:61:36:16:C2
Channel:9
Frequency:2.452 GHz (Channel 9)
Quality=35/70 Signal level=-75 dBm
Encryption key:on
ESSID:"karaca"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s
Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 48 Mb/s
Mode:Master
Extra:tsf=000000050ca3d59c
Extra: Last beacon: 40ms ago
IE: Unknown: 00066B6172616361
IE: Unknown: 010882848B962430486C
IE: Unknown: 030109
IE: Unknown: 2A0104
IE: Unknown: 2F0104
IE: Unknown: 32040C121860
IE: Unknown: 2D1A6C181BFF00000000000000000000000000000000000000000000
IE: Unknown: 3D1609001300000000000000000000000000000000000000
IE: Unknown: 4A0E14000A002C01C800140005001900
IE: Unknown: 7F0101
IE: Unknown: DD0B001CA85001013616C22B09
IE: Unknown: DDB60050F204104A0001101049001E007FC5100018ACBFBEF29A2C7E5563E04772F25589FC30303030303030311044000102103B00010310470010D3EC1E9588B451FD9E0849E4521F4AB5102100194169725469657320576972656C657373204E6574776F726B731023000941697235333431545410240008312E302E302E31311042000F4154313036313135323030353536351054000800060050F204000110110009416972353334315454100800020084103C000103
IE: Unknown: DD090010180201F0040000
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
IE: Unknown: DD180050F2020101800003A4000027A4000042435E0062322F00
Cell 03 - Address: C8:6C:87:8B:8D:DC
Channel:6
Frequency:2.437 GHz (Channel 6)
Quality=36/70 Signal level=-74 dBm
Encryption key:on
ESSID:"ZyXEL3596oT1"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 9 Mb/s
18 Mb/s; 36 Mb/s; 54 Mb/s
Bit Rates:6 Mb/s; 12 Mb/s; 24 Mb/s; 48 Mb/s
Mode:Master
Extra:tsf=0000007d6596f9c0
Extra: Last beacon: 40ms ago
IE: Unknown: 000C5A7958454C333539366F5431
IE: Unknown: 010882848B961224486C
IE: Unknown: 030106
IE: Unknown: 2A0104
IE: Unknown: 32040C183060
IE: Unknown: 2D1A6E1117FF000000010000000000000000000000000C0000000000
IE: Unknown: 3D1606070400000000000000000000000000000000000000
IE: Unknown: 3E0100
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : TKIP CCMP
Authentication Suites (1) : PSK
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : TKIP CCMP
Authentication Suites (1) : PSK
IE: Unknown: DD180050F2020101000003A4000027A4000042435E0062322F00
IE: Unknown: 0B050000237A12
IE: Unknown: 7F0101
IE: Unknown: DD07000C4304000000
IE: Unknown: 0706414C20010D10
IE: Unknown: DD1E00904C336E1117FF000000010000000000000000000000000C0000000000
IE: Unknown: DD1A00904C3406070400000000000000000000000000000000000000
IE: Unknown: DD9F0050F204104A0001101044000102103B00010310470010BC329E001DD811B28601C86C878B8DDC1021001852616C696E6B20546563686E6F6C6F67792C20436F72702E1023001C52616C696E6B20576972656C6573732041636365737320506F696E74102400065254323836301042000831323334353637381054000800060050F20400011011000B5472656E64436869704150100800020084103C000100
lo Interface doesn't support scanning.
enp3s0 Interface doesn't support scanning.
Last edited by chataluck (2013-02-09 19:15:40)

Similar Messages

Cannot connect wifi after updated ios7.1.2

After i updated to ios 7.1.2, i cannot connect wifi but another device can connect wifi normally.

Because...
a) Some people are earnestly trying to help.
b) Some people are clueless about this royal Apple iOS update screwup!
I am extremely ****** off... partly because one of the so-call 'genius' suggestions of "forgetting network" and reapplying degraded my phone from occasional WiFi loss to COMPLETE WiFi loss. Then I wasted two hours trying the other 'genius' suggestions like resetting the entire phone and network settings!
B.S.!
Apple still refuses to acknowledge this problem! What else is new?

Cannot connect wifi, wrong i.p. address, worked before

NO FIX FOR WIFI
cannot connect wifi. thanks for info, as I've read and read but no solution:
I submit: 2g iPHONE firmware 1.1.1 . used wifi fine but now I get weird I.P. addresses , wrong i.p. address, cannot connect . I have connected fine before and can connect fine with other routers.
I have had to configure static i.p. in the past if a conflict with other devices but on DHCP normally. setting static i.p. doesnt help, still cannot connect.tried reset network... don't have weird apps like openssh or any wifi apps.
any ideas?

I never had a problem with WiFi on my original iPhone until I upgraded to 2.0.1. Then WiFi began to drop out, I would have to tweak a lot of settings to get a connection again and another problem surfaced: my phone started loosing time -- even though I have it configured to "set automatically." (Sometimes I would discover it was hours off). I updated to 2.0.2 as soon as it showed up in my iTunes because I assumed it would fix these problems. WRONG! Now my WiFi is totally broken and my phone is unable to sync with MobilMe. I've turned the "push" and "fetch" settings off and am syncing though iTunes.

Just bought a iPhone5, I cannot connect Wifi in my home, whereas, my another iPhone4 can connect Wifi, why? How to resolve? Pls advise. thx.

Just bought iPhone 5 and try to use Wifi at home, but it cannot connect Wifi, whereas, my another iPhone4 can connect Wifi, why? how to resolve? Pls advise. Thanks.

Make sure you're updated to iOS 6.0.2, I know that has had something to do with Wi-Fi for a lot of people.

How can i solve "Cannot connect to the iTune Store" issue on my iPhone?

Hi,
Frequently i'm getting alert message (Cannot Connect to the iTune Store) while use my valid Credential on iPhone 4 (even Itunes application) Setting-> iTunes & App Stores->. but same credential accepted other iPhones too why not in my iPhone 4. same way others Apple ID wouldn't accept in my iPhone 4. how can i solve this problem? please suggest me.
Thanks in Advance,
Suresh Balakrishnan.

Take a look at these instructions:
http://www.digitaltrends.com/mobile/how-to-make-ringtones-for-iphone/

SOLVED: Cannot connect to iTunes store on iPhone 4

I figured I'd post this incase someone else is having this issue. It may not fix it all the time, but it worked for me.
Everytime I tried to download an app, I would get the error message "Cannot connect to iTunes Store". I reset my password and even tried to reboot my phone. SOLUTION: I had to go under Settings > General > Reset > Reset Network Settings.
I was able to connect to iTunes store after that.
Hope this helps anyone with the same issue.

Didn't work for me. Everything was working last night and now no matter what I do I can't connect to the itunes store on my phone via wifi.

I cannot connect wifi on my fone it says authentication problem

i cannot connect to my fone with wifi from my osprey

Have you entered on your phone the correct password for the OSpray's SSID?

[Solved]Cannot connect to Windows Share printer over network.

I'm having trouble connecting to a windows printer via Samba/CUPS.
I've loaded the lp module, but I don't know if I need to load the USB or Parallel ports modules, or both or neither, since this is a network print.
My organization has provided some basic instructions for Mac users. Working off of those, I have a setup with the device URI reading
DeviceURI smb://ksong8:(password)@ucmprint.ucmerced.edu/ucmglobal?waitjob=false
For some reason, the printer reports that it cannot connect to the CIFS share, even though it should be configured correctly.
Even more curiously, I'm able to connect to the share manually with
smbclient //ucmprint.ucmerced.edu/ucmglobal -U ksong8
and then entering my password.
Am I missing something terribly obvious here? I have a sample of logs in debug mode, but they looked okay to me (as well as very verbose), so I won't put them here. I have attached my /etc/cups/printers.conf.
# Printer configuration file for CUPS v1.5.2
# Written by cupsd on 2012-04-02 23:06
# DO NOT EDIT THIS FILE WHEN CUPSD IS RUNNING
<Printer UCMGlobal>
UUID urn:uuid:56cf696f-e7a6-3859-49ea-fc990df764e9
AuthInfoRequired username,password
Info UC Merced Global Print Spool
Location Kolligian Library
MakeModel Generic PostScript Printer
DeviceURI smb://ksong8:(password)@ucmprint.ucmerced.edu/ucmglobal?waitjob=false
State Idle
StateTime 1333433102
Type 8400972
Accepting Yes
Shared No
JobSheets none none
QuotaPeriod 0
PageLimit 0
KLimit 0
OpPolicy default
ErrorPolicy stop-printer
</Printer>
EDIT: Added myself to sys (somehow missed that on the installation) and did some futzing around with the GUI tools. Got some interesting results, but I need to confirm that they work.
Last edited by chipbuster (2012-04-04 04:06:04)

Solved.
As it turns out, either CUPS or Samba does not like having special characters in the password inside of /etc/cups/printers.conf. They should be replaced with "%" and the appropriate ASCII hex code for the symbol.

[SOLVED] Cannot connect to NFS server.

I'm trying to setup a NFS share at home. I have one laptop configured as a server, and one desktop client. Both are running Arch. I can ping both in either way.
For some reason, I cannot connect to the server. At one time, I could connect, but only while having an empty /etc/hosts.deny file (which obviously is very insecure). Now, I cannot even reproduce this.
Thus, I believe the problem is caused by either /etc/hosts.allow or / and by /etc/hosts.deny.
Here is my server's /etc/exports:
/shared 192.168.x.xxx(rw,sync,no_subtree_check,no_root_squash)
And here its /etc/hosts.allow:
ALL:192.168.0.0/255.255.255.0
And finally its /etc/hosts.deny:
ALL: ALL: DENY
Running 'rpcinfo -p' on the server shows output, while running 'rpcinfo -p <server-ip>' on the client prints out 'No remote programs registered.'
From what I've read, when the client wants to connect to the server, the server first checks in hosts.allow to see if the client's allowed to connect. So in my case, it should be able connect.
However, when I run
sudo mount -t nfs 192.168.x.xxx:/ /mnt/SERVER
it tells me
mount.nfs: mount to NFS server '192.168.x.xxx:/`failed: RPC Error: Program not registered
And even if outcomment both hosts.deny and hosts.allow, running the same command prints out
mount.nfs: access denied by server while mounting 192.168.x.xxx:/
I'm clueless. Any help would be greatly appreciated!
Last edited by MrAllan (2009-03-20 15:05:24)

tomk wrote:
Missed a detail on first reading. Your server's exports file makes the /shared directory available to 192.168.x.xxx, but your client mount command tries to mount the server's / i.e. root directory. You can only mount directories that have been exported.
btw, there's no need to conceal internal addresses like that - we all have them, and there's no way anyone can use them to track you down. My laptop address is 10.12.62.99, my server is 192.168.10.10, and my irssi/bittorrent/whatever machine is 192.168.10.69. I challenge anyone to hack me.
But if they know his IP, couldn't they use the lan IP to gain access easier than if they didn't know the subnet addresses? Since the thread is solved, I figured I would ask since I've always wondered about it.
Btw, for anyone have unresolved NFS issues, see this bug report. The arch devs aren't responding to it for some reason, can anyone tell me why?
http://bugs.archlinux.org/task/13434

How do I solve: "Cannot connect to iTunes Store" message

I get this message: Cannot connect to iTunes Store" after I enter my password. I have already accessed the iTunes store, and have downloaded a music sample, but when I try to make a purchase, I can't because after I enter my password, I get this message. Thus, I cannot complete a purchase.

Check out these troubleshooting suggestions:
http://support.apple.com/kb/TS2388
http://support.apple.com/kb/TS1368

[Solved] Cannot connect with wifi-menu after login

I can't connect to the internet after I login. When I try to connect, it says:
Job for netctl@my\x2dnetwork.service failed. See "systemctl status 'netctl@my\x2dnetwork.service'" and "journalctl -xe" for details.
#systemctl status 'netctl@my\x2dnetwork.service'
● netctl@my\x2dnetwork.service - A simple WPA encrypted wireless connection
Loaded: loaded (/etc/systemd/system/netctl@my\x2dnetwork.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Fri 2015-02-06 16:37:35 CST; 1min 23s ago
Docs: man:netctl.profile(5)
Process: 574 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)
Main PID: 574 (code=exited, status=1/FAILURE)
Feb 06 16:37:35 mac network[574]: Starting network profile 'my-network'...
Feb 06 16:37:35 mac network[574]: The interface of network profile 'my-network' is already up
Feb 06 16:37:35 mac systemd[1]: netctl@my\x2dnetwork.service: main process exited, code=exited, status=1/FAILURE
Feb 06 16:37:35 mac systemd[1]: Failed to start A simple WPA encrypted wireless connection.
Feb 06 16:37:35 mac systemd[1]: Unit netctl@my\x2dnetwork.service entered failed state.
Feb 06 16:37:35 mac systemd[1]: netctl@my\x2dnetwork.service failed.
#journalctl -xe
Feb 06 16:37:17 mac dbus[217]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service'
Feb 06 16:37:17 mac udisksd[436]: udisks daemon version 2.1.3 starting
Feb 06 16:37:17 mac dbus[217]: [system] Successfully activated service 'org.freedesktop.UDisks2'
Feb 06 16:37:17 mac udisksd[436]: Acquired the name org.freedesktop.UDisks2 on the system message bus
Feb 06 16:37:18 mac polkitd[271]: Registered Authentication Agent for unix-session:c2 (system bus name :1.29 [/usr/lib/polkit-gnome/polkit-gnome-authen
Feb 06 16:37:18 mac dbus[217]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
Feb 06 16:37:18 mac avahi-daemon[481]: Found user 'avahi' (UID 84) and group 'avahi' (GID 84).
Feb 06 16:37:18 mac avahi-daemon[481]: Successfully dropped root privileges.
Feb 06 16:37:18 mac avahi-daemon[481]: avahi-daemon 0.6.31 starting up.
Feb 06 16:37:18 mac avahi-daemon[481]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Feb 06 16:37:18 mac dbus[217]: [system] Successfully activated service 'org.freedesktop.Avahi'
Feb 06 16:37:18 mac avahi-daemon[481]: Successfully called chroot().
Feb 06 16:37:18 mac avahi-daemon[481]: Successfully dropped remaining capabilities.
Feb 06 16:37:18 mac avahi-daemon[481]: Loading service file /services/sftp-ssh.service.
Feb 06 16:37:18 mac avahi-daemon[481]: Loading service file /services/ssh.service.
Feb 06 16:37:18 mac avahi-daemon[481]: Network interface enumeration completed.
Feb 06 16:37:18 mac avahi-daemon[481]: Registering HINFO record with values 'X86_64'/'LINUX'.
Feb 06 16:37:18 mac avahi-daemon[481]: Server startup complete. Host name is mac.local. Local service cookie is 1997621208.
Feb 06 16:37:18 mac avahi-daemon[481]: Service "mac" (/services/ssh.service) successfully established.
Feb 06 16:37:18 mac avahi-daemon[481]: Service "mac" (/services/sftp-ssh.service) successfully established.
Feb 06 16:37:30 mac sudo[510]: mac : TTY=pts/0 ; PWD=/home/mac ; USER=root ; COMMAND=/usr/bin/wifi-menu
Feb 06 16:37:30 mac sudo[510]: pam_unix(sudo:session): session opened for user root by mac(uid=0)
Feb 06 16:37:35 mac network[574]: Starting network profile 'my-network'...
Feb 06 16:37:35 mac network[574]: The interface of network profile 'my-network' is already up
Feb 06 16:37:35 mac systemd[1]: netctl@my\x2dnetwork.service: main process exited, code=exited, status=1/FAILURE
Feb 06 16:37:35 mac systemd[1]: Failed to start A simple WPA encrypted wireless connection.
-- Subject: Unit netctl@my\x2dnetwork.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit netctl@my\x2dnetwork.service has failed.
-- The result is failed.
Feb 06 16:37:35 mac systemd[1]: Unit netctl@my\x2dnetwork.service entered failed state.
Feb 06 16:37:35 mac systemd[1]: netctl@my\x2dnetwork.service failed.
Feb 06 16:37:35 mac sudo[510]: pam_unix(sudo:session): session closed for user root
Feb 06 16:37:48 mac dbus[217]: [system] Activating via systemd: service name='org.freedesktop.NetworkManager' unit='dbus-org.freedesktop.NetworkManager
Feb 06 16:37:48 mac dbus[217]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.NetworkManager.service': Unit dbus-org.freedesktop
Feb 06 16:37:50 mac logger[626]: ACPI action undefined: PNP0C0A:00
Feb 06 16:38:31 mac logger[653]: ACPI action undefined: PNP0C0A:00
Feb 06 16:39:13 mac logger[657]: ACPI action undefined: PNP0C0A:00
When I ip link set ... down, I wifi-menu and it connects. No need to ip link set ... up.
Here's my /etc/systemd/system/netctl\@my\\x2dnetwork.service as mentioned above.
.include /usr/lib/systemd/system/[email protected]
[Unit]
Description=A simple WPA encrypted wireless connection
BindsTo=sys-subsystem-net-devices-wlp4s0.device
After=sys-subsystem-net-devices-wlp4s0.device
Not sure if this is relevant. Also mentioned above. This is /usr/lib/network/network.
#! /bin/bash
. /usr/lib/network/globals
## Check if a string represents a network interface
# $1: potential interface name
is_interface() {
# Strip any old school alias specifier
[[ -d "/sys/class/net/${1%%:?*}" ]]
## Add an interface
# $1: interface type
# $2: interface name
# $3: interface link (optional)
# $4...: additional arguments
interface_add() {
local type="$1" name="$2" link="$3"
do_debug ip link add ${link:+link "$link"} name "$name" type "$type" "${@:4}" || return
if [[ -x "$PROFILE_DIR/interfaces/$name" ]]; then
source "$PROFILE_DIR/interfaces/$name"
fi
## Delete an interface
# $1: interface name
interface_delete() {
bring_interface_down "$1"
ip link delete "$1"
## Check if an interface is up
# $1: interface name
interface_is_up() {
local flags
read flags < "/sys/class/net/${1%%:?*}/flags"
# IFF_UP is defined as 0x1 in linux/if.h
(( flags & 0x1 ))
## Activate an interface
# $1: interface name
bring_interface_up() {
local interface=$1
ip link set dev "$interface" up &>/dev/null
timeout_wait "${TimeoutUp:-5}" 'interface_is_up "$interface"'
## Deactivate an interface
# $1: interface name
bring_interface_down() {
local interface=$1
ip link set dev "$interface" down &>/dev/null
# We reuse the up timeout (down normally is faster)
timeout_wait "${TimeoutUp:-5}" '! interface_is_up "$interface"'
if [[ $# -ne 2 || $1 != @(start|stop) ]]; then
exit_error "Usage: $0 {start|stop} <profile>"
fi
ensure_root netctl
# Ensure we are not in a transient directory
cd /
# Expose the profile name
Profile=$2
load_profile "$Profile"
case $1 in
start)
report_notice "Starting network profile '$Profile'..."
if is_interface "$Interface" && interface_is_up "$Interface" && \
! is_yes "${ForceConnect:-no}"; then
report_error "The interface of network profile '$Profile' is already up"
exit 1
fi
if ! "${Connection}_up"; then
report_error "Failed to bring the network up for profile '$Profile'"
exit 1
fi
# JP: sandbox the eval
if ! ( eval $ExecUpPost ); then
report_error "ExecUpPost failed for network profile '$Profile'"
# Failing ExecUpPost will take the connection down
"${Connection}_down"
exit 1
fi
report_notice "Started network profile '$Profile'"
stop)
report_notice "Stopping network profile '$Profile'..."
# JP: sandbox the eval
if ! ( eval $ExecDownPre ); then
report_error "ExecDownPre failed for network profile '$Profile'"
# Failing ExecDownPre will leave the profile active
exit 1
fi
if ! "${Connection}_down"; then
report_error "Failed to bring the network down for profile '$Profile'"
exit 1
fi
if is_interface "$Interface" && interface_is_up "$Interface" && \
! is_yes "${ForceConnect:-no}"; then
report_error "The interface of network profile '$Profile' did not go down"
exit 1
fi
report_notice "Stopped network profile '$Profile'"
esac
Last edited by rollypolio (2015-02-07 16:37:01)

I honestly don't remember. I believe I was trying to set up i3status dhcp at the time. Could have been the DHCP configuration file I created at /etc/systemd/network that broke my netctl configuration. I should have mentioned that first. I broke the internet and walked away two days ago and it's slowly coming back to me. I don't follow the relation between systemd, netctl, and dhcp configuration so I'm sorry if I'm not picking up on solutions provided in your links.
I commented the file out right after I started receiving those errors.
$cat /etc/systemd/network/MyDhcp.network
#[Match]
#Name=wlp4s0
#[Network]
#DHCP=v4
$ls -la /etc/systemd/network/MyDhcp.network
drwxr-xr-x 2 root root 4096 Feb 6 09:29 .
drwxr-xr-x 5 root root 4096 Feb 5 20:15 ..
-rw-r--r-- 1 root root 43 Feb 6 09:29 MyDhcp.network
$cat /etc/netctl/my-network
Description='A simple WPA encrypted wireless connection'
Interface=wlp4s0
Connection=wireless
Security=wpa
IP=dhcp
ESSID='ap_becca'
# 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='*********'
# Uncomment this if your ssid is hidden
#Hidden=yes
# Set a priority for automatic profile selection
#Priority=10
#cat /etc/netctl/wlp4s0-Nexxt_5F6CB8
Description='Automatically generated profile by wifi-menu'
Interface=wlp4s0
Connection=wireless
Security=none
ESSID=Nexxt_5F6CB8
IP=dhcp
#cat /etc/netctl/wlp4s0-SJBS
Description='Automatically generated profile by wifi-menu'
Interface=wlp4s0
Connection=wireless
Security=wpa
ESSID=SJBS
IP=dhcp
Key=********
I noticed the first profile does not require sudo.
$ ls -la
total 32
drwxr-xr-x 5 root root 4096 Feb 2 09:32 .
drwxr-xr-x 81 root root 4096 Feb 7 09:42 ..
drwxr-xr-x 2 root root 4096 Jan 31 22:50 examples
drwxr-xr-x 2 root root 4096 Jan 13 07:23 hooks
drwxr-xr-x 2 root root 4096 Jan 13 07:23 interfaces
-rw-r--r-- 1 root root 422 Jan 31 22:52 my-network
-rw------- 1 root root 138 Feb 2 09:32 wlp4s0-Nexxt_5F6CB8
-rw------- 1 root root 145 Feb 2 06:36 wlp4s0-SJBS
I hope this helps.
Which one should I be looking at?:
$ls /usr/lib/systemd/system/ | grep netctl
[email protected]
[email protected]
netctl.service
[email protected]
netctl-sleep.service
To repeat myself, I can connect using wifi-menu after I ip link set wlp4s0 down. I'm just looking for a fix so I can set up automatic connections.
EDIT: I deleted /etc/systemd/network/MyDhcp.network and now it works at startup. Any idea why a commented out file would be having an adverse effect like this?
Last edited by rollypolio (2015-02-07 16:41:41)

[SOLVED]cannot connect to wireless network due to a channel setting

Hello guys, I recently came across a problem with my wireless network.
It was first a system-wide upgrade(adapted from the pacman's log):
[2010-08-22 15:10] Running 'pacman -Syu'
[2010-08-22 15:10] synchronizing package lists
[2010-08-22 15:10] starting full system upgrade
[2010-08-22 16:14] upgraded avahi (0.6.25-3 -> 0.6.27-2)
[2010-08-22 16:14] upgraded nspr (4.8.4-1 -> 4.8.6-1)
[2010-08-22 16:14] upgraded nss (3.12.6-3 -> 3.12.7-1)
[2010-08-22 16:14] upgraded chromium (5.0.375.125-1 -> 5.0.375.127-1)
[2010-08-22 16:14] upgraded curl (7.21.0-1 -> 7.21.1-1)
[2010-08-22 16:14] upgraded freetype2 (2.4.1-1 -> 2.4.2-1)
[2010-08-22 16:14] upgraded gnome-keyring (2.30.3-1 -> 2.30.3-2)
[2010-08-22 16:14] upgraded gstreamer0.10 (0.10.29-1 -> 0.10.30-1)
[2010-08-22 16:14] upgraded orc (0.4.6-1 -> 0.4.7-1)
[2010-08-22 16:14] upgraded udev (160-1 -> 161-1)
[2010-08-22 16:14] upgraded gstreamer0.10-base (0.10.29-1 -> 0.10.30-1)
[2010-08-22 16:14] upgraded gstreamer0.10-base-plugins (0.10.29-1 -> 0.10.30-1)
[2010-08-22 16:14] upgraded k3b (2.0.0-2 -> 2.0.1-2)
[2010-08-22 16:14] upgraded linux-firmware (20100623-2 -> 20100807-1)
[2010-08-22 16:14] >>> Updating module dependencies. Please wait ...
[2010-08-22 16:14] >>> MKINITCPIO SETUP
[2010-08-22 16:14] >>> ----------------
[2010-08-22 16:14] >>> If you use LVM2, Encrypted root or software RAID,
[2010-08-22 16:14] >>> Ensure you enable support in /etc/mkinitcpio.conf .
[2010-08-22 16:14] >>> More information about mkinitcpio setup can be found here:
[2010-08-22 16:14] >>> http://wiki.archlinux.org/index.php/Mkinitcpio
[2010-08-22 16:14]
[2010-08-22 16:14] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2010-08-22 16:14] ==> Building image "default"
[2010-08-22 16:14] ==> Running command: /sbin/mkinitcpio -k 2.6.35-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26.img
[2010-08-22 16:14] :: Begin build
[2010-08-22 16:14] :: Parsing hook [base]
[2010-08-22 16:14] :: Parsing hook [udev]
[2010-08-22 16:14] :: Parsing hook [autodetect]
[2010-08-22 16:14] :: Parsing hook [pata]
[2010-08-22 16:14] :: Parsing hook [scsi]
[2010-08-22 16:14] :: Parsing hook [sata]
[2010-08-22 16:14] :: Parsing hook [usbinput]
[2010-08-22 16:14] :: Parsing hook [keymap]
[2010-08-22 16:15] :: Parsing hook [encrypt]
[2010-08-22 16:15] :: Parsing hook [lvm2]
[2010-08-22 16:15] :: Parsing hook [filesystems]
[2010-08-22 16:15] :: Generating module dependencies
[2010-08-22 16:15] :: Generating image '/boot/kernel26.img'...SUCCESS
[2010-08-22 16:15] ==> SUCCESS
[2010-08-22 16:15] ==> Building image "fallback"
[2010-08-22 16:15] ==> Running command: /sbin/mkinitcpio -k 2.6.35-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26-fallback.img -S autodetect
[2010-08-22 16:15] :: Begin build
[2010-08-22 16:15] :: Parsing hook [base]
[2010-08-22 16:15] :: Parsing hook [udev]
[2010-08-22 16:15] :: Parsing hook [pata]
[2010-08-22 16:15] :: Parsing hook [scsi]
[2010-08-22 16:15] :: Parsing hook [sata]
[2010-08-22 16:15] :: Parsing hook [usbinput]
[2010-08-22 16:15] :: Parsing hook [keymap]
[2010-08-22 16:15] :: Parsing hook [encrypt]
[2010-08-22 16:15] :: Parsing hook [lvm2]
[2010-08-22 16:15] :: Parsing hook [filesystems]
[2010-08-22 16:16] :: Generating module dependencies
[2010-08-22 16:16] :: Generating image '/boot/kernel26-fallback.img'...SUCCESS
[2010-08-22 16:16] ==> SUCCESS
[2010-08-22 16:16] upgraded kernel26 (2.6.34.3-1 -> 2.6.35.2-1)
[2010-08-22 16:16] upgraded kernel26-headers (2.6.34.3-1 -> 2.6.35.2-1)
[2010-08-22 16:16] upgraded libdatrie (0.2.3-1 -> 0.2.4-1)
[2010-08-22 16:16] upgraded libgnome-keyring (2.30.1-1 -> 2.30.1-2)
[2010-08-22 16:16] upgraded libpciaccess (0.11.0-1 -> 0.12.0-1)
[2010-08-22 16:16] upgraded libxvmc (1.0.5-1 -> 1.0.6-1)
[2010-08-22 16:16] upgraded mdadm (3.1.2-2 -> 3.1.3-1)
[2010-08-22 16:16] upgraded pixman (0.18.2-1 -> 0.18.4-1)
[2010-08-22 16:16] upgraded poppler-data (0.4.2-1 -> 0.4.3-1)
[2010-08-22 16:16] upgraded powertop (1.11-2 -> 1.13-2)
[2010-08-22 16:16] upgraded pycairo (1.8.8-1 -> 1.8.10-1)
[2010-08-22 16:16] upgraded pygtk (2.17.0-1 -> 2.17.0-2)
[2010-08-22 16:16] upgraded qimageblitz (0.0.5-1 -> 0.0.6-1)
[2010-08-22 16:16] upgraded usbutils (0.87-1 -> 0.90-1)
[2010-08-22 16:16] upgraded vlc (1.1.2-2 -> 1.1.3-1)
[2010-08-22 16:16] upgraded xextproto (7.1.1-1 -> 7.1.2-1)
[2010-08-22 16:16] upgraded xf86-input-evdev (2.4.0-1 -> 2.4.0-2)
[2010-08-22 16:16] upgraded xproto (7.0.17-1 -> 7.0.18-1)
Then after a reboot, I wouldn't be able to connect to wireless network anymore.
I tried "netcfg Wireless_Archer(my wireless profile's name)" as usual, it replied:
[root@mzws log]# netcfg Wireless_Archer
:: Wireless_Archer up [BUSY]
> WPA Authentication/Association Failed
[FAIL]
Next I tried to bing the network up manually. I followed the "Wireless Setup" and "WPA supplicant" wiki, then I get a timed out problem:
[root@mzws ~]# ifconfig wlan0 up
[root@mzws ~]# iwlist wlan0 scan
wlan0 Scan completed :
Cell 01 - Address: D8:5D:4C:59:52:EC
Channel:13
Frequency:2.472 GHz (Channel 13)
Quality=66/70 Signal level=-44 dBm
Encryption key:on
ESSID:"Archer"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
12 Mb/s; 24 Mb/s; 36 Mb/s
Bit Rates:9 Mb/s; 18 Mb/s; 48 Mb/s; 54 Mb/s
Mode:Master
Extra:tsf=000000000bf666fe
Extra: Last beacon: 70ms ago
IE: Unknown: 0006417263686572
IE: Unknown: 010882848B960C183048
IE: Unknown: 03010D
IE: Unknown: 2A0100
IE: Unknown: 32041224606C
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
Preauthentication Supported
IE: Unknown: DD0900037F01010008FF7F
IE: Unknown: DD1A00037F0301000000D85D4C5952ECDA5D4C5952EC64002C010808
Cell 02 - Address: 00:22:B0:8C:76:D7
Channel:1
Frequency:2.412 GHz (Channel 1)
Quality=22/70 Signal level=-88 dBm
Encryption key:on
ESSID:"szpatrick"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 9 Mb/s
18 Mb/s; 36 Mb/s; 54 Mb/s
Bit Rates:6 Mb/s; 12 Mb/s; 24 Mb/s; 48 Mb/s
Mode:Unknown/bug
Extra:tsf=000000e93e5b9174
Extra: Last beacon: 1340ms ago
IE: Unknown: 0009737A7061747269636B
IE: Unknown: 010882848B961224486C
IE: Unknown: 030101
IE: Unknown: 32040C183060
IE: Unknown: 0706474220010D10
IE: Unknown: 33082001020304050607
IE: Unknown: 33082105060708090A0B
IE: Unknown: DD050050F20500
IE: Unknown: DD0E0050F204104A0001101044000102
IE: Unknown: 050400010000
IE: Unknown: 2A0100
IE: Unknown: 2D1A6E1013FFFF0000010000000000000000000000000C0000000000
IE: Unknown: 3D1601050100000000000000000000000000000000000000
IE: Unknown: 7F0101
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
IE: Unknown: DD180050F2020101000003A4000027A4000042435E0062322F00
IE: Unknown: DD1E00904C336E1013FFFF0000010000000000000000000000000C0000000000
IE: Unknown: DD1A00904C3401050100000000000000000000000000000000000000
IE: Unknown: DD07000C4304000000
Cell 03 - Address: 00:25:68:EB:3F:FC
Channel:11
Frequency:2.462 GHz (Channel 11)
Quality=26/70 Signal level=-84 dBm
Encryption key:on
ESSID:"vodafone3FFB"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s
Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
Mode:Master
Extra:tsf=00000002f6c23184
Extra: Last beacon: 570ms ago
IE: Unknown: 000C766F6461666F6E6533464642
IE: Unknown: 010882848B960C121824
IE: Unknown: 03010B
IE: Unknown: 050400010000
IE: Unknown: 200100
IE: Unknown: 2A0104
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
IE: Unknown: 32043048606C
IE: Unknown: DD180050F2020101020003A4000027A4000042435E0062322F00
IE: Unknown: DD1E00904C334E101BFFFF000000000000000000000000000000000000000000
IE: Unknown: 2D1A4E101BFFFF000000000000000000000000000000000000000000
IE: Unknown: DD1A00904C340B071B00000000000000000000000000000000000000
IE: Unknown: 3D160B071B00000000000000000000000000000000000000
IE: Unknown: DD0900037F01010000FF7F
IE: Unknown: DD0A00037F04010020000000
IE: Unknown: 0706494520010D14
[root@mzws ~]# wpa_supplicant -B -Dwext -i wlan0 -c /etc/wpa_supplicant.conf
[root@mzws ~]# iwconfig wlan0
wlan0 IEEE 802.11bgn ESSID:"Archer"
Mode:Managed Frequency:2.472 GHz Access Point: D8:5D:4C:59:52:EC
Bit Rate=1 Mb/s Tx-Power=14 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=66/70 Signal level=-44 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
[root@mzws ~]# sleep 10s;dhcpcd wlan0
dhcpcd[4076]: version 5.2.7 starting
dhcpcd[4076]: wlan0: rebinding lease of 192.168.1.102
dhcpcd[4076]: wlan0: carrier lost
dhcpcd[4076]: wlan0: carrier acquired
dhcpcd[4076]: wlan0: rebinding lease of 192.168.1.102
dhcpcd[4076]: wlan0: broadcasting for a lease
dhcpcd[4076]: wlan0: carrier lost
dhcpcd[4076]: wlan0: carrier acquired
dhcpcd[4076]: wlan0: rebinding lease of 192.168.1.102
dhcpcd[4076]: wlan0: broadcasting for a lease
dhcpcd[4076]: wlan0: carrier lost
dhcpcd[4076]: wlan0: carrier acquired
dhcpcd[4076]: wlan0: rebinding lease of 192.168.1.102
dhcpcd[4076]: timed out
I tried the "iwconfig wlan0 channel auto", but that didn't work. Here's the output of "lspci | grep -i net":
[root@mzws ~]# lspci | grep -i net
00:19.0 Ethernet controller: Intel Corporation 82567LF Gigabit Network Connection (rev 03)
03:00.0 Network controller: Intel Corporation WiFi Link 1000 Series
So what's the problem here? I searched the forum and google, and it seemed that I connected to a wrong router(for sometimes I only one "carrier lost" then "timed out"), but how was that happened? Things worked quite well before the upgrading as well as in my Windows environment.
Any reply would be appreciated! Thanks in advance!
Last edited by karbon (2010-08-23 06:40:10)

Thanks Proofrific, but I believe it's not, for the DHCP server is a built-in module in my wireless router.
I am now able to connect to my wireless network now. And it seems to be a little kernel bug as I discovered a thread(sorry but I forgot which one) in the forum discussing a similar problem.... Somebody in that post suggested a work-around to change the channel, as their default setting is channel 13 or 12.
I tried and it did work! Just simply open your router's setting page and then change the channel from auto to 3(in my case), and netcfg worked well now. For the manual configuration, I suppose the "iwconfig wlan0 channel 3" should be issued.
Thanks everyone in the forum for providing their solutions!

[SOLVED]Cannot Connect to Wireless Network during Installation

(Sorry, yet another newbie unable to configure a network connection properly)
I've been using Ubuntu for a little while now (since 11.10), and finally decided to give Arch a try (for a number of reasons). I thought I was comfortable enough with the CLI to be able to set this up, especially with the help of the Beginners' Guide (and the rest of the internet), but I still ran into issues with setting up my network connection (practically the first step, ugh).
Following the instructions in the Beginners' Guide, I first brought the interface up with
# ip link set wlp5s4 up
and then used
# wifi-menu wlp5s4
to try and connect, but it gave me a connection failed error.
# systemctl status netctl@wlp5s4\x2dWIN_030.service
gave me the following:
Loaded: loaded (/usr/lib/systemd/system/[email protected]; static)
Active: inactive (dead)
(I'll post the output of 'journalctl -xn' if someone can tell me an easy way to move it between computers, or I'll type it manually if there's no easier way)
I then proceeded to attempt connect without using wifi-menu. I first did
# wpa_supplicant -B -i wlp3s0 -c <(wpa_passphrase "ssid" "psk")
(replacing ssid and psk with the right info, of course), and got the output
Successfully initialized wpa_supplicant
I then did
# dhcpcd wlp5s4
but this timed out.
Following the instructions, I went to the fallback, starting with
# echo 'ctrl_interface=DIR=/run/wpa_supplicant' > /etc/wpa_supplicant.conf
# wpa_passphrase <ssid> <passphrase> >> /etc/wpa_supplicant.conf
The second command resulted in
zsh: parse error near `<'
I'm not sure what I'm doing wrong, but that's what I've done so far. I apologize if this seems like information overload, but I felt more info is better than less.
Anyone have any suggestions as to what my next moves should be? If you want me to post any logs, please let me know.
Last edited by DaimyoKirby (2013-11-03 14:54:15)

Here are the results.
I went through the initial steps, and started the without wifi-menu steps. When I got to where I had a problem previously, this is what happened:
# echo 'ctrl_interface=DIR=/run/wpa_supplicant' > /etc/wpa_supplicant.conf
# wpa_passphrase <ssid> <passphrase> >> /etc/wpa_supplicant.conf
# ip link set wlp5s4 up
I replaced "<ssid>" and "<passphrase>" correctly this time, and all of these commands passed without any output.
I ran into the next command, though, and wasn't exactly sure about it:
# wpa_supplicant -B -D n180211 -c /foobar.conf -i wlp5s4
I assumed I had to replace "/foobar.conf" with "/etc/wpa_supplicant.conf", and this gave me the following output:
Successfully initialized wpa_supplicant
wlp5s4: Unsupported driver 'n180211'
The Beginners' Guide doesn't indicate what outputs you should get from these commands, so assuming that this was a good output, I ran
dhcpcd wlp5s4
but this just ended up timing out as well.

[Solved] Cannot connect to wireless

So I'm trying to connect to wireless but I'm having trouble. It seems to happen no matter what wireless network I try to connect to. I open up wifi-menu and select the network I want to connect to, but I get an error:
Job for netctl@wlp1s0\x2dTSC.service failed. See 'systemctl status netctl@wlp1s0\x2dTSC.service' and 'journalctl -xn' for details
However, looking at those seems to not really give an indication as to what's going on. Here they are:
systemctl status netctl@wlp1s0\x2dTSC.service:
* [email protected] - Networking for netctl profile wlp1s0x2dTSC
Loaded: loaded (/usr/lib/systemd/system/[email protected]; static)
Active: inactive (dead)
Docs: man:netctl.profile(5)
journalctl -xn:
-- Logs begin at Tue 2013-08-27 08:59:38 EDT, end at Thu 2014-03-27 15:26:00 EDT. --
Mar 27 15:20:44 dave-lappy systemd[562]: Starting Default.
-- Subject: Unit UNIT has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit UNIT has begun starting up.
Mar 27 15:20:44 dave-lappy systemd[562]: Reached target Default.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit UNIT has finished starting up.
-- The start-up result is done.
Mar 27 15:20:44 dave-lappy systemd[562]: Startup finished in 158ms.
-- Subject: System start-up is now complete
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- All system services necessary queued for starting at boot have been
-- successfully started. Note that this does not mean that the machine is
-- now idle as services might still be busy with completing start-up.
-- Kernel start-up required KERNEL_USEC microseconds.
-- Initial RAM disk start-up required INITRD_USEC microseconds.
-- Userspace start-up required 158066 microseconds.
Mar 27 15:23:44 dave-lappy su[913]: (to root) dave on pts/0
Mar 27 15:23:44 dave-lappy su[913]: pam_unix(su:session): session opened for user root by (uid=1000)
Mar 27 15:24:19 dave-lappy su[913]: pam_unix(su:session): session closed for user root
Mar 27 15:24:25 dave-lappy su[1069]: (to root) dave on pts/0
Mar 27 15:24:25 dave-lappy su[1069]: pam_unix(su:session): session opened for user root by (uid=1000)
Mar 27 15:24:24 dave-lappy systemd[562]: Time has been changed
-- Subject: Time change
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- The system clock has been changed to REALTIME microseconds after January 1st, 1970.
Mar 27 15:26:00 dave-lappy su[1069]: pam_unix(su:session): session closed for user root
I did a pacman -Syu last night. There wasn't any news on the website that mentioned any updates that might affect the wireless. Otherwise, everything was working fine previously. I can't think of any other changes I've made.
So I'm really not sure what's going on. Any thoughts?
Last edited by arbulus (2014-03-27 21:19:26)

So I decided to just go down the docs in the wiki step by step regarding wireless and netctl. From the netctl page, I did:
systemctl enable [email protected]
and then it started working again. I don't know why it stopped working, but it appears to be up and running now.
Last edited by arbulus (2014-03-27 21:20:38)

[SOLVED] Cannot bring wifi interface up

Hello,
A bit of a newbie here...
I've just installed archlinux on a laptop and I'm trying to get it to use a static IP on the wireless (already suceeded to get it working with a static IP on the wired network) via WEP to an access point that doesn't broadcast its ESSID.
I have set up a netctl profile which runs at boot time. Said profile seems to run correctly and I even get an IP address for the wireless. However, it doesn't seem to bring the wifi interface up and typing "ip link set <INTERFACE> up" as root seems to have no effect. I have already installed the firmware for the card and I'm not successful in getting a connection.
This is the output of the commands I've tried so far:
# ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: wlp2s3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
link/ether 00:12:f0:02:47:bd brd ff:ff:ff:ff:ff:ff
inet 192.168.1.6/26 brd 192.168.1.63 scope global wlp2s3
valid_lft forever preferred_lft forever
3: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
link/ether 00:11:43:4b:d6:ec brd ff:ff:ff:ff:ff:ff
inet 192.168.1.5/26 brd 192.168.1.63 scope global enp2s0
valid_lft forever preferred_lft forever
inet6 fe80::211:43ff:fe4b:d6ec/64 scope link
valid_lft forever preferred_lft forever
# iw dev
phy#0
Interface wlp2s3
ifindex 2
wdev 0x1
addr 00:12:f0:02:47:bd
type managed
# iw dev wlp2s3 link
Not connected.
# ip link set wlp2s3 up
<this command doesn't produce any output>
# ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: wlp2s3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
link/ether 00:12:f0:02:47:bd brd ff:ff:ff:ff:ff:ff
inet 192.168.1.6/26 brd 192.168.1.63 scope global wlp2s3
valid_lft forever preferred_lft forever
3: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
link/ether 00:11:43:4b:d6:ec brd ff:ff:ff:ff:ff:ff
inet 192.168.1.5/26 brd 192.168.1.63 scope global enp2s0
valid_lft forever preferred_lft forever
inet6 fe80::211:43ff:fe4b:d6ec/64 scope link
valid_lft forever preferred_lft forever
# iw dev
phy#0
Interface wlp2s3
ifindex 2
wdev 0x1
addr 00:12:f0:02:47:bd
type managed
# iw dev wlp2s3 link
Not connected.
# lspci -k
02:03.0 Network controller: Intel Corporation PRO/Wireless 2200BG [Calexico2] Network Connection (rev 05)
Subsystem: Intel Corporation Dell Latitude D600
Kernel driver in use: ipw2200
Kernel modules: ipw2200
# dmesg | grep ipw2200
[ 6.606394] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kmprq
[ 6.606401] ipw2200: Copyright(c) 2003-2006 Intel Corporation
[ 6.608009] ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
[ 6.854658] ipw2200: Detected geography ZZD (13 802.11bg channels, 0 802.11a channels)
# rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
As a reference, here you have the netctl profile I created:
Description='WEP encrypted wireless connection'
Interface=wlp2s3
Connection=wireless
Security=wep
ESSID='MYNETWORKNAME'
# Prepend \" to hexadecimal keys
Key=\"01234567890ABCDEF012345678
IP=static
Address=('192.168.1.6/26')
Gateway='192.168.1.XXX'
DNS=('XXX.XXX.XXX.XXX' 'YYY.YYY.YYY.YYY')
SkipNoCarrier=yes
# Uncomment this if your ssid is hidden
Hidden=yes
# Uncomment if you are using an ad-hoc connection
#AdHoc=yes
Thanks in advance for your help/advice!!
Last edited by AMaudio (2013-11-09 21:08:35)

Thanks for the pointers, Strike0. The wired-wireless failover scenario does look quite interesting. So I'd like to explore that option more extensively. I attempted to create a master bond/failover connection via netctl with two slaves: one for the wired connection and another one for the wireless connection. For the wired connection I used a netctl profile and for the wireless connection I used a systemd service manually setting up the wireless connection, somewhat following the wiki pages you refer to.
All three services start up correctly, but when I unplug the ethernet cable, the wireless network doesn't take over. It seems that it's not really connected.
Here's the details of my configuration:
The master failover (bond) netctl profile:
# cat /etc/netctl/failover
Description='A wired connection with failover to wireless'
Interface='bond0'
Connection=bond
BindsToInterfaces=('enp2s0' 'wlp2s3')
IP=static
Address="192.168.1.5/26"
Gateway='192.168.1.1'
DNS=('XXX.XXX.XXX.XXX' 'YYY.YYY.YYY.YYY')
SkipNoCarrier='no'
The failover wired netctl profile:
# cat /etc/netctl/failover_wired
Description='Failover wired network'
Interface=enp2s0
Connection=ethernet
IP=no
SkipNoCarrier=yes
## 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 systemd service for the wireless network:
# cat /etc/systemd/system/network-wireless\@.service
[Unit]
Description=Wireless network connectivity (%i)
Wants=network.target
Before=network.target
BindsTo=sys-subsystem-net-devices-%i.device
After=sys-subsystem-net-devices-%i.device
[Service]
Type=oneshot
RemainAfterExit=yes
#EnvironmentFile=/etc/conf.d/network-wireless@%i
ExecStart=/usr/bin/ip link set dev %i up
ExecStart=/usr/bin/iwconfig wlp2s3 essid MYNETWORKNAME
ExecStart=/usr/bin/iwconfig wlp2s3 key 0123456789ABCDEF
#ExecStart=/usr/bin/ip addr add ${address}/${netmask} broadcast ${broadcast} dev %i
#ExecStart=/usr/bin/ip route add default via ${gateway}
#ExecStop=/usr/bin/ip addr flush dev %i
ExecStop=/usr/bin/ip link set dev %i down
[Install]
WantedBy=multi-user.target
After rebooting the machine, I see that all three profile/services started successfully:
# netctl status failover
[email protected] - A wired connection with failover to wireless
Loaded: loaded (/etc/systemd/system/[email protected]; enabled)
Active: active (exited) since Sat 2013-11-09 13:59:27 GMT; 34min ago
Docs: man:netctl.profile(5)
Process: 165 ExecStart=/usr/lib/network/network start %I (code=exited, status=0/SUCCESS)
Main PID: 165 (code=exited, status=0/SUCCESS)
Nov 09 13:59:24 mycomputer systemd[1]: Starting A wired connection with failover to wireless...
Nov 09 13:59:27 mycomputer network[165]: Starting network profile 'failover'...
Nov 09 13:59:27 mycomputer network[165]: RTNETLINK answers: File exists
Nov 09 13:59:27 mycomputer systemd[1]: Started A wired connection with failover to wireless.
Nov 09 13:59:28 mycomputer systemd[1]: Started A wired connection with failover to wireless.
# netctl status failover_wired
netctl@failover_wired.service - Failover wired network
Loaded: loaded (/etc/systemd/system/netctl@failover_wired.service; enabled)
Active: active (exited) since Sat 2013-11-09 13:59:27 GMT; 34min ago
Docs: man:netctl.profile(5)
Process: 163 ExecStart=/usr/lib/network/network start %I (code=exited, status=0/SUCCESS)
Main PID: 163 (code=exited, status=0/SUCCESS)
Nov 09 13:59:24 mycomputer systemd[1]: Starting Failover wired network...
Nov 09 13:59:27 mycomputer systemd[1]: Started Failover wired network.
Nov 09 13:59:28 mycomputer systemd[1]: Started Failover wired network.
# systemctl status [email protected]
[email protected] - Wireless network connectivity (wlp2s3)
Loaded: loaded (/etc/systemd/system/[email protected]; enabled)
Active: active (exited) since Sat 2013-11-09 13:59:25 GMT; 36min ago
Process: 177 ExecStart=/usr/bin/iwconfig wlp2s3 key 12345667890ABCDEF (code=exited, status=0/SUCCESS)
Process: 175 ExecStart=/usr/bin/iwconfig wlp2s3 essid MYNETWORKNAME (code=exited, status=0/SUCCESS)
Process: 164 ExecStart=/usr/bin/ip link set dev %i up (code=exited, status=0/SUCCESS)
Main PID: 177 (code=exited, status=0/SUCCESS)
Nov 09 13:59:24 mycomputer systemd[1]: Starting Wireless network connectivity (wlp2s3)...
Nov 09 13:59:27 mycomputer systemd[1]: Started Wireless network connectivity (wlp2s3).
This is the output from ip addr show, which as far as I can tell, it's all correct:
# ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp2s0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP qlen 1000
link/ether 00:11:43:4b:d6:ec brd ff:ff:ff:ff:ff:ff
3: wlp2s3: <NO-CARRIER,BROADCAST,MULTICAST,SLAVE,UP> mtu 1500 qdisc pfifo_fast master bond0 state DOWN qlen 1000
link/ether 00:11:43:4b:d6:ec brd ff:ff:ff:ff:ff:ff
4: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
link/ether 00:11:43:4b:d6:ec brd ff:ff:ff:ff:ff:ff
inet 192.168.1.5/26 brd 192.168.1.63 scope global bond0
valid_lft forever preferred_lft forever
inet6 fe80::211:43ff:fe4b:d6ec/64 scope link
valid_lft forever preferred_lft forever
And here's the output from iwconfig. Notice that it says "Access point: not-associated"
# iwconfig
wlp2s3 IEEE 802.11bg ESSID:"MYNETWORKNAME"
Mode:Managed Channel:0 Access Point: Not-Associated
Bit Rate:0 kb/s Tx-Power=20 dBm Sensitivity=8/0
Retry limit:7 RTS thr:off Fragment thr:off
Encryption key:900A-0B0D-4B57-C007-1F5D-5C63-79 Security mode:open
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
lo no wireless extensions.
enp2s0 no wireless extensions.
bond0 no wireless extensions.

[SOLVED] Cannot connect wifi

Similar Messages

Maybe you are looking for