|
IRC Servers
Our main server rotation is
chat.freenode.net. IPv6 users can specify
ipv6.chat.freenode.net. Pointers to
freenode
currently include irc.ghostscript.com, irc.gnu.org, irc.handhelds.org,
irc.linux.org, irc.kde.org and irc.redhat.com. Please see our
acknowledgements
page for the generous groups and organizations who have helped
us to provide this service.
If you're running
Tor,
access is available via our
hidden service.
NOTE:
The network needs servers. We are in particular need of servers on the
Pacific Rim and in the Americas. If you think you might be
able to help our community in this way, please take a look at the
server hosting page
and email us at hosting at freenode dot net. Thanks!
The following table lists freenode client servers, server names indicated in italics are currently NOT
linked to the production network. Apologies for any inconvenience this may cause. Servers with "Yes" in the IPv6
column listen for IPv6 connections and can be connected to via the same hostname as for IPv4. chat.freenode.net has AAAA records for those servers with IPv6 capability, so simply telling your client to connect to chat.freenode.net by IPv6 should work. Please note that due to the low number of IPv6 servers currently in service, we do not provide regional IPv6 rotations.
All freenode servers listen on ports 6665, 6666, 6667, 7000(SSL Only), 7070 (SSL Only), 8000, 8001 and 8002. Please be aware that the below list is at no time authoritative,
and as such our advice is to connect using chat.freenode.net.
Asia/Pacific Rim
none
|
chat.ap.freenode.net
none
|
|
Europe
Frankfurt, DE
Helsinki, FI
Milano, IT
Oslo, NO
Umeå, SE
Moscow, RU
Manchester, UK
Vilnius, LT
Evry, FR
Stockholm, SE
London, UK
Paris, FR
Luxembourg, LU
Rennes, FR
|
chat.eu.freenode.net
kornbluth.freenode.net
orwell.freenode.net
calvino.freenode.net
gibson.freenode.net
leguin.freenode.net
lem.freenode.net
wolfe.freenode.net
sendak.freenode.net
jordan.freenode.net
lindbohm.freenode.net
holmes.freenode.net
barjavel.freenode.net
bartol.freenode.net
pratchett.freenode.net
|
IPv6
Yes
Yes
Yes
Yes
|
United States
Corvallis, OR
Madison, WI
Irvine, CA
Los Angeles, CA
Newark, NJ
Fremont, CA
Washington, DC
San Diego, CA
Chesterbrook, PA
Pittsburgh, PA
|
chat.us.freenode.net
niven.freenode.net
zelazny.freenode.net
brown.freenode.net
anthony.freenode.net
kubrick.freenode.net
verne.freenode.net
clarke.freenode.net
card.freenode.net
simmons.freenode.net
hubbard.freenode.net
|
IPv6
Yes
|
Accessing freenode Via SSL
Since the switch to ircd-seven, freenode now provides SSL client access on all
servers. If your client is not configured to verify SSL certificates, then you
can simply connect, with SSL enabled, on port 7000 or 7070.
If you wish to verify the server certificates on connection, some additional
work may be required. First, ensure that your system has an up-to-date set of
root CA certificates. On most linux distributions this will be in a package
named something like ca-certificates. Many systems install these by default, but
some (such as FreeBSD, on which the package you wish to install is ca_root_nss,
and the cafile to use would be /usr/local/share/certs/ca-root-nss.crt) do not.
For most clients this should be sufficient.
Those of you using irssi will find that it has some oddities in SSL certificate
verification, and will not find the root certificates on its own. To work around
this, use
/connect -ssl_verify -ssl_capath /etc/ssl/certs chat.freenode.net 7000
or on FreeBSD
/connect -ssl_cafile /usr/local/share/certs/ca-root-nss.crt chat.freenode.net 7000
Once you tell irssi where to find the root certificates, it should be
able to verify the certificate correctly.
Accessing freenode Via Tor
The current Tor hidden service address for freenode is
p4fsi4ockecnea7l.onion.
This service can be used by any user with a registered NickServ account.
No further setup steps are necessary beyond that, besides configuring
your client. Information on how to register a nick can be found on
our FAQ page. The Tor hidden service
uses SASL for authentication, which may require the use of additional
scripts in your client to provide support. A collection of scripts and
instructions for use can be found here.
Latencies are improving all the time and can be quite reasonable. You can
always find a pointer to our Tor hidden service in freenode.net
DNS, in an unresolved CNAME record, irc.tor.freenode.net, which can
be retrieved, for example, via the
*nix shell command:
dig +short irc.tor.freenode.net cname
If your IRC client can handle socks5 with remote dns, you can just connect
to the .onion address directly. Otherwise, use Tor's "mapaddress" feature
to fake it. (We do not recommend that you use Privoxy with irssi.
It's unnecessary. Just use the 'mapaddress' approach and torify irssi to
start it up.) Add a line to your
torrc,
as in this example:
mapaddress 10.40.40.40 p4fsi4ockecnea7l.onion
Be sure to HUP (reload) Tor if you change your torrc. After you've made
the change, just connect your torified IRC client to the IP you specified
in your mapaddress statement for the
freenode
service. Tor will do the conversion for you internally and you'll connect
to freenode. In addition to providing
location privacy, the Tor hidden service gives you end-to-end encryption,
providing benefits similar to those of ircs / irc-ssl.
That's all it takes. We appreciate your accessing
freenode
via the Tor hidden service. If you'd like to help us maintain quality
access, please consider providing "middleman" bandwidth to the Tor
network. Just
set your host up as a Tor server
and specify how much bandwidth you want to provide. You don't have to be
an exit node—you can set your exit policy to "reject *:*" and still
help us make up for the bandwith we use for
freenode's
hidden service.
Copyright © 2002-2010 by Peer-Directed Projects Center. Network date and time: Saturday, 31-Jul-2010 11:26:24 GMT.
Comments to email address: web at freenode dot net.
|