https://redmine.pfsense.org/issues/8003
It’s being worked on in snapshots. Jim > On Oct 25, 2017, at 9:03 AM, Edward O. Holcroft <[email protected]> wrote: > > I just upgraded from 2.4.0 to 2.4.1. > > If I view the status of my IPSec tunnels, it seems they have all been > duplicated. > > The original tunnels all show as disconnected, while the second tunnel, > which has no description, shows as connected. > > So all the tunnels still work, it's just that there is new duplicate entry > without a description field populated. If I look in the IPSec tunnel > settings however, there is only tunnel, the correct one, with the > description filed populated. If I hit "connect" on one of the original > tunnels, it does nothing, since of course it is already connected via the > duplicate, unnamed tunnel. > > Has anyone else seen this? > > Any ideas on a way to clean it up? I don't see anything duplicated in the > IPSec xml file. > > ed > > -- > MADSEN, KNEPPERS & ASSOCIATES USA WARNING/CONFIDENTIALITY NOTICE: This > message may be confidential and/or privileged. If you are not the intended > recipient, please notify the sender immediately then delete it - you should > not copy or use it for any purpose or disclose its content to any other > person. Internet communications are not secure. You should scan this > message and any attachments for viruses. Any unauthorized use or > interception of this e-mail is illegal. > _______________________________________________ > pfSense mailing list > https://lists.pfsense.org/mailman/listinfo/list > Support the project with Gold! https://pfsense.org/gold _______________________________________________ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
