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

0001956: main.cgi, interfaceeditor: restart button - MantisBT
MantisBT - Endian Firewall
View Issue Details
0001956Endian FirewallGUIpublic2009-06-19 11:252010-03-03 15:11
peter-endian 
 
normalfeatureN/A
newopen 
2.2-rc3 
future 
0001956: main.cgi, interfaceeditor: restart button
It would be nice to have a button for restarting an uplink. That button actually should only stop the uplink, the uplinksdaemon will start it automatically if the uplink is managed, otherwise it needs also to be started.

If an uplink is not working in a manner that the uplinksdaemon has no possibility to understand that it is not working, users tend to try to restart it.
Since there is no possibility to restart an uplink, they make the uplink unmanaged, and stop/start it, which actually changes the default gateway to that uplink!.
This is not what the user wants.

Correct usage would be to make the uplink unmanaged, stop it and make the uplink back managed, but that's to complicated.
No tags attached.
related to 0001953confirmed peter-endian dashboard should display which uplink currently has the default route 
Issue History
2009-06-19 11:25peter-endianNew Issue
2009-06-19 11:25peter-endianAssigned To => peter-endian
2009-06-19 11:25peter-endianIssue generated from: 0001953
2009-06-19 11:25peter-endianRelationship addedrelated to 0001953
2009-06-19 11:25peter-endianTarget Versionfuture => 2.3
2009-06-19 11:28peter-endianRelationship addedchild of 0001934
2009-06-19 11:29peter-endianNote Added: 0002645
2009-06-19 15:33luca-endianNote Added: 0002648
2009-06-23 18:19peter-endianAssigned Topeter-endian =>
2009-06-26 16:28luca-endianNote Edited: 0002648
2009-08-23 13:36stevenNote Added: 0002888
2009-09-03 17:15peter-endianRelationship deletedchild of 0001934
2009-10-27 13:37peter-endianTarget Version2.3 => 2.3.1
2010-03-03 15:11ra-endianTarget Version2.3.1 => future

Notes
(0002645)
peter-endian   
2009-06-19 11:29   
i think we need to reorganize uplinks display on main.cgi. There is to few space left and much information could also be displayed in a mouseover and/or using status icons
(0002648)
luca-endian   
2009-06-19 15:33   
(edited on: 2009-06-26 16:28)
I've some ideas/suggestions:

1) Tidy table which summarize the uplink status and make possible to do actions.
You can view more information by exploding the uplink view which open a second line under the summarized one.

2) Two table lines for each uplink with more information always displayed

3) Mouse over information (i prefer to have all the information displayed)

Essential information:
- uplink name
- uplink type
- interface ip
- uplink status
- uptime

Interesting information:
- gateway
- netmask
- main external ip*
- network interface
- link speed

Actions:
- perform network test**
- managed
 - manage/unmanage
 - restart
- manual
 - disable/enable
 - restart
 - default route (with a radio button)

* detectip should be improved (future) in order to select which uplink must be used, I've seen that curl has the --interface option which works we can use it.
(pycurl could be used for this aim)

** connection test (future)
A script which performs and reports the following tests:
- cable status
- ping to gateway
- dns resolving
- ping to google

(0002888)
steven   
2009-08-23 13:36   
suggestions all sound good