View Issue Details

IDProjectCategoryView StatusLast Update
0001345unrealircdpublic2003-11-06 23:27
ReporterThe_Nightshift Assigned To 
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionopen 
Product Version3.2-beta18 
Summary0001345: linking problems (Updated info)
DescriptionNote: this was an earlier problem, but I believe the first time round my attempt to keep the acurate server names hidden from the public (I don't want a large amount of people on the network)

I've been trying to link a network consisting of 1 server, one hub (both on unrealIRCd 3.2-beta18), and 1 services server (running epona) (all within the same LAN). However, when services is linked to the hub server and I try to get the other server to link (note: I removed the actual server names [placed <>s around a description of where they stand on the nerwork {I manually substituted <hub> for the hub server name, which does appear properly in the @SNotice, <leaf> for the leaf, and <services> for the services}] since at least one has a working DNS [and I'd like to keep the server fairly private]):

Leaf @SNotice [ 16:25:39 ] · · Server : Notice -- Connection to <hub>[192.168.1.155] activated.

Hub @Snotice [ 16:25:40 ] · · Server : Notice -- Connection to <leaf>[192.168.1.200] activated.

Hub " [ 16:25:40 ] · · Server : Notice -- Connection to <leaf>[192.168.1.200] activated.

leaf " [ 16:25:41 ] · · Server : Notice -- (link) ZIPLink <leaf> -> <hub>[@192.168.1.155.1668] established

leaf " [ 16:25:41 ] · · Server : (link) ZIPLink <hub> -> <leaf>[@192.168.1.200.0] established

leaf " [ 16:25:41 ] · · Server : LocOps -- Link <hub> cancelled, linked in <services>, which hub config disallows

hub " [ 16:25:41 ] · · Server : Notice -- (link) ZIPLink <hub> -> <leaf>[@192.168.1.200.0] established

hub " [ 16:25:42 ] · · Server : (link) ZIPLink <leaf> -> <hub>[@192.168.1.155.1668] established

hub " [ 16:25:42 ] · · Server : Notice -- Link <leaf> -> <hub> is now synced [secs: 0 recv: 0.615 sent: 0.934]

hub " [ 16:25:42 ] · · Server : Notice -- Zipstats for link to <leaf>[@192.168.1.200.0]: decompressed (in): 237/345 (68.7%), compressed (out): 2064/728 (35.3%)

hub " [ 16:25:42 ] · · Server : Lost connection to <leaf>[192.168.1.200]:Unknown Error 10053

leaf "[ 16:26:09 ] · · Server : Notice -- No response from <hub>[192.168.1.155], closing link

however, when I try linking the hub and leaf without services linked into the hub it will work unless I try linking services in after, which yeilds the same error from the leaf. Note: for the hub entry on the leaf's link block I have tried both the acurate DNS name (which my router has blocked) and internal IP of the hub's machine (which yeilds the above results).
Additional InformationI'm sorry if my wording caused any misunderstanding the first time, and for doing a new post of the same problem (wasn't sure if I could edit and reopen the first listing, and didn't want to get it wrong).
3rd party modules

Activities

The_Nightshift

2003-11-06 19:37

reporter   ~0003983

erm..add the words "was misinterprited as a config error on my part" to the end of the first sentenence

The_Nightshift

2003-11-06 19:49

reporter   ~0003984

Additional info: on one occasion I saw another line on the hub's @SNotice, showing an error sent from the leaf, cairo, saying that · · Server : LocOps -- ERROR :from cairo.<domain name, hidden for privacy reasons>[192.168.1.200] -- Closing Link: <hubname, which DNS resolves, and I am therefore hiding>[192.168.1.155] (Not matching hub configuration)

syzop

2003-11-06 23:27

administrator   ~0003985

Well, again... this really looks like an configuration problem on your side. It works fine here (IF configured properly).
See the docs for more info, http://www.vulnscan.org/UnrealIrcd/unreal32docs.html#linkblock
And if you don't understand it, just use hub *;

Issue History

Date Modified Username Field Change
2003-11-06 19:35 The_Nightshift New Issue
2003-11-06 19:37 The_Nightshift Note Added: 0003983
2003-11-06 19:49 The_Nightshift Note Added: 0003984
2003-11-06 23:27 syzop Status new => closed
2003-11-06 23:27 syzop Note Added: 0003985