Peasy Firewall Monitor

[tuxtoo]

Many thanks rcrsn51, works like a dream and I hope you don't mind that I have repacked it for Puppy-4.xx

As peasyfwmon-1.4.pet doesn't have a tray icon in Puppy-412 I have repackaged it with a desktop icon for quick access.

[rcrsn51]

Excellent. I was looking at compiling the tray applet for Puppy 4, but a desktop shortcut is just as good.

[fr33land]

Version 1.5 posted above.

[rcrsn51]

Version 1.6 is posted above. See the Update note.

[keniv]

Hello rcrsn51

I have installed version 1.5 in 412 lite and 410 smp and it works perfectly. Thank you for that. I also use wary 5.5.1 with some extra updates. It nearly works but the first window I see is corrupted. However if I click either OK or Cancel I get the second window which is fine. It can be used to set the tray icon. What I think is the correct first window can also be made to appear. If I re-boot the process is repeated. Is there a way to get it to work properly with wary 5.5.1.

Regards,

Ken.

[rcrsn51]

This app is using standard Xdialog tools to create the two windows. I tested it in Wary 5.5 and it worked fine for me. Your problem must have something to do with your particular video setup.

[keniv]

I,posted already but it has disappeared so I'll repeat it.
I have taken some images in the hope it will help.
Image1 shows the corrupted window.
Image2 shows the window I get if I press OK or Cancel in the first.
Image3 I can bring up from window2. I think it is a good version of window1.
Image4 is the syst info for my monitor. I use XOrg but without the extra driver I use with lucid.
If image2 is a good version of window1 I don't understand how the video set up. Hope this helps.

Regards,

Ken.

[rcrsn51]

This isn't video corruption - PFM is trying to detect what ports in the firewall are open and is getting confused. I'm guessing that you already had the firewall installed when you first ran PFM.

Get v1.6 - it detects open ports a different way.

I don't understand how you are getting from the second window back to the first window - there is no path to do that unless you re-run the program.

[keniv]

OK I'll do it now and report back. I did have the firewall running when I installed v1.5. I'll switch it of before I install v1.6.

Ken.

[rcrsn51]

I don't understand how you are getting from the second window back to the first window - there is no path to do that unless you re-run the program.

Please answer.

[keniv]

I don't understand how you are getting from the second window back to the first window - there is no path to do that unless you re-run the program.

Please answer.

I have just removed v1.5 and replaced it with v1.6. V1.6 is working perfectly in wary. Thank you for that. I'm sorry but I can't exactly remember how I got from image2 to 3. I got from 1 to 2 by clicking OK or Cancel on the corrupted window. I clicked on the button in 2 to bring up the tray icon and clicked OK.This is the point where I'm not sure what I did next. I did however click on the icon a couple of times. I also re-ran the firewall from the window. I also looked in /root/startup to make sure there was something relvant in there. I also rebooted the machine to check the firewall started. I also ran iptables -L -n in a terminal to make sure the firewall was running.
I hope, from the above, you can work out from this how I got to image3.

Regards,

Ken.

[rcrsn51]

Thanks. I have added a post-install script to the PET that removes any existing firewall. That will make PFM build a new basic firewall on the first run.

[keniv]

I think thats a good idea. I did not think to shut off the firewall before I installed v1.5. I'm wondering if I should install v1.6 in 412 lite and 410 smp. v1.5 works with these two. I'd appreciate your advice.

Ken.b

[rcrsn51]

That's up to you. The major changes in v1.6 are with detection of open ports and building the firewall for trusted networks.

[greengeek]

I also ran iptables -L -n in a terminal to make sure the firewall was running..

I am interested to know what information this command offers. Does my output ring any alarm bells with you? -

Code: Select all

# iptables -L -n
Chain INPUT (policy DROP)
target     prot opt source               destination         
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0            state RELATED,ESTABLISHED
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0            state NEW
TRUSTED    all  --  0.0.0.0/0            0.0.0.0/0            state NEW

Chain FORWARD (policy DROP)
target     prot opt source               destination         

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination         
DROP       icmp --  0.0.0.0/0            0.0.0.0/0            state INVALID

Chain TRUSTED (1 references)
target     prot opt source               destination         
ACCEPT     icmp --  0.0.0.0/0            0.0.0.0/0            icmptype 8
DROP       icmp --  0.0.0.0/0            0.0.0.0/0           
REJECT     all  --  0.0.0.0/0            0.0.0.0/0            reject-with icmp-port-unreachable
# 

[keniv]

@greengeek
Your output from iptables -L -n is very like mine. I can't check just now as I don't have access to my old laptop and am replying on a phone.
I'm no expert on this stuff. I asked on another thead how I could tell if the firewall was running. This was what was suggested. I think it displays your set of rules. I think if the firewall is not running they would not be displayed.

@rcrsn51
I think I'll stick with v1.5 for 412 lite and 410 as their not on a local network .

Ken.

[rcrsn51]

Version 1.7 is posted above. It has a single-window user interface.

[keniv]

Now using v1.7 in all four pups. Working in all of them.

Ken.

[rcrsn51]

Excellent. Thanks for testing.

[rcrsn51]

Version 1.8 posted above.