Before I begin, I don't think I noted that this device is a headless NAS. Meaning, if the IP really goes agly, I'll have a bit of a challenge re-entering the configuration. So, I need to either get this bang on the first try, or be assured that it will fall back to a bog standard DHCP address, allowing me to discover it using the Xfinity router admin tool.
As recommended, I entered the configuration for my desired static IP using the nmtui utility. Unfortunately, after I entered the configuration the utility hardly made obvious the simple act of selecting "OK" rather than backing out using the escape key. And, after I backed out using escape, as you might expect, poof, there it went.
So.
I took the most direct approach: edited the dhcpcd.conf file and added what seems to be the correct information. As follows:
# Static wlan0 configuration:
interface wlan0
static ip_address=10.0.0.2/8
#static ip6_address=fd51:42f8:caae:d92e::ff/64
#static routers=10.0.0.1
static domain_name_servers=10.0.0.1 75.75.75.75 76.76.76.76 fd51:42f8:caae:d92e::1
# It is possible to fall back to a static IP if DHCP fails:
# define static profile
#profile static_eth0
#static ip_address=192.168.1.23/24
#static routers=192.168.1.1
#static domain_name_servers=192.168.1.1
# fallback to static profile on eth0
#interface eth0
#fallback static_eth0
So, 2 questions: does this look right? And, if it's not right, will it fall back to the previous DHCP configuration and grab an IP so that I can ssh back into it?
Thx again,
-Z
-- Lord* Adam Zion, MSIS
* Yes, really