Opened 3 years ago

Closed 3 years ago

#549 closed defect (fixed)

IRC Tunnel Issues

Reported by: Bry8Star Owned by: zzz
Priority: major Milestone: 0.8.12
Component: apps/i2ptunnel Version: 0.8.10
Keywords: Cc:
Parent Tickets:

Description

Hi, submitting IRC tunnel issue report, as 'zzz' requested.
Me & few other Irc2P irc members have tried to setup an outproxy to an internet irc server, by creating an IRC Server tunnel, and at 1st, an IRC client tunnel toward that server tunnel.
But did not succeed to connect to that internet irc server from XChat/PChat <--> IRC client tunnel <--> IRC Server tunnel <--> internet IRC server.
So, in 2nd attempt, we tried a Socks IRC client tunnel, that didnt work either : XChat/PChat <--> Socks-IRC client tunnel <--> IRC Server tunnel <--> internet IRC server.
So, in next attempt, i've installed ZNC (an IRC bouncer proxy/gateway server) in my WinXP, created another (2nd) IRC server tunnel which connects to ZNC's service port. And altered previous IRC client tunnels to connect to the 2nd Server tunnel's b64 address/location which uses the ZNC.
So it was, XChat/PChat <--> IRC or Socks-IRC client tunnel <--> IRC Server tunnel <--> ZNC <--> internet IRC server ... none of the IRC client tunnel worked. End user IRC client (XChat/Pchat) was keep on showing "* You need to send your password. Try /quote PASS <username>:<password>".
So, with the help of an ZNC developer (SilverLeo?), we put the ZNC in 'debug' mode, it was showing all type of communication in between ZNC & its clients. As a result of our observation, that developer pointed out, that "before CLI -> ZNC [NICK, there should be CLI -> ZNC[PASS ..". So I2P in both type of IRC client tunnel was dropping some necessary communication/exchange packets which are related to PASSWORDS for user authentication on ZNC, though NICKNAME/USERNAME was going through.
After that, while discussing+reporting about it on irc channel, the I2P member 'postman' also notified in the Irc2P #irc-dev channel, that "please consider that irc-tunnels are doing active filtering and sanitization".
Then Irc2P member "darrob" suggested to use 'Standard Tunnel", so i created a 'Standard' type of client tunnel to connect to the server tunnel, which worked, rightaway. So this worked, XChat/PChat <--> Standard client tunnel <--> IRC Server tunnel <--> ZNC <--> internet IRC server. So a connection to internet irc server, without a ZNC bouncer, will also work.
So, please fix the issues in the "IRC" client tunnels, so it works according to its "IRC" name.
By the way, another thing, inside the client tunnel when i've specified b32 address/location of Server tunnel, or when specified the "irc-server.i2p" address (which i added previously in the 'Master' addressbook as "irc-server.i2p), then those address/location were not able to reach to actual destination properly, but when the b64 long address/location of Server tunnel was used, then that worked. But in the I2PTunnel page those IRC & Standard Client tunnel was displaying/showing long b64 address texts which overflowed those client's rows.

Subtickets

Change History (2)

comment:1 Changed 3 years ago by zzz

  • Component changed from unspecified to apps/i2ptunnel
  • Owner set to zzz
  • Status changed from new to accepted

As your diagnosis shows, the IRC Client tunnel currently filters PASS. Nobody's ever used it before. I'll fix it soon.

comment:2 Changed 3 years ago by zzz

  • Resolution set to fixed
  • Status changed from accepted to closed

fixed 0.8.11-1

Note: See TracTickets for help on using tickets.