# $Id: routing.txt,v 1.4 2009/11/19 06:35:04 avenj Exp avenj $

Simple server routing rundown.

/MAP will always show the current routing layout.
However, it will be relative (as viewed from the local server's perspective)
In a purely technical sense, routing is always relative, but for sanity's sake
it sometimes helps to have a handle on the top-down/logical layout.

For example (bc opers note that this is not a current map):

>eris.oppresses.us -> /MAP
 --- eris.oppresses.us 
 ---  |- cerberus.oppresses.us  
 ---  |- ircd.blackcobalt.net 
 ---  |   `- utility.blackcobalt.net                   
 ---  `- nyx.oppresses.us 
 --- End of /MAP

Versus:

>ircd.blackcobalt.net -> /MAP
 --- ircd.blackcobalt.net  
 ---  |- eris.oppresses.us 
 ---  |   |- cerberus.oppresses.us
 ---  |   `- nyx.oppresses.us
 ---  `- utility.blackcobalt.net
 --- End of /MAP


The map as viewed from eris can be broken down like this:
 ----- eris.oppresses.us --------------------------
 |                       |                        \
 ircd.blackcobalt.net    cerberus.oppresses.us     nyx.oppresses.us
  \
   utility.blackcobalt.net


The map as viewed from ircd.blackcobalt.net:
 ----- ircd.blackcobalt.net -
 |                           \
 eris.oppresses.us            utility.blackcobalt.net
 |
 |--------------------------\
 cerberus.oppresses.us       nyx.oppresses.us


Based on that, a top-down view of the map (with some extra info):
      hub                                   hub
 eris.oppresses.us <----cryptlink----> ircd.blackcobalt.net  # TS6 user servers
         |                                  |
         |                                  |
        /----------------\                  |
cerberus.oppresses.us     nyx.oppresses.us  |
    leaf                    leaf            |
                                            |
                                 utility.blackcobalt.net
                                         (services)
                                         leaf


Now, we lose (SQUIT) the link between eris.oppresses.us and ircd.blackcobalt.

An operator on eris.oppresses.us could do a simple local reconnect:
 -> /connect ircd.*

An operator on ircd.blackcobalt.net could do the same:
 -> /connect eris.*

However, an operator on nyx.oppresses.us would want to connect remotely.
`nyx` is hubbed to `eris` and wants connectivity to ircd.blackcobalt.net:
 -> /connect ircd.* 0 eris.*

Say `cerberus` and `nyx` in the above map generally route to `eris`
...and `eris` dies a fiery death
An operator on ircd.blackcobalt.net could verify that there are redundant connect
lines for `nyx` and `cerberus` using STATS:
 -> /stats c
--- C 1.2.3.4 CTZ cerberus.oppresses.us 6665 servers
--- C 1.2.2.1 CTZ nyx.oppresses.us 6666 servers
 -> /connect nyx*
 -> /connect cerberus*


See also operbasics.txt