diff options
author | Phil Davis <phil.davis@world.inf.org> | 2013-08-14 11:54:19 -0700 |
---|---|---|
committer | Phil Davis <phil.davis@world.inf.org> | 2013-08-14 11:54:19 -0700 |
commit | e2ddbda7ee927e161285a0cd3b19b180ceb9221a (patch) | |
tree | 40c144e9c08775ca2e971474a6352238c85e1cda /usr/local | |
parent | 0caaa8105cabed0b31c606533cabcb7513ca3720 (diff) | |
download | pfsense-e2ddbda7ee927e161285a0cd3b19b180ceb9221a.zip pfsense-e2ddbda7ee927e161285a0cd3b19b180ceb9221a.tar.gz |
Display pfSense interface name on status interfaces
Sometimes it is a bit difficult to work out which interface descriptive name is which pfSense internal interface name (wan, lan, opt1, opt2...). It is useful to know for:
a) hardware that has wan, lan, opt1... pre-printed on the case (some Alix cases for example), making it easier for less-trained remote office staff to work out which cable corresponds to which interface in pfSense.
b) looking in config.xml or other techo places where the internal pfSense name is stored/referenced - knowing that straight from a status GUI display saves having to first find the descriptive name in the config, then the pfSense internal name.
What do you think? Is this a worthwhile place to display this data?
Diffstat (limited to 'usr/local')
-rwxr-xr-x | usr/local/www/status_interfaces.php | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/usr/local/www/status_interfaces.php b/usr/local/www/status_interfaces.php index 0ab83b1..cd71c1b 100755 --- a/usr/local/www/status_interfaces.php +++ b/usr/local/www/status_interfaces.php @@ -81,7 +81,7 @@ include("head.inc"); <?php endif; ?> <tr> <td colspan="2" class="listtopic"> - <?=htmlspecialchars($ifname);?> <?=gettext("interface"); ?> (<?=htmlspecialchars($ifinfo['hwif']);?>) + <?=htmlspecialchars($ifname);?> <?=gettext("interface"); ?> (<?=htmlspecialchars($ifdescr);?>, <?=htmlspecialchars($ifinfo['hwif']);?>) </td> </tr> <tr> |