(old)Puppy Linux Discussion Forum

Sorry guys missed the responses as I've only just checked back.

Thanks Sylvander, glad you like it. It's really a response to requests after my first simple version, that it has developed so far.

Scsijon,

Interesting idea. I'll look into the possibility of further control of the firewall program, although no promises.

It only be my setup, but the firewall settings are not remembered after reboot.. I'm using LupQ 511 and firewallstate-1.7-full..

Anyone experience this?

Here in Boxpup-431, every time I boot, the firewall icon down at bottom right in the system tray, is showing the firewall is OFF.
So I switch it on every time I get to the desktop, which then shows it is ON.

Hi all,
I made a mention in the luci thread.

I loaded the latest luci and this happened for me also on reboot.

I suspect a minor change in the startup routine or network message is causing firewallstate to report incorrectly. I suspect that the firewall is actually 'on'

Check /etc/rc.d/rc.local in geany and the last bit of text should end in 'start'. If it does then the firewall is probably running and firewallstate is reporting incorrectly. I can see it is doing that on my system.

Not much time available but I will look into it.

I just updated the post to version 1.8. there is no need to download if you are using Lucid 5.2 as it is the same.

I've also uploaded the 1.8 C source code

Hi tasmod I'm finally introducing firewallstate into 2.14X, The only thing if possible I would like to see is a large reduction of task on the right click menu, most of those extra's aren't needed and Psync isn't even included, I did try getting Psync going by using 5.2 parts, but I already have a little script that sets the time already that playdayz introduced into upup # hwclock --hctosys --localtime
works for me we also have the latest network monitor that has the X on the taskbar icon if it isn't connected, if you click that it brings up the network manager, etc.
Here how I would like to see it, if possible, I did try to compile the sources but they didn't do anything. what compiling command routine do you use? I tried
gcc `pkg-config --cflags --libs gtk+-2.0` -o "firewallstate-1.8.c" "firewallstate-1.8.c"
but no bin was made. Thanks very much for this great and well needed app.
ttuuxxx

what compiling command routine do you use?

a dragnNrop compiler what else
http://www.murga-linux.com/puppy/viewto ... 5&start=28

Joe

Thanks Joe that works like a treat , You know me I like simple lazy helpers
Now I can edit the code and make the menu more for 2.14X layout
ttuuxxx

already change it, reduced the extra apps and reduced what is displayed in the info related to the apps removed Now its just right I'm one happy camper now
Thanks again guys
ttuuxxx

Full install Lucid 5.2.5

If I select to turn off the firewall.
Firewall is turned off.
On reboot, firewall is back on.
Does not remember off setting on reboot.

New version 1.9 at users request.

=======

ttuuxxx & co.

Glad you like it, posted source for exactly that reason so people could modify to their needs, menu wise.

You never would think, a simple thing as, control of the firewall, would turn into a must have item.
This program has become a must have option.
Thanks for your willingness to make changes.
It just gets better and better!

I have recently found that this tool has an piece of VERY useful information. It contains private and public IP information on its right-click menu from the taskbar.

Does the tool provide a, hopefully time-stamped, log (or is there an option somewhere) of the Public IP addresses? I want to follow the IP changes that are made by my ISP during the course of the day. This could allow me to log and see internet up and down times when they occur.

Thanks in advance.

Not really the remit for Firewallstate.

I would say a simple script would do the job for you though.

The IP is derived from the net and is saved in the tmp folder under the name ipis.txt. This is of course cleared each time the system is shut down.

Look in the /usr/local/firewallstate folder for ipwget script which shows the two net addresses that return your own external address to you.
It should be fairly straightforward to save this to a standard text file in other than the tmp folder.

Thanks Tasmod.

Can you tell me how often this Information Page is updated?. I'm not sure if I need to do something to have it (Public IP) be current? Found this out after monitoring the "Information" for a day.

Thank in advance for this answer

Version 2.0 fixes Firewall ON/OFF in 5.2.8 and 5.2.9 as well as Slacko

Hello, tasmod !

Really like this application of yours; seen it/used it in many recent pups, where it's included by default.

I cannot find the sources for ver. 2.0 of the compiled file /usr/local/firewallstate/firewallstate, perhaps I missed the location of the sources by only reading this first page of the thread .........

Are the sources available for downloading somewhere?

Cheers / MHHP

MHP,

Sorry missed your post.

I'm almost sure that the version 1.8 source was very close to v2.0 but to be sure I uploaded version 2.0 source.

Note that there are other files called but they are annotated in the source and available in the pet. They are gtk scripts that can be read in Geany etc.

Version 2.1 posted.

Information window now updates when called. (So external IP report is correct)

I was asked why the change.

Well, on startup firewallstate retrieves the external IP address and the internal LAN IP. Then stops accessing after placing them in /tmp, this saves further processing.

On a reboot this information is refreshed, no problem, the information is correct.
However, if, as I discovered later, your router drops out and then re-syncs it obtains a new external IP but your system is still running and hasn't rebooted, only your router.
Firewallstate IP checking is not re-run, so the information isn't updated and is incorrect.

I therefore added a call when the right click menu item 'Information' is clicked, to re-run the IP scripts again, thus refreshing the information.

Funny how sometimes an event doesn't take place for quite a while to show up a 'bug'