Time |
Nick |
Message |
00:26 |
|
dun157 joined #ircforever |
01:00 |
|
h|gcp-soju joined #ircforever |
01:00 |
|
youngchief joined #ircforever |
01:00 |
|
youngchief_ joined #ircforever |
01:00 |
|
youngchief joined #ircforever |
01:00 |
|
youngchief joined #ircforever |
01:14 |
|
h|gcp-soju joined #ircforever |
01:14 |
|
youngchief joined #ircforever |
01:14 |
|
youngchief_ joined #ircforever |
03:01 |
|
youngchief joined #ircforever |
03:01 |
|
h|gcp-soju joined #ircforever |
08:14 |
|
dun308 joined #ircforever |
13:15 |
libredev |
IanJ: jrmu: we have three peers in nircd.conf. |
13:15 |
libredev |
1) irc.oddprotocol.org |
13:16 |
libredev |
2) hopm.ircforever.org (localhost) |
13:16 |
libredev |
3) irc.NaStYcOdE.com |
13:16 |
libredev |
I don't even know why 2nd exists. |
13:17 |
libredev |
IanJ: jrmu: what peer I supposed to remove/add/edit. |
13:20 |
libredev |
IanJ: we may configure our peers as fallback instead of removing. |
13:37 |
libredev |
gtlsgamr: I know i am late but if you are interested in joining our team, please ping me. I have to ask some questions. |
13:40 |
libredev |
oh, he is not here, let me PM him. |
13:49 |
libredev |
xfnw: ircnow license is mostly equivalent to public domain. https://en.wikipedia.org/wiki/Public-domain-equivalent_license |
13:49 |
BanaDrop |
Title: Public-domain-equivalent license - Wikipedia |
14:00 |
IanJ |
libredev, IMHO you could do with adding peerings for irc.planetofnix.com, irc.lecturify.net or irc.bsdforall.org, you will need to speak to admins of those systems and have them add you as a peer too. |
14:01 |
IanJ |
For us (nastycode.com) you can just change or add 'passive = yes' for our peering as xfnw suggested. This way it remains if we want to connect in future but you won't initiate a connection to us anymore. |
14:06 |
IanJ |
http://nastycode.com/ngircd/ircnow/ <- some info about it |
14:20 |
libredev |
IanJ: https://yonle.lecturify.net/ircnow_ngircd_links_plan_2.png -- so this is the plan? |
14:21 |
IanJ |
That's Yonle's plan... |
14:22 |
IanJ |
We've given it to #ngircd guys to look at but so far they've not responded. |
14:22 |
IanJ |
As long as we reduce the length of these chains then things should be better: https://0x0.st/HqMj.png |
14:24 |
libredev |
IanJ: how you draw the graph? |
14:25 |
libredev |
with the help of LINKS command |
14:25 |
libredev |
? |
14:29 |
libredev |
IanJ: so every peer connect to irc.planetofnix.com, irc.lecturify.net or irc.bsdforall.org |
14:29 |
libredev |
s/or/and |
14:31 |
IanJ |
xfnw, creates them from /links yes |
14:31 |
IanJ |
libredev, not every peer no, just those of us further down the chain. |
14:32 |
IanJ |
I thought of it like ircnow.org being the hub with those three connected to ircnow.org directly and then the rest of us connecting to one of those three. |
14:32 |
IanJ |
How those 4 peers connect between themselves, I have no idea frankly. |
14:32 |
libredev |
oh i see |
14:33 |
IanJ |
If the three are in a group then we only connec to one of them. |
14:33 |
IanJ |
That's how nastycode.com is currently configured. |
14:33 |
IanJ |
Unfortunately some of those peers have peerings with systems further down the chain. |
14:34 |
libredev |
IanJ: should i keep oddprotocol or not? |
14:34 |
IanJ |
At the time I decided to do it irc.bsdforall.org and irc.planetofnix.com were connected directly with ircnow.org |
14:34 |
IanJ |
libredev, before you remove peerings you need to make sure you have others in place. |
14:34 |
libredev |
yeah |
14:34 |
IanJ |
I would make the ones you don't want to connect to passive, like you're doing for us. |
14:35 |
IanJ |
That will prevent you actively trying to connect to them in future. |
14:36 |
libredev |
so passive means they only going to accept incomming connection if any? |
14:36 |
IanJ |
Passive means if they try to connect to you then you will allow it. |
14:36 |
IanJ |
If they're not passive then you will attempt to connect to them. |
14:36 |
libredev |
IanJ: oh i see |
14:37 |
libredev |
but what if the first peer is down and second peer is passive? |
14:37 |
libredev |
is it going to move to next peer or try to connect to second one. |
14:37 |
IanJ |
Then you will not connect. |
14:37 |
libredev |
oh i see |
14:37 |
IanJ |
So this is where groups come in. |
14:38 |
IanJ |
So I have irc.planetofnix.com, irc.lecturify.net or irc.bsdforall.org in group 001 |
14:38 |
IanJ |
We actively connect to those peers but it will only connect to one of them. |
14:38 |
IanJ |
If we are connected to planetofnix and it goes down then it should move on to irc.lecturify.net |
14:38 |
IanJ |
it will try the next host in the group |
14:39 |
libredev |
or? |
14:39 |
IanJ |
or? |
14:40 |
libredev |
you mean you have 3 peers in config and all of them are non-passive? |
14:40 |
IanJ |
yes |
14:40 |
libredev |
ok i see |
14:40 |
IanJ |
but they're in the same group id. |
14:40 |
IanJ |
If they are different groups then it will try to connect to those too. |
14:41 |
libredev |
ok what servers i supposed to non-passive? |
14:41 |
libredev |
same ones? |
14:41 |
IanJ |
Same as me. |
14:41 |
IanJ |
If I were doing it. |
14:42 |
libredev |
IanJ: ok |
14:43 |
IanJ |
You have to ask the admins of those systems to add a passive peering for you. |
14:45 |
xfnw |
libredev: re PD, indeed, i was touching upon a specific difference |
14:51 |
libredev |
IanJ: yeah, i will send a email to each of those three team and wait for reply. |
14:52 |
libredev |
xfnw: moral right is one of them. |
14:53 |
jrmu |
libredev: the second one hopm is very important, it's mentioned here at https://wiki.ircnow.org/?n=Hopm.Install |
14:53 |
jrmu |
don't delete your hopm unless you want our network to get hit with spam bots |
14:53 |
jrmu |
gtlsgamr ended up joining the team over on #nastycode |
14:55 |
IanJ |
I don't think we have a hopm peer... |
14:55 |
jrmu |
you will want to set up hopm then IanJ |
14:55 |
jrmu |
otherwise your server is wide open to floods from open proxies |
14:55 |
jrmu |
ngircd has no built-in open proxy detector |
14:56 |
libredev |
jrmu: i don't see that in the guide. which para |
14:56 |
jrmu |
"In this guide, we'll setup and configure hopm, an open proxy monitor that kills spam bots." |
14:56 |
jrmu |
first paragraph |
14:56 |
IanJ |
I wonder if that's why we were connected to ourself on 6667 |
14:57 |
libredev |
isn't hopm works as service and not server? |
14:57 |
jrmu |
yes although I recommended using port 16667 to keep 6667 for end users only |
14:57 |
jrmu |
I think services appear as servers to ngircd |
14:57 |
xfnw |
hopm connects as a normal user |
14:58 |
jrmu |
if you use this guide you can test if your hopm works properly https://wiki.ircnow.org/index.php?n=Tor.Torsocks |
14:59 |
jrmu |
https://wiki.ircnow.org/index.php?n=Hopm.Telnet |
14:59 |
libredev |
jrmu: i don't see the [server] block in that guide. |
14:59 |
jrmu |
oh yeah xfnw is right my mistake |
14:59 |
jrmu |
hopm connects as a normal user as operator |
14:59 |
jrmu |
my bad IanJ ^ |
15:00 |
jrmu |
ok then libredev it should be safe to remove hopm as a server, since it should only be connecting as a client with operator status |
15:01 |
libredev |
yeah, ok |
15:01 |
IanJ |
lol |
15:01 |
IanJ |
so the peering was 6667 but looking at the hopm.conf it's running on 16667 |
15:02 |
IanJ |
Why am I not surprised... |
15:03 |
jrmu |
so yeah it should not have a [Server] block, xfnw was correct, hopm should instead connect to ngircd as a client, port 6667 is ok I guess |
15:03 |
jrmu |
the reason someone suggested to me to use port 16667 a while back was to keep all special operator/server traffic on separate ports |
15:03 |
jrmu |
it's not strictly necessary but could make it easier to debug |
15:06 |
IanJ |
Yeah, but our hopm is running 16667 but the peering is 6667, they are mismatched. |
15:06 |
jrmu |
Ah. If there is a [Server] block for hopm, it can probably be safely removed |
15:07 |
jrmu |
that [Server] block can only cause problems since hopm doesn't present itself as an irc server |
15:07 |
xfnw |
jrmu: o.o what would that help debug? its not like theres anything stopping normal users from using that port, and it jumps to a different port after negotiating the connection anyways (so that more than one person can connect) |
15:08 |
jrmu |
xfnw: well we don't advertise those ports publicly! You didn't hear anything here! |
15:08 |
jrmu |
someone suggested it would be easier to tcpdump port 16667 if all servers used that port |
15:08 |
jrmu |
then again I never actually used it so who knows |
15:08 |
jrmu |
it could be easier to firewall off later if you had a ddos attack |
15:09 |
jrmu |
you could selectively add filtering rules for just ports 6667 or 6697 |
15:09 |
jrmu |
I don't know, I never actually ended up taking advantage of it |
15:10 |
xfnw |
i hope you arent linking servers over plaintext lol |
15:10 |
jrmu |
but when peering it's better to use SSL |
15:10 |
jrmu |
well that's what 16697 is for! |
15:10 |
libredev |
better, i say it should be mandatory |
15:11 |
jrmu |
the idea was peering between servers should be on 16697, and then local services on 16667 |
15:12 |
xfnw |
so only irc.ircnow.org needs 16667? |
15:12 |
* IanJ |
comes back from the rabbithole |
15:14 |
libredev |
why 16667, everone should use 16697 with ssl |
15:15 |
jrmu |
xfnw: well maybe you could run a relay or something |
15:15 |
jrmu |
libredev: for localhost ssl is unnecessary |
15:15 |
jrmu |
xfnw: I think my pylink guide used 16667? Maybe? |
15:16 |
libredev |
oh for localhost, i see |
15:19 |
|
Miniontoby joined #ircforever |
15:32 |
|
Lettuce joined #ircforever |
15:32 |
|
agrox joined #ircforever |
15:32 |
libredev |
IanJ: i have edited nastycode as passive peer. i hope you don't get those failed attempts now |
15:33 |
IanJ |
thanks |
15:34 |
IanJ |
You did a 'doas reload ngircd'? |
15:35 |
libredev |
yeah |
15:35 |
IanJ |
Great :) |
15:36 |
IanJ |
Thanks, it was needlessly filling the logs because I had removed the peering our side. |
16:11 |
|
\j_torontomayors joined #ircforever |
16:23 |
|
dun153 joined #ircforever |
16:24 |
|
\j_torontomayors joined #ircforever |
18:27 |
|
dun929 joined #ircforever |
18:35 |
|
dun268 joined #ircforever |
20:23 |
jrmu |
cool thanks libredev |
21:07 |
|
Tympanista joined #ircforever |
21:08 |
jrmu |
greetings Tympanista ! |
21:08 |
jrmu |
welcome to ircforever |
21:09 |
Tympanista |
Hello! Great to be here! |
21:09 |
Tympanista |
Ah, what a learning experience :-) |
21:09 |
jrmu |
cool, well I'd be glad to have you get started with learning openbsd if you're interested |
21:10 |
jrmu |
did you check out the unix101 course? at https://wiki.ircnow.org/?n=Unix101.Unix101 |
21:11 |
Guest43288 |
I will be starting with that course next. |
21:12 |
Guest43288 |
I was trying to get my head around servers/bnc this afternoon how to connect to everything |
21:13 |
jrmu |
ok sounds good Tympanista |
21:13 |
jrmu |
if you have questions, just ping us |
21:13 |
jrmu |
you can also meet our teammates over on #team |
21:14 |
Tympanista |
Alright, great, thank you very much for your help! |
21:15 |
Tympanista |
It's a great thing you are doing here, I literally stumbled on your channel over on LiberaChat (and the whole idea) as we were experimenting switching over (back?) to IRC for a team project |
21:16 |
Tympanista |
(not related to software at all) |
21:18 |
jrmu |
cool |
21:19 |
|
Kilroy joined #ircforever |
21:37 |
|
Zyx| joined #ircforever |
21:48 |
|
Tympanista joined #ircforever |
22:07 |
|
dun232 joined #ircforever |
22:15 |
|
youngchief joined #ircforever |
22:15 |
|
h|gcp-soju joined #ircforever |
22:15 |
|
h|gcp-soju joined #ircforever |
22:15 |
|
h|gcp-soju_ joined #ircforever |
22:15 |
|
h|gcp-soju joined #ircforever |
22:15 |
|
h|gcp-soju_ joined #ircforever |
22:15 |
|
h|gcp-soju joined #ircforever |
22:17 |
|
Tympanista joined #ircforever |
22:43 |
|
Tympanista joined #ircforever |
22:43 |
|
Tympanista left #ircforever |
23:03 |
|
Tympanista joined #ircforever |