Project

General

Profile

Actions

Feature #13161

open

FLASH PORT'S LED button, to help quickly find port that need to be connected to patch&cable

Added by Sergei Shablovsky about 2 months ago. Updated about 2 months ago.

Status:
New
Priority:
Very Low
Assignee:
-
Category:
Web Interface
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Default

Description

Dear pfSense Dev Team!

Seems there are reason to making FLASH PORT'S LED button in sections Interface (and State / Interfaces) , to make a little help for thousands of newcomers or Hard SysEngeneer (who have madness with jacks&cables&patches each day 8+h) quickly find port that need to be connected to patch&cable.

Flashing time 15s would be enough (and in most cases are maximum possible in most NICs).

This is just TWO commands and a PHP-code for button!

Actions #1

Updated by Jim Pingle about 2 months ago

  • Priority changed from Normal to Very Low
  • Target version deleted (2.7.0)

What "two commands" are you referring to?

Flashing NIC LEDs would vary by hardware/driver/etc. There isn't a general function for that on FreeBSD in ifconfig or similar, and FreeBSD doesn't have a tool like etherblink on Linux.

Actions #2

Updated by Sergei Shablovsky about 2 months ago

Jim Pingle wrote in #note-1:

What "two commands" are you referring to?

Flashing NIC LEDs would vary by hardware/driver/etc. There isn't a general function for that on FreeBSD in ifconfig or similar, and FreeBSD doesn't have a tool like etherblink on Linux.

I thinking about led, igb, em... led(4) is not suitable for that ?

igb(4)
Make the identification LED of igb0 blink:
echo f2 > /dev/led/igb0
Turn the identification LED of igb0 off again:
echo 0 > /dev/led/igb0
em(4)
Make the identification LED of em0 blink:
echo f2 > /dev/led/em0
Turn the identification LED of em0 off again:
echo 0 > /dev/led/em0

IMHO, better to:
- start with NICs that already exist in NetGate appliances (igb/em drivers?)
- expand on most used NICs (I thinking not more +3 drivers)

Spending resources on a bunch of other less-known NICs seems to be unreasonable.

Actions

Also available in: Atom PDF