[Solved] Host is not reachable

syhomadara · 2024-09-23 16:30:37

I was trying to connect the login page of the University wifi but I can't access the login page through my laptop. I can access it on my phone but not here.
I checked my IP and DNS and everything is okay.

ping command

PING internet.ut.ac.ir (172.17.49.17) 56(84) bytes of data.
From  (172.17.0.1) icmp_seq=1 Destination Host Unreachable
ping: sendmsg: No route to host
From (172.17.0.1) icmp_seq=2 Destination Host Unreachable
From (172.17.0.1) icmp_seq=3 Destination Host Unreachable
^C
--- internet.ut.ac.ir ping statistics ---
6 packets transmitted, 0 received, +3 errors, 100% packet loss, time 5075ms
pipe 3

Last edited by syhomadara (2024-09-27 16:20:08)

cryptearth · 2024-09-23 16:47:57

https://en.wikipedia.org/wiki/Captive_portal
had the same issue with opensuse when on some public wifi - while anything cool on windows and my android phone linux doesn't like these portals at all

Lone_Wolf · 2024-09-23 19:27:46

ICMP tends to be blocked completely on networks as there are some possibilities to use icmp to perform on attack.
(Blocking everything ICMP related is simpler then only blocking the vulnerable parts.)

Often the login page on such portals can be reached by using http://w.x.y.z or https://w.x.y.z in a browser to connect directly with the router login page.

Please post the outputs of

$ ip a
$ ip route

syhomadara · 2024-09-25 20:04:27

Lone_Wolf wrote:

Often the login page on such portals can be reached by using http://w.x.y.z or https://w.x.y.z in a browser to connect directly with the router login page.

Thanks. I tried with Chrome and Firefox but I got the same error(can not access)

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 ... 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.30.23.211/23 brd 172.30.23.255 scope global dynamic noprefixroute wlan0
       valid_lft 10392sec preferred_lft 10392sec
    inet 172.30.23.43/23 brd 172.30.23.255 scope global secondary dynamic noprefixroute wlan0
       valid_lft 10398sec preferred_lft 9048sec
    inet6 .../64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
4: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 02:42:66:de:f9:e4 brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever
15: enp0s20f0u2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000
    link/ether ... brd ff:ff:ff:ff:ff:ff
    inet 192.168.157.34/24 brd 192.168.157.255 scope global dynamic noprefixroute enp0s20f0u2
       valid_lft 2698sec preferred_lft 2698sec
    inet 192.168.157.35/24 brd 192.168.157.255 scope global secondary dynamic noprefixroute enp0s20f0u2
       valid_lft 2702sec preferred_lft 2252sec
    inet6 .../64 scope link 
       valid_lft forever preferred_lft forever
    inet6 .../64 scope link noprefixroute 
       valid_lft forever preferred_lft forever

ip route
default via 192.168.157.131 dev enp0s20f0u2 proto dhcp src 192.168.157.34 metric 100 
default via 192.168.157.131 dev enp0s20f0u2 proto dhcp src 192.168.157.35 metric 1015 
default via 172.30.22.1 dev wlan0 proto dhcp src 172.30.23.43 metric 3003 
default via 172.30.22.1 dev wlan0 proto dhcp src 172.30.23.211 metric 20600 
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
172.30.22.0/23 dev wlan0 proto kernel scope link src 172.30.23.211 metric 600 
172.30.22.0/23 dev wlan0 proto dhcp scope link src 172.30.23.43 metric 3003 
192.168.157.0/24 dev enp0s20f0u2 proto kernel scope link src 192.168.157.34 metric 100 
192.168.157.0/24 dev enp0s20f0u2 proto dhcp scope link src 192.168.157.35 metric 1015

mithrial · 2024-09-25 20:59:29

Disable docker. They are using the same IP range.

cryptearth · 2024-09-25 21:43:17

it's not conflicting ranges - as there aren't any - but rather the multiple routes and thier metrics:
the default route via 192.168.x has a lower metric than the wifi 172.30.x and hence is preferred - which ends up nowhere
I don't know if disable docker will clean up those routes - if not clear them manual
best case you end up with only one default route remaining

seth · 2024-09-25 21:59:12

Please also post the output of

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

mithrial · 2024-09-26 12:08:38

The target IP range (172.17.49.17) is in the docker range (172.17.x.x). You can see in the ping that the docker host (172.17.0.1) tells you that the destination is not reachable.

Just try stopping docker and test again.

syhomadara · 2024-09-26 15:49:53

seth wrote:

Please also post the output of

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

bluetooth.service                        | bluetooth.target.wants
containerd.service                       | multi-user.target.wants
cronie.service                           | multi-user.target.wants
dbus-org.bluez.service                   | system
dbus-org.freedesktop.nm-dispatcher.service | system
dbus-org.freedesktop.timesync1.service   | system
dhcpcd.service                           | multi-user.target.wants
display-manager.service                  | system
docker.service                           | multi-user.target.wants
fstrim.timer                             | timers.target.wants
gcr-ssh-agent.socket                     | sockets.target.wants
getty@tty1.service                       | getty.target.wants
gnome-keyring-daemon.socket              | sockets.target.wants
lm_sensors.service                       | multi-user.target.wants
NetworkManager.service                   | multi-user.target.wants
NetworkManager-wait-online.service       | network-online.target.wants
nginx.service                            | multi-user.target.wants
p11-kit-server.socket                    | sockets.target.wants
pipewire-pulse.socket                    | sockets.target.wants
pipewire-session-manager.service         | user
pipewire.socket                          | sockets.target.wants
remote-fs.target                         | multi-user.target.wants
sshd.service                             | multi-user.target.wants
systemd-timesyncd.service                | sysinit.target.wants
systemd-userdbd.socket                   | sockets.target.wants
tlp.service                              | multi-user.target.wants
vboxservice.service                      | multi-user.target.wants
wireplumber.service                      | pipewire.service.wants
xdg-user-dirs-update.service             | default.target.wants

syhomadara · 2024-09-26 15:58:51

mithrial wrote:

The target IP range (172.17.49.17) is in the docker range (172.17.x.x). You can see in the ping that the docker host (172.17.0.1) tells you that the destination is not reachable.
Just try stopping docker and test again.

I did that and it worked but is there anything to not change the docker route?

Last edited by syhomadara (2024-09-26 16:17:43)

V1del · 2024-09-26 16:18:19

Disable and stop dhcpcd it will conflict with NetworkManager

seth · 2024-09-26 20:06:06

I did that and it worked but is there anything to not change the docker route?

https://wiki.archlinux.org/title/Docker … network%22

syhomadara · 2024-09-27 16:19:43

thanks, a lot.

syhomadara · 2024-10-12 16:43:01

thx

Last edited by syhomadara (2024-10-12 16:44:20)

Arch Linux

#1 2024-09-23 16:30:37

[Solved] Host is not reachable

#2 2024-09-23 16:47:57

Re: [Solved] Host is not reachable

#3 2024-09-23 19:27:46

Re: [Solved] Host is not reachable

#4 2024-09-25 20:04:27

Re: [Solved] Host is not reachable

#5 2024-09-25 20:59:29

Re: [Solved] Host is not reachable

#6 2024-09-25 21:43:17

Re: [Solved] Host is not reachable

#7 2024-09-25 21:59:12

Re: [Solved] Host is not reachable

#8 2024-09-26 12:08:38

Re: [Solved] Host is not reachable

#9 2024-09-26 15:49:53

Re: [Solved] Host is not reachable

#10 2024-09-26 15:58:51

Re: [Solved] Host is not reachable

#11 2024-09-26 16:18:19

Re: [Solved] Host is not reachable

#12 2024-09-26 20:06:06

Re: [Solved] Host is not reachable

#13 2024-09-27 16:19:43

Re: [Solved] Host is not reachable

#14 2024-10-12 16:43:01

Re: [Solved] Host is not reachable

Board footer