Kyros Hariri wrote:
hello inouk,
thank you for your help.
entering it again that way:
config 'include'
option 'path' '/etc/firewall.fon'
option 'path' '/etc/firewall.user'
caused my fonera not to be accessible anymore from outside (e.g. ssh via
dyndns).
so I couldn't keep this.
Right, as Matthijs said another include should be created for it
the firewall.user is already listed as a path in /etc/config/firewall.
r...@fonera:~# cat /etc/config/firewall | grep -A 1 "include"
config 'include'
option 'path' '/etc/firewall.fon'
--
config 'include' 'proxy'
option 'path' '/etc/firewall.proxy'
--
config 'include'
option 'path' '/etc/firewall.user'
r...@fonera:~#
Hmm when i do this i on a stock firmware i have only have firewall.fon
but generally the very obvious thing is that the firewall.user settings
seem to be overwritten by a internal fonera job every few minutes.
this is the problem's origin which have to be solved in my eyes.
do you agree?
firewall.user might be used by something else... You may want to pick a
name specific to your app like /etc/firewall.websrv or so. If you one
day you want to release your work through a plugin you will just have to
add to your install script:
uci add firewall include; uci set
firewa...@include[-1].path=/etc/firewall.websrv; uci commit firewall
Inouk
_______________________________________________
Development mailing list
[email protected]
http://fonosfera.org/mailman/listinfo/development
