Hello All,

Tinkering with the code. If someone with IPv6 could test my jamnntpd server (both IPv6 and IPv4) to make sure everything is working as intended, I'd appreciate it!

news.pharcyde.org

Regards,
Nick

.... "Не знаю. Я здесь только работаю."

--- Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52
* Origin: thePharcyde_ distribution system (1:154/10)

On 22.7.2017 16:53, Nicholas Boel : All :

Tinkering with the code. If someone with IPv6 could test my jamnntpd
server (both IPv6 and IPv4) to make sure everything is working as
intended, I'd appreciate it!

news.pharcyde.org

telnet 2605:a000:140d:403b:f1d0:1:154:10 119

Connecting To 2605:a000:140d:403b:f1d0:1:154:10...Could not open
connection to the host, on port 119: Connect failed

I can't connect. I can't ping either. :(

'Tommi

---
* Origin: *** nntp://fidonews.mine.nu *** Finland *** (2:221/6.0)

Hello,

On Sat, 22 Jul 2017 21:19:04 +0300, Tommi Koivula -> Nicholas Boel wrote:

news.pharcyde.org

telnet 2605:a000:140d:403b:f1d0:1:154:10 119

Connecting To 2605:a000:140d:403b:f1d0:1:154:10...Could not open connection to the host, on port 119: Connect failed

I can't connect. I can't ping either. :(

Try the address I gave above please. My ipv6 address changed yesterday and my DNS has been changed to reflect it.

Regards,
Nick

.... "Не знаю. Я здесь только работаю."

--- Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52
* Origin: thePharcyde_ distribution system (1:154/10)

Hello Tommi,

On Sat Jul 22 2017 14:34:47, Nicholas Boel wrote to Tommi Koivula:

news.pharcyde.org

telnet 2605:a000:140d:403b:f1d0:1:154:10 119

Connecting To 2605:a000:140d:403b:f1d0:1:154:10...Could not open
connection to the host, on port 119: Connect failed

I can't connect. I can't ping either. :(

Try the address I gave above please. My ipv6 address changed yesterday
and my DNS has been changed to reflect it.

Scratch that. Apparantly _this morning_, not yesterday.. I changed the DNS entries and it hasn't propagated yet. Instead, try the same address above but replace 403b with 60e0.

This is the longest it has ever taken for my DNS to update. Possibly because it's the weekend, but I don't know for sure.

Regards,
Nick

... "Не знаю. Я здесь только работаю."
--- GoldED+/LNX 1.1.5-b20170303
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)

news.pharcyde.org

telnet 2605:a000:140d:403b:f1d0:1:154:10 119

Connecting To 2605:a000:140d:403b:f1d0:1:154:10...Could not open
connection to the host, on port 119: Connect failed

I can't connect. I can't ping either. :(

Try the address I gave above please. My ipv6 address changed yesterday and my DNS has been changed to reflect it.

tommi@boy:~$ host news.pharcyde.org
news.pharcyde.org has address 24.209.142.55
news.pharcyde.org has IPv6 address 2605:a000:140d:403b:f1d0:1:154:10

tommi@boy:~$ telnet -6 news.pharcyde.org 119
Trying 2605:a000:140d:403b:f1d0:1:154:10...

That is the address... No ipv6 connection. :( ipv4 works:

tommi@boy:~$ telnet -4 news.pharcyde.org 119
Trying 24.209.142.55...
Connected to news.pharcyde.org.
Escape character is '^]'.
200 Welcome to JamNNTPd/Linux 1.4 (posting may or may not be allowed, try your luck)
quit
205 Goodbye
Connection closed by foreign host.

'Tommi

---
* Origin: IPv6 Point at [2001:470:1f15:cb0:2:221:1:1] (2:221/1.1)

Try the address I gave above please. My ipv6 address changed yesterday
and my DNS has been changed to reflect it.

Scratch that. Apparantly _this morning_, not yesterday.. I changed the DNS entries and it hasn't propagated yet. Instead, try the same address above but replace 403b with 60e0.

Yes, I was checking the logs at 2:221/6:

18:45:28 [1948] incoming from 2605:a000:140d:60e0:f1d0:1:154:10 (43846) 18:45:28 [1756] incoming session with 2605:a000:140d:60e0:f1d0:1:154:10 18:45:28 [1756] SYS The Pharcyde
18:45:28 [1756] ZYZ Nicholas Boel

This is the longest it has ever taken for my DNS to update. Possibly because it's the weekend, but I don't know for sure.

tommi@boy:~$ telnet 2605:a000:140d:60e0:f1d0:1:154:10 119
Trying 2605:a000:140d:60e0:f1d0:1:154:10...
Connected to 2605:a000:140d:60e0:f1d0:1:154:10.
Escape character is '^]'.
200 Welcome to JamNNTPd/Linux 1.4 (posting may or may not be allowed, try your luck)
list
215 List of newsgroups follows
+GETACCESS+ 1 1 n
.
quit
205 Goodbye
Connection closed by foreign host.

That address is answering.

But hey! My server is there too:

tommi@boy:~$ telnet -6 fidonews.mine.nu 119
Trying 2001:470:1f15:cb0:f1d0:2:221:6...
Connected to fidonews.mine.nu.
Escape character is '^]'.
200 Welcome to JamNNTPd/Cygwin32 1.3 20170718 (posting may be allowed.)
list
215 List of newsgroups follows
+getaccess+ 1 1 y
+localchat+ 1 1 y
+localtest+ 49 1 y
.
quit
205 Goodbye
Connection closed by foreign host.

:D

'Tommi

---
* Origin: IPv6 Point at [2001:470:1f15:cb0:2:221:1:1] (2:221/1.1)

Hello,

On Sat, 22 Jul 2017 23:19:06 +0300, Tommi Koivula -> Nicholas Boel wrote:

18:45:28 [1948] incoming from 2605:a000:140d:60e0:f1d0:1:154:10 (43846) 18:45:28 [1756] incoming session with 2605:a000:140d:60e0:f1d0:1:154:10 18:45:28 [1756] SYS The Pharcyde
18:45:28 [1756] ZYZ Nicholas Boel

Yep, changed it all to reflect that this morning, but it still hasn't taken effect yet. :(

tommi@boy:~$ telnet 2605:a000:140d:60e0:f1d0:1:154:10 119
Trying 2605:a000:140d:60e0:f1d0:1:154:10...
Connected to 2605:a000:140d:60e0:f1d0:1:154:10.
Escape character is '^]'.
200 Welcome to JamNNTPd/Linux 1.4 (posting may or may not be allowed,

That address is answering.

Excellent! At least I was able to follow Konstantine's original diffs and replace the right stuff.

But hey! My server is there too:

Which I would expect, from someone who knows his way around code way better than I do, I'm sure. ;)

Regards,
Nick

.... "Не знаю. Я здесь только работаю."

--- Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52
* Origin: thePharcyde_ distribution system (1:154/10)

Hello,

On Sat, 22 Jul 2017 23:19:06 +0300, Tommi Koivula -> Nicholas Boel wrote:

That address is answering.

And should also be answering via DNS now. I went to my registrar and lowered my
TTL from 30 minutes to 1 minute. That must have lit a fire under the whole process, because within that minute it was working. ;)

Regards,
Nick

.... "Не знаю. Я здесь только работаю."

--- Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52
* Origin: thePharcyde_ distribution system (1:154/10)

Nicholas Boel wrote:

tommi@boy:~$ telnet 2605:a000:140d:60e0:f1d0:1:154:10 119
Trying 2605:a000:140d:60e0:f1d0:1:154:10...
Connected to 2605:a000:140d:60e0:f1d0:1:154:10.
Escape character is '^]'.
200 Welcome to JamNNTPd/Linux 1.4 (posting may or may not be allowed,

That address is answering.

Excellent! At least I was able to follow Konstantine's original diffs
and replace the right stuff.

Great! I'd like to see if it works on cygwin also.

But hey! My server is there too:

Which I would expect, from someone who knows his way around code way better than I do, I'm sure. ;)

Well, my jamnntpd knows nothing about ipv6 but the router does the job. ;)

'Tommi

--- Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:54.0) Gecko/20100101 SeaMonkey/
* Origin: *** nntp://rbb.bbs.fi *** Lake Ylo *** Finland *** (2:221/360)

That address is answering.

And should also be answering via DNS now.

tommi@boy:~$ telnet -6 news.pharcyde.org 119
Trying 2605:a000:140d:60e0:f1d0:1:154:10...
Connected to news.pharcyde.org.
Escape character is '^]'.
200 Welcome to JamNNTPd/Linux 1.4 (posting may or may not be allowed,
try your luck)

Yes! :)

--- Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:54.0) Gecko/20100101 SeaMonkey/
* Origin: *** nntp://rbb.bbs.fi *** Lake Ylo *** Finland *** (2:221/360)

Hello,

On Sun, 23 Jul 2017 10:06:48 +0300, Tommi Koivula -> Nicholas Boel wrote:

Excellent! At least I was able to follow Konstantine's original diffs
and replace the right stuff.

Great! I'd like to see if it works on cygwin also.

If you get around to it, I think I changed a few lines in like 3 different files. There are also lines he removed that aren't even in the 1.3 codebase, which can be ignored.

It's mainly just changing the hard coded IPv4 lines to IPv6. I'm surprised at how easy it was.

Since I did it, my jamnntpd.log also now logs IPv6 connections correctly. Though IPv4 connections are logged kinda wierd (ie: :ffff:192.168.1.1). But that's probably because it's now all coded for IPv6 yet still _allows_ IPv4. I'm sure that's fixable, though.

Well, my jamnntpd knows nothing about ipv6 but the router does the job. ;)

Ah, sneaky! ;)

Regards,
Nick

.... "Не знаю. Я здесь только работаю."

--- Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52
* Origin: thePharcyde_ distribution system (1:154/10)

Hello,

On Sun, 23 Jul 2017 10:08:14 +0300, Tommi Koivula -> Nicholas Boel wrote:

That address is answering.

And should also be answering via DNS now.

tommi@boy:~$ telnet -6 news.pharcyde.org 119
Trying 2605:a000:140d:60e0:f1d0:1:154:10...
Connected to news.pharcyde.org.
Escape character is '^]'.
200 Welcome to JamNNTPd/Linux 1.4 (posting may or may not be allowed,
try your luck)

Yes! :)

Thanks for the assistance, Tommi!

Regards,
Nick

.... "Не знаю. Я здесь только работаю."

--- Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52
* Origin: thePharcyde_ distribution system (1:154/10)

On 07/23/2017 01:00 PM, Nicholas Boel -> Tommi Koivula wrote:

Since I did it, my jamnntpd.log also now logs IPv6 connections
correctly. Though IPv4 connections are logged kinda wierd (ie: :ffff:192.168.1.1).

Please be aware, that you also have to use that notation in the
allow list.


--

De Groeten,
Kees

---
* Origin: Fidonet!, isn't that something from the past? (2:280/5006.4)

Hello,

On Tue, 25 Jul 2017 12:32:18 +0200, Kees Van Eeten -> Nicholas Boel wrote:

Since I did it, my jamnntpd.log also now logs IPv6 connections
correctly. Though IPv4 connections are logged kinda wierd (ie:
:ffff:192.168.1.1).

Please be aware, that you also have to use that notation in the
allow list.

Thanks for the heads up!

At the moment I'm the only user and am using "* P -" for my only line in jamnntpd.allow, which gives all access to the +GET_ACCESS+ area. However, with me setup as a user, it seems I bypass that IP allowance, so unless I'm missing something, I don't think I'll have to modify that file any more as long as I setup username/passwords, right?

Regards,
Nick

.... "Не знаю. Я здесь только работаю."

--- Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52
* Origin: thePharcyde_ distribution system (1:154/10)

Nicholas,

Saturday July 22 2017 08:53, you wrote to All:

Tinkering with the code. If someone with IPv6 could test my jamnntpd server (both IPv6 and IPv4) to make sure everything is working as intended, I'd appreciate it!

news.pharcyde.org

Hi!

I kept planning to share what I have... I was just very embarassed that it didnt build easily... :(

Just no time... but on the bright side my host stayed up w/o issue!

Did you implement IPv6 natively?

Take care,

Matt

---
* Origin: The Byte Museum - www.bytemuseum.org (1:19/10)

Hello Matt,

On Thu Sep 07 2017 22:09:24, Matt Bedynek wrote to Nicholas Boel:

I kept planning to share what I have... I was just very embarassed
that it didnt build easily... :(

No problem. If I want it bad enough, I'll do it myself. ;)

Just no time... but on the bright side my host stayed up w/o issue!

Same here!

Did you implement IPv6 natively?

Yes.

Regards,
Nick

... "Не знаю. Я здесь только работаю."
--- GoldED+/LNX 1.1.5-b20170303
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)

Nicholas,

Friday September 08 2017 15:51, you wrote to me:

Just no time... but on the bright side my host stayed up w/o
issue!

Same here!

Did you implement IPv6 natively?

Yes.

Very nice! We need to get this out so others can benefit / test.

My problem is two jobs + class. :-)

Take care,

Matt

---
* Origin: The Byte Museum - www.bytemuseum.org (1:19/10)

Hello Matt,

On Tue Sep 19 2017 01:36:18, Matt Bedynek wrote to Nicholas Boel:

Did you implement IPv6 natively?

Yes.

Very nice! We need to get this out so others can benefit / test.

I believe Tommi did as well, and maybe another after someone posted their diffs
on the subject while we were discussing it. However, I believe the maintainer of the github sources is my RC, who is about 90% unreachable at most times.

My problem is two jobs + class. :-)

I've created my own "version" here, which also has a workaround/hack for the "CHRS: UTF-8 4" kludge that I wouldn't want in the main branch since it probably breaks every other charset (I haven't tested anything other than UTF-8, so I'm uncertain how it would act).

However, those diffs that were posted on IPv6 support were in a public echo (IPV6 echo maybe?), so the current maintainer could have grabbed them up at any
time in the last 6 months or so, but hasn't.

Regards,
Nick

... "Не знаю. Я здесь только работаю."
--- GoldED+/LNX 1.1.5-b20170303
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)

On 20.09.2017 0:38, Nicholas Boel : Matt Bedynek wrote:

 MB>>> Did you implement IPv6 natively?

 NB>> Yes.

 MB> Very nice!  We need to get this out so others can benefit / test.

I believe Tommi did as well,

Nope, I have IPv6 support in this server, but it is not native in JamNNTPd.

'Tommi

---
* Origin: *** nntp://fidonews.mine.nu *** Finland *** (2:221/6.0)

Hello Tommi,

On Wed Sep 20 2017 20:25:10, Tommi Koivula wrote to Nicholas Boel:

Nope, I have IPv6 support in this server, but it is not native in JamNNTPd.

Ah okay. Well, if one day I decide to revert my change regarding the level 4 parameter for UTF-8, or someone can assist me in the proper way of having jamnntpd allow higher than the level 2 parameter without possibly breaking other charsets, I can submit what I have. Since I don't see that happening any time soon, the diffs are still publicly available in another echo for anyone else to copy/paste like I did. ;)

Regards,
Nick

... "Не знаю. Я здесь только работаю."
--- GoldED+/LNX 1.1.5-b20170303
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)