Re: [pfSense] hi every body

2015-02-03 Thread Khurram Masood
It won't be a problem. Use a good hardware. Specially a good capacity NIC. Regards, _ Khurram Masood Manager Network (IT) Area Coordinator ISO 9000 Network Hardware Section Information Technology Department NED University of Engg. Tech, Karachi.

[pfSense] Unbound error in 2.2

2015-02-03 Thread Brian Caouette
Last 50 system log entries Feb 3 08:19:42 check_reload_status: Reloading filter Feb 3 08:19:41 php-fpm[69134]: /pkg_edit.php: Reloading Squid for configuration sync Feb 3 08:19:33 php-fpm[69134]: /pkg_edit.php: [Squid] - Squid_resync function call pr:1 bp: rpc:no Feb 3 08:19:33

[pfSense] Squid guard

2015-02-03 Thread Brian Caouette
What's the best way to handle custom sgerror.php pages with squidguard? Any time the package updates my custom page is over written. Sent from my U.S. Cellular® Smartphone ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list

[pfSense] dns to openvpn clients

2015-02-03 Thread Randy Bush
2.2-RELEASE (i386) i think i am configured to Redirect Gateway checked DNS Default Domain not checked DNS Servers / Provide a DNS server list to clients but the clients (viscosity) are not learning the dns clue bat, please randy ___ pfSense

Re: [pfSense] dns to openvpn clients

2015-02-03 Thread Kostas Backas
Hi, I have the same issue with viscosity and OS X clients. DNS works fine for internal queries, but no internet for connected clients. Windows clients are working fine. Στάλθηκε από το iPad μου 3 Φεβ 2015, 10:12 μ.μ., ο/η Federico Corradino spiorf...@gmail.com έγραψε: I had a similar

Re: [pfSense] dns to openvpn clients

2015-02-03 Thread Federico Corradino
I had a similar problem with openvpn-gui client on windows 7. The interface info showed the correct dns, and running nslookup everything looked fine, but normal windows applications didn't even tried to query a dns server, and just fail. I solved adding push route-method exe; push

Re: [pfSense] Unbound error in 2.2

2015-02-03 Thread Chris Buechler
That's what you would end up with if you have 2.1.x's dhcpleases binary running on 2.2, and I can't think of any other circumstance that would cause something along those lines. The former version didn't have the -u flag for unbound. Shouldn't be any way for that to occur short of manual