SYSTEM WARNING: 'date_default_timezone_get(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone.' in '/usr/share/mantis/www/core.php' line 264

0001953: dashboard should display which uplink currently has the default route - MantisBT
MantisBT - Endian Firewall
View Issue Details
0001953Endian FirewallNetwork related (VPN, uplinks)public2009-06-18 12:472011-02-01 15:10
luca-endian 
peter-endian 
normalminorhave not tried
confirmedreopened 
2.2-rc3 
future 
0001953: dashboard should display which uplink currently has the default route
It seems that if you disable and re-enable a secondary uplink, it will become the default uplink. The default route will be through that uplink, and this doesn't make any sense..

Tried with main eth static and secondary pppoe.
Steps to reproduce:
- both uplinks are managed without ping hosts option
- disable managed on secondary (pppoe) uplink
- deactivate uplink
- re-activate uplink (don't set managed)

Check via console with route command you will find out that the default route is the secondary uplink.

Even if you wait things don't change. (after 1 hour it was still the same)

It doesn't happen, fortunately, if the pppoe connection goes down.
purple
related to 0001955closed peter-endian main.cgi: display which uplink actually is the default gateway 
related to 0001956new  main.cgi, interfaceeditor: restart button 
Issue History
2009-06-18 12:47luca-endianNew Issue
2009-06-18 12:47luca-endianAssigned To => peter-endian
2009-06-18 12:47luca-endianTag Attached: purple
2009-06-18 12:54luca-endianRelationship addedrelated to 0001856
2009-06-18 12:56luca-endianNote Added: 0002636
2009-06-18 13:02peter-endianNote Added: 0002638
2009-06-18 13:03peter-endianStatusnew => closed
2009-06-18 13:03peter-endianResolutionopen => no change required
2009-06-18 13:28luca-endianNote Added: 0002640
2009-06-18 13:28luca-endianStatusclosed => feedback
2009-06-18 13:28luca-endianResolutionno change required => reopened
2009-06-19 11:13peter-endianNote Added: 0002644
2009-06-19 11:16peter-endianIssue cloned: 0001955
2009-06-19 11:16peter-endianRelationship addedrelated to 0001955
2009-06-19 11:25peter-endianIssue cloned: 0001956
2009-06-19 11:25peter-endianRelationship addedrelated to 0001956
2009-07-24 09:15luca-endianStatusfeedback => confirmed
2009-11-25 17:53peter-endianAssigned Topeter-endian =>
2010-09-21 19:34peter-endianSummarydefault route is switched to other uplinks => dashboard should display which uplink currently has the default route
2010-09-21 19:37peter-endianTarget Version => future
2011-01-20 14:06ra-endianCustomer Occurencies => 0
2011-02-01 08:34ra-endianSeveritymajor => minor
2011-02-01 15:10lorenzo-endianAssigned To => peter-endian

Notes
(0002636)
luca-endian   
2009-06-18 12:56   
Maybe related with http://bugs.endian.it/view.php?id=1467 [^]
(0002638)
peter-endian   
2009-06-18 13:02   
that's correct and it is what you want.

if you remove the managed flag it means the uplink is managed by you manually.
if you bring the uplink up, it means you want to use *that* uplink now. therefore it has also the default gateway.
as long as you don't tick on the managed flag this remains so.
if you have more than one unmanaged uplinks, the last dialed in uplink will have the default gateway.
(0002640)
luca-endian   
2009-06-18 13:28   
It is not really an expected behavior in my opinion.
It should be noticed somewhere, because someone maybe just want to restart a secondary uplink and doesn't imagine that this can cause a downtime on the main as well.

Actually it can be useful a graphical way to change the default route in some circumstances but in this way it's is just unexpected.
Probably an additional control to select the default gateway would be useful.
(0002644)
peter-endian   
2009-06-19 11:13   
If you disable the logic of the uplinksdaemon (set unmanaged) i think it should be clear that you want the uplinks doing what *you* want and not what the uplinksdaemon wants.
If you then bring an uplink up manually, normally you want that that uplink will also be used.
So i think the behaviour is not so bad.

You can restart an uplink by stopping it and putting it back managed, then it will be started automatically. Ok, a restart button maybe would not be that bad.

But you are right with visualization. You will not see which is the actual default gateway. We should change that.

And probably it is also missing in documentation, that can be. Should add it as well.