I'm afraid my dns/dhcp server rpi is still running jessie. I'm not sure where my experimental rpiZW hotspot is but it's certainly pre bookworm so will be similar. I don't know about network manager other than I did have recourse to 'nmcli' on some box for some reason in the past. It's possible "man nmcli" might yield something you can google. The old dhcpd (isc-dhcp-server) typically used a file called "dhcpd.conf" so perhaps a google using these components: "nmcli isc-dhcp-server dhcpd.conf" might hit a thread where someone had to do this. Don't limit yourself to rpi on that either - it's generic linux, aka debian.
You need to clarify as there may not be a problem. eg: my rpiZW ap hotspot hands out ip addresses on its wireless interface and chucks everything through its ethernet. My intranet is 192.168.1.0/26 and the rpiZW is on 192.168.2.0/?? (where ?? = I forget) and uses network address translation (nat) to move stuff between 192.168.1 <-> 192.168.2 subnets. This nat (implemented with iptables) is pretty similar to how I have my rpi firewall configured. In this scenario I'd expect the laptop to be plugged into the rpiZW ethernet but as you say both it and the phone work without problems then perhaps everything is wireless? You could, for instance, ignore the ethernet and add a second wireless dongle, one of which would have a fixed ip address.
It's also possible to have multiple dhcp servers, or in my case, split an old dhcpd into two halves. eg: 192.168.1.0/26 yields 64 (62 usable) ip addresses to be handed out but I have "reserved" the first half as "static". This really only means I have entries in "dhcpd.conf" which do exactly what you desire. This kind of thing....the above being my internal mail server. When it fires up, it asks dhcpd for an address and because it's mac address matches, it is given "sdvmf64mail.swampdog" which requires a dns lookup and I have such set as a permanent record in dns (aka 'named', bind9) - fixed-address" can be a simple ip address btw.
That's complicated. Now I can say it again less complex. The dhcp server only hands out the top 32 addresses but dns knows about all 64. It saves me having to mess with servers, setting fixed ip. I just add their mac address in an entry like the above. The reality tends to mean wired clients are sat in the lower 32 ip range and wireless clients in the upper 32 range.
My isp device has been set to pure cable modem (disabling its dns/dhcp and wireless). I use my own wireless access points and they have dns/dhcp disabled as well but they point to my rpi dns/dhcp . Thus everything "just works" (to use a bethesda-ism). Major headache to set up. I'm in no hurry to change it.
You need to draw a network/communication diagram. One as it is now. One as you want it in the field. Note if everything is on the same subnet it will all be able access everything else. There may be a way to fudge things.
I haven't even got started on ssh and tunnelling.
I posted a lot because it'll likely be a few days before I can post again.
You need to clarify as there may not be a problem. eg: my rpiZW ap hotspot hands out ip addresses on its wireless interface and chucks everything through its ethernet. My intranet is 192.168.1.0/26 and the rpiZW is on 192.168.2.0/?? (where ?? = I forget) and uses network address translation (nat) to move stuff between 192.168.1 <-> 192.168.2 subnets. This nat (implemented with iptables) is pretty similar to how I have my rpi firewall configured. In this scenario I'd expect the laptop to be plugged into the rpiZW ethernet but as you say both it and the phone work without problems then perhaps everything is wireless? You could, for instance, ignore the ethernet and add a second wireless dongle, one of which would have a fixed ip address.
It's also possible to have multiple dhcp servers, or in my case, split an old dhcpd into two halves. eg: 192.168.1.0/26 yields 64 (62 usable) ip addresses to be handed out but I have "reserved" the first half as "static". This really only means I have entries in "dhcpd.conf" which do exactly what you desire. This kind of thing..
Code:
host sdvmf64mail { hardware ethernet 52:54:00:02:1f:ba; fixed-address sdvmf64mail.swampdog; }That's complicated. Now I can say it again less complex. The dhcp server only hands out the top 32 addresses but dns knows about all 64. It saves me having to mess with servers, setting fixed ip. I just add their mac address in an entry like the above. The reality tends to mean wired clients are sat in the lower 32 ip range and wireless clients in the upper 32 range.
My isp device has been set to pure cable modem (disabling its dns/dhcp and wireless). I use my own wireless access points and they have dns/dhcp disabled as well but they point to my rpi dns/dhcp . Thus everything "just works" (to use a bethesda-ism). Major headache to set up. I'm in no hurry to change it.
You need to draw a network/communication diagram. One as it is now. One as you want it in the field. Note if everything is on the same subnet it will all be able access everything else. There may be a way to fudge things.
I haven't even got started on ssh and tunnelling.
I posted a lot because it'll likely be a few days before I can post again.
Statistics: Posted by swampdog — Sat Aug 23, 2025 5:23 pm