Routing plan
From Blitzed
The routing plan is now dynamically generated (by sonorous) so the routing plan is not shown below any longer; however, this page will be updated to show a summary of how network routing should look like in an ideal scenario as well as showing current Y: and H:lines.
[edit] Y: lines
# Class 50 - Hub to hub, autoconnect Y:50:90:60:1:550000 # Class 51 - Hub to hub, no autoconnect Y:51:90:60:0:550000 # Class 30 - Hub to leaf, hubs should never autoconnect to leafs Y:30:90:0:0:550000 # Class 40 - Leaf to hub, autoconnect Y:40:90:60:1:500000 # Class 41 - Leaf to hub, no autoconnect Y:41:90:60:0:500000 # Class 10 - IRC Operators Y:10:90:0:10:250000 # Class 1 - Normal Users Y:1:90:0:1024:100000
NOTE: For the class 1, change 1024 to number of fds you specified during 'config'
[edit] Routing overview
The routing plan displays the following characteristics:
- EU local hubbing duties split between penguin, smalahove and tabasco.
- NA local hubbing duties split between raisin and sausage.
- Each regional hub ideally autoconnects to two hubs in same region.
- Primary EU/NA link penguin/raisin (autoconnect).
- Secondary EU/NA link smalahove/raisin (autoconnect).
- Tertiary EU/NA link tabasco/sausage (autoconnect).
- All hubs can connect to all other hubs (non-autoconnect unless otherwise noted).
- Each leaf ideally autoconnects to two or more local hubs.
- All leaves can connect to all hubs (non-autoconnect unless otherwise noted).
- By connecting locally first it is hoped we can avoid situations where we have multiple transcontinental links.
NOTE: For the class 50 and 40 C/N lines, remember to put your PRIMARY link LAST as the config is read from bottom to top. The C/N lines for your server are already in the correct order!
[edit] H: lines
Every server needs to have these H: lines:
H:*::penguin.uk.eu.blitzed.org H:*::raisin.hub.us.blitzed.org H:*::sausage.tx.us.blitzed.org H:*::services.blitzed.org H:*::smalahove.hub.eu.blitzed.org H:*::tabasco.uk.eu.blitzed.org