Page 1 of 1
how to handle autoconnect entrys with two hubs?
Posted: Wed Nov 03, 2004 6:03 pm
by diskman
hmm i think topic is self explayning... ehhmm ok
i have a network with two hubs
if the leafs have in the hub link lines autoconnect set then they connecting to both hubs at the same time --> errors like "server already exists" and leaf is not linked
there are any good ideas how the link lines should be set?
sorry for my bad english
Posted: Wed Nov 03, 2004 8:27 pm
by aquanight
I'm not too sure, but I think the maxclients line in the server class can be used to control autoconnect. In other words, try setting the maxclients in your Server class to 1 and see if that helps.
Posted: Wed Nov 03, 2004 8:30 pm
by diskman
oh... looks interresting... i will try it
Posted: Wed Nov 03, 2004 8:56 pm
by diskman
hmm...
doesnt work...
[21:48:39] *** (s) Notice -- Connection to hub.xxxirc.net[123.123.12.12] activated.
[21:48:39] *** (s) Notice -- Connection to althub.xxxirc.net[123.123.12.12] activated.
thats the way the server connects to the hub... iam not testing the hub connects to the server...
but i think it works like an gline...
connection... "handshake".... limit?? (limit true ->> disconnect, limit false continue)
it should working like an zline
connection on port xx -->> serverport --> limit?? (true/false)
between the updates i have tried some variants first autoconnect from hub to leaf and from leaf to hub --> fatal *g*
now I am running the hubs completly passive and the leafs are connection at the same time to both hubs
if now one has any idea i will try:
one hub active and one passive
the link lines at the leaf the same one autoconnect the other not
should i post the results?
greetz diskman
P.S: Yes I am German and can't talk english
Re: how to handle autoconnect entrys with two hubs?
Posted: Wed Nov 03, 2004 10:13 pm
by katsklaw
diskman wrote:hmm i think topic is self explayning... ehhmm ok
i have a network with two hubs
if the leafs have in the hub link lines autoconnect set then they connecting to both hubs at the same time --> errors like "server already exists" and leaf is not linked
there are any good ideas how the link lines should be set?
sorry for my bad english
Leaf: You should only have 1 autoconnect in the conf file. It's uplink.
Hub: Hubs should have autoconnects for every server it links to, however no 2 servers should have autoconnects for the same server. Meaning server 1 and server 2 should not have autoconnects for server 3. One or the other .. but not both.
Posted: Thu Nov 04, 2004 7:41 pm
by diskman
hmm ok i will try
i dont want a map where a hub is linked to another hab trough a leaf do you know what i mean?
but if iy compile leaf as laef thad should not work....
ok i will see
Posted: Thu Nov 04, 2004 7:46 pm
by diskman
could a nice feuture...
a options flag like "second-hub"
effected that server first will autoconnect to normal entry an if this fails autoconnect to link line where option flag "second-hub" is set
should i request it?? or any arguments against this feauture?
Posted: Thu Nov 04, 2004 10:53 pm
by katsklaw
diskman wrote:could a nice feuture...
a options flag like "second-hub"
effected that server first will autoconnect to normal entry an if this fails autoconnect to link line where option flag "second-hub" is set
should i request it?? or any arguments against this feauture?
I don't think it sounds like a bad suggestion to have a "connect here if the first server fails" .. however I think good old fashion brain power is best. Meaning that IRCops should be trained enough to do routing and not solely rely on autoconnects.
Also as a side note. I usually compile all servers as hubs (except those shells that require leaf only) and configure all servers as hubs as well. This give me and my staff the freedom to connect a server to the fastest link possible and use any and all servers as hubs and reduces the amount of time the net is split.