Asuka C:Line help

mouselike · Idler Joined: 09 Dec 2003 Posts: 258

the only thing i can suggest is letting port 4400 bind to all available ip's unless its a shared box like payed hosting etc then you may have to contact the root to solve it, then letting it try to connect.

This was actually a problem we had on one of our ircd boxes, we had to bind to a local ip rather than a wan ip in order for it to be able to bind due to ethernet being all wrong.

Acidblood · none Joined: 11 Jan 2005 Posts: 9

It is hosted on a shared box and i emailed the hosting provider seeing if theres anything they can do about it.

Thanks for all your help! Very Happy

runuen · none Joined: 23 Mar 2004 Posts: 7

Hey man, I had this problem too! I got like 2 servers connected (Hub to Hub Links and Hub to Hub Services) but then NOTHING else would connect. I tried to connect new leafs on seperate providers and everything! I never did figure out the problem (My C:Lines/P:Lines/M:Lines were all correct and I rehashed, restarted, killed and started again an hour later) so I went to beware. Beware isn't anywhere near as good as IRCu but I wanted aliases and bircd has EASY linking with no problems. I'm interested in someone finding an answer to the problem soon too because I want ircu again!

Proto · Lurker Joined: 23 May 2004 Posts: 150 Location: IRC

If you need some help with asuka drop by my net, irc.hazenet.org

Acidblood · none Joined: 11 Jan 2005 Posts: 9

I realised it was a F:Line that was causing the problems. Because my IRCD was hosted on a machine with multiple IP addresses i had to set F:VIRTUAL_HOST:TRUE . This solved the problem for me. Was a stupid mistake really. Hope this helps!