[Raspbian-devel] Suggestions for a Pi's Ethernet interface LEDs and tracking in /boot/config.txt.

[John W. Kitz]

Dave,

Thanks for taking the time to respond.

On 2018-06-07 01:32, Dave Stevens wrote:
> On Wed, 6 Jun 2018 23:40:51 +0200
> "John W. Kitz" <John.Kitz-hob at xs4all.nl> wrote:
> 
>> 1. Is it technically feasible to track the activity related to a Pi's
>> Ethernet interface?
> 
> I don't understand what aspect of the port's activity you want to track

See my original post, my reply to Stian and e.g.:

https://superuser.com/questions/1236248/what-kind-of-network-activity-the-blinking-ethernet-led-really-indicates

https://docs.oracle.com/cd/E19910-01/E21500-01/bbjdcdaf.html

http://www.deltamotion.com/support/webhelp/rmctools/Communications/Ethernet/Ethernet_Link_LED.htm

https://www.ibm.com/support/knowledgecenter/STPVGU_7.8.0/com.ibm.storage.svc.console.780.doc/svc_etheractled_37prgy.html

> - is it the data rate, chip temperature, error rate, or content?

These are what one would typically monitor using SNMP and MRTG, OpenNMS 
or some other, either non-commercial or commercial, product. I.e. no 
these are not the kind of metrics that I'm referring to here.

>   Different solutions would apply. For content you might consider
>   tcpdump or wireshark. I'm most familiar with wireshark so I'd use
>   that. There's a thread here you might find informative:
> 
> https://raspberrypi.stackexchange.com/questions/13780/pi-performance-tcpdump-vs-wireshark
> 
> Dave

Regards, Jk.