You are not logged in.
Pages: 1
I'm using the University Wi-Fi login to connect to the internet, but after login, it disconnects, and need to log in again. However, in my internet profile, it says that I was connected and not disconnected.
I don't have a problem in other distros and windows but in the Arch and my friend's laptop(he has Arch too) we have this problem.
I have a question is there any way to log in automatically?
Last edited by syhomadara (2024-10-16 17:45:32)
Offline
What are you login in to, is this a captive portal? How log after you log in does it "disconnect"? And how do you determine (i.e., operationally define) "disconnect" in this context? What are the outputs of the following commands when this happens? What network management software are you using?
ip a
ping -c 3 google.com
ping -c 3 8.8.8.8
Last edited by Trilby (2024-10-09 18:45:30)
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
Also post the output from
sudo dmesg -T
before, during, after, and post/name the timestamps for the various steps from your logon - so one can find the corresponding lines in dmesg log to your action.
Last edited by ua4000 (2024-10-09 19:11:40)
Offline
I'd rather look at the journal since it logs the userspace as well.
Offline
What are you login in to, is this a captive portal? How log after you log in does it "disconnect"? And how do you determine (i.e., operationally define) "disconnect" in this context? What are the outputs of the following commands when this happens? What network management software are you using?
ip a ping -c 3 google.com ping -c 3 8.8.8.8
It asks me to log in again(I can't access the internet or ping).
ping -c 3 www.google.com
PING www.google.com (216.239.38.120) 56(84) bytes of data.
64 bytes from any-in-2678.1e100.net (216.239.38.120): icmp_seq=1 ttl=105 time=118 ms
64 bytes from any-in-2678.1e100.net (216.239.38.120): icmp_seq=2 ttl=105 time=173 ms
64 bytes from any-in-2678.1e100.net (216.239.38.120): icmp_seq=3 ttl=105 time=135 ms
--- www.google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 117.855/141.735/172.698/22.942 ms
ping -c 3 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=106 time=114 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=106 time=114 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=106 time=140 ms
--- 8.8.8.8 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 113.522/122.397/139.584/12.154 ms
Offline
Also post the output from
sudo dmesg -T
before, during, after, and post/name the timestamps for the various steps from your logon - so one can find the corresponding lines in dmesg log to your action.
I thinks these messages relevants.
wlan0: authenticate with d0:21:f9:25:97:e3
[Sat Oct 12 20:09:58 2024] wlan0: send auth to d0:21:f9:25:97:e3 (try 1/3)
[Sat Oct 12 20:09:58 2024] wlan0: authenticated
[Sat Oct 12 20:09:58 2024] wlan0: associate with d0:21:f9:25:97:e3 (try 1/3)
[Sat Oct 12 20:09:58 2024] wlan0: RX AssocResp from d0:21:f9:25:97:e3 (capab=0x411 status=0 aid=14)
[Sat Oct 12 20:09:58 2024] wlan0: associated
[Sat Oct 12 20:09:59 2024] i915 0000:00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=3651 end=3652) time 218 us, min 1073, max 1079, scanline start 1067, end 1081
[Sat Oct 12 20:10:05 2024] i915 0000:00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=4016 end=4017) time 144 us, min 1073, max 1079, scanline start 1071, end 1081
[Sat Oct 12 20:10:09 2024] i915 0000:00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=4258 end=4259) time 204 us, min 1073, max 1079, scanline start 1072, end 1086
[Sat Oct 12 20:10:10 2024] i915 0000:00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=4270 end=4271) time 159 us, min 1073, max 1079, scanline start 1072, end 1082
[Sat Oct 12 20:10:10 2024] i915 0000:00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=4282 end=4283) time 206 us, min 1073, max 1079, scanline start 1072, end 1086
[Sat Oct 12 20:10:11 2024] i915 0000:00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=4356 end=4357) time 218 us, min 1073, max 1079, scanline start 1071, end 1085
[Sat Oct 12 20:10:13 2024] i915 0000:00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=4477 end=4478) time 204 us, min 1073, max 1079, scanline start 1072, end 1085
[Sat Oct 12 20:10:41 2024] warning: `ThreadPoolForeg' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211
[Sat Oct 12 20:10:47 2024] i915 0000:00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=6497 end=6498) time 262 us, min 1073, max 1079, scanline start 1068, end 1085
[Sat Oct 12 20:10:47 2024] i915 0000:00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=6509 end=6510) time 204 us, min 1073, max 1079, scanline start 1071, end 1085
[Sat Oct 12 20:10:57 2024] wlan0: deauthenticating from d0:21:f9:25:97:e3 by local choice (Reason: 3=DEAUTH_LEAVING)
[Sat Oct 12 20:10:58 2024] wlan0: authenticate with d0:21:f9:25:97:e3
[Sat Oct 12 20:10:58 2024] wlan0: send auth to d0:21:f9:25:97:e3 (try 1/3)
[Sat Oct 12 20:10:58 2024] wlan0: authenticated
[Sat Oct 12 20:10:58 2024] wlan0: associate with d0:21:f9:25:97:e3 (try 1/3)
[Sat Oct 12 20:10:58 2024] wlan0: RX AssocResp from d0:21:f9:25:97:e3 (capab=0x411 status=0 aid=14)
[Sat Oct 12 20:10:58 2024] wlan0: associated
[Sat Oct 12 20:11:05 2024] i915 0000:00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=7571 end=7572) time 318 us, min 1073, max 1079, scanline start 1061, end 1082
[Sat Oct 12 20:11:08 2024] i915 0000:00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=7799 end=7800) time 332 us, min 1073, max 1079, scanline start 1067, end 1087
[Sat Oct 12 20:11:09 2024] systemd-journald[331]: Time jumped backwards, rotating.
[Sat Oct 12 20:11:14 2024] i915 0000:00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=8153 end=8154) time 317 us, min 107
Offline
I'd rather look at the journal since it logs the userspace as well.
what should I do journalctl ?
Offline
What / where is the "It" that asks you to log in again? What are you loging in to? What about all the other questions I asked: I didn't post them for fun - the answers are important for us to be able to help you.
I gather you mean that when you try to open a web page you're redirected to some captive portal page - this would fit with the ping results. But is this what you mean?? Remember we don't see what you see, you need to describe the symptoms to us. You also didn't post the output from `ip a`, please add that.
Also please do not keep adding new posts when you were the last to post - use the "edit" button if you have more to add - or ideally, take some time to think through what you are posting first - as one example, rather than asking about how to get a journal, you could look at the pages in our wiki specifically on the journal and / or on troubleshooting that guide users on how to collect the relevant data. We are here to help - but those who make a clear effort to participate in the troubleshooting process will consistently get better results here.
Last edited by Trilby (2024-10-12 17:14:21)
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
What / where is the "It" that asks you to log in again? What are you loging in to? What about all the other questions I asked: I didn't post them for fun - the answers are important for us to be able to help you.
I gather you mean that when you try to open a web page you're redirected to some captive portal page - this would fit with the ping results. But is this what you mean?? Remember we don't see what you see, you need to describe the symptoms to us. You also didn't post the output from `ip a`, please add that.
Also please do not keep adding new posts when you were the last to post - use the "edit" button if you have more to add - or ideally, take some time to think through what you are posting first - as one example, rather than asking about how to get a journal, you could look at the pages in our wiki specifically on the journal and / or on troubleshooting that guide users on how to collect the relevant data. We are here to help - but those who make a clear effort to participate in the troubleshooting process will consistently get better results here.
ُThanks for your suggestion I will try to get used to the forum rules. About the new post, I think I should reply to all questions in separate posts thanks for the point that you said.
Exact things that happened:
I open the portal page and log in then it says you successfully log in, but after 30 sec or 1 minute it redirects me to the portal login page to log in again and I don't have any access to the internet. I realize that it keeps the previous login as a logged-in system in the system tracker. Sometimes I need to click disconnect bottom at the system tracker page because it forces us to log in with only 2 devices at the same time.
I have this issue at my previous University with a different system for login.
The portal page uses a specific port at that IP.
I don't know what should I add more to these details that I say sry about that.
These are the codes:
ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
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 noprefixroute
valid_lft forever preferred_lft forever
2: enp7s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
link/ether 08:97:98:b7:09:b6 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 9c:29:76:f7:77:5e brd ff:ff:ff:ff:ff:ff
inet 172.16.157.224/24 brd 172.16.157.255 scope global dynamic noprefixroute wlan0
valid_lft 3228sec preferred_lft 3228sec
inet 172.16.157.231/24 brd 172.16.157.255 scope global secondary dynamic noprefixroute wlan0
valid_lft 3234sec preferred_lft 2784sec
inet6 fe80::4f93:cb51:4e7c:5a32/64 scope link
valid_lft forever preferred_lft forever
inet6 fe80::e25d:ee8a:834f:d8e1/64 scope link noprefixroute
valid_lft forever preferred_lft forever
5: br-e504f8aeb196: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 02:42:d9:79:0e:c9 brd ff:ff:ff:ff:ff:ff
inet 172.18.0.1/16 brd 172.18.255.255 scope global br-e504f8aeb196
valid_lft forever preferred_lft forever
6: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 02:42:c6:7c:7f:2c brd ff:ff:ff:ff:ff:ff
inet 10.10.0.1/24 brd 10.10.0.255 scope global docker0
valid_lft forever preferred_lft forever
Network manager:
find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
dhcpcd.service | multi-user.target.wants
NetworkManager.service | multi-user.target.wants
NetworkManager-wait-online.service | network-online.target.wants
Offline
Disable and stop the dhcpcd.service
If that's not the cause:
I thinks these messages relevants.
what should I do journalctl ?
Please post your complete system journal for the boot:
sudo journalctl -b | curl -F 'file=@-' 0x0.st
Offline
If this is a university captive portal, those are typically used only for the "guest" networks. If you are a student or otherwise affiliated with the university, they likely have a different network (different SSID) without a captive portal (but perhaps eduroam which is also a pain to configure, but once you figure it out it is readily automated for reconnecting).
Otherwise there is no reliable way to automatically connect to captive portals, as every one is different. There have been some tools designed to be "general purpose" captive portal handlers - but every one I've seen was pretty much crap and written by someone who frequents one or two different captive portals and can confidently say "my tool works on every captive portal I use" which says nothing of it's general applicability.
Last edited by Trilby (2024-10-13 13:18:10)
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
Please post your complete system journal for the boot:
sudo journalctl -b | curl -F 'file=@-' 0x0.st
I disabled dhcpcd I'll check the problem after 12 hours because I need to wait for the system to kill my access.
before connecting(after boot)
sudo journalctl -b | curl -F 'file=@-' 0x0.st
curl: (52) Empty reply from server
after first login
sudo journalctl -b | curl -F 'file=@-' 0x0.st
http://0x0.st/X6vt.txt
after 1 min that I disconnected
sudo journalctl -b | curl -F 'file=@-' 0x0.st
curl: (52) Empty reply from server
perhaps eduroam which is also a pain to configure, but once you figure it out it is readily automated for reconnecting.
thanks for your advice and other explanations I'll try them.
I have to notice that my Uni is in Iran and there is no Iran on the list of countries in Eduroam website https://cat.eduroam.org/#
Last edited by syhomadara (2024-10-13 17:03:55)
Offline
Oct 13 20:08:24 hosein NetworkManager[684]: <info> [1728837504.9204] dhcp4 (wlan0): state changed new lease, address=172.16.157.66
Oct 13 20:08:29 hosein dhcpcd[692]: wlan0: leased 172.16.157.64 for 3600 seconds
You're currently obtaining two leases, I'd be less than surprised if that is the cause of your symptoms (there're no obvious issues w/ the carrier)
Fwwi, NM doesn't reach the connected_global state, if that doesn't change after fixing the dhcpcd situation, see https://wiki.archlinux.org/title/Networ … nnectivity and whether the checked URL is reachable from within the university network.
Offline
Oct 13 20:08:24 hosein NetworkManager[684]: <info> [1728837504.9204] dhcp4 (wlan0): state changed new lease, address=172.16.157.66 Oct 13 20:08:29 hosein dhcpcd[692]: wlan0: leased 172.16.157.64 for 3600 seconds
You're currently obtaining two leases, I'd be less than surprised if that is the cause of your symptoms (there're no obvious issues w/ the carrier)
Thank you all it worked after disabling dhcpcd.
Offline
Pages: 1