Re: [pfSense] IPv6 nat

You can use NPT Em 16 de nov de 2017 5:19 PM, "Daniel" escreveu: > Hi there, > > > > i added a privat ipv6 LAN on my pfsense which has to do NAT like on IPv4. > > > > But it seems that NAT with ipv6 is not possible. Is there anyway or is it > not possible to NAT IPv6

[pfSense] IPv6 nat

Hi there, i added a privat ipv6 LAN on my pfsense which has to do NAT like on IPv4. But it seems that NAT with ipv6 is not possible. Is there anyway or is it not possible to NAT IPv6 Connections? root@web1:~# traceroute6 heise.de traceroute to heise.de (2a02:2e0:3fe:1001:302::), 30

Re: [pfSense] acme package: DNS-nsupdate configurable update zone

On Thu, Nov 16, 2017 at 4:22 AM, Brian Candler wrote: > On 16/11/2017 10:30, Brian Candler wrote: > >> Unfortunately in the pfSense (2.4.1) GUI, I can't see a way to configure >> this. >> >> I would like either: >> >> - an extra setting for "dynamic update zone", which is

Re: [pfSense] Packetloss

I don't have a specific answer but if you know the setting you can try the System > Advanced, System Tunables page. -- Steve Yates ITS, Inc. -Original Message- From: List [mailto:list-boun...@lists.pfsense.org] On Behalf Of Daniel Sent: Thursday, November 16, 2017 6:36 AM To: pfSense

[pfSense] Packetloss

Hi there, as some of you guys know i had a lot of packetloss. It is/was because the WAN Interface runs full of traffic. Normaly behavour is the no packets gets droped. They get queued as I understand and the ping RTT increase extremely. It seems I need to increase in TCP Buffer size.

Re: [pfSense] acme package: DNS-nsupdate configurable update zone

On 16/11/2017 10:30, Brian Candler wrote: Unfortunately in the pfSense (2.4.1) GUI, I can't see a way to configure this. I would like either: - an extra setting for "dynamic update zone", which is appended to the nsupdate name - an override for the whole name (i.e. can replace

[pfSense] acme package: wrong agreement URL

Trying to use the acme package with pfsense 2.4.1 and the LetsEncrypt staging server Certificate enrolment failed, although all the output was in green. /tmp/acme//acme_issuecert.log shows HTTP 400 errors, with the following response: [Thu Nov 16 10:28:19 UTC 2017]

[pfSense] acme package: DNS-nsupdate configurable update zone

Hi, I have a feature request which I thought I'd discuss here before creating a ticket. I use Letsencrypt with the DNS01 challenge, so I can get certs for internal DNS names which are not reachable over the Internet. To avoid making all my zones subject to dynamic updates, I use CNAME

Re: [pfSense] Error Captive Portal

On 11/16/2017 01:28 AM, Kleber Carvalho wrote: Any idea what can I do about it ? You could start off by providing what version you're running. Doug ___ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with