Open ashthespy opened 1 year ago
The back end uses dhcpcd.conf to set up static IP for both wired and wireless.
dhcpcd.conf
Whereas, wireless.js uses the following to get for IP address handling. https://github.com/volumio/volumio3-os/blob/be48af7083d42c9d6cb4a530abb4e817e992a788/volumio/bin/wireless.js#L122-L132
wireless.js
Some issues come to light:
/data/configuration/wlanstatic
dhclient
/usr/bin/sudo /sbin/dhcpcd
dhcpcd | -n, --rebind
err
launch
callback
sync=false
dhcpcd
The back end uses
dhcpcd.conf
to set up static IP for both wired and wireless.Whereas,
wireless.js
uses the following to get for IP address handling. https://github.com/volumio/volumio3-os/blob/be48af7083d42c9d6cb4a530abb4e817e992a788/volumio/bin/wireless.js#L122-L132Some issues come to light:
/data/configuration/wlanstatic
that doesn't exist.dhclient
just runs/usr/bin/sudo /sbin/dhcpcd
with out any arguments. Wouldn't it be better to explicitly calldhcpcd | -n, --rebind
err
passed to the callback inlaunch
callback
will be triggered immediately (sync=false
), not waiting for the network connection to succeed before requesting an IP address viadhclient
(dhcpcd
in this case).