@gsiemon: My portal dashboard is currently showing a Gold subscription expiry of 3 April 2017 and my newly registered SG-1000 seems to have an entirely separate expiration date (12 months after the date I registered it). Same for me …  :)

I figured it was probably something stupid…fat fingering the mask was a sure way to get there. Thanks for all of your help!

Days?  heheh dok there are some that don't get it after weeks ;) heheheh

You don't. /etc/rc.initial is not localized.

No, you do not add any static routes for interfaces connected to pfSense itself. Other than that, produce a network diagram.

OK guys ! I found out the problem ! It caused by firewall > Nat > Outbound I created a manual mapping on my LAN Interface allow Source : Source port : Destination : Destination Port : Nat address : Nat port Any : Any : Any : Any : Nat address : Any I changed it to Source : Source port : Destination : Destination Port : Nat address : Nat port This Fiirewall : Any : Any : Any : Nat address : Any now i got my all visitor IP address ! ;)

@NOYB: @mahmoudsabry: after that i can't ping or open gui how can i fix this Console option 15) Restore recent configuration If that don't work then Console option 4) Reset to factory defaults it works thanks alot i tried to restore from the web i had a backup from 1 week ago

Looks like this was a hardware issue. I replaced one of the NIC's with a new one and it started working right away. I'm guessing FreeBSD didn't like the chipset as it it works fine in every OS I've used it in (before and after). It worked fine on this box as well, it just would not pass browser traffic through it. Nothing else has changed about the config, so that had to be the problem. Thanks for the input!

THANK YOU A LOT, Bruh. Like a lot.. Now I'll just look on the VM option.. I'll be super safe this time. Thanks.. I'll update here of what happens. You guys are great.

I had a similar issue the day I upgraded to v2.3.2 back in July…. and I'm still convinced something changed, but that's another conversation. As soon as I upgraded to v2.3.2, the DNS forwarder stopped resolving.  I tried both the resolver and the forwarder to no avail.  The fix for me was to deselect "ALL" from the interfaces section and manually selecting my "LAN" interface.  As soon as that was done, DNS started resolving again and my issues went away.

If you setup the DNS domain overrides to forward internal DNS resolution properly and use DNS hostnames rather than IP addresses on your clients for internal resources properly, it should be fairly seamless to migrate the servers since there's effectively no changes to be made to the individual clients. If you use DDNS hostnames, even remote warrior VPN configurations won't need changes - just switch the DDNS updates over to the new site.

"How do IT learners fix their Wi-Fi (add extensions)?" Huh?  People that want good wifi install properly placed AP.  They would connect them to their switch..  They would not try to bridge interfaces on pfsense?  It takes all of 5 seconds to get an AP up and running on a network.

@Derelict: @stormrage: Could I make this so that the subnet can be changed when it reaches my pfSense box? ModemRouter(192.168.1.1/24) >>                                                [WAN1]>    pfSense (10.0.0.1/22) ModemRouter(192.168.1.1/24>Another Router(192.168.1.1/25)>>  [WAN2]> I can add another router infront of WAN2 so that the subnet can be changed when it reaches pfSense box? ModemRouter(192.168.1.1/24) >> [WAN1]>    pfSense (10.0.0.1/22) ModemRouter(192.168.1.1/24>Another Router(**192.168.2.1/24**)>>  [WAN2]> More like that - sure. Thank you! I will try that and return with the results :)

@Derelict: I would like to know how would you do with using pfsense as your main ISP router / firewall. Do you need any support from the ISP ? The absolute best/proper thing to do is have the ISP assign a /29 to your WAN interface then route the /28 to an address on that. That address being your WAN interface address. (If they need you to justify the /29 tell them you need at least 3 addresses there for your High-Availability setup.) Then you just number the DMZ with the /28 (or a smaller subnet of that, leaving the rest for other purposes) and disable NAT for it. And you're done. Any other solution involves yucky things like Proxy ARP, 1:1 NAT, and bridging. Thank you very much this was the answer of my question.

Have you looked at the ntopng package? I find it quite comprehensive in telling me who did what etc.