This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas]Feature request (fo consideration): broadcast rate measurement?
- Previous message (by thread): [atlas]Feature request (fo consideration): broadcast rate measurement?
- Next message (by thread): [atlas]Feature request (fo consideration): broadcast rate measurement?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jesper Skriver
jesper at skriver.dk
Sat Apr 9 11:42:50 CEST 2011
Hi As I see it the atlas project is about getting a global view. So in my book the last thing we want is stats about the local LAN segment the probe is connected to. Further more for privacy and security reasons the probes should in my mind gather as little information about the directly attached network as possible. /Jesper "Wilfried Woeber, UniVie/ACOnet" <Woeber at CC.UniVie.ac.at> wrote: >Xmas WishList 2011 :-) > >Looking at the yellow LED of the probes, I presume that their Ethernet IF >operates in promiscuous mode. Even if not... > >I'd like to see some (easily configurable) measurement available, at least >the rate of broadcast-packets on the probe's net. > >On a more elaborate basis, maybe according to simple paramters like a >protocol/port combination. > >Would this make sense to implement and be of interest to others? > >Thanks for consideration, >Wilfried. > >PS: yes, I do know about Netflow, WireShark and similar, but the beauty of > the ATLAS Probe Approach is imho in the ready-nade UI :-) >
- Previous message (by thread): [atlas]Feature request (fo consideration): broadcast rate measurement?
- Next message (by thread): [atlas]Feature request (fo consideration): broadcast rate measurement?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]