Hmm Same issue occurred VOIP SPA3102 is mapped (in States/States) to an old WAN IP address and fails to register. Manually deleted the two incorrect states and all is good again (new states formed with current WAN IP address) It seems the above config setting was not being followed? Thanks.

ARRIS  >:( >:( nothing  but problems since my ISP replaced the Cisco Modem with the Arris  :'( :'(

I am an idiot. I didn't catch what you guys meant by Double NAT until I actually sat down and thought about it. Logged into ISP router and fixed the forwarding and now it works. Thanks again all!

@johnpoz: Is this wifi or wired? 26MB is like watching paint dry for any sort of local copy..  So I take it this is wireless? If anything your hairpin should be slower then when using 2 different nics.. But what other traffic is flowing at time of copy on these nics? Yep, both situation is server on 1Gbps cable, client on 300Mbps wifi. For cable to cable it will be better. I can accept 26Mbps when on wifi, but 5 - 16Mbps is definitely too slow  :o I mean, for both conditions, gateway is involved, only difference is the first one is on same nic/port, second one involves two nic/ports. But all of them are 1Gbps, and I don't see high CPU usage or high memory usage  :-\ :-\

It's even written in the log. WSAEADDRNOTAVAIL - Impossible d'assigner la requête d'adresse

Even Splunk is free if you are pumping in <500 MB of logs per day.

Ok, so I'm totally messing this up and misunderstanding the rule requirements  :-. The new pfSense Definitive book arrives today, so it's a good time to update to 2.3.4 and reset things. Once I have more meaningful questions, I'll revisit this.

It isn't relevant to pfSense. That is a firmware/hardware issue on systems that support vPro. Nothing we sell has that feature, either, so the only way it would be relevant here is if someone happened to buy and use their own hardware with that feature.

Thanks a lot! I just have one problem, it doesn't show me the maps as you can see on the pic.  

Rate limiter in pfsense looks pretty easy to use ;) If your looking to rate limit inside your network use your switching infrastructure.. If your saying you limit your client to X that its not working?

http://lmgtfy.com/?q=syslog+server+howto

Is OPT1 your PIA interface?  Maybe try it with DNSSEC disabled and see if that makes any difference? I don't use OpenVPN, but this might help:     https://www.privateinternetaccess.com/pages/client-support/pfsense It doesn't seem like its DNSBL related, but you can use this trick to quickly bypass DNSBL while debugging this issue… Disable Cron in the General Tab Put a # in front of the "Server: include:" line in the Resolver and  "Save/Apply".... To reverse - remove the #, save and apply to re-enable DNSBL. Configure the cron setting. You could try to run a tcpdump command in pfSense to collect all DNS requests, and see whats getting blocked from those specific devices... See the details in the DNSBL Enable checkbox - blue info block icons.

You do not manage users and keys in the shell. Use the GUI. System > User Manager. Add keys in the field. Do not try to use the wheel group. Use the sudo package GUI to grant extra privileges.

Good, glad you were able to resolve this.

So, in this case there isnt way how to find inner ip? Exist something like package for logging with this option and necessary information? Or pfsense isnt able to log it? Our previous system based on linux with iptables was capable for it.

Sorry guys any help would be great please?

Thanks  you sir doktor. How about my suggestion is working?