IRC-Junkie.org - IRC News » freenode

KVIrc recommends updates for freenode users

phrozen77 — Sat, 13 Feb 2010 17:45:53 +0000

The KVIrc team has issued an update of their IRC client although it’s technically still at RC2.

The update is recommended for all users of the freenode IRC network that experience problems with “Excess Flood” disconnects from the network, mostly due to autojoining a large number of channels where the client automatically issues a series of commands (/WHO, gets channelmodes and lists of bans as well as ban and invite exemptions) – neither of those events have been rate-limited in the past.

Also, users of the psyBNC and ZNC bouncers (possibly others too) that experienced a bug with the client – searching for CAPABILITIES would hang the connection – can look forward to a fix for that in the new snapshots.

If you want to use a version from their SVN repository, you’re urged to use at least revision 3940 if you’re experiencing said “Excess Floods” and if you want to use features like quiet bans and authentication via SASL (which have been introduced lately on freenode) you should install at least revision 3959.

To retrieve KVIrc from SVN use this command:

svn co https://svn.kvirc.de/svn/trunk/kvirc

To get an already compiled version, take a look at their snapshot directories for your OS on their FTP.

KVIrc recommends updates for freenode users is a post from: IRC-Junkie.org - IRC News

This post is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Deutschland license.

freenode migration to ircd-seven successfully completed

phrozen77 — Sat, 30 Jan 2010 09:24:28 +0000

Just as announced, the migration away from the aged hyperion IRCd to the new ircd-seven started at 7:30am UTC – here’s a short summary of the events:

5 minutes early, christel of freenode staff announced via Global that she’s preparing the move:

-christel- [Global Notice] Good morning all! As you are aware we’re about to start the migration over to ircd-seven shortly, I am about to take a snapshot of the services database and copy across topics and channelmodes (bans, invexes etc). This means that any changes you make to channel modes or services after this point (on hyperion) will be lost. We’ll be a bit noisy as the migration goes on and will global to keep you updated. Thanks for your patience

Shortly after that she announced that a few servers will not immediately return into the main round-robin because they need upgrades:

-christel- [Server Notice] Hi, for users on calvino we would encourage you to make sure that your client is set to reconnect to main rotation (chat.freenode.net) as this server will not be immediately available after migration. Thank you!

-christel- [Global Notice] Hi all, services and channel states have now been migrated over to the new production network. We’re migrating utility bots/pseudoservers as we speak and we’re nearly ready for users. Users connected to calvino, crichton, kubrick, leguin and verne may wish to make sure they are re-connecting to chat.freenode.net as these servers will not be immediately linked on newnet as they are pending upgrades first. Thank you!

Just little over an hour later, christel posted an update via Global, declaring the switchover complete:

-christel- [Global Notice] Hi all, The migration is complete! newnet is up and running and you may now manually connect to irc.freenode.net, ports stay the same, however SSL listens on ports 7000 and 7070 if you wish to connect via SSL. We’ll be taking down hyperion servers momentarily and we shall see you on the other side! Thank you!

-christel- [Global Notice] The migration is complete and went smoothly, thank you for your patience while we transferred state from hyperion to seven, thank you to seven and charybdis developers for making ircd-seven happen and than you to freenodes infrastructure team for all getting dug in! Website FAQ is updated, as is our blog. You may wish to familiarise yourself with changes. Thanks!

The loophole that allowed users of the Firefox webbrowser to connect to the network via Javascript and spam channels has been fixed and a feature to block channel-wide CTCPs has been implemented in the new IRCd which is a major improvement and should keep the spammers at bay.

Another much-anticipated feature of the new IRCd is client- and server-side SSL which is now available on ports 7000 and 7070 network-wide. A possibly not complete list of new features and changes the new IRCd introduces can be found here, here and here.

Congratulations to the freenode staff team for the smooth migration!

freenode migration to ircd-seven successfully completed is a post from: IRC-Junkie.org - IRC News

This post is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Deutschland license.

freenodes ircd-seven is in the final testing stage

phrozen77 — Wed, 13 Jan 2010 10:05:31 +0000

ircd-seven, the IRCd that is going to replace the aged hyperion IRCd currently in use on freenode, is in the final stages of testing.

After being in the public testing phase for over one year, it seems it is finally ready to go into production use on the network.

In an announcement, freenode staff write that after “extensive testing by users and staff, we are now preparing for the switch-over which is taking place at the end of this month” and that they’d like to thank “those of you who have helped test, those who have botted the testnet and in particular those who have helped us find and iron out bugs”.

Those who make use of bots on freenode are advised to “take these last couple of weeks to make sure that they work with the new ircd, so as to not experience disappointment on switch-over for the production network”.

Closing the announcement they write that if “all going well, the switch-over is scheduled for Saturday January 30th 2010″.

freenodes ircd-seven is in the final testing stage is a post from: IRC-Junkie.org - IRC News

This post is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Deutschland license.

Freenode under DDoS

phrozen77 — Tue, 15 Dec 2009 20:49:50 +0000

What many have suspected has now been confirmed – the root cause of the many netsplits on the freenode IRC network during the last days have been caused by ongoing DDoS attacks on their sponsors.

Freenode staffer JonathanD writes in their blogpost that they are experiencing a “heavy DDoS against several locations at which some of our servers are hosted. The attack is ongoing and cause a lot of disruption, both to users of the network and unfortunately to projects/companies/individuals whos infrastructure is hosted at the same locations as us” but also writes that they are “working hard to try curb the attacks as best they can.”

He also writes that they will keep their staffblog updated on the issues and recommends that “users of the network will also be able to receive (infrequent) status updates via global notice and slightly more frequent updates via wallops for those who have chosen to go +w (/umode +w or /mode yournick +w) will enable wallops in your irc client should you wish to see these.”

In closing he apologizes for “the inconvenience this no doubt causes for you and your project(s) and we would like to thank you all (in particular, our very generous and dedicated sponsors) for the patience and support while the issues are still ongoing.”

Freenode under DDoS is a post from: IRC-Junkie.org - IRC News

This post is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Deutschland license.

Freenode issues

phrozen77 — Tue, 08 Dec 2009 18:28:54 +0000

Not only was (and is) Freenode being hit by some bored kiddy – to add insult to the injury they’re currently experiencing major stability issues, resulting in many netsplits throughout the day.

As JonathanD writes in their most-recent blogpost they’ve been “facing some fairly major splits today as there have been issues between some of our major hubs” and that they’ve “rerouted these and are working on tracing down the cause of any other splits” and that their “staff are already hard at work on these issues and will resolve them as quickly as possible”.

The following global notices have been sent on the network to let the users know what is going on:

[Global Notice] Hi all, we appear to be having some connectivity issues with our main US hub, as a result of this we are temporarily without services, if this affects your channel please contact staff in #freenode for assistance. We’re looking into the issues as we speak. Thank you for your patience.

[Global Notice] Hi all, we’re having some major issues with connectivity at the DC hosting one of our hidden hubs, I’m going to re-route around it, which will cause about twice as much noise as the splits already made. Apologies for the inconvenience.

JonathanD also notes that “these and other issues are a large part of the reason for the upcoming migration to ircd-seven, and we still need your help in that regard.” They are “still in need help testing the new ircd and working out the bugs”, so if you feel like being part of the solution he asks you to “have a look at this posting for information on how you can test the new ircd.”

Freenode issues is a post from: IRC-Junkie.org - IRC News

This post is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Deutschland license.