You are not logged in.

#1 2013-07-07 12:12:24

drasticraft
Member
From: mars
Registered: 2013-07-05
Posts: 55
Website

Wifi-menu intermittenty failing to connect to any network

It's like flipping a coin! Sometimes it works, but more often then not, I get:

Job for netctl@wlp2s0\x2dsinbin.service failed. See 'systemctl status netctl@wlp2s0\x2dsinbin.service' and 'journalctl -xn' for details.

It almost always fails after I try to download a package with pacman and forget it isn't connected, then go to connect it.

My Network's SSID is sinbin. My old man suggested the name, and I never really got to changing it. smile

So, the way I have to connect is to do

reboot

and then right after I log in I do wifi-menu.
Any other time, and it doesn't work.

So, lookng at the first thing it asks me to look at is:

drasticraft wrote:

systemctl status netctl@wlp2s0\x2dsinbin.service

Alright, so this command's output pretty much shows that everything went fine, but that it is inactive.

Networking for netctl profile wlp2s0x2dsinbin
   Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static)
   Active: inactive (dead)
   Docs: man:netctl.profile(5)

Now, for the second command:

drasticraft wrote:

journalctl -xn

Jul 07 08:14:07 BRFN network[632]: Starting network profile 'wlp2s0-sinbin'...
Jul 07 08:14:07 BRFN kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
Jul 07 08:14:08 BRFN kernel: wlp2s0: authenticate with 84:1b:5e:4c:6b:41
Jul 07 08:14:09 BRFN kernel: wlp2s0: send auth to 84:1b:5e:4c:6b:41 (try 1/3)
Jul 07 08:14:09 BRFN kernel: wlp2s0: authenticated
Jul 07 08:14:09 BRFN kernel: wlp2s0: associate with 84:1b:5e:4c:6b:41 (try 1/3)
Jul 07 08:14:09 BRFN kernel: wlp2s0: RX AssocResp from 84:1b:5e:4c:6b:41 (capab=0x411 status=0 aid=6)
Jul 07 08:14:09 BRFN kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
Jul 07 08:14:09 BRFN kernel: wlp2s0: associated
Jul 07 08:14:09 BRFN dhcpcd[691]: version 5.6.8 starting
Jul 07 08:14:09 BRFN dhcpcd[691]: wlp2s0: broadcasting for a lease
Jul 07 08:14:14 BRFN dhcpcd[691]: wlp2s0: offered 10.0.0.10 from 10.0.0.1
Jul 07 08:14:14 BRFN dhcpcd[691]: wlp2s0: acknowledged 10.0.0.10 from 10.0.0.1
Jul 07 08:14:14 BRFN dhcpcd[691]: wlp2s0: checking for 10.0.0.10
Jul 07 08:14:19 BRFN dhcpcd[691]: timed out
Jul 07 08:14:19 BRFN network[632]: DHCP IP lease attempt failed on interface 'wlp2s0'
Jul 07 08:14:19 BRFN kernel: wlp2s0: deauthenticating from 84:1b:5e:4c:6b:41 by local choice (reason=3)
Jul 07 08:14:19 BRFN kernel: cfg80211: Calling CRDA to update world regulatory domain
Jul 07 08:14:19 BRFN network[632]: Failed to bring the network up for profile 'wlp2s0-sinbin'
Jul 07 08:14:19 BRFN systemd[1]: netctl@wlp2s0\x2dsinbin.service: main process exited, code=exited, status=1/FAILURE
Jul 07 08:14:19 BRFN systemd[1]: Failed to start Networking for netctl profile wlp2s0-sinbin.
Jul 07 08:14:19 BRFN systemd[1]: Unit netctl@wlp2s0\x2dsinbin.service entered failed state.

If you need any more information, just ask.

Last edited by drasticraft (2013-07-09 15:56:16)

Offline

#2 2013-07-11 21:46:40

leflore
Member
From: Columbus, OH
Registered: 2013-07-09
Posts: 11

Re: Wifi-menu intermittenty failing to connect to any network

How are you starting wifi-menu?


"Whoever has ears, let him hear"

Offline

#3 2013-07-13 13:43:33

drasticraft
Member
From: mars
Registered: 2013-07-05
Posts: 55
Website

Re: Wifi-menu intermittenty failing to connect to any network

like this:

wifi-menu

Offline

#4 2013-07-13 14:57:34

smokn
Member
Registered: 2010-06-13
Posts: 17

Re: Wifi-menu intermittenty failing to connect to any network

I have a problem very similar to yours, posted about it here.
So check it once in a while maybe you'll find something that helps. And i'll do the same
https://bbs.archlinux.org/viewtopic.php?id=166638

Last edited by smokn (2013-07-13 14:57:57)

Offline

#5 2013-07-13 17:43:28

leflore
Member
From: Columbus, OH
Registered: 2013-07-09
Posts: 11

Re: Wifi-menu intermittenty failing to connect to any network

Are you able to re-authenticate using

# netctl reenable sinbin 

?


"Whoever has ears, let him hear"

Offline

#6 2013-07-13 21:48:15

jonr
Member
From: Brno, Czech Republic
Registered: 2013-07-12
Posts: 2
Website

Re: Wifi-menu intermittenty failing to connect to any network

That was also happening to me here and when starting i3 I just couldn't connect using wifi-menu because the interface wasn't up.
It all worked after I installed wpa_actiond and then: # systemctl enable netctl-auto@interface.service
https://wiki.archlinux.org/index.php/Netctl


"What we do in life, echoes in eternity"

Offline

#7 2013-07-15 01:53:43

BGK
Member
From: France
Registered: 2013-07-06
Posts: 30

Re: Wifi-menu intermittenty failing to connect to any network

Jul 07 08:14:09 BRFN kernel: wlp2s0: associated
Jul 07 08:14:09 BRFN dhcpcd[691]: version 5.6.8 starting
Jul 07 08:14:09 BRFN dhcpcd[691]: wlp2s0: broadcasting for a lease
Jul 07 08:14:14 BRFN dhcpcd[691]: wlp2s0: offered 10.0.0.10 from 10.0.0.1
Jul 07 08:14:14 BRFN dhcpcd[691]: wlp2s0: acknowledged 10.0.0.10 from 10.0.0.1
Jul 07 08:14:14 BRFN dhcpcd[691]: wlp2s0: checking for 10.0.0.10
Jul 07 08:14:19 BRFN dhcpcd[691]: timed out
Jul 07 08:14:19 BRFN network[632]: DHCP IP lease attempt failed on interface 'wlp2s0'

I would say your system is unable to set the offered IP (10.0.0.10) on your wifi interface after getting the DHCPACK from the server. You might want to check if:
- You don't  have another interface using this IP (loopback/tun/tap/ethernet interface)
- There is no computer already using this IP on your network.

Also you could try to:
- Set an IP to your wifi interface manually rather than using dhcpcd and see what happens.
- Understand why would dhcpcd fail to set this IP (or any IP?) to this interface.

Last edited by BGK (2013-07-15 01:54:34)

Offline

#8 2013-07-15 02:15:14

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 20,354

Re: Wifi-menu intermittenty failing to connect to any network

Not a solution, but a possible work around; certainly another data point....

What if you try dhclient instead of dhcpcd ?  I have seen dhclient be more tolerant of broken networks.  dhcpcd seems to err on the side of caution.


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

Board footer

Powered by FluxBB