The pfSense Store

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - El Scorcho

Pages: [1]
1

I arrived here via Google looking for the answer to this problem and wanted to comment on this because it does matter.

In ESXi you can't do snapshots (or backups via tools like Veeam) unless ESXi thinks the host is in a consistent state. As long as this message appears, ESXi thinks the host is inconsistent, so no snapshots/backups.

I just just took a snapshot of pfSense 2.4.1 CE vm in ESXI 6.5. Whatcha talking about?

I'm running ESXi 6.5.0 Update 1 (Build 6765664). I'm running pfSense 2.4.1-RELEASE (amd64).

ESXi reports "The configured guest OS (FreeBSD (64-bit)) for this virtual machine does not match the guest that is currently running (FreeBSD 11.1-RELEASE-p2). You should specify the correct guest OS to allow for guest-specific optimizations." for my pfSense VM.

If I attempt to take a snapshot of the pfSense VM ESXi errors out with "Failed - The operation is not allowed in the current state."

That's what I'm talking about.

2
I don't think that warning really matters.  VMWare is simply not properly identifying the Guest OS but you already manually selected FreeBSD, so the drivers and hardware emulation is accurate.  The same occurs when I update to brand new releases of macOS or Ubuntu builds.

I arrived here via Google looking for the answer to this problem and wanted to comment on this because it does matter.

In ESXi you can't do snapshots (or backups via tools like Veeam) unless ESXi thinks the host is in a consistent state. As long as this message appears, ESXi thinks the host is inconsistent, so no snapshots/backups.

3
OpenVPN / Re: Clients can't connect after Site to Site Tunnel
« on: June 30, 2014, 07:52:09 pm »
Hmm. No local DNS resolution, but no routes to the Internet either. Frustrating.

4
OpenVPN / Re: Clients can't connect after Site to Site Tunnel
« on: June 30, 2014, 07:32:46 pm »
Oof. I've narrowed it down to DNS, but I can't figure out for the life of me why it's not working. I've tried giving the clients all manner of DNS server, including local servers. I've also tried not providing DNS servers to the clients. Neither works.

I'd still appreciate any help anyone might be able to offer.

5
OpenVPN / Clients can't connect after Site to Site Tunnel
« on: June 28, 2014, 09:39:01 am »
Hi, all. Any help with this issue would be appreciated. I'm still fairly new to pfSense, so patience is also appreciated.

For several months now I've been running an OpenVPN server on pfSense at Site A, with an OpenVPN client on pfSense at Site B. This is a peer-to-peer shared key tunnel that routes all LAN traffic from Site B to Site A. This has been working very well since we implemented it.

However, prior to implementing the site to site tunnel we were using an OpenVPN server at Site B for remote clients to connect back to the Site B LAN. Since the implementation of the site to site tunnel, this has stopped working. Clients can still connect to the OpenVPN server at Site B, but can't access the LAN or Internet. This leads me to believe there's a routing issue, but I can't figure out what it might be.

I'm not sure what other information would be helpful for troubleshooting, but I'm happy to fetch it.

Thanks much!

6
Installation and Upgrades / Re: Patching/Upgrading OpenSSL
« on: April 08, 2014, 12:01:58 pm »
Thanks for letting the rest of us know!

7
Installation and Upgrades / Re: Patching/Upgrading OpenSSL
« on: April 08, 2014, 09:55:23 am »
Nice rant. However, you should focus that rant at the openssl guys who introduced this brainfart in the first place... Additionally, reading the source code, the entire openssl thing needs a rewrite from scratch.

That strategy isn't helpful for fixing the product that we're here to discuss, which is still vulnerable.

I really like pfSense, but the response here is discouraging. This is being treated quite seriously and with high priority almost everywhere else, but here it seems the users are being lectured for even asking about a fix.

Pages: [1]