Thanks for the quick reply and explanation.  I didn't realized it was using a SRV record.  I'm likely seeing a localized issue since I see now that it fails (randomly) on different packages.  Sorry for the noise.

Hi,
I can confim the procedure suggested by Yarick

This solved the issue

Regards
Greyhat

Hi jimp,

thank you, the simplest solution #3 (

3. Wait until 2.3.5-p1 drops later this week and attempt to update again then and see if it corrects itself.

) has succeeded!

Now the correct version is shown everywhere! :)

I noticed one strange thing during the upgrades (2.3.4_1 -> 2.3.5 and 2.3.5 -> 2.3.5_1). After the first upgrade, everything were upgraded except of the kernel. Rebooting did not help. The kernel was upgraded only after executing the upgrade process the second time. The disk slice was duplicated, and the possibility to go back to the previous version was lost. :(

Best regards
yarick123

Once I connected via console, most of the console options did not work. Missing libraries or similar error messages. Was unable to recover the config, but my linux skills are minimal. Maybe if I had that I could have worked in the shell to find it.
Anyway, ended up doing a fresh install after downloading the community image. As an owner of a pfsense device, I thought I should have been entitled to the better image. No matter at this point. Everything reinstalled and working. And I have a good backup of the config!
Very odd to me how the upgrade indicated success but obviously failed. Hope that never recurs.

I have the same issue.

I have two pfSense routers, both were just upgraded to 2.4.2-RELEASE-p1 from 2.3.4-RELEASE-p1. L2TP/IPSec worked great on 2.3.4-RELEASE-p1 on both routers. After upgrading, I can no longer connect to the L2TP server on one (yes, just one) of the routers. I am trying to connect from a Macbook Pro (MacOS 10.12.6) and an iPhone 6S+ (iOS 11.2.1). On both devices, the connection fails with "The L2TP-VPN server did not respond. Try reconnecting. If the problem continues, verify your settings and contact your Administrator." My ppp.log file on my Mac looks pretty much identical to what onlime posted. The most recent entries in my L2TP system log on the router is:

Dec 28 08:51:29 l2tps: L2TP: waiting for connection on 1.2.3.4 1701
Dec 28 08:51:29 l2tps: process 50431 started, version 5.8 (nobody@pfSense_factory-v2_4_2_amd64-pfSense_factory-v2_4_2-job-12 19:34 16-Nov-2017)
Dec 28 08:51:29 l2tps:
Dec 28 08:51:29 l2tps: Multi-link PPP daemon for FreeBSD

All still works great on the other router…super weird. The main difference between the two routers is the one that is broken is set up with two VLANs and the other (the one that still works) just has a single LAN (no VLANs). Because of this, I am thinking the issue lies with some VLAN configuration, but I am not too sure how to confirm/troubleshoot this. Any tips or hints would be greatly appreciated!

NM
I hadnt properly inserted the other USB…..  Happy new year!!  im off to a great start.

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