@doktornotor: I think you can try to nuke /var/db/pkg and run pkg update - then you'll run into issues with files from packages that already exist but the pkg does not know about them, that is if you actually managed to install something before I just tried and it works well !! Thank you !!

thank you for your helps

No, it has not been fixed in 2.2.2. Either use a 2.2.3 snapshot or apply the patch manually. https://redmine.pfsense.org/projects/pfsense/repository/revisions/98615a3156d86aed1a560f109087d7e1ad4bf990

Glad to hear its working better, I've been liaising with Exetel to work through these fixes since late last week. I still see a heartbeat problem which means the connection drops more frequently than it should but at least it reconnects automatically. Would you mind checking your logs and seeing if you can identify how frequently your connection drops and reconnects?

Hello, I'm having this same error occur so when I look at the backup log one is firing off every hour which seems to much.  I believe it has something to do with pfBlockerNG updating every hour.  Is there a way to eliminate pfBlockerNG update from firing off the auto config updater? thanks, Jim

@KOM: But did you actually disable IPv6?  Read this: Block all IPv6 without logging and without bogonsv6 table One would think that when you chose to have IPV6 disabled that means don't freaking bother me with stuff like this. I wonder where the human element of these changes come from because I see no common sense to it. I am going to read that thread and then head to each and every box to turn this off… WHY?????????

That's SSDP/UPnP from your ZTE router. http://en.wikipedia.org/wiki/Simple_Service_Discovery_Protocol Just ignore it.

Indeed it was. I will definitely do that. Thanks for your feedback!

Go back to MicroCenter and buy a switch. Take back the wireless card and buy a separate AP. You'll have much better performance and coverage from the wifi.

@almabes: If you're not running the NanoBSD image put your pfSense box on a UPS.  The UFS filesystem doesn't like to deal with repeated failings of the local electrical utility.  That killed another customer pfSense firewall. After getting the bill for the firewall recovery, they had no problem with me installing a UPS. My PC, laptop, pfsense box and monitor are all hooked to a UPS.  I spent too much money on my main PC to trust the electrical of a 60 year old house.  :-)

I see….... I think i need to clean my glasses  :o

No, not reqs per sec. The Firewall - Traffic Shaping - Limiter -> using dummynet. (Yeah, CP uses dummynet as well.)

When you say "failover does not work" what do you mean specifically? You may have a firewall rule preventing traffic from the LAN routing over the other WAN connection.  Can you verify that a client on the LAN can route successfully out of both WAN connections?  I usually hit something like checkip.dyndns.org to see where I'm routing out of.

I will need to change up my internal address's as im currently using the 192.168.1.X range at home and have a bunch of static addresses that would need to be changed to avoid conflicts. pfSense's DHCP server for LAN makes handling "static" internal addresses very easy, just set all your devices to use DHCP and assign the addresses you want them to have as entries in the DHCP server "DHCP Static Mappings" table. Leveraging the DNS features in pfSense can greatly simplify your life across two linked subnets.  With a little proper setup you can create different domains for each house, say "freenhm1" and "freenhm2".  Then a computer or device on each network (say "mywrkpc") could be addressed as "mywrkpc.freenhm1" or "hiswrkpc.freenhm2" without having to remember all the IP addresses. As in all things computer related, pre-planning is your friend.  But pfSense gives you plenty of flexibility to accommodate most things you can think of….