Firewall status tray icon - firewallstate-2.1
No, quite simple really.
It was meant for a first run tray applet for new Puplets. Just to remind you to turn on the firewall by running the wizard.
So a new Puppy install would show as 'firewall off' and the option to run the wizard as a reminder in the tooltip. That's why I added the quit and remove.
Now, when you have a clean install the rc.local file has no entry for firewall. When you run the wizard it appends the 'firewall start' script instruction there. I just check for that script. i don't check for the rc.firewall.
In effect once the firewall wizard is run it should not need changing. However, if you wish to turn it off then alter the script to show 'firewall stop' not 'firewall start'
It was meant for a first run tray applet for new Puplets. Just to remind you to turn on the firewall by running the wizard.
So a new Puppy install would show as 'firewall off' and the option to run the wizard as a reminder in the tooltip. That's why I added the quit and remove.
Now, when you have a clean install the rc.local file has no entry for firewall. When you run the wizard it appends the 'firewall start' script instruction there. I just check for that script. i don't check for the rc.firewall.
In effect once the firewall wizard is run it should not need changing. However, if you wish to turn it off then alter the script to show 'firewall stop' not 'firewall start'
Rob
-
The moment after you press "Post" is the moment you actually see the typso 8)
-
The moment after you press "Post" is the moment you actually see the typso 8)
OK, I see your point.
But the tray applets first intention wasn't to be a full time app, however i did change it subject to requests, so i suppose it had better be accurate in it's reporting.
I've just done a couple of experiments both loading and unloading modules.
My simple method will change state if the text is changed but not reflect an accurate actual change until rebooted.
Unloading the module has no effect on the script so firewallstate will be inaccurate.
I will experiment with code to look at running the lsmod output to a file and parse that checking for iptables.
But the tray applets first intention wasn't to be a full time app, however i did change it subject to requests, so i suppose it had better be accurate in it's reporting.
I've just done a couple of experiments both loading and unloading modules.
My simple method will change state if the text is changed but not reflect an accurate actual change until rebooted.
Unloading the module has no effect on the script so firewallstate will be inaccurate.
I will experiment with code to look at running the lsmod output to a file and parse that checking for iptables.
Rob
-
The moment after you press "Post" is the moment you actually see the typso 8)
-
The moment after you press "Post" is the moment you actually see the typso 8)
Hmmm, I've carried out further tests.
The only way to turn the firewall off easily is to change the text in rc.local to 'firewall stop' and reboot. Otherwise delete the rc.firewall and reboot again.
All require a reboot and the rc.local changes, so I can't see a reason to change the code at the moment. Unless anyone knows otherwise.
I have changed the code and tested but it is easier the original way as this seems to be universal in operation.
I wrote a pet to turn firewall on and off a while back, it's on here somewhere.
The only way to turn the firewall off easily is to change the text in rc.local to 'firewall stop' and reboot. Otherwise delete the rc.firewall and reboot again.
All require a reboot and the rc.local changes, so I can't see a reason to change the code at the moment. Unless anyone knows otherwise.
I have changed the code and tested but it is easier the original way as this seems to be universal in operation.
I wrote a pet to turn firewall on and off a while back, it's on here somewhere.
Rob
-
The moment after you press "Post" is the moment you actually see the typso 8)
-
The moment after you press "Post" is the moment you actually see the typso 8)
tasmod wrote:Hmmm, I've carried out further tests.
The only way to turn the firewall off easily is to change the text in rc.local to 'firewall stop' and reboot. Otherwise delete the rc.firewall and reboot again.
All require a reboot and the rc.local changes, so I can't see a reason to change the code at the moment. Unless anyone knows otherwise.
I have changed the code and tested but it is easier the original way as this seems to be universal in operation.
I wrote a pet to turn firewall on and off a while back, it's on here somewhere.
hm...looks like it works
Code: Select all
/etc/rc.d # ./rc.firewall stop
-> Projectfiles.com Linux Firewall version 2.0rc9 running.
-> Performing sanity checks. [ PASSED ]
-> Firewall disabled.
/etc/rc.d # ./rc.firewall start
-> Projectfiles.com Linux Firewall version 2.0rc9 running.
-> Performing sanity checks...... [ PASSED ]
-> Building firewall.... [ DONE ]
-> Successfully secured the following addresses: 192.168.1.112.
I wrote the original pet to do just that.
I was setting up a router and network and kept getting weird results due to the firewall. So I quickly wrote the script and gui to turn it on and off whilst I carried out tests.
Zigbert incorporated in his all encompassing setup program.
I suppose I could incorporate it in the app along with a menu launch entry if you want.
I was setting up a router and network and kept getting weird results due to the firewall. So I quickly wrote the script and gui to turn it on and off whilst I carried out tests.
Zigbert incorporated in his all encompassing setup program.
I suppose I could incorporate it in the app along with a menu launch entry if you want.
Rob
-
The moment after you press "Post" is the moment you actually see the typso 8)
-
The moment after you press "Post" is the moment you actually see the typso 8)
In the custom section I put "631/tcp" .. seemed to work .. I can print puppy machine to puppy machine. Enabled some of the other things too. Forget exactly. Patriot would know or rcrsn51.8-bit wrote:Just what does a person need to change in rc.firewall to allow network printing to bypass the firewall?
The reason I ask is that if I set up the firewall accepting default, shared printers are not seen by linux guest systems.
Cheers
Puppy Linux Blog - contact me for access
OK, back on the code.
After testing I found the app would work for most users 100% but if a user used my on/off app or a cli command then it wouldn't reflect the status.
This is because the commands work direct with rc.firewall and do not write to the rc.local to reflect the change in realtime.
So code changed and checks lsmod for ip_tables at jpeps suggestion. (thanks)
Edit: removed icon code request. Now working.
After testing I found the app would work for most users 100% but if a user used my on/off app or a cli command then it wouldn't reflect the status.
This is because the commands work direct with rc.firewall and do not write to the rc.local to reflect the change in realtime.
So code changed and checks lsmod for ip_tables at jpeps suggestion. (thanks)
Edit: removed icon code request. Now working.
Rob
-
The moment after you press "Post" is the moment you actually see the typso 8)
-
The moment after you press "Post" is the moment you actually see the typso 8)
Thanks for the feedback, much appreciated.
Version 1.3 posted, works regardless of commands issued elsewhere.
Incorporates ON/OFF in menu, should you need it.
Regarding the External IP address info. It's been interesting seeing my external IP change occasionally by BT.
Version 1.3 posted, works regardless of commands issued elsewhere.
Incorporates ON/OFF in menu, should you need it.
Regarding the External IP address info. It's been interesting seeing my external IP change occasionally by BT.
Rob
-
The moment after you press "Post" is the moment you actually see the typso 8)
-
The moment after you press "Post" is the moment you actually see the typso 8)
Thanks bigpup much appreciated.
-----
Version 1.4 released
I think this is probably the last version as the menu is now a bit large and I don't want to encroach on the main menu system.
I've added the 3 options for settings as reported in Information on menu.
I've also added Psync for accurate time setting.
-----
Version 1.4 released
I think this is probably the last version as the menu is now a bit large and I don't want to encroach on the main menu system.
I've added the 3 options for settings as reported in Information on menu.
I've also added Psync for accurate time setting.
Rob
-
The moment after you press "Post" is the moment you actually see the typso 8)
-
The moment after you press "Post" is the moment you actually see the typso 8)
I agree there's something to be said about keeping things simple. Psync, set time & date, etc., are already readily available in desktop settings. "Choose keyboard layout" doesn't work, but is available through Choose Country. (I think most of this gets set up initially anyway during first bootup).tasmod wrote:Thanks bigpup much appreciated.
-----
Version 1.4 released
I think this is probably the last version as the menu is now a bit large and I don't want to encroach on the main menu system.
I've added the 3 options for settings as reported in Information on menu.
I've also added Psync for accurate time setting.