Bug #271


PPP configuration files not copied

Added by Marcus Brown almost 12 years ago. Updated over 11 years ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
Affected Architecture:


The ppp.conf, ppp.linkup, and ppp.linkdown files are not copied to the new installation when performing a manual upgrade from the wegGUI. It's easy to go into PPP interface configure and save the configuration again, which re-creates the files, but it always takes about 8 or 10 clicks in the "Connect" button before I remember that I just updated to a new image and I have the default ppp.conf file in /etc/ppp.
Is it a good idea to create a ppp directory on /conf and symlink to the /etc/ppp directory?

Actions #1

Updated by Chris Buechler almost 12 years ago

  • Category set to Interfaces
  • Target version set to 2.0

There is no default configuration, and no copying of any configurations, those files are generated from the configuration on the system. I don't think it's upgrade related, seems it's probably related to reboots in general. If you just reboot do you see the same thing?

Actions #2

Updated by Marcus Brown almost 12 years ago

If you check the /etc/ppp directory of a fresh install there is a ppp.conf file from the ppp package. The new ppp.conf file generated by pfsense definitely survives reboot, but doesn't automatically get copied to the second disk slice when you upgrade. It's a small convenience issue that is unintuitive since after I stall and reboot the config seems identical in every other way from the GUI and functionally. I forgot to mention this applies to nano upgrade process. I don't have experience with how the full install upgrade process works.

Actions #3

Updated by Ermal Luçi almost 12 years ago

  • Status changed from New to Feedback

This should be fixed on new snapshots.

Actions #4

Updated by Chris Buechler over 11 years ago

  • Status changed from Feedback to Resolved

Also available in: Atom PDF