guys, one correction: all the tries I did was migrating pfsense 1.2.3 to 2.1.1
I just tried one last shoot with new pfsense 2.1.2 and it WORKED as expected! Alex On Tue, Apr 22, 2014 at 4:40 PM, Alexsander Rodrigues < [email protected]> wrote: > Well, that was exactly what I did. (Sorry, I did mention only vpn/ipsec > cause was the only component didn't work as expected). > the other option (upgrade the pfsense 1.2.3 to 2.1.2) is not possible due > to some tech/business limitations. > I think I'll recreate all vpn/ipsec manually this time and keep searching > later (just for curiosity). If I get something new I'll let you know. > > Thanks anyway > > Alex > > > > On Tue, Apr 22, 2014 at 3:38 PM, Jim Pingle <[email protected]> wrote: > >> On 4/22/2014 2:15 PM, Alexsander Rodrigues wrote: >> > I see. By upgrading the configuration file you mean to upgrade the >> > pfsense 1.2.3 to 2.1.1 and then to export the configuration file? >> >> That, or you can take the whole 1.2.3 config.xml and restore that to a >> firewall already running 2.1.2, and then from there export the ipsec >> section and import into another 2.1.2 system. >> >> Jim >> >> _______________________________________________ >> List mailing list >> [email protected] >> https://lists.pfsense.org/mailman/listinfo/list >> > > > > -- > *Alexsander A. Rodrigues* > *IT & Operations* > > T +55 51 3346 8282 | R 212 | C +55 51 9449 9009 > *www.zenvia.com.br* <http://www.zenvia.com.br/> > -- *Alexsander A. Rodrigues* *IT & Operations* T +55 51 3346 8282 | R 212 | C +55 51 9449 9009 *www.zenvia.com.br* <http://www.zenvia.com.br/>
_______________________________________________ List mailing list [email protected] https://lists.pfsense.org/mailman/listinfo/list
