Ircnow
Server Locations
Location | Hostname |
---|---|
Las Vegas, USA | irc.lecturify.net |
Las Vegas, USA | irc.inspirenet.org |
Las Vegas, USA | irc.shelltalk.net |
New York, USA | irc.ircforever.org |
New York, USA | irc.bsdforall.org |
New York, USA | irc.nastycode.com |
New York, USA | irc.planetofnix.com |
Roost, Luxembourg | irc.oddprotocol.org |
Roost, Luxembourg | irc.thunderirc.net |
Roost, Luxembourg | irc.freeirc.org |
Miami, USA | cloud9p.org |
Miami, USA | irc.ircnow.org |
Miami, USA | irc.rpblc.net |
Yonles' Plan
IanJ's Plan http://docs.nastycode.com/ngircd/ircnow/
Everyone, except for irc.ircnow.org, irc.bsdforall.org, irc.planetofnix.com and irc.lecturify.net, create a group containing:
- irc.bsdforall.org
- irc.planetofnix.com
- irc.lecturify.net
Talk to the admins of those systems to create peerings with them, if you don't have them already.
To create a peer you need to add a section like the following to your ngircd.conf:
Talk to the admins of those systems to create peerings with them, if you don't have them already.
To create a peer you need to add a section like the following to your ngircd.conf:
[Server] Name = irc.planetofnix.com Host = irc.planetofnix.com Bind = <your_ip_address> Port = 16697 MyPassword = <shared_token> PeerPassword = <shared_token> Group = 001 ;Passive = no SSLConnect = true ;ServiceMask = *Serv,Global
I wasn't sure how to best to suggest irc.ircnow.org, irc.bsdforall.org, irc.planetofnix.com and irc.lecturify.net arrange their peerings between themselves. However, this arrangement means noone is more than 2 hops from irc.ircnow.org.
IRC Discussion
#team 2023-05-19 10:47 < Yonle> https://yonle.lecturify.net/ircnow_ngircd_links_plan.txt 11:47 < IanJ> Well, I had a plan but Yonle has decided he has an alternative plan... 11:48 < IanJ> So now I'm waiting on feedback from the ngircd developer to see what he thinks of Yonles' plan. 12:11 <@izzyb> I posted this on the wiki earlier 12:11 <@izzyb> https://wiki.ircnow.org/index.php?n=Ngircd.Ircnow 12:13 <@izzyb> was thinking it makes sense for each team to be in a local group with its neighbors in the same region 12:13 <@izzyb> and for each region to be in a group 12:14 <@izzyb> so then we'd have 4 groups of 3 12:15 <@izzyb> I'll add Yonle's link to the wiki page 12:15 <@izzyb> IanJ: I didn't see your plan. did you post it someplace? 12:17 < Error> lol 12:17 < Error> IanJ 12:18 < Error> what you wanted to do! 12:18 < Error> not that i would understand it all! 12:20 < IanJ> I was going to ask some folks to change their peerings to try and flatten the ircnow irc network a bit. 12:21 < IanJ> Try to reduce the effects of the netsplits when a server goes down or has a problem. 12:21 <@izzyb> yeah I agree, question is what the best configuration 12:21 < IanJ> At the moment some servers are connected in a big long chain, several hops from ircnow.org and if any server in that chain goes down, any of them stacked up behind it are split too. 12:22 <@izzyb> https://wiki.ircnow.org/index.php?n=Ngircd.Ircnow 12:22 < IanJ> Lets see what the ngircd guys say, if Yonle's design is a go then I'm willing to give it a try. It's got to be better than what's happening at the moment. 12:26 <@izzyb> Yonle: how did you choose the groupings in your plan? 12:28 <@izzyb> IanJ: how about your plan? what groupings did you use? 12:29 <@izzyb> Perhaps we should start with a list of the groupings we currenly have? 12:29 <@izzyb> I'll publish my current configuration on the wiki page
Current Configuration
planetofnix.com
Peers: irc.ircnow.org, irc.rpblc.net, irc.freeirc.org, irc.shell.oddprotocol.org, irc.inspirenet.org
All in group 003. Last 2 set as passive = yes.
nastycode.com
Peers in group 001: irc.bsdforall.org, irc.lecturify.net, irc.planetofnix.com
Passive peerings for irc.ircforever.org and irc.shelltalk.net have been removed by me to force connection elsewhere (hopefully further up the tree) when they next require a peering.
NOTE Passive peerings allow the peer to connect to you but you will not initiate a connection to them.