fixed bug in tunnel monitoring code

This commit is contained in:
csoler 2018-04-14 11:48:55 +02:00
parent 66df281f25
commit 3c9af3d2e7
No known key found for this signature in database
GPG Key ID: 7BCA522266C0804C

View File

@ -704,11 +704,11 @@ void RsGxsNetTunnelService::autowash()
#ifdef DEBUG_RSGXSNETTUNNEL #ifdef DEBUG_RSGXSNETTUNNEL
std::cerr << " active, with client-side peers : "; std::cerr << " active, with client-side peers : ";
#endif #endif
should_monitor_tunnels = true ; should_monitor_tunnels = false ;
} }
else else
{ {
should_monitor_tunnels = false ; should_monitor_tunnels = true ;
#ifdef DEBUG_RSGXSNETTUNNEL #ifdef DEBUG_RSGXSNETTUNNEL
std::cerr << " active, and no client-side peers available : " ; std::cerr << " active, and no client-side peers available : " ;
#endif #endif
@ -719,8 +719,9 @@ void RsGxsNetTunnelService::autowash()
std::cerr << " passive : "; std::cerr << " passive : ";
#endif #endif
// check if the group is in active or passive mode, in which case make sure that turtle manages tunnels or not. // We should also check whether the group is supplied using another tunnel. If so, no need to request tunnels.
// if active, then we check wether they are tunnels are not. If not, we ask turtle to monitor. // Otherwise the engine will keep requesting tunnels for all groups.
#warning CODE MISSING HERE
if(should_monitor_tunnels) if(should_monitor_tunnels)
{ {