This is the code to implement a bridge between IRCnet 2.10.x servers and Hybrid/comstud/th servers. There are two parts, a bridge between TS servers and non-TS servers, part1-ts-to-non-ts/ (any variant) and a bridge between 2.8 and 2.10 servers, part2-ircnet/ There are three ways to do the TS to non-TS bridge part1-ts-to-non-ts-hyb4.3/ channel.c - This is needed to reconstruct an SJOIN from an IRCnet combined JOIN/MODE. Stick this in ircd/ in the source tree. NOTE: This violates TSora, but it's needed for Hyb5 and higher servers. channel-ts.diff - The diff that generates the channel.c above ircd-hybrid-4.3.tar.gz - The base distribution. This MUST be configured to allow Non-TS server linkages. no-ip-links.diff - This patch removes the annoying [ip] in LINKS Apply to s_serv.c ===OR=== part1-ts-to-non-ts-csr31/ csr-channel-ts.diff - This is needed to reconstruct an SJOIN from an IRCnet combined JOIN/MODE. Stick this in ircd/ in the source tree. NOTE: This violates TSora, but it's needed for Hyb5 and higher servers. csr-no-ip-links.diff - This patch removes the annoying [ip] in LINKS Apply to s_serv.c irc2.8.21+CSr31pl4.tar.gz - The base distribution. This MUST be configured to allow Non-TS server linkages. csr-wallops-allow.diff - This patch allows user generated WALLOPS to be sent through csr-ts-second-part.diff - Another patch that must be used to help stop TS0 propogation ===OR=== part1-ts-to-non-ts-ts3ora/ irc2.8.21+TSora3.tar.gz - The base distribution. This MUST be configured to allow Non-TS server linkages. ts3-channel-ts.diff - This is needed to reconstruct an SJOIN from an IRCnet combined JOIN/MODE. Stick this in ircd/ in the source tree. NOTE: This violates TSora, but it's needed for Hyb5 and higher servers. ts3-no-ip-links.diff - This patch removes the annoying [ip] in LINKS Apply to s_serv.c ts3-operwall.diff - This patch adds an OPERWALL command, which just calls m_wallops. This will transparently transform OPERWALL's to WALLOPS ts3-wallops-is-not-channel.diff - Allow WALLOPS to be passed through without turning them into PRIVMSG's to #wallops -- It is recommended that you use 2.8.21+TS3ora, as the other two have "bastardized" WALLOPS commands, automatically turning WALLOPS into OPERWALL's downstream, even with the patches in broken/ installed. -- part2-ircnet/ 2.9.2p3.ip-hide.diff - This patch removes the annoying [ip] in LINKS Apply to s_serv.c 2.9-operwall.diff - This patch adds an OPERWALL command, which just calls m_wallops. This will transparently transform OPERWALL's to WALLOPS 2.9-nocomment.diff - This removes the nick from the PART comment in anything coming from the Hybrid side irc2.9.2p3.tgz - The base distribution. This MUST be configured to allow 2.8 protocol linkages. It may also be good to disable SERVICES on this part of the bridge. wallops-allow.diff - Allow WALLOPS to be passed through without turning them into PRIVMSG's to #wallops -- The network can be constructed like the following /------------------------\ |EFnet Compatible Network| |Running Hybrid 5/6/7 | |CSr29 or higher | |comstud 1.x | |+th5 or 6 | \------------------------/ | | /--------------------------\ \---------|Hybrid 4.3 with patches OR| |CSr31pl4 with patches OR | |2.8.21+TSora2 with patches| \--------------------------/ | | /---------------------------\ \--------|IRCnet 2.9.2p3 with patches| \---------------------------/ | | /-------------------------\ \-----------|IRCnet Compatible Network| |Running 2.9/2.10/irce | \-------------------------/ -- Although this is a little complicated, and brings ancient code into the mix, I believe that it is a good way to bridge the gap between these two protocols, allowing for most normal server functions to go through without issue. Some things will not properly go through the bridge. Services will not appear on the other side (services as IRCnet implements), channels MAY have desync issues, and there's a possibility of weird collides. IPv6 clients may be rejected by the Hybrid side, especially if old Hybrid servers are present. Many things will work though, including all normal channel activity, KILL's and IRCnet's ident prefixes. At the present time, user generated WALLOPS will not pass through part1. As I test more, I will add more to this document. -- This bridge is not in production anywhere at the present time.