ack to the pfSense...
I do not find this solution very elegant but what can you do? :-)
Regards,
Philipp
-Original Message-
From: List [mailto:list-boun...@lists.pfsense.org] On Behalf Of Lars
Wuerfel
Sent: 9 August, 2016 7:26
To: list@lists.pfsense.org
Subject: Re: [pfSense] DNS-forwarder thro
August, 2016 7:26
To: list@lists.pfsense.org
Subject: Re: [pfSense] DNS-forwarder through OpenVPN "stopped working"
with 2.3.2
Philipp,
I am facing the same problem here since the Upgrade to 2.3.2
DNS resolution through the OpenVPN tunnel works with site2site VPN.
But it doe
? :-)
Regards,
Philipp
> -Original Message-
> From: List [mailto:list-boun...@lists.pfsense.org] On Behalf Of Lars
> Wuerfel
> Sent: 9 August, 2016 7:26
> To: list@lists.pfsense.org
> Subject: Re: [pfSense] DNS-forwarder through OpenVPN "stopped working"
> with 2.3
Philipp,
I am facing the same problem here since the Upgrade to 2.3.2
DNS resolution through the OpenVPN tunnel works with site2site VPN.
But it does not work with with remote login from my laptop.
This worked up to version 2.3.1_p5
Do you have a solution meanwhile?
Thanks and Regards
Lars
On
Hi again,
> From: Philipp Tölke [mailto:philipp.toe...@fos4x.de]
> Sent: 27 July, 2016 16:01
>
>> Check the system routing table. From the sound of the errors, it would
>> appear that the firewall routing table does not include a route back to
>> the VPN client subnet.
>
> Interesting: The
Hi all, Hi Jim,
Thanks for your fast reply!
> From: Jim Pingle
> Sent: 27 July, 2016 15:37
>
> On 07/27/2016 08:45 AM, Philipp Tölke wrote:
>> since the update to 2.3.2 yesterday our external devices do not get
>> DNS-Replies anymore.
>
> What version was this firewall running previously?
2.3.1
On 07/27/2016 08:45 AM, Philipp Tölke wrote:
> since the update to 2.3.2 yesterday our external devices do not get
> DNS-Replies anymore.
What version was this firewall running previously?
> We have configured the DNS-Forwarder to listen on the interface and
> sockstat show it's listening on
Hi all,
since the update to 2.3.2 yesterday our external devices do not get
DNS-Replies anymore.
We have configured the DNS-Forwarder to listen on the interface and
sockstat show it's listening on *:53. We have a rule allowing everything
to pass to "self" on port 53.
With tcpdump I can see that
