Hi List,
I recently upgraded a 1.2.3 machine with an MTU setting of 1300 to 2.0.1
and saw some weird behavior - some, but not all web sites not loading at
all or loading reeeaallly sloooowly. As it turns out, the MTU value
ended up in the MSS field after the upgrade.
Manually moving it from one field to the other in the web GUI
(Interfaces/WAN) and applying the change fixed the issue.
Was that a freak incident or is it a bug in the upgrade routine?
I must admit that I didn't run an in-place upgrade from a booted
pfSense, rather, I proceeded like this:
1) install the pre-upgrade package in 1.2.3 and remove all comments with
foreign characters so the XML would show up as clean
2) install 2.0.1 to a blank drive on an identical machine, giving the
same storage location for the config file as on the "live" machine
3) swap OS drives in "live" machine
4) upon boot, 2.0.1 reads the 1.2.3 config file and converts it to 2.0.1
format
This worked for 31 out of 32 machines - the one that didn't work
immediately was the one with the non-standard MTU.
Kind Regards
Stefan
_______________________________________________
List mailing list
[email protected]
http://lists.pfsense.org/mailman/listinfo/list
