New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FS#1972 - omcproxy doesn't start at boot if enabled, works ok when started manually #6909
Comments
howl: Using the hint I provided makes procd saying that omcproxy crashed 6 times in a row because the respaw, despite it then works because it gets started again because the trigger I decided to make a new init script so, I have done a new omcproxy init script heavily bassed in the igmpproxy one:
If someone could review it and if it could be used in omcproxy package, go ahead, I put the OpenWrt.org copyright because as I said it only was a simple adoption and adjust of the igmpproxy init script logic to the way omcproxy config is. |
dedeckeh: Fixed in commit https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=df8f8bad082ea5280c19c9091c099b28b7e2fc67 |
howl:
Supply the following if possible:
I have configured properly omcproxy, works fine starting it manually with "service omcproxy start", no problems at all. The issue is when booting up the device the startup script exits with 0 because the PROXIES variable is empty because no interfaces are ready when the script starts. Commenting Line number 117:" [ -n "$PROXIES" ] || return 0" makes it work as it should. The network triggers seems to make it start when the interfaces are ready.
Also in lines number 89 and 100 the proto specified for the firewall rules are any, but it's more correct udp.
Will report in omcproxy github too.
The text was updated successfully, but these errors were encountered: