SixXS::Sunset 2017-06-06

IRCnet Kline 2001:768:1900::/40
[de] Shadow Hawkins on Wednesday, 13 August 2003 13:42:16
just to let you know: 2001:768:1900::/40 is klined on irc.uni-erlangen.de and linz.irc.at with reason "K-lined: abusive clients over inactive Tunnelbroker". I guess someone with a tunnel/subnet from sixxs abused IRCnet rules. irc@uni-erlangen.de doesn't respond to me. Dunno what really happened - hopefully the kline gets removed soon.
IRCnet Kline 2001:768:1900::/40
[ch] Jeroen Massar SixXS Staff on Wednesday, 13 August 2003 15:46:46
They didn't notify either info@sixxs.net or abuse@sixxs.net. Apparently some people misbehave on IRC, thus they get blocked. IRC is certainly one of the things we don't care about. IPv6 is not only for IRC. As long as it can't be used, it can't be abused either.
inet6num: 2001:0768:1900::/40 netname: SIXXS-NET descr: Tunnelbroker Germany at Cybernet descr: http://www.sixxs.net country: DE admin-c: SIXT1-RIPE tech-c: SIXT1-RIPE mnt-by: PSINET-UK-SYSADMIN changed: network-ripe@uk.psi.com 20030718 source: RIPE status: ALLOCATED-BY-LIR
And that URL has a perfectly sane Contact page with a perfectly working abuse team. Also all the abusers can be found by using whois, which is also noted there.
IRCnet Kline 2001:768:1900::/40
[de] Carmen Sandiego on Thursday, 13 November 2003 14:31:50
If every range would get his own RIPE entry, this wouldnt be a problem. If someone abuses the service he would be punished, not everyone else too. Uwe
IRCnet Kline 2001:768:1900::/40
[ch] Jeroen Massar SixXS Staff on Thursday, 13 November 2003 14:53:03
Abusers should be reported nicely to abuse@sixxs.net which will cause those abusers to be removed directly.
IRCnet Kline 2001:768:1900::/40
[de] Carmen Sandiego on Thursday, 13 November 2003 15:12:24
At least on IRCnet there are other problems too now. There are too many that use sixxs (this range at least) to connect to IRCnet, so the classlimit is reached. I know that IRC is not the main purpose of sixxs/ipv6, but it's a nice and easy way to test if your connection is working. And IMO ipv6 should be used everywhere where it can be used. Is there a great problem to report the ranges notated in whois.sixxs.net back to ripe or why won't you do this? Uwe
IRCnet Kline 2001:768:1900::/40
[ch] Jeroen Massar SixXS Staff on Thursday, 13 November 2003 17:31:01
At least on IRCnet there are other problems too now. There are too many that use sixxs (this range at least) to connect to IRCnet, so the classlimit is reached.
IMHO you shouldn't be complaining at all. You have an IPv4 address, use that for IRC. And as you mentioned yourself IPv6 is not for IRC but apparently you do think so as you feel limited. The fact that the connection limit is reached basically also says that too many people are using IPv6 solely for IRC.
I know that IRC is not the main purpose of sixxs/ipv6, but it's a nice and easy way to test if your connection is working.
You might want to look at ping6 and traceroute6 and other ICMP tools.
And IMO ipv6 should be used everywhere where it can be used.
Many many many people have already proven that IPv6 can be used for IRC a long time ago. Maybe you should find an alternative thing to do with your IPv6 connectivity?
Is there a great problem to report the ranges notated in whois.sixxs.net back to ripe or why won't you do this?
RIPE has some weird AUP which doesn't allow a 'seperate' entity like SixXS to register subnets for an ISP. There has been quite some discussion about this as most of the POP's would like to see this for other reasons. But as apparently your sole reason for requesting this is IRC... don't hold your breath.

Please note Posting is only allowed when you are logged in.

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker