Hi James
Well I didn’t actually change anything following your steps above as the ethernet adaptor was already set for DHCP.
And firing it up again tonight the hotspot is still happily sharing internet access. It definitely was not doing that previously so unless Mint has some element of self-repair built in I don’t know what changed that.
Whilst I am happy that it is working I always want to know why something is so, and thus whether it will be replicated when we do another install.
ifconfig still shows the 10.42. IP range but not the 10.10.
user1@rachel:~$ ifconfig
enp0s25: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.38 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::2f99:3cb9:434:a830 prefixlen 64 scopeid 0x20
ether 68:f7:28:7a:34:2a txqueuelen 1000 (Ethernet)
RX packets 12863 bytes 13682288 (13.6 MB)
RX errors 4 dropped 0 overruns 0 frame 2
TX packets 3780 bytes 705196 (705.1 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 20 memory 0xf0600000-f0620000
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 1000 (Local Loopback)
RX packets 436 bytes 47904 (47.9 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 436 bytes 47904 (47.9 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlp3s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.42.0.1 netmask 255.255.255.0 broadcast 10.42.0.255
inet6 fe80::60ef:f222:4d9f:fc0 prefixlen 64 scopeid 0x20
inet6 fe80::5359:c2ec:621e:c9b prefixlen 64 scopeid 0x20
ether cc:3d:82:4e:e9:cc txqueuelen 1000 (Ethernet)
RX packets 775 bytes 173846 (173.8 KB)
RX errors 0 dropped 1 overruns 0 frame 0
TX packets 898 bytes 434938 (434.9 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
user1@rachel:~$
Just doing a bit more digging…
The x240 is allocating client addresses to all the devices on the hotspot in the 10.10.10.x range despite the RACHEL menu saying that it is connected to 10.42.0.1. (and showing LAN correctly as 192.168.1.38). Is there some kind of alias IP going on here?
Some info here: Link that does not seem to tie up with the IP range we are getting on DHCP.
" By default wifi hotspot get 10.42.0.1
IP address and the network is 10.42.0.0/24
. In the background NetworkManager
runs a DHCP
server through dnsmasq
which will provide IP address to all wifi users from 10.42.0..0/24
network."
Regards
Andrew