https://redmine.pfsense.org/https://redmine.pfsense.org/favicon.ico?16780521162010-09-26T16:07:41ZpfSense bugtrackerpfSense - Bug #882: IP aliases should not synchttps://redmine.pfsense.org/issues/882?journal_id=32842010-09-26T16:07:41ZPierre POMESpierre.pomes@gmail.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Feedback</i></li><li><strong>Assignee</strong> set to <i>Pierre POMES</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul><p>The line to prevent synchronization (as for "proxyarp") was missing, probably because "ipalias" VIP type was added in pfSense 2.0.</p> pfSense - Bug #882: IP aliases should not synchttps://redmine.pfsense.org/issues/882?journal_id=34202010-10-17T23:28:46ZChris Buechlercbuechler@gmail.com
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li></ul> pfSense - Bug #882: IP aliases should not synchttps://redmine.pfsense.org/issues/882?journal_id=34242010-10-18T15:02:49ZThiago Wittthiago.witt@gmail.com
<ul></ul><p>Hi, I've just tested it with the latest snapshot and it seems the problem remains.</p>
<p>Looking at the source, I think I found the problem, well at least it seems to do the trick here with no side-effects:</p>
<p>--- /tmp/rc.filter_synchronize 2010-10-18 16:56:50.000000000 <del>0200<br />+<ins>+ /etc/rc.filter_synchronize 2010-10-18 16:52:24.000000000 -0200<br /><code>@ -51,7 +51,7 </code>@<br /> global $config;<br /> $new_section = &$config['virtualip'];<br /> foreach($new_section['vip'] as $section) {<br /></del> if($section['mode'] "proxyarp") {<br /></ins> if($section['mode'] "proxyarp" || $section['mode'] == "ipalias") {<br /> unset($section);<br /> }</p>
<p>I hope it helps.</p> pfSense - Bug #882: IP aliases should not synchttps://redmine.pfsense.org/issues/882?journal_id=34252010-10-18T15:18:15ZPierre POMESpierre.pomes@gmail.com
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>Assigned</i></li><li><strong>% Done</strong> changed from <i>100</i> to <i>0</i></li></ul><p>Thanks for the report. I will doublecheck.</p>
<p>Pierre</p> pfSense - Bug #882: IP aliases should not synchttps://redmine.pfsense.org/issues/882?journal_id=34262010-10-18T15:58:44ZPierre POMESpierre.pomes@gmail.com
<ul><li><strong>Status</strong> changed from <i>Assigned</i> to <i>Feedback</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul><p>Hi Thiago,</p>
<p>A new fix hax been commited. Can you please try again ?</p>
<p>Thanks again,<br />Pierre</p> pfSense - Bug #882: IP aliases should not synchttps://redmine.pfsense.org/issues/882?journal_id=34342010-10-19T10:35:29ZThiago Wittthiago.witt@gmail.com
<ul></ul><p>Hi Pierre,</p>
<p>I just update both my systems with gitsync and now it no longer syncs the aliases, so that's ok.</p>
<p>Now the problem is that I also want to have an alias VIP only on the slave, but when I create or modify a VIP on the master it deletes the extra aliases created on the slave.</p>
<p>What I'm trying to do is to have 2 CARP VIPs on the same interface, but each using a different subnet, that's why I need an alias on each system, so I can create the second CARP VIP, otherwise it won't let me.</p>
<p>Should I open a new ticket?</p>
<p>Thanks,<br />Thiago</p> pfSense - Bug #882: IP aliases should not synchttps://redmine.pfsense.org/issues/882?journal_id=34372010-10-19T16:52:00ZPierre POMESpierre.pomes@gmail.com
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li></ul><p>Hi Thiago,</p>
<p>Ok for the new ticket. I will put this one to resolved since the initial report is now ok.</p>
<p>Thanks,<br />Pierre</p>