@BlueKobold: What else can I try? This is new pfsense box… See above. What kind of connection method you were setting up at the pfSense box? DHCP, static public IP address or something else? Is the Arris a pure modem or a router? After rebooting the pfSense was the given MAC address from you also inside or gone? Perhaps you might be needing the new MAC Adress from the new Arris modem? Please help! I am pulling my hair out! Don´t do so this only looks good for Bruce Willis! Thank you all for the help. I had Charter switch out the cable modem from the Arris to a cisco modem. Fired up the cisco and it worked instantly …. even without having to change the mac address. It seems like on another forum I had read where some of the newer cable modems don't work with pfsense.  Thought I would share for someone else who might have the same issue. Here is another person who had the same issue as me on the pfsense forums..... https://forum.pfsense.org/index.php?action=profile;area=showposts;u=287475 Again... thanks for all the help!!! :D

Yep, That was it. Thanks!

Thank you.

NAT Reflection is one way to do it, but it's generally not recommended.  Always test your port forwards from the WAN side.  I find my phone is quite handy for such testing, and there is an official RDP app from MS for Android, for example..

@MrGreen: If anyone know a good public CA that provides S/MIME certs please let me know. www.startssl.com

nevermind… post solution for others. In User groups delete this User config - deny config write  

Distance is just one of the factors, because your latency to the destination is largely from physical distance in many cases. Not always the case though, you could be taking some extremely sub-optimal path to get there. ISPs' Internet routing is generally least-cost (monitarily for them), not necessarily best path.

All there and works, you have to be logged in though.

Guessing you cleared out the <installedpackages>section of the config backup before restoring. Though uPNP is in base now, its config is still under <installedpackages>. It restores fine where the settings are correctly in the restored config.</installedpackages></installedpackages>

@virgiliomi: The Monitor graphs don't provide that data anymore. RRD is not the most accurate way to be tracking total traffic anyway, as it loses accuracy as soon as 8 hours because it averages data to reduce the amount of data needed to be stored long-term. If you want to track this using RRD's data, you can add the "RRD Summary" package, which will add an item to the Status menu allowing you to see the RRD total traffic numbers with some basic settings. jdillard has been working on bringing vnstat over to the 2.3.x world as a more accurate way to track total traffic, providing graphs for a variety of time periods (I believe vnstat can show daily, weekly, and monthly graphs, though what he will have available, I don't know). A couple of his posts over in this thread include links to screenshots of the graphs. Ok sounds good, thanks for the info!

Am eagerly awaiting ntopng! Really would like to have the ability to track AND document activity of specific users

kpa - Thanks so much!

https://doc.pfsense.org/index.php/Remove_F1_Boot_Prompt

Thank You Guys, it worked !

Under 'System Logs/Firewall' you ought to be able to filter the log to help pinpoint the culprit. Otherwise, install Ntop and have a look at the traffic logs there. It should certainly show you which machine is behind the traffic you're seeing.

so after removing the pfsense virtual machine, I ended up having problems again with my pfsense router. my user logins kept changing back to defaults. I wasn't able to remote into my servers through the pfsense box, then I couldn't access the router via its external ip address. I decided to go back to my Cisco router. pfsense just wasn't stable for more than 3 weeks. I even did the update for 2.3.lastest. this product wasn't stable enough for my production environment. sorry for the bad review. Do you also install Ciscos iOS on oyur own hardware? And if this will be then not really fine working is Cisco then the guilty one or you!? Feel free to get a SG-unit from the pfSense shop to get rid of that pain and get a flawless working network back. Over a really long time customers, users and clients were were begging for own hardware from pfSense it selfs and then it would be there and all the folks where fiddling together their own units like before. Why?

Much appreciated guys, thanks for your feedback.

Thank you (pan_2) i solve it by put the DVR ip address in (allowed ip address) in (Captive Portal) …

Or simple solution on windows is just add this reg key and it should all be gone. elevated prompt reg add hklm\system\currentcontrolset\services\tcpip6\parameters /v DisabledComponents /t REG_DWORD /d 255 reboot Top put it back how you found it reg delete hklm\system\currentcontrolset\services\tcpip6\parameters\ /v DisabledComponents /f reboot When you get ready to use ipv6, the netsh commands jorgeO posted allow you to turn off the 3 different transition methods ms thought in their infinite wisdom it was a good idea to turn all 3 at the same time… JFC they think their user base is just complete morons.. the reg key above will turn it all off and even the teredo and isatap and 6to4 interfaces will be gone.