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] Software Probs
- Previous message (by thread): [atlas] Software Probs
- Next message (by thread): [atlas] Software Probs
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Philip Homburg
philip.homburg at ripe.net
Fri Nov 28 18:52:08 CET 2014
Hi Shahin, On 2014/11/26 15:56 , Shahin Gharghi wrote: > The other way to save probes is making probes multi-home. > For example I have 4 probes in one place to monitor 4 different IP > prefixes and paths. I know because of the hardware limits we can't use > sub-interfaces but we can set 4 IP addresses manually and add 4 any > route by the source, then we can save 3 other probes. One thing to keep in mind is that there are very good reasons to try to keep probes as simple as possible. Even if that means installing 4 probes in one location. Extra complexity translates into extra testing effort and more bugs. What is gained by using the hardware more efficiently can be lost easily in more engineering effort. At this moment, making a probe multi-homed would be a significant engineering effort because just about all code implicitly assumes that every probe has exactly one interface. (I assume that from a hardware point of view, VLAN tagging would allow a probe to be connect to different ethernets) Philip
- Previous message (by thread): [atlas] Software Probs
- Next message (by thread): [atlas] Software Probs
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]