Hello All,

I've made a change in nntpserv.c:

WRAP_LENGTH = 79

To test, I've read a bunch of messages in both slrn and Thunderbird, and
posted a couple times with both, also (though I don't think posting would
have much to do with this setting). Things seem better than they were
before. Feel free to give it a try if you're seeing some wierd wrapping
issues. :)

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
* Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)

Hello, Nicholas!

Wednesday February 28 2024 19:54, from Nicholas Boel -> All:

I've made a change in nntpserv.c:

Unless I am missing something, there have been a couple of patches to jamnntpd/smapinntpd announced in this echo conference but none of them have landed on GitHub.

Where do you guys commit your changes?
Maybe https://github.com/ftnapps/jamnntpd - ame committed 8 years ago
Maybe https://github.com/ftnapps/smapinntpd/ - ame committed 11 years ago

Best Regards,
Nil
--- GoldED+/LNX 1.1.5
* Origin: -=NIL BBS=- (1:16/101)

On Thu, 29 Feb 2024 03:55:28 -0500, Nil Alexandrov -> Nicholas Boel wrote:

Unless I am missing something, there have been a couple of patches to jamnntpd/smapinntpd announced in this echo conference but none of them have
landed on GitHub.

Where do you guys commit your changes?
Maybe https://github.com/ftnapps/jamnntpd - ame committed 8 years ago Maybe https://github.com/ftnapps/smapinntpd/ - ame committed 11 years ago

So far on our own personal systems, while working out some bugs and/or limitations. I'm not sure anyone alive right now was given any commit
access to either one of those links.

Most of us basically built from one of those above links, and have added patches together in discussion here, and maybe a bit via netmail.

Problem is, I don't believe any of us are self proclaiming ourselves as a programmer of any kind, so (in my opinion) we have been working together
this way and has worked so far.

Are we somehow able to gain access to either of those github sites if the original maintainer has passed away?

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
* Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)

On Thu, 29 Feb 2024 01:54:22 -0600, Nicholas Boel -> All wrote:

Hello All,

I've made a change in nntpserv.c:

WRAP_LENGTH = 79

To test, I've read a bunch of messages in both slrn and Thunderbird, and posted a couple times with both, also (though I don't think posting would have much to do with this setting). Things seem better than they were before. Feel free to give it a try if you're seeing some wierd wrapping issues. :)

Nevermind this. Back to WRAP_LENGTH = 72 when it started making lines I
quoted too long.

Also just realized I had changed the mailnews.wraplength setting in
Thunderbird early on to 75 columns when it was 72 to begin with. So I
reverted that as well in hopes that it fixes the original issue.

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
* Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)

On 01.03.2024 3:50, Nicholas Boel wrote:

NB> Hello All,

NB> I've made a change in nntpserv.c:

NB> WRAP_LENGTH = 79

NB> To test, I've read a bunch of messages in both slrn and Thunderbird, and
NB> posted a couple times with both, also (though I don't think posting would
NB> have much to do with this setting). Things seem better than they were
NB> before. Feel free to give it a try if you're seeing some wierd wrapping
NB> issues. :)

Nevermind this. Back to WRAP_LENGTH = 72 when it started making lines I quoted too long.

I played with this once, set it to 990. It helps, but it created issues with quoting. That was before the fixes of Carlos. I'll try again. :)

'Tommi

---
* Origin: jamnntpd/lnx (2:221/1.0)

29/02/2024 3:55, Nil Alexandrov -> Nicholas Boel:

Unless I am missing something, there have been a couple of patches to jamnntpd/smapinntpd announced in this echo conference but none of them have landed on GitHub.

Where do you guys commit your changes?
Maybe https://github.com/ftnapps/jamnntpd - ame committed 8 years ago Maybe https://github.com/ftnapps/smapinntpd/ - ame committed 11 years ago

I'm maintaining my modified JamNNTPd version at this fork: https://github.com/cnb/jamnntpd
Check commits to see latest patches.

Carlos

--- Mozilla Thunderbird
* Origin: cyberiada-NNTP (2:341/234.99)

On Wed, 28 Feb 2024 20:55:28 -0500, Nil Alexandrov -> Nicholas Boel wrote:

Hello, Nicholas!

Wednesday February 28 2024 19:54, from Nicholas Boel -> All:

 NB>> I've made a change in nntpserv.c:

Unless I am missing something, there have been a couple of patches to jamnntpd/smapinntpd announced in this echo conference but none of them have landed on GitHub.

Where do you guys commit your changes?
Maybe https://github.com/ftnapps/jamnntpd - ame committed 8 years ago Maybe https://github.com/ftnapps/smapinntpd/ - ame committed 11 years ago

Thanks for getting the ball rolling. You made me get off my ass and figure out github. I had only known 'clone' and 'pull' until recently.

I have forked them both, and they are currently matching each other with patches and features. Please check the CHANGELOG to see what's been done:

https://github.com/axxisd/jamnntpd
https://github.com/axxisd/smapinntpd

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
* Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)

On 15 Mar 2024, Nicholas Boel said the following...

I have forked them both, and they are currently matching each other with patches and features. Please check the CHANGELOG to see what's been done:

https://github.com/axxisd/jamnntpd
https://github.com/axxisd/smapinntpd

This is awesome, thank you! :)


Jay

... Put Ex-Lax in your gas tank to make your car go

--- Mystic BBS v1.12 A49 2023/04/30 (Linux/64)
* Origin: Northern Realms (1:229/664)

On 15 Mar 2024, Nicholas Boel said the following...

https://github.com/axxisd/jamnntpd
https://github.com/axxisd/smapinntpd

Would it be possible to include:

fidoconfig2jamnntpd.pl
checkgroups.pl
echomailjam2hpt.pl

In these repositories as well?


Jay

... By the power vested in me by the internet, I now pronounce you man and wifi

--- Mystic BBS v1.12 A49 2023/04/30 (Linux/64)
* Origin: Northern Realms (1:229/664)

Hello, Nicholas!

Friday March 15 2024 17:21, from Nicholas Boel -> Nil Alexandrov:

Unless I am missing something, there have been a couple of
patches to jamnntpd/smapinntpd announced in this echo conference
but none of them have landed on GitHub.

Where do you guys commit your changes?
Maybe https://github.com/ftnapps/jamnntpd - ame committed 8 years
ago Maybe https://github.com/ftnapps/smapinntpd/ - ame committed
11 years ago

Thanks for getting the ball rolling. You made me get off my ass and
figure out github. I had only known 'clone' and 'pull' until recently.

It is never late to learn new things, especially if you are coming from CVS or SVN or whatever world. Cause the whole world is now on git as an industry standard.

I have forked them both, and they are currently matching each other
with patches and features. Please check the CHANGELOG to see what's
been done:
https://github.com/axxisd/jamnntpd
https://github.com/axxisd/smapinntpd

Ah, it is not about repo anymore, it is more about a commitment to be a maintainer for both projects. :-)

Though, it would be more fun if you can merge them in a way that there is a #ifdef use SMAPI or jamlib, cause the rest should be exactly the same.
As a sanity check, if you process NNTP requests differently, then you are basically failed. This is the same code which had forked worked at some point and later continued in a separate directions.

Best Regards,
Nil
--- GoldED+/LNX 1.1.5-b20240306
* Origin: FidoNet member since 1995 (1:16/101)

On Fri, 15 Mar 2024 20:01:24 -0400, Jay Harris -> Nicholas Boel wrote:

 NB>> https://github.com/axxisd/jamnntpd
 NB>> https://github.com/axxisd/smapinntpd

This is awesome, thank you!  :)

Future plans include expanding on more user defined login options. 'notearline' was my first test to see if I could do it. Now that I know I can, the others should be easier. :)

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
* Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)

On Fri, 15 Mar 2024 20:11:24 -0400, Jay Harris -> Nicholas Boel wrote:

Would it be possible to include:

fidoconfig2jamnntpd.pl
checkgroups.pl
echomailjam2hpt.pl

In these repositories as well?

Check the 'util' subdirectory, as it is mentioned in the CHANGELOG. :)

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
* Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)

On Sat, 16 Mar 2024 03:12:22 +0300, Nil Alexandrov -> Nicholas Boel wrote:

Thanks for getting the ball rolling. You made me get off my ass
figure out github. I had only known 'clone' and 'pull' until
recently.

It is never late to learn new things, especially if you are coming
from CVS or SVN or whatever world. Cause the whole world is now on
git as an industry standard.

I didn't come from CVS or SVN, I came from never really programming before, so never had anything I needed to 'commit', 'push', 'rebase', etc. It was just a bit of a learning curve to go in the opposite direction from just being an end user to a maintainer.

I have forked them both, and they are currently matching each
with patches and features. Please check the CHANGELOG to see
what's been done:

https://github.com/axxisd/jamnntpd
https://github.com/axxisd/smapinntpd

Ah, it is not about repo anymore, it is more about a commitment to be
a maintainer for both projects. :-)

Kind of, I guess. The code hasn't been touched since like 2013 (Maybe some spelling errors and dates changed till about 2016). So my commitment is really only to myself, but may as well share it since they both fix quite a few things that were outstanding bugs.

Though, it would be more fun if you can merge them in a way that
there is a #ifdef use SMAPI or jamlib, cause the rest should be
exactly the same. As a sanity check, if you process NNTP requests differently, then you are basically failed. This is the same code
which had forked worked at some point and later continued in a
separate directions.

First, I don't think there is really any good reason for an option, as smapi supports JAM, Squish, and MSG formats, and is far more up to date than jamlib. Also, jamlib isn't even 64bit compatible.

Second, it would probably require a LOT more than just an #ifdef. Both programs are definitely *not* the same as far as code goes. They're similar, but quite a bit different at the same time. The most recent feature I added to Smapinntpd first, and when I ported it over to Jamnntpd it wasn't as easy as I had thought it would be. Then again, I don't really consider myself a programmer, but it definitely wasn't just a direct copy/paste. Some lines needed to be changed completely (usually lines utilizing jamlib or smapi, of course).

For now, if I add a feature to one, I will most likely add it to the other as well. Then I will make sure to try to fix my mistakes and typos. :)

- Jamlib working on 64bit without the -m32 option would be nice.

- Including smapi with smapinntpd and it all compiling together in one shot would also be nice (I tried once already, and failed), so one doesn't have to go out of their way to install dependencies. I will try this again at some point.

It's a fun little project to cure some times of boredom, that's for sure.

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
* Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)

On Fri, 15 Mar 2024 20:11:24 -0400, Jay Harris -> Nicholas Boel wrote:

Would it be possible to include:

fidoconfig2jamnntpd.pl
checkgroups.pl
echomailjam2hpt.pl

In these repositories as well?

My bad. jamnntpd was the last one I was working on, and I added them there. I realized I hadn't added them to smapinntpd yet. Should be there now. :)

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
* Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)

On Friday March 15 2024, Nicholas Boel said the following...

My bad. jamnntpd was the last one I was working on, and I added them there. I realized I hadn't added them to smapinntpd yet. Should be
there now. :)

Yup, I see it there now, thanks so much.


Also, in my smapinntpd.allow I had just one uncommented line:

127.0.0.1

When I upgraded to this version I was getting "Access Denied" messages, assuming due to the IPv6 support.

Changing the line to ::ffff:127.0.0.1 didn't seem to help, changing it to *127.0.0.1 seemed to do the trick.

Not sure if you would want to include that as an example for IPv4 addresses in that file? I haven't looked, but I'm wondering if the code reading smapinntpd.allow doesn't recognize the : character.


Jay

... I asked a Frenchman if he played video games. He said Wii!
--- GoldED+/LNX 1.1.5-b20240309
* Origin: Northern Realms (1:229/664)

Hi Jay.

16 Mar 24 14:18, you wrote to Nicholas Boel:

Changing the line to ::ffff:127.0.0.1 didn't seem to help, changing it to *127.0.0.1 seemed to do the trick.

Good to know! I've been running the ipv6-patched version for years, but never limited the access via the .allow file. "*" there only. :)

'Tommi

--- FMail-lnx 2.3.0.0-B20240317
* Origin: Linux 6.1.21-v7+ armv7l (2:221/6.26)

On Sat, 16 Mar 2024 19:18:40 -0400, Jay Harris -> Nicholas Boel wrote:

Yup, I see it there now, thanks so much.

Great!

Also, in my smapinntpd.allow I had just one uncommented line:

127.0.0.1

When I upgraded to this version I was getting "Access Denied" messages, assuming due to the IPv6 support.

Changing the line to ::ffff:127.0.0.1 didn't seem to help, changing it
to *127.0.0.1 seemed to do the trick.

This is the original default line that has always been there, and should be changed to suit your needs.

" What Is 127.0.0.1

127.0.0.1 is a host loopback address. Host loopback refers to the fact that no data packet addressed to 127.0.0.1 should ever leave the computer (host), sending it --- instead of being sent to the local network or the internet, it simply gets "looped back" on itself, and the computer sending the packet becomes the recipient."

Also, in the paragraph above it tells you "*" supercedes the rest of what follows, so *127.0.0.1 is actually just "*", and with that said...

If you want to allow ALL connections, use:

* <read group> <post group>

Keep in mind, this file is only allowing NON-LOGGED IN clients access to specific groups.

You DON'T want to allow access to all of your message areas prior to them setting up an account with you and logging in, so you setup a dummy area and group like "+GETACCESS+" in group X (for example) and that would be the only group and area a non-logged in account would have access to. They can post a message there requesting access to anything else, which you would have to set them up manually in the smapinntpd.users file, where you specify what LOGGED IN accounts have access to.

Not sure if you would want to include that as an example for IPv4 addresses in that file?  I haven't looked, but I'm wondering if the code reading smapinntpd.allow doesn't recognize the : character.

I don't think "*" should be a default example in any case, since that could potentially cause problems. so I think the '127.0.0.1' is and always has been just a placeholder for people to change.

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
* Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)

On Sun, 17 Mar 2024 14:07:14 +0200, Tommi Koivula -> Jay Harris wrote:

Hi Jay.

16 Mar 24 14:18, you wrote to Nicholas Boel:

 JH>> Changing the line to ::ffff:127.0.0.1 didn't seem to help,

changing it to

 JH>> *127.0.0.1 seemed to do the trick.

Good to know! I've been running the ipv6-patched version for years, but never limited the access via the .allow file. "*" there only. :)

From smapinntpd.allow:

# "*" can be used as a wildcard. Everything after "*" is ignored, i. e.
# 127.0.*.1 is equivalent to 127.0.*. Just write "*" alone on a line to
# allow all IP numbbers.

This means *127.0.0.1 = *

Which is exactly what you're doing already.

127.0.0.1 is probably just a placeholder for the host machine itself, so that you're not allowing traffic from the outside world without knowledge of it if/when one tries starting smapinntpd up for the first time without specifics.

You can always try limiting actual IP addresses in that file (and by all means, try actual IPv6 addresses to see if they work).

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
* Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)

On 17 Mar 2024, Nicholas Boel said the following...

Also, in the paragraph above it tells you "*" supercedes the rest of what follows, so *127.0.0.1 is actually just "*", and with that said...

Ah, I missed that part. No wonder it works! :)

I don't think "*" should be a default example in any case, since that could potentially cause problems. so I think the '127.0.0.1' is and
always has been just a placeholder for people to change.

Before I just had 127.0.0.1 as I only want to allow connections from nginx running on the same VPS.

What would I put in smapinntpd.allow if I wanted to restrict access to a single IPv4 address?

I don't have port 5000 exposed to the public internet, so it's not really much of a concern, more of a belt & suspenders approach.


Jay

... I have an inferiority complex but it's not a very good one

--- Mystic BBS v1.12 A49 2023/04/30 (Linux/64)
* Origin: Northern Realms (1:229/664)

On Sun, 17 Mar 2024 17:58:28 -0400, Jay Harris -> Nicholas Boel wrote:

Ah, I missed that part.  No wonder it works!  :)

:)

Before I just had 127.0.0.1 as I only want to allow connections from
nginx running on the same VPS.

What would I put in smapinntpd.allow if I wanted to restrict access to a single IPv4 address?

I would assume the exact IPv4 address you want to allow (if it is outside your LAN). If it's the same machine smapinntpd is running on, try your LAN IP address (192.168.1.xxx, or whatever it is). If you want to allow any machine from inside your LAN, you can probably do something like 192.168.1.*. You could also try your WAN IP address, if you wish to connect from the same computer, but for some reason want to connect using a FQDN.

Tinker with it. I believe you can put multiple lines in there, and wildcards should work. Please let me know if you run into any problems, as I've always just used "*" in that file, so I don't have much testing with it.

I don't have port 5000 exposed to the public internet, so it's not
really much of a concern, more of a belt & suspenders approach.

Sure, I get what you mean.

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
* Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)

On 17 Mar 2024, Nicholas Boel said the following...

What would I put in smapinntpd.allow if I wanted to restrict access t single IPv4 address?

I would assume the exact IPv4 address you want to allow (if it is
outside your LAN).

I'm not sure if I'm explaining this very well. This is exactly what I was doing with the pre-IPv6 patched version & it seemed to work.

In this latest version the only thing that seems to work is *.

$ cat smapinntpd.allow
[cut commented lines]
127.0.0.1
173.32.178.232

$ telnet localhost 5000
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
502 Access denied.
Connection closed by foreign host.


From my laptop:
C:\Users\Jay>telnet 170.75.168.188 5000
502 Access denied.

Connection to host lost.


From smapinntpd.log:
17-Mar-24 17:12:30 (::ffff:127.0.0.1:57298) Connection established to
localhost
17-Mar-24 17:12:30 (::ffff:127.0.0.1:57298) Access denied (not in allow list) 17-Mar-24 17:13:11 (::ffff:173.32.178.232:61225) Connection established to cpe1056117c4a5b-cm1056117c4a59.cpe.net.cable.rogers.com
17-Mar-24 17:13:11 (::ffff:173.32.178.232:61225) Access denied (not in allow list)


For now I'll stick with just a single * on its own line.


Jay

... The only splits I can do are of the banana variety

--- Mystic BBS v1.12 A49 2023/04/30 (Linux/64)
* Origin: Northern Realms (1:229/664)

On Sun, 17 Mar 2024 22:29:56 -0400, Jay Harris -> Nicholas Boel wrote:

I'm not sure if I'm explaining this very well.  This is exactly what I was doing with the pre-IPv6 patched version & it seemed to work.

Ok. I see what you're saying now.

In this latest version the only thing that seems to work is *.

$ cat smapinntpd.allow
[cut commented lines]
127.0.0.1
173.32.178.232

$ telnet localhost 5000
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
502 Access denied.
Connection closed by foreign host.

I'm going to assume you have SmapiNNTPd listening on port 5000?

That said, it seems to be connecting fine, but now something may be broken with the .allow file now (I get this is what you were trying to explain before).

Did you try putting ::ffff:127.0.0.1 in there for shits and giggles to see if it let you in?

From smapinntpd.log:
17-Mar-24 17:12:30 (::ffff:127.0.0.1:57298) Connection established to localhost
17-Mar-24 17:12:30 (::ffff:127.0.0.1:57298) Access denied (not in allow list)
17-Mar-24 17:13:11 (::ffff:173.32.178.232:61225) Connection established
to cpe1056117c4a5b-cm1056117c4a59.cpe.net.cable.rogers.com
17-Mar-24 17:13:11 (::ffff:173.32.178.232:61225) Access denied (not in allow list)

For now I'll stick with just a single * on its own line.

I'll take a look and see what I can find. Thanks for the info!

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
* Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)

On Sun, 17 Mar 2024 22:29:56 -0400, Jay Harris -> Nicholas Boel wrote:

From smapinntpd.log:
17-Mar-24 17:12:30 (::ffff:127.0.0.1:57298) Connection established to localhost
17-Mar-24 17:12:30 (::ffff:127.0.0.1:57298) Access denied (not in allow list)
17-Mar-24 17:13:11 (::ffff:173.32.178.232:61225) Connection established
to cpe1056117c4a5b-cm1056117c4a59.cpe.net.cable.rogers.com
17-Mar-24 17:13:11 (::ffff:173.32.178.232:61225) Access denied (not in allow list)

For now I'll stick with just a single * on its own line.

I've kind of figured out what's going on, at the moment. Since IPv6 support was added, it is now storing the full address.domain (lookup) there. Basically, what you're seeing in the log after "Connection established to" is what is being checked for in smapinntpd.allow.

Looking at your log above:

Try putting 'localhost' in that file, rather than 127.0.0.1. And if you want to allow your laptop, try putting this in there:

cpe1056117c4a5b-cm1056117c4a59.cpe.net.cable.rogers.com

If you connect via IPv6, look at your smapinntpd.log again to see what to use.

Let me know if that works for you (for now).

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
* Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)

On Sunday March 17 2024, Nicholas Boel said the following...

I've kind of figured out what's going on, at the moment. Since IPv6 support was added, it is now storing the full address.domain (lookup) there. Basically, what you're seeing in the log after "Connection established to" is what is being checked for in smapinntpd.allow.

Try putting 'localhost' in that file, rather than 127.0.0.1. And if
you want to allow your laptop, try putting this in there:

cpe1056117c4a5b-cm1056117c4a59.cpe.net.cable.rogers.com

Yup, putting localhost & the rogers.com hostname into smapinntpd.allow does the trick.

::ffff:127.0.0.1 still didn't allow connections from localhost.


Thanks,


Jay

... Sometimes I forget the word boomerang but it always comes back to me
--- GoldED+/LNX 1.1.5-b20240309
* Origin: Northern Realms (1:229/664)

On Mon, 18 Mar 2024 12:22:58 -0400, Jay Harris -> Nicholas Boel wrote:

 NB>> Try putting 'localhost' in that file, rather than 127.0.0.1. And if
 NB>> you want to allow your laptop, try putting this in there:

 NB>> cpe1056117c4a5b-cm1056117c4a59.cpe.net.cable.rogers.com

Yup, putting localhost & the rogers.com hostname into smapinntpd.allow does the trick.

::ffff:127.0.0.1 still didn't allow connections from localhost.

Yep, I noticed that after I replied to you and went to actually test it for myself. :)

Did you by chance try out the latest version with huskylib and smapi included? I'd like to know if it works for you (compiling, that is.. nothing has changed with the .allow file yet).

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
* Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)

On 18 Mar 2024, Nicholas Boel said the following...

Did you by chance try out the latest version with huskylib and smapi included? I'd like to know if it works for you (compiling, that is.. nothing has changed with the .allow file yet).

Yes, I cloned that one & ran the ./build.sh first which worked and then make linux went off without a hitch as well.

Was nice not having to go into the file & point it to the husky sources, good work! :)


Jay

... How do you make a Kleenex dance? Put a little boogie in it

--- Mystic BBS v1.12 A49 2023/04/30 (Linux/64)
* Origin: Northern Realms (1:229/664)

On Mon, 18 Mar 2024 23:51:04 -0400, Jay Harris -> Nicholas Boel wrote:

On 18 Mar 2024, Nicholas Boel said the following...

 NB>> Did you by chance try out the latest version with huskylib and smapi
 NB>> included? I'd like to know if it works for you (compiling, that is..
 NB>> nothing has changed with the .allow file yet).

Yes, I cloned that one & ran the ./build.sh first which worked and then make linux went off without a hitch as well.

Excellent, glad to hear! And thanks for testing.

Was nice not having to go into the file & point it to the husky sources, good work!  :)

Definitely shouldn't have to do that. :)

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
* Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)