i have a big problem.
i have a big problem.
i have an ircd network. my oses are freebsd and i am using unreal3.2.5
i have 1 hub and a lot of leaf.
my hıb server is irc.abc.net
ex: i connect my 3 leaf to my hub. it is everything oK.
i am entering in the hub and write /squit leaf1.abc.net or /squit leaf1.* and after that leaf1 left from my network.
after that when i write /connect leaf1.* , it connects but in that time the other leafs says:
[13:47] -irc.abc.net- *** LocOps -- ERROR :from leaf2.abc.net[] -- Server leaf1.abc.net already exists from irc.abc.net
they says the server which i lefted from server is still on server. and they squit in that time.
Did you understand?
i squit a link and re connect a link, in that time other links says the link is already connected on irc.. and we are squiting. and they close the connection.
What is my problem?
i have 1 hub and a lot of leaf.
my hıb server is irc.abc.net
ex: i connect my 3 leaf to my hub. it is everything oK.
i am entering in the hub and write /squit leaf1.abc.net or /squit leaf1.* and after that leaf1 left from my network.
after that when i write /connect leaf1.* , it connects but in that time the other leafs says:
[13:47] -irc.abc.net- *** LocOps -- ERROR :from leaf2.abc.net[] -- Server leaf1.abc.net already exists from irc.abc.net
they says the server which i lefted from server is still on server. and they squit in that time.
Did you understand?
i squit a link and re connect a link, in that time other links says the link is already connected on irc.. and we are squiting. and they close the connection.
What is my problem?
The problem is that as you quite rightly said the leaf still thinks its connected to the hub. This is because either the leaf didnt actually receive the SQUIT message or didnt associate it with the hub server so as far as the leaf is concerned the connection is still established. You shouldnt have to wait for long before the leaf should register the disconnection to itself a sa ping timeout.
How long you need to wait depends on the ping frequency in the class block used by the servers link block.
The alternative is youll have to get an oper on the leaf to /squit the hub even though its actually already disconnected. The reason for this is so you can tell the leaf that the hub has been disconnected.
The alternative is youll have to get an oper on the leaf to /squit the hub even though its actually already disconnected. The reason for this is so you can tell the leaf that the hub has been disconnected.
i squit a leaf from my hub and reconnect it. in that time another leaf said it is already and quit. after that i use the /connect command with the quitten leaf, in that time the other leaf said it is already it has gone. one by one. they says it is already. i can't connect both of them. i can only by restarting hub..
cculha all of the servers do see it. What's happening is a server you think is a leaf is actually a hub so the server you want to get rid of is configured to connect to the server that it connects to. All you have to do is login to the server that the server you are trying to get rid of is connected to and /squit it from there. I'll give you a little demo below. You want to get rid of Leaf 2
/map from Hub 1
Hub1
-Leaf1
-Leaf2
-Leaf3(which is really a hub)
/squit Leaf1 while on Hub1
/map from Hub1
Hub1
-Leaf2
-Leaf3
--Leaf1
/squit leaf1 while on Leaf3
/map from Leaf3
Hub1
-Leaf2
-Leaf3
do you understand?
/map from Hub 1
Hub1
-Leaf1
-Leaf2
-Leaf3(which is really a hub)
/squit Leaf1 while on Hub1
/map from Hub1
Hub1
-Leaf2
-Leaf3
--Leaf1
/squit leaf1 while on Leaf3
/map from Leaf3
Hub1
-Leaf2
-Leaf3
do you understand?