On 2015-Mar-05, at 11:46 AM, Chris Buechler wrote:
> The description of what's enabled/disabled got confused from Jim's
> earlier post I think. LRO and TSO are both disabled by default,
> hardware checksum offloading is enabled by default.
Just for the record, Jim's message ended with:
---
It’s
> See if this helps:
>
> https://doc.pfsense.org/index.php?title=Redirecting_all_DNS_Requests_to_pfSense&redirect=no
>
>
This works perfectly! Thank you. Resolving using Google's DNS now returns
our internal servers.
Wow this list is fast :)
Thanks again everyone.
Marc
__
On Thu, Mar 5, 2015 at 9:16 PM, Chris Bagnall
wrote:
>
> This. Out of interest, is there a particular reason why you need to use
> Google's public DNS at all - especially now that pfSense 2.2 has a 'proper'
> DNS resolver (rather than just a cache)
I hadn't seen this, thanks for pointing that o
On Thu, Mar 5, 2015 at 1:26 PM, DV wrote:
>
> On Wed, Mar 4, 2015 at 10:17 AM, Jim Thompson wrote:
>>
>> In case it’s not clear by now, these settings are all *disabled* by
>> default in pfSense.
>
> I am pretty sure that I haven't changed these settings in my various
> production pfsense devices
Marc Peiser wrote on Thu, Mar 5 2015 at 12:48 pm:
> So I was thinking I could route some publicly available DNS servers like
> googles via my VPN but forward the request onto my nameservers to answer
> instead.
See if this helps:
https://doc.pfsense.org/index.php?title=Redirecting_all_DN
On Thu, Mar 5, 2015 at 9:02 PM, Vick Khera wrote:
>
> It seems like you should figure out why your client VPN software is
> broken, and fix that.
>
>
We have a mix of mac, linux and windows desktops, they all seem to have
issues so I'm looking for a cleaner solution rather than trying to
patch/fi
On Wed, Mar 4, 2015 at 10:17 AM, Jim Thompson wrote:
> In case it's not clear by now, these settings are all *disabled* by
> default in pfSense.
I am pretty sure that I haven't changed these settings in my various
production pfsense devices, but they all have "Disable hardware checksum
offload
On 5/3/15 7:02 pm, Vick Khera wrote:
It seems like you should figure out why your client VPN software is broken,
and fix that.
This. Out of interest, is there a particular reason why you need to use
Google's public DNS at all - especially now that pfSense 2.2 has a
'proper' DNS resolver (rath
On Thu, Mar 5, 2015 at 1:48 PM, Marc Peiser wrote:
> Any ideas how I might make this work? Or is there a better solution to
> this problem?
>
It seems like you should figure out why your client VPN software is broken,
and fix that.
My personal solution was to just make the internal hostnames re
On Wed, Mar 4, 2015 at 5:08 PM, Jim Thompson wrote:
> > Ah, so I should have asked _before_ ordering the NICs? $;-)
>
> There are many of you, and few of us.
>
As a Netgate and pfSense customer, I think it would help *everyone* if you
just posted the "special" settings for the devices you sell.
Hi everyone
I'm having a few issues with our internal DNS servers and our openvpn
clients. We run some internal dnsmasq forwarding nameservers (10.10.10.10 &
10.10.10.20) to resolve internal hosts that aren't resolvable publically.
I've configured openvpn to push these nameservers to the client to
11 matches
Mail list logo
