Hi,
The example wildcard DNS record given here :
https://doc.pfsense.org/index.php/Wildcard_Records_in_DNS_Forwarder is
inaccurate w/pfsense 2.2.
Thanks to this post (
https://unbound.net/pipermail/unbound-users/2009-April/000560.html ) I
have been able to set a wildcard, with the
I think this issue has been solved:
- issue was errors similar to:
---
[ There were error(s) loading the rules: pfctl: DIOCADDRULE: Invalid argument -
The line in question reads [0]: ]
---
and/or an error indicating that it can't allocate memory (but there's over 50%
of the memory reported as
That's definitely the cable modem's NAT getting confused. If you can get the
phones to randomize their source ports on their OpenVPN traffic, that might
resolve. I'm not sure if that's possible on those phones. In stock OpenVPN,
specifying lport 0 in the config will make it choose a random
On 19 February 2015 at 14:51, Chuck Mariotti cmario...@xunity.com wrote:
That's definitely the cable modem's NAT getting confused. If you can get
the phones to randomize their source ports on their OpenVPN traffic, that
might resolve. I'm not sure if that's possible on those phones. In stock
On 02/19/2015 07:03 AM, Guillaume wrote:
The example wildcard DNS record given here :
https://doc.pfsense.org/index.php/Wildcard_Records_in_DNS_Forwarder is
inaccurate w/pfsense 2.2.
The page is correct, but if you note the name it was specific to the DNS
Forwarder only (dnsmasq), not the DNS
You could try TCP for the OpenVPN if the phones will support it. The vast
majority of your traffic will be UDP so you wont get the joy of TCP in TCP
exponential standoffs.
Cheers
Jon
The phones do support TCP (an option on a per line basis offers UDP/TCP).
Could you clarify what you mean by
Ya, I am testing that in lab now with an Asus rt-ac68u I have. Going to see
what behavior is for disconnects, etc... Will also have to figure out how to
remote into the phones and the rules, etc...
From: List [mailto:list-boun...@lists.pfsense.org] On Behalf Of Odhiambo
Washington
Sent:
Le 19/02/2015 14:27, Jim Pingle a écrit :
On 02/19/2015 07:03 AM, Guillaume wrote:
The example wildcard DNS record given here :
https://doc.pfsense.org/index.php/Wildcard_Records_in_DNS_Forwarder is
inaccurate w/pfsense 2.2.
The page is correct, but if you note the name it was specific to the
