Re: [pfSense] firewall rules with fqdn-alias

Hi Martin Do you have a dot at the end of the fqdn like in bind configs ? Pfsense doesnt like a dot at the end. With e.g. host.domain.tld It works fine With host.domain.tld. It works not So if you use a dot at the end please remove it Br Stephan Am 18.05.2016 00:12 schrieb "Martin Fuchs"

Re: [pfSense] Soeckris Net5501 SSD

The Intel S37xx is their data center line right? We've had some weird stuff in Windows and Linux servers get fixed by drive firmware updates. There have been multiple updates since fall 2015. Weird as in the Intel software in Windows showed both drives in a RAID 1 failed, though Windows

Re: [pfSense] firewall rules with fqdn-alias

Hi ! I recreated these alias tables with a shorter name (they were called dacotaHOSTS and now are called dacota) and now it works... Perhaps there might be some problem ? The problem however seems solved for now... regards, Martin > From: st...@teamits.com > To: list@lists.pfsense.org > Date:

Re: [pfSense] firewall rules with fqdn-alias

Hi ! I recreated these alias tables with a shorter name (they were called dacotaHOSTS and now are called dacota) and now it works... Perhaps there might be some problem ? The problem however seems solved for now... regards, Martin > From: st...@teamits.com > To: list@lists.pfsense.org > Date:

Re: [pfSense] firewall rules with fqdn-alias

Hi ! I recreated these alias tables with a shorter name (they were called dacotaHOSTS and now are called dacota) and now it works... Perhaps there might be some problem ? The problem however seems solved for now... regards, Martin > From: st...@teamits.com > To: list@lists.pfsense.org > Date:

[pfSense] IPv6 with Comcast and two pfSense - invalid prefix length, XID mismatch

We have an application with a Comcast-provided SMC router and two pfSense routers (Comcast <- building <- tenant). The building router (v2.3.0) gets an IPv6 address and can ping out. However in its DHCP logs I see: dhcp6c invalid prefix length 64 + 4 + 64 dhcp6c XID mismatch

[pfSense] Switching from 2.3.1 DEV to 2.3.1 REL ?

I had switched through the GUI to Branch development snapshots experimental while I was initially in 2.3-REL on some boxes. It helped a lot in the interim. Following announcement of 2.3.1-REL I just switched the GUI settings back to Stable branch. But upon checking for new update, it offers me

Re: [pfSense] IPv6 with Comcast and two pfSense - invalid prefix length, XID mismatch

On Wed, May 18, 2016 at 7:14 PM, Steve Yates wrote: > We have an application with a Comcast-provided SMC router and two pfSense > routers (Comcast <- building <- tenant). The building router (v2.3.0) gets > an IPv6 address and can ping out. However in its DHCP logs I see: >

Re: [pfSense] firewall rules with fqdn-alias

Hi ! Sounds reasonable, but there's no dot at the end ... Regards, martin -Ursprüngliche Nachricht- Von: List [mailto:list-boun...@lists.pfsense.org] Im Auftrag von WolfSec-Support Gesendet: Mittwoch, 18. Mai 2016 09:26 An: pfSense Support and Discussion Mailing List

Re: [pfSense] firewall rules with fqdn-alias

Is there a length limit for alias names? If it's an invalid alias I would think one of the logs should show something when the firewall rules are applied...I recall seeing errors in there before... -- Steve Yates ITS, Inc. -Original Message- From: List

Re: [pfSense] Soeckris Net5501 SSD

Karl, There are numerous other similar answers to be found, but here’s mine: Get away from CF if you can. The modern performance and wear leveling work is in sata and DOM, those are better devices. Abandon the nano-BSD and just find the miscellaneous checkbox to put /tmp and /var in

Re: [pfSense] Soeckris Net5501 SSD

Ed, you said it well here: "wear leveling work is in SATA and DOM" I think this is an important point, because If I understand correctly, there is nothing inherent to DOM or SATA to make it more or less suitable to the excellent implementations we've seen of over-provisioning, wear-leveling