On 2024-07-14 14:11, Felix Fietkau wrote:
On 14.07.24 11:47, Roman Yeryomin wrote:
On 2024-07-14 10:42, Felix Fietkau wrote:
On 14.07.24 02:34, Roman Yeryomin wrote:
It is pretty common use case for a network device to be configured
as DHCP client but having some fallback static IP address whe
On 14.07.24 11:47, Roman Yeryomin wrote:
On 2024-07-14 10:42, Felix Fietkau wrote:
On 14.07.24 02:34, Roman Yeryomin wrote:
It is pretty common use case for a network device to be configured
as DHCP client but having some fallback static IP address where it
would be reachable for, e.g., configu
On 2024-07-14 10:42, Felix Fietkau wrote:
On 14.07.24 02:34, Roman Yeryomin wrote:
It is pretty common use case for a network device to be configured
as DHCP client but having some fallback static IP address where it
would be reachable for, e.g., configuration.
This reacts on udhcpc events and
On 14.07.24 02:34, Roman Yeryomin wrote:
It is pretty common use case for a network device to be configured
as DHCP client but having some fallback static IP address where it
would be reachable for, e.g., configuration.
This reacts on udhcpc events and sets/removes ipaddr which is
configured on
It is pretty common use case for a network device to be configured
as DHCP client but having some fallback static IP address where it
would be reachable for, e.g., configuration.
This reacts on udhcpc events and sets/removes ipaddr which is
configured on an iface from network config.
This means th
