removed

Eventually, perhaps, but there are a lot of people out there that still insist on using it despite its shortcomings. There is a big red warning in the next version of pfSense warning people off of it.

You notice there is no specific dns suffix when you get other dns servers. I would sniff the traffic actually and verify that server is sending bad and not sending missing info. This will also verify its not a different dns server since you will see the mac in the sniffs of the dhcp server your talking to. I am running 2.1-BETA0 (i386) built on Fri Nov 2 10:50:45 EDT 2012 FreeBSD 8.3-RELEASE-p4 And have never seen such an issue - curious why such a low lease time? 2 hours seems a bit low unless you change information often?

works fine now, thanks ermal

This morning i updated to version 2.1-BETA0 (amd64) built on Thu Nov 8 16:38:54 EST 2012 and the problems are gone. CARP is working now with dual stack (IPv4 and IPv6 are both working). There are no more errors coming in the log files now. Thank you for fixing this.

So most of that is multicast UDP non-234-179.ipredate.net.50023 > 239.100.5.1.1234 And a bunch of other .2, .7, in this same multicast range I would guess IPTV based stream???  But without seeing the actual packet details its hard to say for sure. ipredate.net – I show that as NetRange:      208.87.32.0 - 208.87.39.255 CIDR:          208.87.32.0/21 OriginAS: NetName:        SECUREHOST Could be someone trying to request some sort of video stream? Clearly ODD, you might be able to gleen some better info from the details of the packets.  Do a capture on pfsense diag, and then open it up in your fav analyzer -- wireshark for example

ermal has put in a patch, the next snap should fix this issue for limiters with schedule set as none

Gotcha, thanks for clarifying in any case :)

i had spoken to creater of alix for a upgraded board and the below is what he said apu = AMD 1 GHz dual core, 2 or 4 GB DDR3, 3 RTL8111E Gigabit Ethernet, 2 miniPCI express, 1 m-SATA SSD, 1 SD card connected via USB, same form factor as alix2d13. Expected ~ Q1 2013.

I will try, but pfSense-Full-Update-2.1-BETA0-i386-20121106-0041.tgz ipv6 tunnel not work. I will waiting for good version.

confirm it work on my side too.

i have the same issue on PE860 stuck at 38% any solution ?

ahh well i see. yes that could be the problem ;-)

In the meantime: dnsmasq has been bumped to the latest version, feel free to check out snapshots.

Thanks jimp.

Try to put the Preprocessors >  Max Queued Bytes 11048576 (10 MB) or above and the Max Queued Segs 30000 or above. See if that works for you.

Hey, thanks for the reply, but can you be a little more specific? Which one: "Firewall Maximum Tables" or "Firewall Maximum Tables Entries"? Both are blank. EDIT: I've increased the "Firewall Maximum Table Entries" to 200000 since the word count for /etc/bogonsv6 was 63301. Hope this will solve the problem. Cheers, Szop