You are not logged in.

Pages: 1

#1 2017-10-16 20:41:30

whitesnow
Member
Registered: 2015-01-04
Posts: 52

[Solved] problem in hotel wifi network, systemd-resolve not working,

Hello,

I'm no network specialist, but here is what i have.

I'm in a Hotel now, with wifi, this works with the company laptop windows 7, with my android phone too. But archlinux does not.

It is an open wifi, then one has to log in either via facebook or register a password via e-mail.

The symptom was: the webbrowser only tells: server not found.

So I entered google and found this and that, but no solution.

Now, what I found is:

nslookup www.google.de
gives an answer, also for other servers

but systemd-resolve www.google.de
gives

www.google.de: resolve call failed: 'www.google.de'

now at one place, I read "write it into /etc/hosts".

Well this works, if I write:

172.217.16.163 www.google.de

into /etc/hosts, then systemd-resolve finds that record, and the webbrowser shows that page.

Only I hardly can do that for all the webservers.

Has anyone any idea regarding that?

Thanks in advance.

Till this moring at home I had wifi working with DHCP, just like here.
Well, the network manager is Wicd-gtk.

Last edited by whitesnow (2017-10-17 19:53:58)

Offline

#2 2017-10-16 20:43:25

Slithery
Administrator
From: Norfolk, UK
Registered: 2013-12-01
Posts: 5,776

Re: [Solved] problem in hotel wifi network, systemd-resolve not working,

Does trying to visit google.com in your browser bring up the login page?

No, it didn't "fix" anything. It just shifted the brokeness one space to the right. - jasonwryan
Closing -- for deletion; Banning -- for muppetry. - jasonwryan

aur - dotfiles

Offline

#3 2017-10-16 21:12:40

whitesnow
Member
Registered: 2015-01-04
Posts: 52

Re: [Solved] problem in hotel wifi network, systemd-resolve not working,

no, maybe I should revert / comment all my entries in /etc/hosts, but I could not log in before.

Well, now I have to restart the browser.

So, no it only shows: "Server not found Firefox can't find the server at www.google.com"

nslookup www.google.com
gives
172.217.16.164
systemd-resolve www.google.com
"www.google.com: resolve call failed: 'www.google.com' not found

What else did I find?

This router runs openwrt.
But this was up to now a one time event. That the connection to 10.1.0.1 showed the login page of openwrt, now it shows nothing again.

And than it starts reconnectiong to login.freefii.de, for a little time shows a logo, than again "Server not found".

Last edited by whitesnow (2017-10-17 05:23:48)

Offline

#4 2017-10-17 15:22:59

seth
Member
Registered: 2012-09-03
Posts: 50,957

Re: [Solved] problem in hotel wifi network, systemd-resolve not working,

cat /run/systemd/resolve/resolv.conf
cat /etc/resolv.conf
stat /etc/resolv.conf

Well, the network manager is Wicd-gtk.

Errrrr.... then why does "systemd-resolve" not simply complain "resolve call failed: Unit dbus-org.freedesktop.resolve1.service not found."?
Why are you trying it at all?

systemctl list-units| grep -iE '(net|wicd|dhcp|conn)'

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#5 2017-10-17 16:47:06

whitesnow
Member
Registered: 2015-01-04
Posts: 52

Re: [Solved] problem in hotel wifi network, systemd-resolve not working,

Thank you for your replay.

ws1% cat /run/systemd/resolve/resolv.conf 
# This file is managed by man:systemd-resolved(8). Do not edit.
#
# This is a dynamic resolv.conf file for connecting local clients directly to
# all known DNS servers.
#
# Third party programs must not access this file directly, but only through the
# symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a different way,
# replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.

nameserver 208.67.222.222
nameserver 208.67.220.220
search lan
ws1% cat /etc/resolv.conf
domain lan
search lan
nameserver 208.67.222.222
nameserver 208.67.220.220
ws1% stat /etc/resolv.conf
  File: /etc/resolv.conf
  Size: 74        	Blocks: 1          IO Block: 512    regular file
Device: 14h/20d	Inode: 127236      Links: 1
Access: (0644/-rw-r--r--)  Uid: (  195/systemd-resolve)   Gid: (  195/systemd-resolve)
Access: 2017-10-17 18:26:06.754502320 +0200
Modify: 2017-10-17 18:26:05.754502316 +0200
Change: 2017-10-17 18:26:05.764502316 +0200
 Birth: -
ws1% systemctl list-units | grep -iE '(net|wicd|dhcp|conn)'
  sys-devices-pci0000:00-0000:00:19.0-net-enp0s25.device                                                                loaded active plugged   82579LM Gigabit Network Connection (Lewisville) (ThinkPad T520)                  
  sys-devices-pci0000:00-0000:00:1c.1-0000:03:00.0-net-wlp3s0.device                                                    loaded active plugged   Centrino Advanced-N 6205 [Taylor Peak] (Centrino Advanced-N 6205 (802.11a/b/g/n))
  sys-subsystem-net-devices-enp0s25.device                                                                              loaded active plugged   82579LM Gigabit Network Connection (Lewisville) (ThinkPad T520)                  
  sys-subsystem-net-devices-wlp3s0.device                                                                               loaded active plugged   Centrino Advanced-N 6205 [Taylor Peak] (Centrino Advanced-N 6205 (802.11a/b/g/n))
  sys-fs-fuse-connections.mount                                                                                         loaded active mounted   FUSE Control File System                                                         
  systemd-resolved.service                                                                                              loaded active running   Network Name Resolution                                                          
  systemd-timesyncd.service                                                                                             loaded active running   Network Time Synchronization                                                     
  vnstat.service                                                                                                        loaded active running   vnStat network traffic monitor                                                   
  wicd.service                                                                                                          loaded active running   Wicd a wireless and wired network manager for Linux                              
  network-online.target                                                                                                 loaded active active    Network is Online                                                                
  network.target                                                                                                        loaded active active    Network                                                                          
  nss-lookup.target                                                                                                     loaded active active    Host and Network Name Lookups

Why did I try systemd-resolve? That's quite simple I don't know how the nameresolution works in linux, and found that in the internet.

Offline

#6 2017-10-17 17:44:16

whitesnow
Member
Registered: 2015-01-04
Posts: 52

Re: [Solved] problem in hotel wifi network, systemd-resolve not working,

So thanks a lot for this hint.

sudo systemctl stop systemd-resolved.service

gave me a working network.

But still I don't get it.

How should I know that?
Should I disable that service permanently?

When I was at this Hotel before, at Apr 03 - April 05, the systemd-resolved.service at least left traces in the log, I can post that:

Apr 04 20:50:46 ws1 systemd-resolved[2951]: Positive Trust Anchors:
Apr 04 20:50:46 ws1 systemd-resolved[2951]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
Apr 04 20:50:46 ws1 systemd-resolved[2951]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-ad
Apr 04 20:50:46 ws1 systemd-resolved[2951]: Using system hostname 'ws1'.
Apr 04 20:50:46 ws1 systemd-resolved[2951]: Switching to system DNS server 192.168.1.1.
Apr 04 20:50:46 ws1 systemd[1]: Started Network Name Resolution.


Apr 04 20:53:13 ws1 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
Apr 04 20:53:13 ws1 dhclient[3965]: Internet Systems Consortium DHCP Client 4.3.5
Apr 04 20:53:13 ws1 dhclient[3965]: Copyright 2004-2016 Internet Systems Consortium.
Apr 04 20:53:13 ws1 dhclient[3965]: All rights reserved.
Apr 04 20:53:13 ws1 dhclient[3965]: For info, please visit https://www.isc.org/software/dhcp/
Apr 04 20:53:13 ws1 dhclient[3965]: 
Apr 04 20:53:13 ws1 dhclient[3965]: Listening on LPF/wlp3s0/a0:88:b4:b6:0f:74
Apr 04 20:53:13 ws1 dhclient[3965]: Sending on   LPF/wlp3s0/a0:88:b4:b6:0f:74
Apr 04 20:53:13 ws1 dhclient[3965]: Sending on   Socket/fallback
Apr 04 20:53:13 ws1 dhclient[3965]: DHCPDISCOVER on wlp3s0 to 255.255.255.255 port 67 interval 3
Apr 04 20:53:13 ws1 dhclient[3965]: DHCPREQUEST on wlp3s0 to 255.255.255.255 port 67
Apr 04 20:53:13 ws1 dhclient[3965]: DHCPOFFER from 10.1.0.1
Apr 04 20:53:13 ws1 dhclient[3965]: DHCPACK from 10.1.0.1
Apr 04 20:53:13 ws1 dhclient[3965]: bound to 10.1.0.17 -- renewal in 1682 seconds.
Apr 04 20:53:14 ws1 systemd-resolved[2951]: Switching to system DNS server 208.67.222.222.
Apr 04 20:53:14 ws1 systemd-resolved[2951]: Using degraded feature set (UDP) for DNS server 208.67.222.222.
Apr 04 20:53:16 ws1 systemd[1]: Time has been changed
Apr 04 20:53:16 ws1 systemd[3086]: Time has been changed
Apr 04 20:53:16 ws1 systemd-timesyncd[2871]: Synchronized to time server 108.61.190.139:123 (2.de.pool.ntp.org).


Apr 04 21:01:31 ws1 systemd-resolved[2951]: Switching to system DNS server 208.67.220.220.
Apr 04 21:01:31 ws1 systemd-resolved[2951]: Switching to system DNS server 208.67.222.222.
Apr 04 21:01:31 ws1 systemd-resolved[2951]: Using degraded feature set (UDP) for DNS server 208.67.220.220.
Apr 04 21:01:33 ws1 systemd-resolved[2951]: Switching to system DNS server 208.67.220.220.
Apr 04 21:01:33 ws1 systemd-resolved[2951]: Switching to system DNS server 208.67.222.222.
Apr 04 21:01:33 ws1 systemd-resolved[2951]: Switching to system DNS server 208.67.220.220.
Apr 04 21:01:35 ws1 systemd-resolved[2951]: Switching to system DNS server 208.67.222.222.
Apr 04 21:01:35 ws1 systemd-resolved[2951]: Switching to system DNS server 208.67.220.220.
Apr 04 21:01:36 ws1 systemd-resolved[2951]: Switching to system DNS server 208.67.222.222.
Apr 04 21:01:37 ws1 systemd-resolved[2951]: Switching to system DNS server 208.67.220.220.
Apr 04 21:01:39 ws1 systemd-resolved[2951]: Switching to system DNS server 208.67.222.222.
Apr 04 21:01:43 ws1 systemd-resolved[2951]: Switching to system DNS server 208.67.220.220.
Apr 04 21:01:45 ws1 systemd-resolved[2951]: Switching to system DNS server 208.67.222.222.


Apr 04 21:13:38 ws1 systemd-resolved[2951]: Switching to system DNS server 208.67.220.220.
Apr 04 21:13:38 ws1 systemd-resolved[2951]: Grace period over, resuming full feature set (UDP+EDNS0+DO+LARGE) for DNS server 208.67.220.220.
Apr 04 21:13:38 ws1 systemd-resolved[2951]: Using degraded feature set (UDP) for DNS server 208.67.220.220.


Apr 04 21:21:15 ws1 dhclient[3979]: DHCPREQUEST on wlp3s0 to 10.1.0.1 port 67
Apr 04 21:21:15 ws1 dhclient[3979]: DHCPACK from 10.1.0.1
Apr 04 21:21:15 ws1 dhclient[3979]: bound to 10.1.0.17 -- renewal in 1355 seconds.
Apr 04 21:21:31 ws1 systemd-resolved[2951]: Switching to system DNS server 208.67.222.222.
Apr 04 21:21:31 ws1 systemd-resolved[2951]: Grace period over, resuming full feature set (UDP+EDNS0+DO+LARGE) for DNS server 208.67.222.222.
Apr 04 21:21:31 ws1 systemd-resolved[2951]: Using degraded feature set (UDP) for DNS server 208.67.222.222.


Apr 04 21:54:17 ws1 systemd-resolved[2951]: Switching to system DNS server 208.67.220.220.
Apr 04 21:54:17 ws1 systemd-resolved[2951]: Grace period over, resuming full feature set (UDP+EDNS0+DO+LARGE) for DNS server 208.67.220.220.
Apr 04 21:54:17 ws1 systemd-resolved[2951]: Switching to system DNS server 208.67.222.222.
Apr 04 21:54:17 ws1 systemd-resolved[2951]: Using degraded feature set (UDP) for DNS server 208.67.220.220.
Apr 04 22:07:42 ws1 dhclient[3979]: DHCPREQUEST on wlp3s0 to 10.1.0.1 port 67
Apr 04 22:07:42 ws1 dhclient[3979]: DHCPACK from 10.1.0.1
Apr 04 22:07:42 ws1 dhclient[3979]: bound to 10.1.0.17 -- renewal in 1572 seconds.


Apr 04 22:24:17 ws1 systemd-resolved[2951]: Switching to system DNS server 208.67.220.220.

and to compare from yesterday and today

Oct 16 18:02:20 ws1.home-pc.example.com systemd-resolved[3320]: Positive Trust Anchors:
Oct 16 18:02:20 ws1.home-pc.example.com systemd-resolved[3320]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
Oct 16 18:02:20 ws1.home-pc.example.com systemd-resolved[3320]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Oct 16 18:02:20 ws1.home-pc.example.com systemd-resolved[3320]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-ad
Oct 16 18:02:20 ws1.home-pc.example.com systemd-resolved[3320]: Using system hostname 'ws1.home-pc.example.com'.
Oct 16 18:02:20 ws1.home-pc.example.com kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready


Oct 16 18:26:58 ws1.home-pc.example.com kernel: iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
Oct 16 18:26:58 ws1.home-pc.example.com kernel: iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
Oct 16 18:26:58 ws1.home-pc.example.com systemd-resolved[2404]: Positive Trust Anchors:
Oct 16 18:26:58 ws1.home-pc.example.com systemd-resolved[2404]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
Oct 16 18:26:58 ws1.home-pc.example.com systemd-resolved[2404]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Oct 16 18:26:58 ws1.home-pc.example.com systemd-resolved[2404]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-ad
Oct 16 18:26:58 ws1.home-pc.example.com systemd-resolved[2404]: Using system hostname 'ws1.home-pc.example.com'.
Oct 16 18:26:58 ws1.home-pc.example.com kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
Oct 16 18:26:58 ws1.home-pc.example.com systemd[1]: Started Network Name Resolution.
Oct 16 18:26:58 ws1.home-pc.example.com systemd[1]: Reached target Network is Online.


Oct 16 20:37:14 ws1.home-pc.example.com systemd-resolved[13587]: Positive Trust Anchors:
Oct 16 20:37:14 ws1.home-pc.example.com systemd-resolved[13587]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
Oct 16 20:37:14 ws1.home-pc.example.com systemd-resolved[13587]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Oct 16 20:37:14 ws1.home-pc.example.com systemd-resolved[13587]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-a
Oct 16 20:37:14 ws1.home-pc.example.com systemd-resolved[13587]: Using system hostname 'ws1.home-pc.example.com'.
Oct 16 20:37:14 ws1.home-pc.example.com systemd[1]: Started Network Name Resolution.
Oct 16 20:38:26 ws1.home-pc.example.com dhclient[8619]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 5
Oct 16 20:38:31 ws1.home-pc.example.com dhclient[8619]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 11
Oct 16 20:38:42 ws1.home-pc.example.com dhclient[8619]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 10
Oct 16 20:38:52 ws1.home-pc.example.com dhclient[8619]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 18
Oct 16 20:39:10 ws1.home-pc.example.com dhclient[8619]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 17
Oct 16 20:39:18 ws1.home-pc.example.com sudo[14494]:     root : TTY=pts/41 ; PWD=/home/cbr ; USER=root ; COMMAND=/usr/bin/ln -s /run/systemd/resolve/resolv.
Oct 16 20:39:18 ws1.home-pc.example.com sudo[14494]: pam_unix(sudo:session): session opened for user root by (uid=0)
Oct 16 20:39:18 ws1.home-pc.example.com sudo[14494]: pam_unix(sudo:session): session closed for user root
Oct 16 20:39:25 ws1.home-pc.example.com dhclient[32276]: DHCPREQUEST on wlp3s0 to 10.1.0.1 port 67
Oct 16 20:39:25 ws1.home-pc.example.com dhclient[32276]: DHCPACK from 10.1.0.1
Oct 16 20:39:25 ws1.home-pc.example.com dhclient[32276]: bound to 10.1.0.29 -- renewal in 1714 seconds.
Oct 16 20:39:27 ws1.home-pc.example.com dhclient[8619]: No DHCPOFFERS received.
Oct 16 20:39:27 ws1.home-pc.example.com dhclient[8619]: No working leases in persistent database - sleeping.
Oct 16 20:44:40 ws1.home-pc.example.com dhclient[8619]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 5
Oct 16 20:44:45 ws1.home-pc.example.com dhclient[8619]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 9
Oct 16 20:44:54 ws1.home-pc.example.com dhclient[8619]: DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 9


Oct 16 21:33:52 ws1.home-pc.example.com systemd[1]: Stopping Network Name Resolution...
Oct 16 21:33:52 ws1.home-pc.example.com systemd[1]: Stopped Network Name Resolution.
Oct 16 21:33:52 ws1.home-pc.example.com systemd[1]: Starting Network Name Resolution...
Oct 16 21:33:53 ws1.home-pc.example.com systemd-resolved[20046]: Positive Trust Anchors:
Oct 16 21:33:53 ws1.home-pc.example.com systemd-resolved[20046]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
Oct 16 21:33:53 ws1.home-pc.example.com systemd-resolved[20046]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Oct 16 21:33:53 ws1.home-pc.example.com systemd-resolved[20046]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-a
Oct 16 21:33:53 ws1.home-pc.example.com systemd-resolved[20046]: Using system hostname 'ws1.home-pc.example.com'.
Oct 16 21:33:53 ws1.home-pc.example.com systemd[1]: Started Network Name Resolution.


Oct 16 21:53:40 ws1.home-pc.example.com dhclient[14488]: DHCPREQUEST on wlp3s0 to 10.1.0.1 port 67
Oct 16 21:53:40 ws1.home-pc.example.com dhclient[14488]: DHCPACK from 10.1.0.1
Oct 16 21:53:40 ws1.home-pc.example.com dhclient[14488]: bound to 10.1.0.29 -- renewal in 1476 seconds.
Oct 16 22:00:54 ws1.home-pc.example.com dhclient[32276]: DHCPREQUEST on wlp3s0 to 10.1.0.1 port 67
Oct 16 22:00:54 ws1.home-pc.example.com dhclient[32276]: DHCPACK from 10.1.0.1
Oct 16 22:00:54 ws1.home-pc.example.com dhclient[32276]: bound to 10.1.0.29 -- renewal in 1780 seconds.

_____________________________________

Oct 17 19:01:58 ws1.home-pc.example.com sudo[19248]: pam_unix(sudo:session): session opened for user root by (uid=0)
Oct 17 19:01:58 ws1.home-pc.example.com systemd[1]: Stopping Network Name Resolution...
Oct 17 19:01:58 ws1.home-pc.example.com systemd[1]: Stopped Network Name Resolution.
Oct 17 19:01:58 ws1.home-pc.example.com sudo[19248]: pam_unix(sudo:session): session closed for user root
Oct 17 19:02:22 ws1.home-pc.example.com systemd-timesyncd[2054]: Synchronized to time server 46.165.221.137:123 (0.de.pool.ntp.org).
Oct 17 19:02:42 ws1.home-pc.example.com dhclient[19634]: Killed old client process
Oct 17 19:02:42 ws1.home-pc.example.com wicd[2098]: Killed old client process
Oct 17 19:02:43 ws1.home-pc.example.com dhclient[19634]: Internet Systems Consortium DHCP Client 4.3.6
Oct 17 19:02:43 ws1.home-pc.example.com dhclient[19634]: Copyright 2004-2017 Internet Systems Consortium.
Oct 17 19:02:43 ws1.home-pc.example.com wicd[2098]: Internet Systems Consortium DHCP Client 4.3.6
Oct 17 19:02:43 ws1.home-pc.example.com wicd[2098]: Copyright 2004-2017 Internet Systems Consortium.
Oct 17 19:02:43 ws1.home-pc.example.com wicd[2098]: All rights reserved.
Oct 17 19:02:43 ws1.home-pc.example.com wicd[2098]: For info, please visit https://www.isc.org/software/dhcp/
Oct 17 19:02:43 ws1.home-pc.example.com dhclient[19634]: All rights reserved.
Oct 17 19:02:43 ws1.home-pc.example.com dhclient[19634]: For info, please visit https://www.isc.org/software/dhcp/
Oct 17 19:02:43 ws1.home-pc.example.com dhclient[19634]: 
Oct 17 19:02:43 ws1.home-pc.example.com dhclient[19634]: Listening on LPF/wlp3s0/a0:88:b4:b6:0f:74
Oct 17 19:02:43 ws1.home-pc.example.com dhclient[19634]: Sending on   LPF/wlp3s0/a0:88:b4:b6:0f:74
Oct 17 19:02:43 ws1.home-pc.example.com wicd[2098]: Listening on LPF/wlp3s0/a0:88:b4:b6:0f:74
Oct 17 19:02:43 ws1.home-pc.example.com wicd[2098]: Sending on   LPF/wlp3s0/a0:88:b4:b6:0f:74
Oct 17 19:02:43 ws1.home-pc.example.com wicd[2098]: Sending on   Socket/fallback
Oct 17 19:02:43 ws1.home-pc.example.com dhclient[19634]: Sending on   Socket/fallback
Oct 17 19:02:43 ws1.home-pc.example.com dhclient[19634]: DHCPRELEASE on wlp3s0 to 10.1.0.1 port 67
Oct 17 19:02:43 ws1.home-pc.example.com wicd[2098]: DHCPRELEASE on wlp3s0 to 10.1.0.1 port 67
Oct 17 19:02:44 ws1.home-pc.example.com kernel: wlp3s0: deauthenticating from c6:6e:1f:41:0a:26 by local choice (Reason: 3=DEAUTH_LEAVING)
Oct 17 19:02:44 ws1.home-pc.example.com kernel: iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
Oct 17 19:02:44 ws1.home-pc.example.com kernel: iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
Oct 17 19:02:44 ws1.home-pc.example.com kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
Oct 17 19:02:44 ws1.home-pc.example.com wicd[2098]: Failed to connect to non-global ctrl_ifname: wlp3s0  error: No such file or directory
Oct 17 19:02:44 ws1.home-pc.example.com dhclient[19687]: Internet Systems Consortium DHCP Client 4.3.6
Oct 17 19:02:44 ws1.home-pc.example.com dhclient[19687]: Copyright 2004-2017 Internet Systems Consortium.
Oct 17 19:02:44 ws1.home-pc.example.com wicd[2098]: Internet Systems Consortium DHCP Client 4.3.6
Oct 17 19:02:44 ws1.home-pc.example.com wicd[2098]: Copyright 2004-2017 Internet Systems Consortium.
Oct 17 19:02:44 ws1.home-pc.example.com wicd[2098]: All rights reserved.
Oct 17 19:02:44 ws1.home-pc.example.com wicd[2098]: For info, please visit https://www.isc.org/software/dhcp/
Oct 17 19:02:44 ws1.home-pc.example.com dhclient[19687]: All rights reserved.
Oct 17 19:02:44 ws1.home-pc.example.com dhclient[19687]: For info, please visit https://www.isc.org/software/dhcp/
Oct 17 19:02:44 ws1.home-pc.example.com dhclient[19687]: 




Oct 17 19:02:45 ws1.home-pc.example.com wicd[2098]: Sending on   LPF/wlp3s0/a0:88:b4:b6:0f:74
Oct 17 19:02:45 ws1.home-pc.example.com wicd[2098]: Sending on   Socket/fallback
Oct 17 19:02:45 ws1.home-pc.example.com dhclient[19706]: Sending on   LPF/wlp3s0/a0:88:b4:b6:0f:74
Oct 17 19:02:45 ws1.home-pc.example.com dhclient[19706]: Sending on   Socket/fallback
Oct 17 19:02:45 ws1.home-pc.example.com dhclient[19706]: DHCPRELEASE on wlp3s0 to 10.1.0.1 port 67
Oct 17 19:02:45 ws1.home-pc.example.com dhclient[19706]: send_packet: Network is unreachable
Oct 17 19:02:45 ws1.home-pc.example.com wicd[2098]: DHCPRELEASE on wlp3s0 to 10.1.0.1 port 67
Oct 17 19:02:45 ws1.home-pc.example.com wicd[2098]: send_packet: Network is unreachable
Oct 17 19:02:45 ws1.home-pc.example.com wicd[2098]: send_packet: please consult README file regarding broadcast address.
Oct 17 19:02:45 ws1.home-pc.example.com wicd[2098]: dhclient.c:2739: Failed to send 300 byte long packet over fallback interface.
Oct 17 19:02:45 ws1.home-pc.example.com dhclient[19706]: send_packet: please consult README file regarding broadcast address.
Oct 17 19:02:45 ws1.home-pc.example.com dhclient[19706]: dhclient.c:2739: Failed to send 300 byte long packet over fallback interface.
Oct 17 19:02:45 ws1.home-pc.example.com kernel: iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
Oct 17 19:02:45 ws1.home-pc.example.com kernel: iwlwifi 0000:03:00.0: Radio type=0x1-0x2-0x0
Oct 17 19:02:45 ws1.home-pc.example.com kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
Oct 17 19:02:45 ws1.home-pc.example.com wicd[2098]: Failed to connect to non-global ctrl_ifname: wlp3s0  error: No such file or directory
Oct 17 19:02:45 ws1.home-pc.example.com wicd[2098]: Error for wireless request "Set Bit Rate" (8B20) :
Oct 17 19:02:45 ws1.home-pc.example.com wicd[2098]:     SET failed on device %s ; No such device.
Oct 17 19:02:47 ws1.home-pc.example.com dhclient[19724]: Internet Systems Consortium DHCP Client 4.3.6
Oct 17 19:02:47 ws1.home-pc.example.com dhclient[19724]: Copyright 2004-2017 Internet Systems Consortium.
Oct 17 19:02:47 ws1.home-pc.example.com dhclient[19724]: All rights reserved.
Oct 17 19:02:47 ws1.home-pc.example.com dhclient[19724]: For info, please visit https://www.isc.org/software/dhcp/
Oct 17 19:02:47 ws1.home-pc.example.com dhclient[19724]: 
Oct 17 19:02:47 ws1.home-pc.example.com dhclient[19724]: Listening on LPF/wlp3s0/a0:88:b4:b6:0f:74
Oct 17 19:02:47 ws1.home-pc.example.com dhclient[19724]: Sending on   LPF/wlp3s0/a0:88:b4:b6:0f:74
Oct 17 19:02:47 ws1.home-pc.example.com dhclient[19724]: Sending on   Socket/fallback
Oct 17 19:02:47 ws1.home-pc.example.com dhclient[19724]: DHCPDISCOVER on wlp3s0 to 255.255.255.255 port 67 interval 5
Oct 17 19:02:47 ws1.home-pc.example.com kernel: wlp3s0: authenticate with c4:6e:1f:40:f9:54
Oct 17 19:02:47 ws1.home-pc.example.com kernel: wlp3s0: send auth to c4:6e:1f:40:f9:54 (try 1/3)
Oct 17 19:02:47 ws1.home-pc.example.com kernel: wlp3s0: authenticated
Oct 17 19:02:47 ws1.home-pc.example.com kernel: wlp3s0: associate with c4:6e:1f:40:f9:54 (try 1/3)
Oct 17 19:02:47 ws1.home-pc.example.com kernel: wlp3s0: RX AssocResp from c4:6e:1f:40:f9:54 (capab=0x421 status=0 aid=4)
Oct 17 19:02:47 ws1.home-pc.example.com kernel: wlp3s0: associated
Oct 17 19:02:47 ws1.home-pc.example.com kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
Oct 17 19:02:52 ws1.home-pc.example.com dhclient[19724]: DHCPDISCOVER on wlp3s0 to 255.255.255.255 port 67 interval 8
Oct 17 19:02:52 ws1.home-pc.example.com dhclient[19724]: DHCPREQUEST on wlp3s0 to 255.255.255.255 port 67
Oct 17 19:02:52 ws1.home-pc.example.com dhclient[19724]: DHCPOFFER from 10.1.0.1
Oct 17 19:02:52 ws1.home-pc.example.com dhclient[19724]: DHCPACK from 10.1.0.1
Oct 17 19:02:52 ws1.home-pc.example.com dhclient[19724]: bound to 10.1.0.29 -- renewal in 1697 seconds.

I don't know what to look for.

Offline

#7 2017-10-17 18:53:50

seth
Member
Registered: 2012-09-03
Posts: 50,957

Re: [Solved] problem in hotel wifi network, systemd-resolve not working,

On a formal note, please rather edit your posts as long as nobody has replied.

On topic:
systemd-resolved is part of systemd-networkd. If you don't use that to manage your network, it will *only* break things (because on top of conflicts, it also works fundamentally different than any other unix network managing...)
So yes, disable it permanently.

I cannot say why your network failed before, but if you run in trouble again, safely return with the updated logs. Everything that has systemd-resolved and anything but systemd-networkd in it will expectably cause trouble.
(And inb4: I'd personally not recommend to change to systemd-networkd)

How should I know that?

Arch has a terrific wiki and a forum filled with nerds. Those are basically the reasons to use archlinux itfp tongue

Back to serious:
The network section of the wiki stresses to only use one network managing servive at a time and the services themselves are also well explained.
Please get used to look there before looking at random google results.

=> https://wiki.archlinux.org/index.php/Network

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#8 2017-10-17 19:16:22

whitesnow
Member
Registered: 2015-01-04
Posts: 52

Re: [Solved] problem in hotel wifi network, systemd-resolve not working,

Well, thank again, thanks a lot, and sorry for the trouble, I probably did read:


https://wiki.archlinux.org/index.php/wicd

wiki - wicd  wrote:

Disable any existing network management services, including netctl, netcfg, dhcpcd, and networkmanager. Refer to Systemd#Using units.
Note: You might need to stop and disable the network daemon instead of netctl, which is a current replacement for network service. If unsure, try disabling both.

As it did not mention systemd-networkd, and I don't remember installing that network manger, so I probably did not know about that.

Offline

Pages: 1

Board footer

Powered by FluxBB