Hello, First thanks for the community developers and supporter for this awesome software I have been running it for years and it always did the job and never caused me a trouble after good configurations.
recently I've upgraded to version 19 from an older one, I didn't notice any faced any issue except that an old custom routing init script isn't working anymore:
#!/bin/sh /etc/rc.common
START=25
start()
{
sleep 20
ip route add default via 192.168.40.1
ip rule add from 192.168.50.0/24 priority 10 table wan2
ip route add 192.168.50.0/24 dev br-landenver table wan2
ip route add default via 127.104.21.** table wan2
}
I've tried to move start to 100 and increase sleep to 60 second but it doesn't help. When I run it manully using
/etc/init.d/customrule start
it runs perfectly.
I thought it could be an issue with the new PROCD so I wrote this:
I've checked it in /etc/rc.d/S... it is enabled.
Regarding the config in /etc/config/network I couldn't find if it accept the priority flag used by "ip" it seemed important to have my setup work.
I hope I can make those few commands works instead of moving to more complicated things, but I may have to at the end.
I do not It think you can use PROCD here. I would revert to the first version and debug it.
Add exec >>/root/log 2>&1 as the second line followed by set -x, reboot, then check the /root/log file for how the script ran and what happened.
It is possible that you have to implement this as a hot plug script instead: there could be something that resets the interfaces after your script is finished.
100 is naturally wrong.
The number gets placed to the end of the symlink filename in /etc/rc.d, which files are then evaluated in alphabetical order, so 100 would be pretty much like 10.
Range is 01-99 ( and preferably 01-94, as /etc/rc.local is evaluated at 95)
/etc/rc.local would also be a natural place for those commands.