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/[email protected]/
[atlas] [ripe.net #1087678] problem with connection to network
- Previous message (by thread): [atlas] [ripe.net #1087678] problem with connection to network
- Next message (by thread): [atlas] [ripe.net #1087678] problem with connection to network
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Philip Homburg
philip.homburg at ripe.net
Tue May 28 11:26:21 CEST 2013
On 5/28/13 10:50 , Dmitriy Kazimirov wrote: > hi, > Well,ok. thanks > 1st question: > - Probe is hosted behind Dual-WAN router with 2 residtual connections with 2 different ISPs. Both connections are online, traffic is load-balanced between them. Right now I configured router to allow probe traffic via main connection. Should I allow router to just switch between connections as all other devices on internal network do ? Should I ask for 2nd probe and lock it into 2nd connection? > (If that's matter, I use Astaro Security Gateway software appliance as router) > Hi, For getting consistent results it would be best to configure the router to use just one connection for the probe. I think it is best to get the current probe to be stable for a while before asking for a second probe.
- Previous message (by thread): [atlas] [ripe.net #1087678] problem with connection to network
- Next message (by thread): [atlas] [ripe.net #1087678] problem with connection to network
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]