https://redmine.pfsense.org/https://redmine.pfsense.org/favicon.ico?16780521162013-07-06T05:44:32ZpfSense bugtrackerpfSense - Bug #3075: Can't delete unused Virtual IP "referenced by a least one gateway"https://redmine.pfsense.org/issues/3075?journal_id=118752013-07-06T05:44:32ZChris Buechlercbuechler@gmail.com
<ul></ul><p>that input validation should only apply when it's the only VIP that exists in that gateway's subnet.</p> pfSense - Bug #3075: Can't delete unused Virtual IP "referenced by a least one gateway"https://redmine.pfsense.org/issues/3075?journal_id=118772013-07-06T11:12:04ZChristian McDonaldcmcdonald@netgate.com
<ul></ul><p>I'm not sure that I'm following you. Let's say my block of public IPs is as follows:</p>
<p>1.1.1.30 (gateway)<br />1.1.1.29<br />1.1.1.28<br />1.1.1.27<br />1.1.1.26<br />1.1.1.25</p>
<p>If my wan interface is set as 1.1.1.29 with gateway 1.1.1.30, and I have a virtual IP set as 1.1.1.25, if that VIP is not being used with anything (NAT, etc.), why shouldn't I be able to delete it? Like I said, I know I did this a few times without any problems under older builds. Thanks</p> pfSense - Bug #3075: Can't delete unused Virtual IP "referenced by a least one gateway"https://redmine.pfsense.org/issues/3075?journal_id=118792013-07-06T12:53:19ZRenato Botelhorenato@netgate.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Feedback</i></li><li><strong>Assignee</strong> set to <i>Renato Botelho</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul><p>The fix for <a class="issue tracker-1 status-3 priority-4 priority-default closed" title="Bug: IP Aliases cannot be used for routes/gateways (Resolved)" href="https://redmine.pfsense.org/issues/2962">#2962</a> introduced this issue. I fixed it, please check tomorrow's snapshot.</p> pfSense - Bug #3075: Can't delete unused Virtual IP "referenced by a least one gateway"https://redmine.pfsense.org/issues/3075?journal_id=118802013-07-06T16:16:30ZChristian McDonaldcmcdonald@netgate.com
<ul></ul><p>Thanks Renato!</p> pfSense - Bug #3075: Can't delete unused Virtual IP "referenced by a least one gateway"https://redmine.pfsense.org/issues/3075?journal_id=119622013-07-13T13:02:07ZDan Lundqvistbetateam.mrzaz@gmail.com
<ul></ul><p>Sent to forum on 9th July<br /><a class="external" href="http://forum.pfsense.org/index.php/topic,64326.0.html">http://forum.pfsense.org/index.php/topic,64326.0.html</a></p>
<p>I have just updated to the latest build (2.1-RC0 (i386) built on Tue Jul 9 23:03:10 EDT 2013" <br />but still see this problem when trying to remove "*IP Alias*" entries.</p>
<p>I get <strong>"This entry cannot be deleted because it is still referenced by at least one Gateway."</strong> when trying<br />to remove one <strong>IP Alias</strong>. (I only have one primary IP defined in the WAN-interface .51 at end<br />and one VirtualIP <strong>IP Alias</strong> with .53 at the end. Is in same subnet as primary IP and only have one VirtualIP defined.</p>
<p>basically this is the setup:<br />xx.xx.165.1/24 Gateway<br />xx.xx.165.51/24 Main WAN IP<br />xx.xx.165.53/24 VirtualIP <strong>IP Alias</strong> With NOTHING tied like NAT or similar. Just created <strong>IP Alias</strong>.</p>
<p>The "IP Alias" was created in an earlier build from June.</p>
<p>I was only doing some tests for a colleague and need to undefine the <strong>IP Alias</strong> as this IP<br />is normally used in another router and is temporary disconnected so I could do the test.<br />As long as this IP is now tied to pfSense it will answer ARPs and I will get an IP collision.</p>
<p>I found another thread that was dealing with similar but for CARP IP and that was suppose to <br />be fixed but still have problem with IP Alias.<br /><a class="external" href="http://forum.pfsense.org/index.php/topic,64156.0.html">http://forum.pfsense.org/index.php/topic,64156.0.html</a></p>
<p>Best regards<br />Dan Lundqvist<br />Stockholm, Sweden</p> pfSense - Bug #3075: Can't delete unused Virtual IP "referenced by a least one gateway"https://redmine.pfsense.org/issues/3075?journal_id=120902013-07-30T13:49:10ZRenato Botelhorenato@netgate.com
<ul></ul><p>It's fixed now. Please test with tomorrow snapshot or gitsync</p> pfSense - Bug #3075: Can't delete unused Virtual IP "referenced by a least one gateway"https://redmine.pfsense.org/issues/3075?journal_id=121502013-08-08T16:16:33ZDan Lundqvistbetateam.mrzaz@gmail.com
<ul></ul><p>I can confirm that the bugfix is now working OK also on IP-Alias after testing.<br /><strong>I propose to close this bug.</strong></p>
<p>Best regards<br />Dan Lundqvist<br />Stockholm, Sweden</p> pfSense - Bug #3075: Can't delete unused Virtual IP "referenced by a least one gateway"https://redmine.pfsense.org/issues/3075?journal_id=121512013-08-08T16:51:43ZChris Buechlercbuechler@gmail.com
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Closed</i></li></ul><p>thanks</p> pfSense - Bug #3075: Can't delete unused Virtual IP "referenced by a least one gateway"https://redmine.pfsense.org/issues/3075?journal_id=274352016-06-06T06:30:00ZTobi Miller
<ul></ul><p>I have pfsense 2.3 (amd64) running and this issue seems to be present again. I have setup a main virtual IP which I use to bind services. Now I added another virtual IP from the same subnet, but now I cannot remove this newly added virtual ip. The error message always is "This entry cannot be deleted because it is still referenced by at least one Gateway." <br />My setup:</p>
<p>Subnet xx.xx.xx.208/29<br />GW xx.xx.xx.209<br />virtIP xx.xx.xx.210<br />virtIP xx.xx.xx.214</p>
<p>the second virtual IP I want to remove, but fails with error above</p> pfSense - Bug #3075: Can't delete unused Virtual IP "referenced by a least one gateway"https://redmine.pfsense.org/issues/3075?journal_id=293282016-11-08T07:38:20ZFlavio Stanchinaflavio.stanchina@ies.it
<ul></ul><p>I've got this error on 2.3.2_1, on a CARP VIP I just added for a test. I'm 100% sure that VIP is not being used for anything (added it, checked if it was MASTER on the dashboard, immediately went back to delete it). It's outside the interface's subnet, if that makes a difference, and I have three other VIPs on that interface (all of them outside the interface's subnet).</p>
<p>This happened on a non-production firewall where I'm testing a scenario I want to replicate in production, so this is going to be a problem for me in a few days.</p>