User:Adys/News/Items/Woah, finally

I just finished a few hours ago installing and configuring an IRC bouncer. Here are a few facts for the ones interested in setting one up: 1) There is NO documentation on IRC bouncers on the net. None I used to say there is absolutely everything on the net - I didn't think THAT would be lacking. 2) Some dedicated server providers block port 6667 by default, both incoming and outgoing - OVH does at least. Luckily, you should be able to modify that somewhere. 3) The only comparison of IRC bouncers on the net is here. 4) Don't search, all the best bouncers lack an important feature. irssi-proxy lacks backlogs, ctrlproxy lacks documentation & support, znc lacks multiserver connection, ezbounce lacks TONS of stuff...

I tried the ones above except ezbounce, and I spent a LONG time trying to configure ctrlproxy, thinking it was the one suiting my needs the most. They say they have an user friendly interface, I have yet to find it. I then came back on my choice and gave ZNC a try. This one is wonderful. I did however spend a good hour trying to configure all the channels I was in...

I also said ZNC does not support multiple networks, and this is true. Luckily, I could work that around: Create as many users as you have networks. Adys, Adys2, Adys3... I highly recommend using the webadmin plugin, by the way. It's sickly wonderful. Give them the same password, and assign each user to a certain network. Now, the hard part is hoping your IRC client does not suck. You need to create multiple networks of the same address on the port you assigned at first. You will have to change the Username for each server, since this is the only factor redirecting you to a different backlog. Since XChat does not offer that possibility, I created an onconnect file on the first network, that automatically signed on the other servers. (x = ip, p = port) /newserver x.x.x.x pppp username:password

There. I hope this ends up helping someone.