https://ipinfo.io/AS1668/172.168.0.0/16-172.168.0.0/23 172.168.0.140 belongs to AOL.  I know you probably do not want to hear it but until you fix your "LAN" problem your probably going to continue to have intermittent problems based on the fact that certain programs can be hard coded for the standards. Easy- drop the 8 and make it 172.16.0.0/24

in overall for this problem to be salved, is to put the harddrive in to another laptop an install the OP, and then switch back the harddrive to the previous laptop to configuer the OP.

How do I connect my wifi to Pfsense?. Please help.

Thanks for share the solution.

@johnpoz: … So your trying to use the updater in pfsense - is this even viable anymore? Their doc's say to use the client to keep your IP updated https://support.opendns.com/hc/en-us/articles/227987787 https://support.opendns.com/hc/en-us/articles/227987867-What-is-the-OpenDNS-Dynamic-IP-updater-client- I am not sure that the dyndns opendns setting in pfsense works with opendns anymore.. Yep. It does. The build-in Dyn Updater works just fine. I'm using it since this morning - and was using OpenDNS ones in the past to see if it could do something good for my network, except break all DNSSEC/DANE/…. (so I ditched it). Then the FreeBSD/pfSense gods invented the Resolver, and I was very happy with it. @johnpoz: Does your IP change.. Many a isp even when your "dynamic" since your router is on all the time, it just renews your dhcp lease and your IP rarely changes.. Before I changed isp I had the same IP for years!!  And since I have moved to new isp I have had the same IP since be with them.. Couple of months. You're right. Even with a IP WAN that changes every time - no need to setup the automatic DyNDNS procedure. Just set everything up and hard code the IP WAN in the settings of OpenDNS. It will work then just until the IP WAN changes.

Problem solved. It looks like the bridge interface name was set incorrectly during the upgrade process: Config on 2.0.1 <lan><enable><if>bridge0</if> <ipaddr>192.168.69.1</ipaddr> <subnet>24</subnet> <spoofmac></spoofmac></enable></lan> Same config on 2.3.4 <lan><enable></enable> <if>vr0</if> <ipaddr>192.168.69.1</ipaddr> <subnet>24</subnet> <spoofmac></spoofmac></lan> After correcting the value and rebooting the bridge is working as expected. Can anybody explain it? Is it a known bug / glitch?

@flash0151: I'm trying to add a patch to my system running ver 2.4.2 and the documentation reads I …. Just for my personal curiosity, what documentation were you reading. I tried Googling =https://www.google.fr/search?q=pfsense+patch+&ie=utf-8&oe=utf-8&client=firefox-b&gfe_rd=cr&dcr=0&ei=vatEWqWeMqeBtgfH44AYpfSense patch, the very first link would be able to help you right away : https://doc.pfsense.org/index.php/System_Patches ;)

Hello , I already cleanup this files. But after latest update the problem desperate. So it's good ! Thank for your help :) Bye

workaround was : MTU settings for GRE interfaces new 2.4 version MTU 1376 old 2.3.4 version MTU 1400 in this case old<–> old <--working old<--> new <--working new<--> new <--working

Finally i could install development snapshot build. I even configured the LAN ip address. but now i cant access the Webgui of pfsense. no matter which ip address i change. Can i get help here in accessing my pfsense Webgui pls…. thanks in advance

https://forum.pfsense.org/index.php?topic=110515.msg766964#msg766964 More information on what me and Martin worked on, I am hoping my patch which Martin submitted on github got accepted, but maybe it didnt, as the patch should resolve this issue for anyone using pfsense on hardware with at least 1 gig of ram. –edit-- It has been approved 2 days ago. https://github.com/pfsense/pfsense/pull/3881 https://redmine.pfsense.org/issues/8125

Please help me!!!

@bab5470: @Gertjan: Does it say : 2.4.2-RELEASE-p1 (amd64) built on Tue Dec 12 13:45:26 CST 2017 FreeBSD 11.1-RELEASE-p6 ? Nope: 2.4.2-RELEASE-p1 (amd64) built on Tue Dec 12 13:45:26 CST 2017 FreeBSD 10.3-RELEASE-p19 So how do I upgrade from FreeBSD 10.3 to 11.1? Shouldn't PFSense do this for me when I check for updates? Looks like this from the shell will do the trick: pfSense-upgrade -d I'm now on 11.1 and I can install packages again! Thanks!!

Hi, Should be https://firmware.netgate.com/pkg/pfSense_factory-v2_4_2_amd64-core/All (click and see for yourself) pfSense-rc-2.4.2_1.txz The latest is  "2.4.2_1" - not "2.4.2". Try what is proposed elsewhere : Visit System => Update => System Update and switch away from Latest stable 2.4.x (Latest stable). Validate Then set it back to "Latest stable 2.4.x (Latest stable)" and validate. Try again. Btw : your are on the AMD (64 bits version) right know, right ? if you are using a 386 version, a re install implies.

Yes You're welcome

Thanks for that johnpoz I wasn't aware d-link made 8 port managed switches. Well with that here is what I'll do. I'll buy the SG-1000 along with the d-link 8 port smart switch. Instead of having port 1 LAN-192.168.0.0/24 port 2 DMZ-192.168.200.0/24 port 3 WAN-0.0.0.0/0 I'll do this port 1 vlan 2-LAN-192.168.0.0/24 port 1 vlan 3-DMZ-192.168.200.0/24 port 2 WAN-0.0.0.0/0 Thanks for everyones help.