You are not logged in.

#1 2014-12-04 09:00:12

Duxon
Member
Registered: 2010-12-01
Posts: 41

[SOLVED] WiFi: Connected to SSID eduroam, but no internet connection

Hi everyone,

I'm having a weird issue with my laptop at my university.
The connection with eduroam is established (using NetworkManager) and sometimes works for some seconds or a minute, but always breaks down shortly after. The WiFi stays connected.

I'm having a hard time to pin this problem down, any help is appreciated.

This is what I know:

  1. Eduroam works well with the same configuration on other hardware.

  2. My laptop's WiFi works well with other APs.

  3. It's probably no DNS resolve issue. I can't connect to direct IPs either.

  4. Disabling power saving did not help

    # iw wlp1s0 set power_save off

This is my journal-log when it happened, nothing suspicious, right?

Dez 04 09:35:00 rolfgang NetworkManager[408]: <info> (wlp1s0): supplicant interface state: authenticating -> associating
Dez 04 09:35:00 rolfgang NetworkManager[408]: <info> (wlp1s0): supplicant interface state: associating -> associated
Dez 04 09:35:00 rolfgang NetworkManager[408]: <info> (wlp1s0): supplicant interface state: associated -> completed
Dez 04 09:35:00 rolfgang NetworkManager[408]: <info> Activation (wlp1s0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'eduroam'.
Dez 04 09:35:00 rolfgang NetworkManager[408]: <info> Activation (wlp1s0) Stage 3 of 5 (IP Configure Start) scheduled.
Dez 04 09:35:00 rolfgang NetworkManager[408]: <info> Activation (wlp1s0) Stage 3 of 5 (IP Configure Start) started...
Dez 04 09:35:00 rolfgang NetworkManager[408]: <info> (wlp1s0): device state change: config -> ip-config (reason 'none') [50 70 0]
Dez 04 09:35:00 rolfgang NetworkManager[408]: <info> Activation (wlp1s0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Dez 04 09:35:00 rolfgang NetworkManager[408]: dhcpcd[7658]: version 6.6.4 starting
Dez 04 09:35:00 rolfgang NetworkManager[408]: <info> dhcpcd started with pid 7658
Dez 04 09:35:00 rolfgang NetworkManager[408]: <info> Activation (wlp1s0) Stage 3 of 5 (IP Configure Start) complete.
Dez 04 09:35:00 rolfgang NetworkManager[408]: dhcpcd[7658]: wlp1s0: adding address fe80::89fe:f138:d594:203f
Dez 04 09:35:00 rolfgang NetworkManager[408]: dhcpcd[7658]: if_addaddress6: Permission denied
Dez 04 09:35:00 rolfgang NetworkManager[408]: dhcpcd[7658]: DUID 00:01:00:01:19:8e:2f:4b:c4:85:08:0b:2d:0e
Dez 04 09:35:00 rolfgang NetworkManager[408]: dhcpcd[7658]: wlp1s0: IAID 08:0b:2d:0e
Dez 04 09:35:00 rolfgang NetworkManager[408]: <info> (wlp1s0): DHCPv4 state changed nbi -> preinit
Dez 04 09:35:01 rolfgang NetworkManager[408]: dhcpcd[7658]: wlp1s0: soliciting an IPv6 router
Dez 04 09:35:01 rolfgang NetworkManager[408]: dhcpcd[7658]: wlp1s0: rebinding lease of 141.76.77.209
Dez 04 09:35:06 rolfgang NetworkManager[408]: <info> Activation (wlp1s0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Dez 04 09:35:06 rolfgang NetworkManager[408]: <info> Activation (wlp1s0) Stage 4 of 5 (IPv6 Configure Timeout) started...
Dez 04 09:35:06 rolfgang NetworkManager[408]: <info> Activation (wlp1s0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
Dez 04 09:35:07 rolfgang NetworkManager[408]: dhcpcd[7658]: wlp1s0: leased 141.76.77.209 for 600 seconds
Dez 04 09:35:07 rolfgang NetworkManager[408]: dhcpcd[7658]: wlp1s0: adding route to 141.76.76.0/22
Dez 04 09:35:07 rolfgang NetworkManager[408]: <info> (wlp1s0): DHCPv4 state changed preinit -> reboot
Dez 04 09:35:07 rolfgang NetworkManager[408]: <info>   address 141.76.77.209
Dez 04 09:35:07 rolfgang NetworkManager[408]: <info>   plen 22 (255.255.252.0)
Dez 04 09:35:07 rolfgang NetworkManager[408]: <info>   gateway 141.76.76.1
Dez 04 09:35:07 rolfgang NetworkManager[408]: <info>   server identifier 141.30.1.225
Dez 04 09:35:07 rolfgang NetworkManager[408]: <info>   lease time 600
Dez 04 09:35:07 rolfgang NetworkManager[408]: <info>   nameserver '141.30.66.135'
Dez 04 09:35:07 rolfgang NetworkManager[408]: <info>   nameserver '141.30.66.1'
Dez 04 09:35:07 rolfgang NetworkManager[408]: <info>   domain name 'dip.tu-dresden.de'
Dez 04 09:35:07 rolfgang NetworkManager[408]: <info> Activation (wlp1s0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Dez 04 09:35:07 rolfgang NetworkManager[408]: <info> Activation (wlp1s0) Stage 5 of 5 (IPv4 Commit) started...
Dez 04 09:35:07 rolfgang NetworkManager[408]: <info> (wlp1s0): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
Dez 04 09:35:07 rolfgang NetworkManager[408]: <info> Activation (wlp1s0) Stage 5 of 5 (IPv4 Commit) complete.
Dez 04 09:35:07 rolfgang NetworkManager[408]: <info> (wlp1s0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
Dez 04 09:35:07 rolfgang NetworkManager[408]: <info> (wlp1s0): device state change: secondaries -> activated (reason 'none') [90 100 0]
Dez 04 09:35:07 rolfgang NetworkManager[408]: <info> NetworkManager state is now CONNECTED_LOCAL
Dez 04 09:35:07 rolfgang NetworkManager[408]: <info> (wlp1s0): roamed from BSSID 1C:1D:86:2B:A3:41 (eduroam) to 1C:E6:C7:1D:27:8E (eduroam)
Dez 04 09:35:07 rolfgang NetworkManager[408]: <info> NetworkManager state is now CONNECTED_GLOBAL
Dez 04 09:35:07 rolfgang NetworkManager[408]: <info> Policy set 'eduroam' (wlp1s0) as default for IPv4 routing and DNS.
Dez 04 09:35:07 rolfgang NetworkManager[408]: <info> Writing DNS information to /usr/bin/resolvconf
Dez 04 09:35:07 rolfgang NetworkManager[408]: <info> Activation (wlp1s0) successful, device activated.
Dez 04 09:35:20 rolfgang NetworkManager[408]: <info> (wlp1s0): roamed from BSSID 1C:E6:C7:1D:27:8E (eduroam) to (none) ((none))
Dez 04 09:35:20 rolfgang NetworkManager[408]: <info> (wlp1s0): supplicant interface state: completed -> authenticating
Dez 04 09:35:21 rolfgang NetworkManager[408]: <info> (wlp1s0): supplicant interface state: authenticating -> disconnected
Dez 04 09:35:21 rolfgang NetworkManager[408]: <info> (wlp1s0): supplicant interface state: disconnected -> scanning
Dez 04 09:35:21 rolfgang NetworkManager[408]: <info> (wlp1s0): supplicant interface state: scanning -> authenticating
Dez 04 09:35:21 rolfgang NetworkManager[408]: <info> (wlp1s0): supplicant interface state: authenticating -> associating
Dez 04 09:35:21 rolfgang NetworkManager[408]: <info> (wlp1s0): supplicant interface state: associating -> associated
Dez 04 09:35:21 rolfgang NetworkManager[408]: <info> (wlp1s0): supplicant interface state: associated -> completed
Dez 04 09:35:21 rolfgang NetworkManager[408]: <info> (wlp1s0): roamed from BSSID (none) ((none)) to 1C:E6:C7:1D:27:8E (eduroam)

How can I proceed from here? Thank you in advance.

Last edited by Duxon (2015-06-02 18:10:36)

Offline

#2 2014-12-08 18:00:49

emanuelx
Member
From: Portugal
Registered: 2012-11-06
Posts: 30

Re: [SOLVED] WiFi: Connected to SSID eduroam, but no internet connection

if your wireless is atheros try this

sudo nano /etc/modprobe.d/ath9k.conf

and paste ctrl+shift+v

options ath9k nohwcrypt=1

save ctrl+o and exit ctrl+x

reboot

Offline

#3 2014-12-08 18:33:30

Head_on_a_Stick
Member
From: The Wirral
Registered: 2014-02-20
Posts: 8,263
Website

Re: [SOLVED] WiFi: Connected to SSID eduroam, but no internet connection

There are 3 links for eduroam in the ArchWiki and they all point to this:
https://wiki.archlinux.org/index.php/WP … se#connman

There is also this thread:
https://bbs.archlinux.org/viewtopic.php?id=182937

Hope this helps; I've never used eduroam so I can't help directly, sorry.


Para todos todo, para nosotros nada

Offline

#4 2014-12-10 10:56:01

Duxon
Member
Registered: 2010-12-01
Posts: 41

Re: [SOLVED] WiFi: Connected to SSID eduroam, but no internet connection

Thanks for your answers.

emanuelx wrote:

if your wireless is atheros try this

I'm not using Atheros, instead an Intel Chipset with the iwlwifi module.

Connman is new to me, I am going to give it a try. Wicd didn't solve this issue, so I thought it's related to my firmware or kernel instead of the networking manager.

Offline

#5 2014-12-10 12:10:40

emanuelx
Member
From: Portugal
Registered: 2012-11-06
Posts: 30

Re: [SOLVED] WiFi: Connected to SSID eduroam, but no internet connection

Duxon wrote:

Thanks for your answers.

emanuelx wrote:

if your wireless is atheros try this

I'm not using Atheros, instead an Intel Chipset with the iwlwifi module.

Connman is new to me, I am going to give it a try. Wicd didn't solve this issue, so I thought it's related to my firmware or kernel instead of the networking manager.

i tried ubuntu 14.10, and wireless is a shit, i put arch linux with cinnamon and wireless is fine now.

i think is must be a problem of network manager.

Offline

#6 2015-04-20 09:04:08

Duxon
Member
Registered: 2010-12-01
Posts: 41

Re: [SOLVED] WiFi: Connected to SSID eduroam, but no internet connection

Connmann and wicd didn't help. Actually I want to use NetworkManager either way, so I've tried out a live session with Antergos (an Arch Linux derivate):

Eduroam works just fine there. Now what can I do to reset NetworkManager completely? I feel like resetting it from the GUI isnt sufficient. Reinstalling also did not help.
I would try reinstalling my whole system, so you see the amount of my resignation.
Any help is appreciated.

Offline

#7 2015-04-21 12:08:53

TheFiddler
Member
Registered: 2009-02-09
Posts: 38

Re: [SOLVED] WiFi: Connected to SSID eduroam, but no internet connection

For what it's worth, I am encountering the exact same issue on a Broadcom BCM4313 802.11bgn ada

Every network I have tried works correctly; eduroam works for a few seconds or minutes, then it simply stops responding (the adapter remains connected, but no packets can be sent or received.)

This happens with both linux 3.19 and 4.0.


The Open Toolkit: OpenGL, OpenAL, OpenCL and Vulkan for Mono/.Net.

Offline

#8 2015-05-02 08:19:11

Duxon
Member
Registered: 2010-12-01
Posts: 41

Re: [SOLVED] WiFi: Connected to SSID eduroam, but no internet connection

Well, may it have something to do with dhcpd? It seems it fails to start, but apparently that's no problem on different WiFis...

Mai 02 10:13:07 rolfgang chromium.desktop[4693]: [4693:4736:0502/101307:ERROR:connection_factory_impl.cc(366)] Failed to connect to MCS endpoint with error -21
...skipping...
Mai 02 10:11:57 rolfgang dhcpd[28879]: 
Mai 02 10:11:57 rolfgang dhcpd[28879]: No subnet declaration for wlp1s0 (10.100.43.64).
Mai 02 10:11:57 rolfgang dhcpd[28879]: ** Ignoring requests on wlp1s0.  If this is not what
Mai 02 10:11:57 rolfgang dhcpd[28879]: you want, please write a subnet declaration
Mai 02 10:11:57 rolfgang dhcpd[28879]: in your dhcpd.conf file for the network segment
Mai 02 10:11:57 rolfgang dhcpd[28879]: to which interface wlp1s0 is attached. **
Mai 02 10:11:57 rolfgang dhcpd[28879]: 
Mai 02 10:11:57 rolfgang dhcpd[28879]: 
Mai 02 10:11:57 rolfgang dhcpd[28879]: Not configured to listen on any interfaces!
Mai 02 10:11:57 rolfgang dhcpd[28879]: 
Mai 02 10:11:57 rolfgang dhcpd[28879]: If you think you have received this message due to a bug rather
Mai 02 10:11:57 rolfgang dhcpd[28879]: than a configuration issue please read the section on submitting
Mai 02 10:11:57 rolfgang dhcpd[28879]: bugs on either our web page at www.isc.org or in the README file
Mai 02 10:11:57 rolfgang dhcpd[28879]: before submitting a bug.  These pages explain the proper
Mai 02 10:11:57 rolfgang dhcpd[28879]: process and the information we find helpful for debugging..
Mai 02 10:11:57 rolfgang dhcpd[28879]: 
Mai 02 10:11:57 rolfgang dhcpd[28879]: exiting.
Mai 02 10:11:57 rolfgang systemd[1]: dhcpd4.service: control process exited, code=exited status=1
Mai 02 10:11:57 rolfgang systemd[1]: Failed to start IPv4 DHCP server.
Mai 02 10:11:57 rolfgang systemd[1]: Unit dhcpd4.service entered failed state.
Mai 02 10:11:57 rolfgang systemd[1]: dhcpd4.service failed.
Mai 02 10:11:57 rolfgang polkitd[703]: Unregistered Authentication Agent for unix-process:28874:341184 (system bus name :1.94, object path /org/freedesktop/PolicyKit1/Authentica
Mai 02 10:12:11 rolfgang chromium.desktop[4693]: libpng warning: iCCP: known incorrect sRGB profile
Mai 02 10:13:04 rolfgang kernel: wlp1s0: authenticate with c4:7d:4f:57:8b:8e
Mai 02 10:13:04 rolfgang kernel: wlp1s0: send auth to c4:7d:4f:57:8b:8e (try 1/3)
Mai 02 10:13:04 rolfgang systemd-networkd[534]: wlp1s0          : lost carrier
Mai 02 10:13:04 rolfgang systemd-networkd[534]: wlp1s0          : DHCP lease lost

Offline

#9 2015-05-02 08:25:11

joehillen
Member
Registered: 2015-01-08
Posts: 20

Re: [SOLVED] WiFi: Connected to SSID eduroam, but no internet connection

Duxon wrote:

Well, may it have something to do with dhcpd?

Maybe, try switching to dhclient as suggested here.

Offline

#10 2015-05-02 11:35:21

frederik
Member
Registered: 2014-01-05
Posts: 8

Re: [SOLVED] WiFi: Connected to SSID eduroam, but no internet connection

Just in case someone finds this by having the same problem with netctl:

NetworkManager hast problems with dhcpcd connecting to eduroam (802.1x) networks.
Netctl has problems with dhclient connecting to those networks.

Switching helps in both cases.

Cheers,

Offline

#11 2015-05-04 14:40:29

Duxon
Member
Registered: 2010-12-01
Posts: 41

Re: [SOLVED] WiFi: Connected to SSID eduroam, but no internet connection

Thanks, that definitely is the right path.

I've now found out that my connection immediately works after typing

 # dhclient wlp1s0
RTNETLINK answers: File exists

How can I avoid typing this in everytime I've connected to eduroam?
What I've tried so far didn't help (according to our wiki and forums):
- uninstalling dhcpcd
- editing /etc/NetworkManager/NetworkManager.conf
-- adding dhcp=internal
-- adding dhcp=dhclient
- removing /var/lib/dhclient/dhclient.leases

Also, it seems I sometimes have to repeat executing sudo dhclient wlp1s0 in order to stay connected.
I'm not familiar enough with this whole process of dhcp. Why does it behave so strangely and why is my fix a dirty workaround?

Greetings

Offline

#12 2015-06-02 18:09:55

Duxon
Member
Registered: 2010-12-01
Posts: 41

Re: [SOLVED] WiFi: Connected to SSID eduroam, but no internet connection

Wow! This issue annoyed the hell out of me for about 2 years.
I think it is finally fixed:

Simply add net.ifnames=0 to your kernel lines at boot. This brings back the old names like wlan0 for wlp1s0....

I guess I will never know what's the actual cause of this, but I have to admit, it was some hard two years I had to endure with Arch Linux. Thanks to the few people who tried to help.

Offline

Board footer

Powered by FluxBB