Peasy Firewall Monitor
The tray applet is a 32bit binary, so you need a 64bit version. Attached below, but I don't know if it will be compatible. Please report.slavvo67 wrote:Installed in Quirky Xerus64 (actually RU Xerus but interchangeable from my standpoint). Seems to work except for the install tray applet.
[Edit] This version is also compatible with Fatdog.
That's the thing about firewalls. The only true test is to run from a second machine and probe the first machine with a tool like PeasyPort.Seems to work
---------------------------
- Attachments
-
- peasyfwmon_64bit-2.1.pet
- Updated 2017-07-25
Recognizes multiple networks - (23.91 KiB) Downloaded 587 times
-
- peasyfwmon_2state_tray_64bit-1.0.pet
- (5.24 KiB) Downloaded 602 times
Last edited by rcrsn51 on Tue 25 Jul 2017, 18:19, edited 14 times in total.
The tray applet seems to be working --- Thank you! Thank you for the Peasyport tip. I'll have to test a little....
I have a suggestion but I'm not sure if it's practical or how difficult to accomplish. It would be nice to have a box that says Open Port [ _ _ ] to simplify opening a specific port #. Then, you would probably need a close port X or close all ports. Just a thought but it's nice, either way!
I have a suggestion but I'm not sure if it's practical or how difficult to accomplish. It would be nice to have a box that says Open Port [ _ _ ] to simplify opening a specific port #. Then, you would probably need a close port X or close all ports. Just a thought but it's nice, either way!
When I temporarily turn off the firewall, only ports 139 and 445 reflect as being opened using Peasyscan with a different computer.
Actually, the above might be a Peasyport issue. When I removed the firewall, Peasyport only reported back the ports above as being opened.
Practical value is say you're using Python Simple Server. No?
Update: I see what you're doing. So you're using port 24 for trusted LAN and that can be used with Python Simple Server as well as any. So, only question is can you turn off the trusted lan (port 24) without shutting down the firewall and restarting?
Also, still checking on the Peasyport discrepancy. I may have had the firewall up on the computer using Peasyport to scan. Still, not sure why it would show 2 open ports when that computer would be locked down..... I'll let you know what I find...
Actually, the above might be a Peasyport issue. When I removed the firewall, Peasyport only reported back the ports above as being opened.
Practical value is say you're using Python Simple Server. No?
Update: I see what you're doing. So you're using port 24 for trusted LAN and that can be used with Python Simple Server as well as any. So, only question is can you turn off the trusted lan (port 24) without shutting down the firewall and restarting?
Also, still checking on the Peasyport discrepancy. I may have had the firewall up on the computer using Peasyport to scan. Still, not sure why it would show 2 open ports when that computer would be locked down..... I'll let you know what I find...
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?slavvo67 wrote:Actually, the above might be a Peasyport issue. When I removed the firewall, Peasyport only reported back the ports above as being opened.
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.Practical value is say you're using Python Simple Server. No?
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.
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?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.
Maybe you can give an example of how it would be used?
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?
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.
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?
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.Maybe you can give an example of how it would be used?
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.
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.
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.
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
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
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?
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?
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....
Last edited by slavvo67 on Thu 23 Feb 2017, 04:42, edited 1 time in total.
I'm not doubting you but there seems to be an inconsistency with that statement. I'll continue to test.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.
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.
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.
PFM uses that exact same script to build its initial firewall. It simply modifies the script to make Trusted LAN.
I will do that next on the page 3 download.Is your update on page 1 64bit?
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.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.