[pfSense] Hostname resolution of OpenVPN-connected clients

2015-11-11 Thread Marco
Hello, we use pfSense since quite a while with success and are very happy overall. Recently we set up OpenVPN and are facing a DNS issue. Hosts in the LAN can be addressed using the hostname (thanks to “Register DHCP leases in the DNS Resolver”) which is working perfectly fine. Hosts on the

[pfSense] 2.2.5 squidGuard fails to start

2015-11-11 Thread Volker Kuhlmann
After squid and squidguard updates it is neccessary to re-download the blacklist before attempting to restart squid/guard. Done. When applying the squidguard config https://xxx/pkg_edit.php?xml=squidguard.xml=0 An error results and squid isn't running. No change after several iterations of squid

Re: [pfSense] [Bulk] Re: darkstat

2015-11-11 Thread Josh Karli
Apparently my package installations were corrupted during the upgrade from 2.2.4 amd64 to 2.2.5 amd64. It had the reinstalling packages warning for hours after the install, then i had to unlock them and manually reinstall them. For some reason darkstat went away after I uninstalled and then

Re: [pfSense] Latency issues with 2.2.25 Release

2015-11-11 Thread Jon Gerdes
On Wed, 2015-11-11 at 07:47 -0800, Wade Blackwell wrote: > Good morning list, >I recently upgraded to *2.2.5-RELEASE * (amd64) on a VMware > stack > and noticed that my Wan latency shot up by about 100ms rtt. Nothing > else on > the box had changed. I reverted to a pre-upgrade snapshot and

Re: [pfSense] Hostname resolution of OpenVPN-connected clients

2015-11-11 Thread Espen Johansen
I think you have to set up a radius server and assign ip based on the user. That way they will be "static" and then add DNS entries to that static IP. My 2cents, -lsf ons. 11. nov. 2015, 15.47 skrev Marco : > Hello, > > we use pfSense since quite a while with success and are

[pfSense] Latency issues with 2.2.25 Release

2015-11-11 Thread Wade Blackwell
Good morning list, I recently upgraded to *2.2.5-RELEASE * (amd64) on a VMware stack and noticed that my Wan latency shot up by about 100ms rtt. Nothing else on the box had changed. I reverted to a pre-upgrade snapshot and the latency went back down to 10-12 ms rtt. Anyone seen anything

Re: [pfSense] Hostname resolution of OpenVPN-connected clients

2015-11-11 Thread Vick Khera
On Wed, Nov 11, 2015 at 2:46 AM, Marco wrote: > How to access the mobile hosts via the same hostname regardless if > they are connected to the LAN or VPN? > Via some form of dynamic DNS perhaps? It seems it should be possible to have the openvpn client run some script that