Home Page › Forums › Network Management › ZeroShell › Can’t add new firewall rules
- This topic is empty.
-
AuthorPosts
-
June 5, 2013 at 11:56 am #43671
reaperz
ParticipantHello
My zeroshell box used to work well, but now I am getting trouble trying to add new firewall rules. I got over hundred rules.
When i try to add new rule, I sometimes get “Rule does not exist”
Or if adding is successful, saving new rules gives that kind of error:
“Jun 05 11:24,18 ERROR: Chain INPUT not saved: cp: cannot create regular file _/var/register/system/net/FW/Chains/INPUT/Rules/118/NotD…”
Those are red error messages, that you get on lower side of screen.
so far only fix i have found is to restart the zeroshell router several times. Then I can add new firewall rules. Until some days/weeks later I can’t add them again without restarting. Any idea what might be going on? I got enough disk space (200MB free). Also RAM is not a problem (4GB).
I have Zeroshell 1.0 beta16 running 3.2.9 kernel
Any ideas what might be going on and how to fix this?
August 19, 2013 at 10:44 am #52769reaperz
ParticipantHas anyone had similar problems? Cause this one is still biting me in the back, have to restart zeroshell router if i want to add rules.
May 17, 2014 at 2:36 pm #52770Yhoni
Member@reaperz wrote:
Has anyone had similar problems? Cause this one is still biting me in the back, have to restart zeroshell router if i want to add rules.
I have the same problem with Release 3.0.0.
When I try to add new rules to the firewall I get the following error and not recorded:
May 17 16:24,09 ERROR: Chain INPUT not saved: cp: cannot stat _/var/register/system/net/FW/tmp/Chains/INPUT/Rules/015/ParallelThan’: …
Warning: last changes not saved!Where is the problem?
I Zeroshell run from a usb stick 3 GB and I have enough free space.
May 17, 2014 at 2:42 pm #52771Yhoni
MemberDo you have an error this path:?
_/var/register/system/net/FW/tmp/Chains/INPUT/Rules/015/ParallelThan ‘
Should have a single quote ” ‘ ” instead of an underscore “_” in the beginning of the path?
May 17, 2014 at 7:33 pm #52772Yhoni
MemberI have the same error when trying to delete the firewall changes.
May 17 21:31,34 ERROR: Last changes to chain INPUT not cancelled:rm: cannot remove _/var/register/system/net/FW/tmp/Chains/INPUT//Rul…
Where is the problem ?
May 18, 2014 at 7:14 am #52773Yhoni
MemberHow could I add rules to the firewall from the console?
Thanks.
May 18, 2014 at 1:35 pm #52774redfive
Participant@Yhoni
Sample with INPUT chain, before, issue the commandiptables -vL INPUT --line-number
you will have a look about the existing rules an their exact position (including the LOG’s rules) , then assume that you want to add a rule in the 20th line , so
iptables -I INPUT 20 ..... ....... ....... ........ ...... -j ......
You could add the command in Startup/Cron , Firewall Chain, so, even after a reboot, you’d find the rule applied. Remember that this rule , will be applied always in the 20th position, so you could have to adjust the script if you will remove or add some rules via gui, which are above the newest one inserted by the script.
It should work…
RegardsMay 20, 2014 at 11:23 am #52775Yhoni
Member@redfive wrote:
@Yhoni
Sample with INPUT chain, before, issue the commandiptables -vL INPUT --line-number
you will have a look about the existing rules an their exact position (including the LOG’s rules) , then assume that you want to add a rule in the 20th line , so
iptables -I INPUT 20 ..... ....... ....... ........ ...... -j ......
You could add the command in Startup/Cron , Firewall Chain, so, even after a reboot, you’d find the rule applied. Remember that this rule , will be applied always in the 20th position, so you could have to adjust the script if you will remove or add some rules via gui, which are above the newest one inserted by the script.
It should work…
RegardsIt works perfect.
Thank you.
May 20, 2014 at 11:38 am #52776Yhoni
MemberRepeat.
Excuse me.
May 20, 2014 at 4:45 pm #52777DrmCa
ParticipantAs firewall web interface works fine for me in v.3 and always worked previously, I would suspect a broken downloaded image, or disk errors on the profile partition. Try downloading the image again, rebuilding your boot media and running disk check.
-
AuthorPosts
- You must be logged in to reply to this topic.