Static IP address configuration does not seem to be respected

[jeskko]

Tried configuring a static IP address and it shows in the config:

web-888:/# fgrep -A8 ip_address /media/mmcblk0p1/config/admin.json
   "ip_address": {
      "use_static": true,
      "ip": "172.22.52.67",
      "netmask": "255.255.255.0",
      "gateway": "172.22.52.1",
      "dns1": "1.1.1.1",
      "dns2": "1.0.0.1",
      "commit_use_static": true
   },

But still, dhcpcd is being run:

web-888:/# ps -ef |fgrep dhcp
 1411 dhcpcd    0:00 dhcpcd: [manager] [ip4]
 1413 root      0:00 dhcpcd: [privileged proxy]
 1415 dhcpcd    0:00 dhcpcd: [network proxy]
 1416 dhcpcd    0:00 dhcpcd: [control proxy]

and device has fetched the address from dhcp:

web-888:/# fgrep dhcp /var/log/messages
Apr  8 06:08:21 web-888 daemon.info dhcpcd[1411]: dhcpcd-10.0.6 starting
Apr  8 06:08:23 web-888 daemon.info dhcpcd[1413]: lo: using static address 127.0.0.1/8
Apr  8 06:08:23 web-888 daemon.info dhcpcd[1413]: lo: adding route to 127.0.0.0/8
Apr  8 06:08:23 web-888 daemon.info dhcpcd[1413]: eth0: waiting for carrier
Apr  8 06:08:25 web-888 daemon.info dhcpcd[1413]: eth0: carrier acquired
Apr  8 06:08:25 web-888 daemon.info dhcpcd[1413]: eth0: soliciting a DHCP lease
Apr  8 06:08:29 web-888 daemon.info dhcpcd[1413]: eth0: offered 172.22.52.67 from 172.22.52.1
Apr  8 06:08:29 web-888 daemon.info dhcpcd[1413]: eth0: leased 172.22.52.67 for 86400 seconds
Apr  8 06:08:29 web-888 daemon.info dhcpcd[1413]: eth0: adding route to 172.22.52.0/24
Apr  8 06:08:29 web-888 daemon.info dhcpcd[1413]: eth0: adding default route via 172.22.52.1
Apr  8 06:08:29 web-888 daemon.info dhcpcd[1413]: eth0: pid 0 deleted route to 172.22.52.0/24

(dhcp currently provisions the same address as in the attempted static config, but this causes an issue in case the dhcp server is not available when the device reboots).

Tried to search the filesystem and source code and was not able to find anything using the static ip configuration lines.

[jurajbujdoso]

I am not using static config, but when I understand the config

cat /etc/dhcpcd.conf |grep -v "#"

profile static_eth0
static ip_address=192.168.1.100/24
static routers=192.168.1.1
static domain_name_servers=192.168.1.1

interface eth0
fallback static_eth0

eth0 will attempt to get an IP address via DHCP first, and if that fails, it will fallback to a static IP defined in the static_eth0 profile.

There is also nice feature directly in chrome browser without nothing to configure:
http://web-888.local:8073
(https://www.rx-888.com/web/guide/connect.html)

avahi-resolve-host-name web-888.local

My config files have records:

"ip_address": {
      "use_static": false,
      "ip": "",
      "netmask": "",
      "gateway": "",
      "dns1": "",
      "dns2": ""
   },

What ip address range is visible on your device, when there is no dhcp running?
Reflect your /etc/dhcpcd.conf changes in config.json ?

Juraj

[jeskko]

It appears that there is not anything that updates the dhcpcd.conf according the static ip configuration that is in the config file (which is defined in the web GUI). So even if I configure 172.22.52.67 in the GUI (and it shows in admin.json), when the device is in network without DHCP, I get the 192.168.1.200 address that's by default in the dhcpcd.conf.

[jurajbujdoso]

I just also check, that update IP in webgui does not reflect changes in dhcpd.conf after reboot.

I have seen in source code that, changes in web interface try to modify file /etc/network/interfaces

                system("rm /etc/network/interfaces");
                system("touch /etc/network/interfaces");
                system("lbu commit -d");

and the file is WAD

cat /etc/network/interfaces 

auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
    address 10.0.1.2
    netmask 255.255.255.0
    gateway 10.0.1.1
iface wlan0 inet static
    address 192.168.7.2
    netmask 255.255.255.252
    network 192.168.7.0
    gateway 192.168.7.1

The file has been change successful.

possible cause:

The question is which of the network configuration files have priority when dhcp is not present:

/etc/network/interfaces                                       /etc/init.d/networking restart           
or 
/etc/dhcpcd.conf                                                    /etc/init.d/dhcpd restart           

have bigger priority.

Situation in version web-888: Installed version: v2025.312

I have running dhcp all the time and have modify for static IP.
Then I reboot the server and my network config is valid :

 eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    inet 10.0.1.2/24 scope global eth0
       valid_lft forever preferred_lft forever
    inet 10.0.1.3/24 brd 10.20.7.255 scope global secondary dynamic noprefixroute eth0
       valid_lft 120sec preferred_lft 97sec

I get IP from dhcp and static IP is as well configured, as you can see.
But it could be, that second IP is configure due the fact, that I have running dhcp instance.
And there could be difference in behavior when there is NO dhcp present.

Try to update to latest firmware and replace full sdcard content.
If it does not work, bellow is quick fix, which change dhcpd.conf and interfaces config persistent.

// Till you made any web-gui change which triggers network change.

QUICK FIX

# change both file so they reflect your changes for eth0 IP address
vi /etc/dhcpcd.conf
vi /etc/network/interfaces 

#save changes
lbu commit -d"

#reboot device
reboot

Good luck - Juraj
Ps: And please let me know if it helps and if you have had current image or older.

[jeskko]

Another restart without working dhcp (this time with recent images). Situation after DHCP has been restored in the network:

web-888:~# ip addr show dev eth0
3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether b2:20:1a:d4:4a:02 brd ff:ff:ff:ff:ff:ff
    inet 172.22.52.67/24 scope global eth0
       valid_lft forever preferred_lft forever
    inet 192.168.1.100/24 brd 192.168.1.255 scope global noprefixroute eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::b020:1aff:fed4:4a02/64 scope link
       valid_lft forever preferred_lft forever

So it has gotten an address 172.22.52.67 in addition to the static config in dhcpcd.conf

web-888:~# ip route
default via 192.168.1.1 dev eth0  src 192.168.1.100  metric 1003
127.0.0.0/8 dev lo scope host  src 127.0.0.1  metric 1001
172.22.52.0/24 dev eth0 scope link  src 172.22.52.67
192.168.1.0/24 dev eth0 scope link  src 192.168.1.100  metric 1003

but no default route from dhcp.

So I'd stay in my opinion that current image does not respect static ip configuration.

[eiddor]

I'm having this issue as well, though the workaround from @jurajbujdoso helped.

This is a new device and I have tried the latest stable (0312) and alpha (1117) releases.

At first I could only resolve web-888.local with IPv6, so I had to open the admin URL on my iPhone to force it to use static IPv4. It became reachable from my network after that, however I was still getting the 192.168.1.100 address every time which was also overriding the default gateway on my 10.x network.