I have an embedded device, which uses a "configuration editor" to produce a single user config file.
We have devices running with hardware dating back to CM1 , CM3, all sorts, boards and heaven knows what issue of Debian. I cannot upgrade old units to a new OS.
On the WAN interface I only offer fixed IPV4 at present or "try it if you like but no guarantee " DHCP.
Some models have a separate eth1 LAN interface with only fixed IP, but not the models using Pi boards.
Very early at unit start up the file /etc/network/interfaces is dynamically created from the user config file. It contains the LL device, but not for any good reason. It always sets up eth0, often with aliases.
This system has worked fine for 15 years, and I'd like it to go on working until I absolutely have to code up a new way to do things. Change is costly, supporting 2 methods in parallel in our codebase is horrible.
On 12.5 ( not lite ) this seemed to still work. I created the file and something read it and set up the interfaces. I left NM running ( I assume ) and expected it would ignore lo and eth0 as documented.
On 12.8 putting a definition for eth0 in there stops the default "run DHCP on eth0" behaviour. But nothing actually implements what the file specifies. eth0 does not appear in the output of ifcpnfig, nor can I apparently ifup it.
So the question is, what is the simplest change I can make to 12.8lite so eth0 etc are configured according to /etc/network/interfaces again.
TVM David
We have devices running with hardware dating back to CM1 , CM3, all sorts, boards and heaven knows what issue of Debian. I cannot upgrade old units to a new OS.
On the WAN interface I only offer fixed IPV4 at present or "try it if you like but no guarantee " DHCP.
Some models have a separate eth1 LAN interface with only fixed IP, but not the models using Pi boards.
Very early at unit start up the file /etc/network/interfaces is dynamically created from the user config file. It contains the LL device, but not for any good reason. It always sets up eth0, often with aliases.
This system has worked fine for 15 years, and I'd like it to go on working until I absolutely have to code up a new way to do things. Change is costly, supporting 2 methods in parallel in our codebase is horrible.
On 12.5 ( not lite ) this seemed to still work. I created the file and something read it and set up the interfaces. I left NM running ( I assume ) and expected it would ignore lo and eth0 as documented.
On 12.8 putting a definition for eth0 in there stops the default "run DHCP on eth0" behaviour. But nothing actually implements what the file specifies. eth0 does not appear in the output of ifcpnfig, nor can I apparently ifup it.
So the question is, what is the simplest change I can make to 12.8lite so eth0 etc are configured according to /etc/network/interfaces again.
TVM David
Statistics: Posted by myshkin-uk — Fri Feb 21, 2025 11:11 pm — Replies 1 — Views 50