Some more information about my laptop configuration.
When I have the laptop connected via ethernet to a LAN port of the router (no wifi):
$ip route
default via 158.110.96.1 dev eth0 proto static
158.110.96.0/24 dev eth0 proto kernel scope link src 158.110.96.145 metric 1
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.42.1
$ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
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
valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST<BROADCAST,MULTICAST,UP>UP,LOWER_UP> mtu 1500 qdisc mq state DOWNUP group default qlen 1000
link/ether 1c:75:08:48:59:95 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 5c:ac:4c:3c:5d:b2 brd ff:ff:ff:ff:ff:ff
inet 192158.168110.096.111145/24 brd 192158.168110.096.255 scope global wlan0eth0
valid_lft forever preferred_lft forever
inet6 fe80::5eac1e75:4cff8ff:fe3cfe48:5db25995/64 scope link
valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether 5c:ac:4c:3c:5d:b2 brd ff:ff:ff:ff:ff:ff
4: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 56:84:7a:fe:97:99 brd ff:ff:ff:ff:ff:ff
inet 172.17.42.1/16 scope global docker0
valid_lft forever preferred_lft forever
Trying to access 192.168.1.1
triggers the captive portal login, but I cannot access the config page.
Here's the output when the ethernet cable is connected to the WAN of my router and my laptop is connected to the wifi network of the router (ideally I'd like to be able to access router settings from this configuration, without having to add cables to my router etc.):
$ip route
default via 192158.168110.096.1 dev wlan0 proto static
172158.17110.096.0/1624 dev docker0wlan0 proto kernel scope link src 172158.17110.4296.1119 metric 9
192172.16817.0.0/2416 dev wlan0docker0 proto kernel scope link src 192172.16817.042.111 metric 91
Here's the output for ip addr
and ip route
when the ethernet cable is connected to the WAN of my router and my laptop is connected to the wifi network of the router (ideally I'd like to be able to access router settings from this configuration, without having to add cables to my router etc.):
$ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
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
valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether 1c:75:08:48:59:95 brd ff:ff:ff:ff:ff:ff
inet6 fe80::1e75:8ff:fe48:5995/64 scope link
valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 5c:ac:4c:3c:5d:b2 brd ff:ff:ff:ff:ff:ff
inet 158.110.96.119/24 brd 158.110.96.255 scope global wlan0
valid_lft forever preferred_lft forever
inet6 fe80::5eac:4cff:fe3c:5db2/64 scope link
valid_lft forever preferred_lft forever
4: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 56:84:7a:fe:97:99 brd ff:ff:ff:ff:ff:ff
inet 172.17.42.1/16 scope global docker0
valid_lft forever preferred_lft forever
$ip route
default via 158.110.96.1 dev wlan0 proto static
158.110.96.0/24 dev wlan0 proto kernel scope link src 158.110.96.119 metric 9
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.42.1
Trying to access 192.168.1.1
triggers the captive portal login, but I cannot access the config page.
With my current configuration trying to connect the laptop via ethernet to the WAN of the router fails saying that IP configuration is missing.
Note that I only care about being able to access the internet and to access the router configuration page. I don't care about other things in the network configuration.