Opened 5 years ago

Last modified 5 years ago

#1337 assigned task

Check IRC/HTTP filter for IPv6

Reported by: Eche|on Owned by: Eche|on
Priority: maintenance Milestone: 0.9.21
Component: apps/i2ptunnel Version: 0.9.13
Keywords: Cc:
Parent Tickets: Sensitive: no

Description

Moin

If a IPv6 only client connect to IRC/HTTP via I2P, does our IRC/HTTP client tunnel filter IPv6?
Or do they only filter IPv4 addresses?

echelon

Subtickets

Change History (1)

comment:1 Changed 5 years ago by zzz

Milestone: 0.9.150.9.21
Owner: set to Eche|on
Priority: majormaintenance
Status: newassigned

I don't see any problem with filtering. But in some places including DCC code, it pretends that the server is at 127.0.0.1. Generally it strips out the "real" IP and puts in 127.0.0.1. So whatever the real IP is, doesn't matter.

If there's any issues with IPv6 they are best discovered by testing with a particular client. I did a quick look in a couple minutes but I'm not going to audit the code.

Reducing priority and assigning back to you to test if desired. xchat raw log, for example, could be helpful here. Then either add info or close.

Note: See TracTickets for help on using tickets.