MSGID: 1:154/10 65f736f8
REPLY: 1:229/664 22545ed1
PID: SmapiNNTPd/Linux 2.2.1
CHRS: UTF-8 4
TZUTC: -0500
TID: hpt/lnx 1.9 2024-02-05
On Sun, 17 Mar 2024 17:58:28 -0400, Jay Harris -> Nicholas Boel wrote:

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

:)

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

 JH> What would I put in smapinntpd.allow if I wanted to restrict access to a
 JH> 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.

 JH> I don't have port 5000 exposed to the public internet, so it's not
 JH> 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)
SEEN-BY: 15/0 90/1 103/705 105/81 106/201 120/616 123/10 124/5016
SEEN-BY: 128/260 135/225 153/757 7715 154/10 30 40 50 700 203/0 218/700
SEEN-BY: 220/90 221/0 6 226/18 30 227/114 229/110 112 113 206 307
SEEN-BY: 229/317 426 428 470 664 700 240/1120 5832 266/512 280/464
SEEN-BY: 280/5003 5555 282/1038 291/111 292/8125 301/1 310/31 320/219
SEEN-BY: 322/757 341/66 234 342/200 396/45 423/120 460/58 256 1124
SEEN-BY: 467/888 633/280 712/848 770/1 2320/105 3634/12 5020/400 5054/30
PATH: 154/10 280/464 460/58 229/426