A few basic questions about features from a NOOB -
-
I believe if your running current version this is the default function now.. unless under misc you enabled this checkbox
"By default schedules clear the states of existing connections when the expiration time has come. This option overrides that behavior by not clearing states for existing connections. "
I would suggest test it before assuming it works is all.
-
@Hollander:
there are really so few, few, few, communities on the internet where you will find so many ex-tre-me-ly skilled and kind people who will help in case of problems. The FreeBSD spirit lives in this forum too).
I haven't been here long, but I can vouch for that. This forum has helped me a lot.
10-15 years ago, I was building Freesco boxes for friends and family for dialup. I guess I got lazy when broadband and wifi got common and used off the shelf.
I now can't imagine using a cheap, commercial router for anything other than an AP.
-
I believe if your running current version this is the default function now.. unless under misc you enabled this checkbox
"By default schedules clear the states of existing connections when the expiration time has come. This option overrides that behavior by not clearing states for existing connections. "
I would suggest test it before assuming it works is all.
Found it in Advanced/Misc! I will have a loock ath the states the coming evenings and come back with results… Many thanks!
-
Yesterday evening: 08:00 the Schedule closed down the internet for some users, at 08:38 the states of at least one of those users were still present (e.g. browser session). :-\
-
Sorry for the delayed response. Got a ton of stuff on my plate and so little time to manage it. Ughh.
@Holander - Yes, yes, yes and yes. LOL Couldn't agree with you more. I am an IT guy since Windows 95 and been running my own small biz IT shop for 14 tears…err, I mean years now. Never fooled with my own router though. Was tempted a few times but never did. For my clients, it was important to not monkey around so hardware appliances were the best route and for now I will keep it that way until I gain mad skillz with pfSense. lol I don't know Linux. I never run into it, never have clients ask about it, never needed to. My little pond is basically Windows, Windows, Windows...which is easier on me because I can focus on just that. But for me, pfSense is going to happen and then I am going to play with FreeNAS next year.
#2 While its possible to create timed firewall rules - you can run into a setup where the session is already active and working beyond your schedule.. You might want to schedule a reset of the firewall states for when your firewall rules change based upon time.
#3 While yes it is possible to allow access to the pfsense web gui from any interface - common security practices would say you wouldn't want to allow from the public internet - and even wireless might not be good idea. Wireless is quite often a vector of attack vs wired, so as mentioned you might want to limit firewall access to only from wired connections. But if your ok with the security implications - then sure you can allow access to the gui from anywhere you want from any device that can run a browser.
For #2 -
BINGO! That is what I was concerned about! As long as it is possible to resolve through a reset, I will be happy. I will do my research and learn how and test it.For #3 -
I just wanted to know for the sake that if I was watching TV and could quickly check or reset something, etc. from my Android phone or tablet, that would be nice. I also have my Win 7 laptop and could admin it via Wifi or LAN as well but a quick flip of the smartphone would be sweet. lolI believe if your running current version this is the default function now.. unless under misc you enabled this checkbox
"By default schedules clear the states of existing connections when the expiration time has come. This option overrides that behavior by not clearing states for existing connections. "
I would suggest test it before assuming it works is all.
Nice!!!!!!!!!!
@chemlud:
Yesterday evening: 08:00 the Schedule closed down the internet for some users, at 08:38 the states of at least one of those users were still present (e.g. browser session). :-\
OH NO! My fears return! lol
I was thinking of doing a Kabini build but since I am in no rush (just bought a Netgear R7000 3 months ago and this thing is handling everything I throw at it with DD-WRT KONG on it) I might wait to see if AMD puts Beema on a desktop socket! Would so love to build a box with that 10-15W TDP instead of 25W Kabini. I am sure there will be some kind of announcement in the next 60-90 days. ANd that is time for me to play with pfSense under VMWARE in my lab anyway.
-
If you are looking at a low power embedded build then consider booting from flash using the nanobsd images. Since they run almost entirely from RAM there isn't really an issue with unexpected shutdown. I pull the plug on home box without worrying at all.
Also…
@DownloadDeviant:I don't know Linux. I never run into it, never have clients ask about it, never needed to.
..before anyone else gets in, pfSense is built on FreeBSD. FreeBSD in not Linux. ;) But it is quite similar and since you know neither it makes no odds!
Steve
-
That was one of the things I was looking to investigate and learn about. I assumed that would be my best route. Now, I am a NOOB so I have not had a chance yet to research much but I figured either just a big old 8,16, or even 32GB USB flash drive or CF card would be fine. I even have an older Patriot 60GB Inferno SSD laying around collecting dust.
But I also have to figure out what other packages I will be running. I use a VPN service so OpenVPN, I also thought Squid/SquidGuard might be good. I don't know what else I will want to install or try but cannot imagine it would go beyond a 16GB USB drive.
-
Ok to answer your question about killing states. See my below example.
I listed the states for my workstation at home (I am vpn'd in currentl).. so see lots of states, I xxx'd out my public IP. I then killed the states for that 192.168.1.100 IP and it killed 18 states.. See when look at states for that IP none listed. Red arrow, then look again and 1 state, then look again a few seconds later I see more states.
So the command pfctl -k IPaddress could be setup to run when after your schedule kicks in to kill kids sessions. Or you could issue a pfctl -f state
Which would kill all states - if possible target just his IP.. so doesn't break your connections.
-
To quote Daffy Duck - "Juh-rool, Juh-rool!" ;D lol As in Drool Drool.
My mouth is watering just thinking about that running every single night, shutting things down and letting me relax!!!!!!!!!!
I think that works perfectly with my plan which was to basically lock things and allowing only specific devices by MAC address in general, then setting the time limit to his IP or MAC. Then that command could be run and it would leave everything else alone. Right now I have my DD-WRT config'd to shut off his access at 11pm and reboot at 11:01PM. But, as I have said, it is a 50/50 thing. Sometimes it works and sometimes he still can connect. Can't wait to kick his ass out in 3 more years…lol
-
How tech savvy is your kid? If it were me, I'd be running it against his MAC. At the least, most kids nowadays know how to change an IP address :P That can be spoofed as well, which returns to my original question, how tech savvy?
-
Ok to answer your question about killing states. See my below example.
I listed the states for my workstation at home (I am vpn'd in currentl).. so see lots of states, I xxx'd out my public IP. I then killed the states for that 192.168.1.100 IP and it killed 18 states.. See when look at states for that IP none listed. Red arrow, then look again and 1 state, then look again a few seconds later I see more states.
I added to the Cron tab two jobs for two different IPs:
Should work every 08:05 pm, huh? :-) I will monitor this…
-
Ok to answer your question about killing states. See my below example.
I listed the states for my workstation at home (I am vpn'd in currentl).. so see lots of states, I xxx'd out my public IP. I then killed the states for that 192.168.1.100 IP and it killed 18 states.. See when look at states for that IP none listed. Red arrow, then look again and 1 state, then look again a few seconds later I see more states.
So the command pfctl -k IPaddress could be setup to run when after your schedule kicks in to kill kids sessions. Or you could issue a pfctl -f state
Which would kill all states - if possible target just his IP.. so doesn't break your connections.
Useful, John, thank you for this suggestion ;D
But, as always, I don't understand it: you first kill the states, then they are re-restablished by the system, then you have to kill them again via a cronjob? But won't they be established again then?
Or more fundamentally: shouldnt the firewall schedule take care of this automatically? As in: this is not a bug, it is a feature'? ( ;D )
-
@Hollander:
Useful, John, thank you for this suggestion ;D
But, as always, I don't understand it: you first kill the states, then they are re-restablished by the system, then you have to kill them again via a cronjob? But won't they be established again then?
Or more fundamentally: shouldnt the firewall schedule take care of this automatically? As in: this is not a bug, it is a feature'? ( ;D )
If you kill the states after a scheduled "end of internet access" the states can't be re-established…
-
yeah mine was just an example of the command, I don't have any firewall rules blocking access on a schedule. Just showing that I killed them, and they show all gone. Then sure they will try and reconnect. But in the posters case his new scheduled rule will prevent them from being created.
-
How tech savvy is your kid? If it were me, I'd be running it against his MAC. At the least, most kids nowadays know how to change an IP address :P That can be spoofed as well, which returns to my original question, how tech savvy?
My thought as well. By extension, the MAC address can often be changed too. You may have better success in a small network by blocking all network traffic EXCEPT the devices that you specifically want to allow during your restricted hours.
-
Thank you John and Chemlud ;D
It would have been perfect if, on using the schedules, functionality had been built in to kill states for that rule automatically, but this workaround will work too.
How tech savvy is your kid? If it were me, I'd be running it against his MAC. At the least, most kids nowadays know how to change an IP address :P That can be spoofed as well, which returns to my original question, how tech savvy?
My thought as well. By extension, the MAC address can often be changed too. You may have better success in a small network by blocking all network traffic EXCEPT the devices that you specifically want to allow during your restricted hours.
Is it that easy to spoof your LAN-ip adress, from, say, Win7? For even kids?
:o
A partial workaround might be static IP with deny unknown clients' on the DHCP-server(?) Of course, that also hardly is 100% fool proof, as kid might simply scan the LAN and take ip of parent (provided parent isn't online).
-
@Hollander:
Is it that easy to spoof your LAN-ip adress, from, say, Win7? For even kids?
:o
All it takes is access to the device manager where the settings for the network adapter device offers you a field where you can enter the MAC address you want to use instead of the pre-programmed one.
-
@Hollander:
For even kids?
Especially for kids! They don't know it might be or should be difficult so they poke around until intil it's done. They've never known a computer that wasn't on the internet or a firewall that couldn't be eventually broken. Also they probably have a lot of friends who are also learning about this stuff and there's literally thousands of pages on the web explaining how to do it. Safer to assume kids know more than you! ;)
Steve
-
Especially for kids! …
DHCP, with static mapping based on MAC, with "deny unknown clients", with static ARP. What would be the work-around to get internet access? :-\
EDIT: Cron job for killing states works apparently fine! However, it looks as if states for one of the users were already killed when the firewall went to "BLOCK"… strange...
-
I'm not saying that it's impossible to lock down a computer to prevent 'unauthorised' internet access. It's easy enough to put a security policy on a Windows box to prevent users changing the MAC but how many home computers have that?
I'm just saying that most computer literate school age children have probably come up against some sort of web/connection filter at some point and those who are minded to do so have probably looked into ways to get around it. Someone they are friends with will have suggested finding the MAC of a local authorised machine from the ARP table and changing your MAC to it. That friend will then gain popularity for doing so. Everybody wins. Except the network admin/parents!It would be a mistake to assume that just because users are children they will not be familiar with basic networking. It's in their interests to keep you thinking they aren't. ;)
Steve
