-
Notifications
You must be signed in to change notification settings - Fork 229
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
Unable to start issue #633
Comments
[Wed Sep 27 11:03:35 2023]23950 Exiting because of error initializing firewall rules |
Warning: iptables-legacy tables present, use iptables-legacy to see them Warning: iptables-legacy tables present, use iptables-legacy to see themWarning: iptables-legacy tables present, use iptables-legacy to see themWarning: iptables-legacy tables present, use iptables-legacy to see themWarning: iptables-legacy tables present, use iptables-legacy to see themWarning: iptables-legacy tables present, use iptables-legacy to see themWarning: iptables-legacy tables present, use iptables-legacy to see themWarning: iptables-legacy tables present, use iptables-legacy to see them[5][Wed Sep 27 11:20:31 2023]25205 Initializing firewall rules Warning: iptables-legacy tables present, use iptables-legacy to see themWarning: iptables-legacy tables present, use iptables-legacy to see themWarning: iptables-legacy tables present, use iptables-legacy to see themWarning: iptables-legacy tables present, use iptables-legacy to see themWarning: iptables-legacy tables present, use iptables-legacy to see themWarning: iptables-legacy tables present, use iptables-legacy to see themWarning: iptables-legacy tables present, use iptables-legacy to see themWarning: iptables-legacy tables present, use iptables-legacy to see themWarning: iptables-legacy tables present, use iptables-legacy to see themWarning: iptables-legacy tables present, use iptables-legacy to see themWarning: iptables-legacy tables present, use iptables-legacy to see themWarning: iptables-legacy tables present, use iptables-legacy to see themWarning: iptables-legacy tables present, use iptables-legacy to see themWarning: iptables-legacy tables present, use iptables-legacy to see them[3][Wed Sep 27 11:20:39 2023]25205 Exiting because of error initializing firewall rules |
I suspect that you are missing some dependencies. On OpenWrt the dependencies for NoDogSplash would be:
|
A refresh was made to confirm the installation of all dependent packages. But still unable to start.
Looking forward to hearing back again.
原始邮件
发件人:"Moritz Warning"< ***@***.*** >;
发件时间:2023/9/27 18:52
收件人:"nodogsplash/nodogsplash"< ***@***.*** >;
抄送人:"iooico1"< ***@***.*** >;"Author"< ***@***.*** >;
主题:Re: [nodogsplash/nodogsplash] Unable to start issue (Issue #633)
I suspect that you are missing some dependencies.
On OpenWrt the dependencies for NoDogSplash would be:
libpthread
libmicrohttpd-no-ssl
iptables-nft
iptables-mod-nat-extra
iptables-mod-ipopt
iptables-mod-conntrack-extra
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
The dependency package has been determined to be fully installed, but the firewall cannot be configured and cannot run.
A refresh was made to confirm the installation of all dependent packages. But still unable to start.
Looking forward to hearing back again.
原始邮件
发件人:"Moritz Warning"< ***@***.*** >;
发件时间:2023/9/27 18:52
收件人:"nodogsplash/nodogsplash"< ***@***.*** >;
抄送人:"iooico1"< ***@***.*** >;"Author"< ***@***.*** >;
主题:Re: [nodogsplash/nodogsplash] Unable to start issue (Issue #633)
I suspect that you are missing some dependencies.
On OpenWrt the dependencies for NoDogSplash would be:
libpthread
libmicrohttpd-no-ssl
iptables-nft
iptables-mod-nat-extra
iptables-mod-ipopt
iptables-mod-conntrack-extra
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
@mwarning @iooico1 The problem was a bug in the "iptables" pseudo package that is intended to install the various iptablesxx packages. Unfortunately if another package has just "iptables" as a dependency, the hacky iptables-zz-legacy will be installed. In a situation like this, opennds could not see the "iptables" tables, so exited, just like nodog does here. The solution was to use opkg to force remove all iptablesxx packages, then re-install iptables-nft. I suspect it may well be the same issue here. |
I tried uninstalling all the plugins in iptables-xx, but they are still invalid and cannot be used~ Could you give me some other suggestions? Thank you very much.
原始邮件
发件人:"Rob White"< ***@***.*** >;
发件时间:2023/9/27 23:08
收件人:"nodogsplash/nodogsplash"< ***@***.*** >;
抄送人:"iooico1"< ***@***.*** >;"Mention"< ***@***.*** >;
主题:Re: [nodogsplash/nodogsplash] Unable to start issue (Issue #633)
@mwarning @iooico1
The Warning: iptables-legacy tables present, use iptables-legacy to see them message was sometimes seen in the pre-nftables version of opennds (it was the same dependencies at that time).
The problem was a bug in the "iptables" pseudo package that is intended to install the various iptablesxx packages.
Unfortunately if another package has just "iptables" as a dependency, the hacky iptables-zz-legacy will be installed.
Even worse, it is possible to have both iptables-zz-legacy and iptables-nft installed at the same time.
In a situation like this, opennds could not see the "iptables" tables, so exited, just like nodog does here.
The solution was to use opkg to force remove all iptablesxx packages, then re-install iptables-nft.
After a reboot, all was well.
I suspect it may well be the same issue here.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
I am a technical novice and am currently using Nodogsplash 5.0.1 for openwrt configuration. During use, it was found that the expected input command feedback was: nodogsplash protocol not started (Error: No such file or directory). I hope the leaders can provide suggestions for modification or installation.
The text was updated successfully, but these errors were encountered: