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
| Anonymous | Login | 2020-05-28 18:10 UTC |  |
| Main | My View | View Issues | Change Log | Roadmap |
| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||||
| 0001953 | Endian Firewall | Network related (VPN, uplinks) | public | 2009-06-18 12:47 | 2011-02-01 15:10 | ||||||
| Reporter | luca-endian | ||||||||||
| Assigned To | peter-endian | ||||||||||
| Priority | normal | Severity | minor | Reproducibility | have not tried | ||||||
| Status | confirmed | Resolution | reopened | ||||||||
| Platform | OS | OS Version | |||||||||
| Product Version | 2.2-rc3 | ||||||||||
| Target Version | future | Fixed in Version | |||||||||
| Summary | 0001953: dashboard should display which uplink currently has the default route | ||||||||||
| Description | 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. | ||||||||||
| Tags | purple | ||||||||||
| Attached Files | |||||||||||
 Relationships |
|||||||||||
|
|||||||||||
 Relationships |
|
Notes |
|
|
(0002636) luca-endian (developer) 2009-06-18 12:56 |
Maybe related with http://bugs.endian.it/view.php?id=1467 [^] |
|
(0002638) peter-endian (administrator) 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 (developer) 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 (administrator) 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. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2009-06-18 12:47 | luca-endian | New Issue | |
| 2009-06-18 12:47 | luca-endian | Assigned To | => peter-endian |
| 2009-06-18 12:47 | luca-endian | Tag Attached: purple | |
| 2009-06-18 12:54 | luca-endian | Relationship added | related to 0001856 |
| 2009-06-18 12:56 | luca-endian | Note Added: 0002636 | |
| 2009-06-18 13:02 | peter-endian | Note Added: 0002638 | |
| 2009-06-18 13:03 | peter-endian | Status | new => closed |
| 2009-06-18 13:03 | peter-endian | Resolution | open => no change required |
| 2009-06-18 13:28 | luca-endian | Note Added: 0002640 | |
| 2009-06-18 13:28 | luca-endian | Status | closed => feedback |
| 2009-06-18 13:28 | luca-endian | Resolution | no change required => reopened |
| 2009-06-19 11:13 | peter-endian | Note Added: 0002644 | |
| 2009-06-19 11:16 | peter-endian | Issue cloned: 0001955 | |
| 2009-06-19 11:16 | peter-endian | Relationship added | related to 0001955 |
| 2009-06-19 11:25 | peter-endian | Issue cloned: 0001956 | |
| 2009-06-19 11:25 | peter-endian | Relationship added | related to 0001956 |
| 2009-07-24 09:15 | luca-endian | Status | feedback => confirmed |
| 2009-11-25 17:53 | peter-endian | Assigned To | peter-endian => |
| 2010-09-21 19:34 | peter-endian | Summary | default route is switched to other uplinks => dashboard should display which uplink currently has the default route |
| 2010-09-21 19:37 | peter-endian | Target Version | => future |
| 2011-01-20 14:06 | ra-endian | Customer Occurencies | => 0 |
| 2011-02-01 08:34 | ra-endian | Severity | major => minor |
| 2011-02-01 15:10 | lorenzo-endian | Assigned To | => peter-endian |
|
Issue History |
| Copyright © 2000 - 2012 MantisBT Group |
 |