Arch Linux

TheSaint

Member

From: my computer

Registered: 2007-08-19

Posts: 1,536

dhcpd != dnsmasq :o

Hello forum,

I'm working to connect my SBC via SSH. So I use the NIC for both side. To get the SBC access I must run a DHCP server from my laptop. Since I decided to remove dnsmasq and use dhcp server I found a difference. I swap the server because I'm using systemd-resolved so I don't use a DNS caching anymore.
I found a strange behavior by using dhcp. When I need to issue a sudo command to the SSH shell, then the process freeze. Which is not same using the dnsmasq's DHCP server.
I can't figure whether that is a flaw or a feature, which for the latter might have some configuration to fix. This is dhcpd.conf

$ cat /etc/dhcpd.conf

option domain-name-servers 67.215.92.210, 8.8.8.8, 8.8.4.4;
option subnet-mask 255.255.255.0;

default-lease-time 600;
max-lease-time 7200;

authoritative;
subnet 192.168.2.0 netmask 255.255.255.0 {
   range 192.168.2.2 192.168.2.9;
   option domain-name "home";
   option routers 192.168.2.1;
}

This is dnsmasq.conf

$ cat /etc/dnsmasq.conf
port=0
interface=enp4s0
interface=wlp3s0
bind-interfaces
dhcp-range=192.168.2.4,192.168.2.20,2h

Both connection work fine, just dhcp will disconnect upon a sudo command through the SSH.

---

do it good first, it will be faster than do it twice the saint