Debian 9 WPA_Supplicant Dhclient No Gateway

metallica1973 · 10-15-2019, 03:08 PM

Its been a while since I have posted anything in this forum so hello. Long story short, I have a Debian distro in which I decided to not network-manager to control my wireless nics but rather /etc/network/interfaces and wpa_supplicant.conf. Everything works fine using:

Code:

apt-get remove network-manager
...
...
cat /etc/network/interfaces

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

allow-hotplug wlan0
iface wlan0 inet dhcp
wireless-essid "Mindyourdamnbusiness"
#key_mgmt="NONE"
	wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

cat /etc/wpa_supplicant/wpa_supplicant.conf

ctrl_interface=/run/wpa_supplicant
update_config=1

network={
	ssid="Mindyourdamnbusiness"
	#scan_ssid=1
	key_mgmt=NONE
	}

All works fine with connecting to the AP as it assigns an ip, subnet but oddly does not add the default GW. So what I have to do is manually add it as in:

Code:

sudo ip route add default via 192.168.1.1

So since Debian 9 went away with rc.local, I added a service using systemd:
https://wiki.debian.org/systemd/Services
pointing to my little shell script that simply adds the gateway. I dont understand why the dhclient is not doing this automatically this would prevent the need to do this entirely.

berndbausch · 10-15-2019, 06:19 PM

While my knowledge of DCHP and its client-side implementation is not that deep, here are a few steps that I would take (no particular order):

I don't know where dhclient writes its logs on Debian 9, but I would look there. The systemd journal, perhaps?
check if the DHCP server sends the gateway in the first place
run dhclient with the debug option -d to look into its decision-making process
check the lease file
verify dhclient.conf. Perhaps it doesn't request the router?
you are not the only one with this problem. Even though other cases may be different, they might inspire further tests or general insight into the dhclient process.

ondoho · 10-17-2019, 03:04 AM

Is dhclient still present and working ion your system?

Code:

systemctl status dhclient

might shed some light, and also what hapened around this:

Code:

apt-get remove network-manager

residual config masking dhclient?

...just guessing at this stage.

metallica1973 · 10-28-2019, 08:58 AM

Thank all of you in advance

Code:

manwiththemasterplan@Confucious:~$ sudo systemctl status dhclient
[sudo] password for manwiththemasterplan: 
Unit dhclient.service could not be found.

manwiththemasterplan@Confucious:~$sudo apt-get install isc-dhcp-common
Reading package lists... Done
Building dependency tree       
Reading state information... Done
isc-dhcp-common is already the newest version (4.4.1-2).
0 upgraded, 0 newly installed, 0 to remove and 106 not upgraded.

One thing that I didnt notice in the logs that stood out was:

Code:

/var/log/syslog-Oct 28 08:34:24 Confucious systemd[1]: Started Network Manager Script Dispatcher Service.
/var/log/syslog:Oct 28 08:34:24 Confucious systemd[1]: sroute.service: Service RestartSec=100ms expired, scheduling restart.
/var/log/syslog:Oct 28 08:34:24 Confucious systemd[1]: sroute.service: Scheduled restart job, restart counter is at 3.
/var/log/syslog-Oct 28 08:34:24 Confucious systemd[1]: Stopped static route.
/var/log/syslog-Oct 28 08:34:24 Confucious systemd[1]: Started static route.
/var/log/syslog-Oct 28 08:34:24 Confucious systemd[1]: Started Login Service.
/var/log/syslog:Oct 28 08:34:24 Confucious sroute[781]: Error: Nexthop has invalid gateway.
/var/log/syslog-Oct 28 08:34:24 Confucious NetworkManager[658]: <info>  [1572266064.4033] device (wlan0): driver supports Access Point (AP) mode
/var/log/syslog:Oct 28 08:34:24 Confucious systemd[1]: sroute.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
/var/log/syslog:Oct 28 08:34:24 Confucious systemd[1]: sroute.service: Failed with result 'exit-code'.
/var/log/syslog-Oct 28 08:34:24 Confucious NetworkManager[658]: <info>  [1572266064.4053] manager: (wlan0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/3)

So I removed network-manager like suggested and its the same results:

Code:

Oct 28 09:52:56 Confucious /usr/lib/gdm3/gdm-x-session[821]: (II) xfree86: Adding drm device (/dev/dri/card0)
Oct 28 09:52:56 Confucious systemd[1]: sroute.service: Service RestartSec=100ms expired, scheduling restart.
Oct 28 09:52:56 Confucious systemd[1]: sroute.service: Scheduled restart job, restart counter is at 5.
Oct 28 09:52:56 Confucious systemd[1]: Stopped static route.
Oct 28 09:52:56 Confucious systemd[1]: sroute.service: Start request repeated too quickly.
Oct 28 09:52:56 Confucious systemd[1]: sroute.service: Failed with result 'exit-code'.
Oct 28 09:52:56 Confucious systemd[1]: Failed to start static route.

uteck · 10-28-2019, 09:32 AM

Check if systemd.networkd is installed, if so it is 'helping' and needs to be removed also for your manual settings to work.
I had to remove it to get WICD to work when I replaced Network-Mangler.

berndbausch · 10-28-2019, 09:56 AM

Quote:

Originally Posted by metallica1973

Code:

Oct 28 09:52:56 Confucious systemd[1]: sroute.service: Start request repeated too quickly.

To me, this indicates an error in the sroute configuration which makes sroute fail immediately. It is started again, fails again etc.

Check the config. You should find it in the sroute.service unit file. The name of the sroute.service unit file is displayed by the systemctl status command.

And/or the sroute log: journalctl -u sroute.