Peasy Firewall Monitor

[rcrsn51]

Actually, the above might be a Peasyport issue. When I removed the firewall, Peasyport only reported back the ports above as being opened.

That's exactly how it should be. A port only opens if there is a service using it. Were you expecting to see all 1024 standard ports open?

Practical value is say you're using Python Simple Server. No?

Suppose you have Python Simple Server running on port 8000. So you allow that port on the firewall. All the firewall is now doing is blocking a bunch of other ports that aren't active anyway.

The value of the "trusted LAN" procedure is that it allows traffic through whatever ports you choose to open to anyone on the LAN, without having specify them individually.

It also lets you communicate with network devices that might be advertising their presence on ports that you don't know about.

[slavvo67]

The value of the "trusted LAN" procedure is that it allows traffic through whatever ports you choose to open to anyone on the LAN, without having specify them individually.

Forgive me, as networking has been one of my many weaknesses. So, you're opening the trusted LAN so if I open let's say Port 8000 on one computer, I can go to 198.162.0.0:8000 without having to open that port through the firewall and it will work because the computers are on the same local network?

Maybe you can give an example of how it would be used?

[rcrsn51]

Exactly.

But here is something else to consider. Assuming that you are on a LAN behind a router, the ONLY computers that can see the server are those on the LAN. In which case, why do you need a firewall in the first place?

Maybe you can give an example of how it would be used?

The objective of PFM is to give people who absolutely insist on running a firewall a tool that works, even though they don't need it.

The only people who might need a firewall are those with a public IP address and are directly exposed to the Internet. But they shouldn't have any ports open anyway because they aren't sharing anything.

[slavvo67]

Wow! Like if I tree falls in the woods and nobody is there to hear it, does it make a sound? Very enlightening. Thank you and thank you for the excellent tool!

[rcrsn51]

PFM began in 2013 because people were getting confused by the various Puppy firewalls. They couldn't get file/print sharing to work because the firewall was blocking it, even though they were certain that the firewall was off.

They needed a diagnostic tool that could show them EXACTLY what the firewall was doing.

Consider this: you install the firewall because you are concerned that malicious outside users can somehow "see into your computer". You then set up a SAMBA server to share data with your family, so you open Port 139 on the firewall. You just exposed all that data to those malicious users! Meanwhile, the firewall is protecting a bunch of other ports that aren't even active.

The firewall is having the opposite effect of what you want. The only thing that makes any sense is Trusted LAN.

[slavvo67]

One of the unexpected benefits of using your PFM was being able to simply use Plex with the build firewall for trusted LAN option. Streaming to my Roku just opened a new door.

I did come across an issue, today but I'm not sure if it's because of PFM or if it was my network. I was using a hotspot (phone) and for some reason, I think PFM was blocking it. The reason I think it was PFM is because when I shutdown the firewall and ran the usual linux firewall, my web started working. Like I said, it could have been my hotspot not working quite right but I'll test some more during the week and report back.

Thanks again,

Slavvo67

[rcrsn51]

If you had Trusted LAN set for your home network, then tethered to your phone, you are now on a different network. You would need to run Trusted LAN again to allow the new network.

[slavvo67]

No, this was at work; not using trusted LAN but launching the firewall with PFM. So, I did a complete shutdown of the firewall and used PFM to launch the regular firewall. Again, it could be me and my hotspot so I will test some more...

Thanks again!

[rcrsn51]

Actually, this raises an interesting question. If you join some other network, like a public hotspot, you probably DON'T want to be using Trusted LAN. You would be better off running the default maximum firewall. Let me get back to you on this.

If you run PFM for the first time and create the initial firewall, you get exactly the same one as if you run the Linux Firewall app from the Network menu.

[Edit] What Puppy are you using?

[rcrsn51]

PFM v1.9 posted above. See the Update note.

[slavvo67]

Actually Quirky Xerus 64bit. Actually my derivative RU Xerus64 but same thing, more or less. Actually, I can't wait to get any kinks out and add it to WoofQ and use it in my next update....

[slavvo67]

If you run PFM for the first time and create the initial firewall, you get exactly the same one as if you run the Linux Firewall app from the Network menu.

I'm not doubting you but there seems to be an inconsistency with that statement. I'll continue to test.

Is your update on page 1 64bit? - Thanks

Also,would you consider an icon update when say the firewall is temporarily shutdown. It would be nice to have that as a graphic indicator on screen.

[rcrsn51]

If you run the traditional Linux Firewall app from the Network menu and select "Automagic", it generates the script /etc/rc.firewall. When this script is run, it starts the firewall in your current session.

PFM uses that exact same script to build its initial firewall. It simply modifies the script to make Trusted LAN.

Is your update on page 1 64bit?

I will do that next on the page 3 download.

Also,would you consider an icon update when say the firewall is temporarily shutdown. It would be nice to have that as a graphic indicator on screen.

That's not going to happen. This has been the cause of problems in the past - when the icon gets out of sync with the actual status of the firewall. It's not worth the amount of code and CPU cycles needed to keep it in sync when all you need to do is click your mouse to get all the information.

[rcrsn51]

@slavvo67: I found a bug that sometimes prevents the firewall from auto-starting on the next boot. It is fixed in the 64bit v1.9 posted above.

[slavvo67]

Okay. I found it on page 3 and downloaded. I'll continue to test. Necessary or not, it's a very nice polished product. I think that I'll continue using it going forward. Will you continue to provide updates on the 64 bit version?

Again, very much appreciated.

[rcrsn51]

Will you continue to provide updates on the 64 bit version?

Yes, but I'm not expecting any. The current version does everything it needs to do, and I'm not planning to add any cute new features.

Thanks for all your help.

[rcrsn51]

Still v1.9 but with some code cleanup. Avoids some potential timing problems.

[rcrsn51]

For users who are afraid that their firewall might somehow spontaneously turn itself off, and really want a tray icon to inform them when it happens, and are willing to sacrifice the extra CPU cycles to run it, here is "a two-state solution". Install the attached PET.

[keniv]

I am using the latest v1.9 in the latest version of lucid 5282s2. Just tried the tray icon pet but it does not seem to alter it in any way. Am I missing something?

Ken.

[rcrsn51]

The only Lupu I have is lupu-5.2.8.7-20150702 and it works there. If you temporarily switch the firewall on/off, you should see the icon change from full-height to half-height.