That was it! I had not entered the gateway on the switch! Thanks for the help! It seems that I have a lot to learn, I was sure I had something configured wrong with pfSense

Not that I'm aware of

@signalz said in Var out of space, or is it?: I'm having a problem with /var supposedly running out of space. It's configured for 60MB, on the dashboard it shows 108% CPU usage, but du -mhs /var says it's only using 30MB. The DNS service crashes constantly and watchdog can't always restart it. I stopped snort as a temporary fix. I've had it set up for a while so I don't think that's causing the problem. My most recent changes on this box were a change to an alias used by snort's passlist and adding services to watchdog to monitor. Why is /var out of space but really not? Snort can use quite a bit of space in /var for its logs, especially on a busy network and if you have lots of Snort rules enabled and firing. What kind of hardware are you running on? Why is /var so restricted? That is where all of the logging happens.

So I came across this and I know it is a little stale, but thanks for the tips. I'm quite comfortable with VI, so that was no issue. I was just wondering why you didn't create a symbolic link? I think that would be actually simpler. I'm not clear if that will go away after a reboot, or a firmware/os update. I wanted to offload my Pfblocker data. I set it up yesterday and within a few hours it has filled up my var partition.

No problem. Let us know if that doesn't help. Steve

You'll need to configure a route to pass the customer to site 2 and also the reverse.

That's great to hear! As far as the YouTube content... Hmmm that's a tricky one! Might be a little bit beyond my pay grade! Ruling out a coincidence, I'd be thinking it's something to do with the port that they use or a connection (firewall state) being kept open, but I'd only be guessing.

I don't use this service, but a quick look at those instructions and it seems to me you'd want to do the following: At step 10, make a copy of the rule you created, edit it and change the gateway back to the default gateway. Make sure this rule is the last one in the list. Save the changes. When you want to route everything thru the vpn, leave things as is. When you want to route everything thru your ISP, disable the vpn gateway rule by clicking on its check mark and saving the changes.

Well, first off pfSense blocks everything coming in to WAN by default, so unless you add a NAT rule to pass through those ICMP packets, nothing will happen. Plus, the Block Private Networks setting will prevent WAN from responding to any private ip traffic unless you remove that restriction.

Why do you think the local LAN fails? The local LAN does not pass through pfSense. What happens if you try to ping another device?

@recklessop said in Keep config after a "hardware" change?: @bmeeks sorry... yes creating from a template... so new MAC's, UUID's, etc A template and a clone are sort of two radically different things. A template usually starts with a "fresh" un-configured version of the VM's OS such as Windows, or in this case, pfSense. A clone is a simple copy of an existing VM byte-for-byte. Sounds like you need to re-create your template by configuring a firewall to be just like you want it, and then using that VM to create your template. What's happening is the config.xml file in your template is in an out-of-the-box state instead of having your custom configuration stored within it.

@jimp said in OpenSSH User Enumeration: We pulled in patches for that to 2.4.4 a few days ago ( See https://www.netgate.com/docs/pfsense/releases/2-4-4-new-features-and-changes.html#security )> But your port 22 shouldn't be open to the world anyhow, especially not with Yep- Just for the naysayers our there.. I opened 22 on my test firewall this morning before I left for the field. As I sit here having lunch I checked in with it. Did an update (daily on this box) to the latest snap. Within seconds of it being back up IP's started connecting to port 22 trying to guess user/pass combos. 16 different IP's in five minutes. I can't imagine what that would be like if it had been open for days..

@clcporto said in Forced upgrade? 2.3 pkg repository disabled?: pkg-static install -f pkg Thanks for the response, it helped me a lot. my system worked after I gave this command via putty, and then System> Update> Update Settings Legacy stable version (Security / Errata only 2.3.x)

Hi Everyone. I tried the shell change , rebooted and all is well.

I seem to have gotten it working. Not sure, but it was the gateways for the OpenVPN was messed up. Between fiddling, with settings in OpenVPN and restarting the service, it seems to have fixed itself. As far as I can tell, I didn't change any settings, but what seem to fix it, was switching the vpn subnet addresses, then switching them back, seemed to fix itself. ?? Regardless it is working properly now.

@oddussiben-3161 said in Time to remove Growl ?: i might be out of bound, but can we consider having push notification maybe using telegram bot or pushbullet? That's a topic for a new thread, but if there is a notification method that has a lightweight client available for FreeBSD (read: few or no dependencies) then we can explore adding it in. I'm sure people would like to see things like Slack or other push notification services. I have not looked at what is out there to know what might make a good candidate. Start a new thread and perhaps others will chime in.