pfSense bugtracker: Issueshttps://redmine.pfsense.org/https://redmine.pfsense.org/favicon.ico?16780521162010-10-20T07:37:44ZpfSense bugtracker
Redmine pfSense - Bug #961 (Resolved): Config sync doesn't remove the last alias on the slavehttps://redmine.pfsense.org/issues/9612010-10-20T07:37:44ZThiago Wittthiago.witt@gmail.com
<p>If I setup two systems with carp sync and create an alias, it will sync correctly with the slave, but when I remove it on the master, it won't remove from the slave. It only happens when I remove the last alias on the master, if there was more than one alias, then it also gets removed from the slave.</p> pfSense - Bug #960 (Resolved): Problem with config sync + ipsec + special charactershttps://redmine.pfsense.org/issues/9602010-10-20T07:33:14ZThiago Wittthiago.witt@gmail.com
<p>When the description field in ipsec's phases 1 and 2 contains special characters such as accentuation config sync is unable to sync to slave.</p>
<p>E.G. I had a phase2 that was causing problems by having a 'ã' in the description. In the master XML it was translated to the correct html entity (ã) but it wouldn't sync over to the slave until I removed it.</p> pfSense - Bug #959 (Resolved): Config sync removes alias VIPs on the slavehttps://redmine.pfsense.org/issues/9592010-10-20T07:25:01ZThiago Wittthiago.witt@gmail.com
<p>I want to have 2 CARP VIPs on the same interface, but each using a different subnet, so I need an alias on each system for the second subnet to be able to create the second CARP VIP, otherwise it won't let me.</p>
<p>The problem is that when I create or modify a VIP on the master it deletes the extra aliases created on the slave, and the CARP VIPs that use the second subnet become invalid on the slave.</p>
<p>I think pfsync shouldn't remove the extra aliases on the slave when synchronizing.</p> pfSense - Bug #936 (Resolved): Bad racoon.conf generated with localid_type=addresshttps://redmine.pfsense.org/issues/9362010-10-05T11:15:28ZThiago Wittthiago.witt@gmail.com
<p>When setting up a new Phase 2 IPSEC connection in the GUI, if 'Local Network' is set to 'Address', then an invalid racoon.conf is generated with fatal error (parse error on sainfo line).</p>
<p>Example of generated sainfo:<br />sainfo address 200.123.123.123 any</p>
<p>It should be something like:<br />sainfo address 192.168.40.40 any address 200.123.123.123 any</p>
<p>Workaround is simple - specify Local Network type as Network and specify the local address with a /32 netmask.</p>