FlexHub Forum

Redirect system

Offline LadyStardust

  • *****
  • 257
  • aka Puma
Redirect system
« on: January 25, 2011, 21:36:30 »
Redirecting system in FlexHub. To check redirecting settings in FlexHub type        !set redirects
If you want to change any settings that you can see listed below, use !set <redirect type> <value>

   !set rd_adc_disabled <address>                      Value: no.adcdisabled.redirect.specified:8000        
When ADC is disabled, users connecting to the hub via ADC protocol will be redirected specified address. Own NMDC hubaddress can be used.
(ADC can be disabled with !set allowadc false)
e.g. !set rd_adc_disabled your.nmdc.hub.address:2006
   !set rd_breakloop_enable <false/true>                     Value: false
Break a redirect loop if a redirected users keeps reconnecting to the hub. Warning: experimental feature!
   !set rd_breakloop_timeout <time>                  Value: 120 ( 0 day(s) 00:02:00 )                   
Time in seconds since last redirect that a user will be considered to be in a redirect-loop
   !set rd_breakloop_times <number>                       Value: 5                                           
Number of allowed reconnects before a user is considered to be in a redirect-loop
   !set rd_deadend <address>                               Value: no.deadend.redirect.specified:8000          
End redirect address for users in a redirect-loop. Only used when !set rd_breakloop_enable is set up to "true"
   !set rd_deadendfail <address>                          Value: no.deadendfail.redirect.specified:8000        
Redirect address for users who are still reconnecting after being send to the deadend address
   !set rd_flood <address>                                Value: no.flood.redirect.specified:8000            
Redirect address for users that are flooding (in any way - mainchat flood, pm flood, search flood etc)
   !set rd_full <address>                                  Value: no.hubfull.redirect.specified:8000          
Redirect address for when hub is full (user's limit is specified with !set maxusers command)
   !set rd_main <address>                                  Value: no.main.redirect.specified:8000             
General redirect address (where users get redirected after kick/ban etc.)
   !set rd_maxhubs <address>                               Value: no.minslots.redirect.specified:8000         
Redirect address for users with too many hubs (maximum hubs allowed by a user can be specified with !set maxhubs command)
   !set rd_maxshare <address>                              Value: no.maxshare.redirect.specified:8000         
Redirect address for users with too large share (maximum share allowed by a user can be specified with !set maxshare command)
   !set rd_maxslots <address>                            Value: no.maxslots.redirect.specified:8000         
Redirect address for users with too many slots (maximum amount of slots allowed by a user can be specified with !set maxslots command)
   !set rd_minshare <address>                             Value: no.minshare.redirect.specified:8000
Redirect address for users with too small share (minimum amount of share allowed by a user can be specified with !set minshare command)
   !set rd_minslots <address>                              Value: no.minslots.redirect.specified:8000         
Redirect address for users with too few slots ( minimum amount of slots allowed by a user can be specified with !set minslots command)
   !set rd_nmdc_disabled <address>                         Value: adc://no.nmdcdisabled.redirect.specified:8000        
When NMDC is disabled, users with NMDC will be redirected here. Own ADC hubaddress can be used (NMDC can be disabled with !set allownmdc false)
   !set rd_passive <address>                              Value: no.passive.redirect.specified:8000          
Redirect address for passive users if passive users aren't allowed to join. (to disallow check !set allowpassive command)
Best regards,
LS