Tcp-wrappers

General system
#1

How do I allow a connection from a noip address?

Added to /etc/hosts.allow :

sshd : 192.168.0.5 xirconuk.ddns.net

The 192 bit works like a dream. It just hangs on the noip bit.

Any ideas?

#2

Does ddns.net set an rDNS (or PTR) record for the IP address that points to the expected hostname?

#3

Isn’t the client list comma delimited?

#4

Not according to https://man.archlinux.org/man/community/tcp-wrappers/hosts_access.5.en . :man_shrugging:

#5

List elements should be separated by blanks and/or commas.

I guess not :smile:

1 Like
#6

I deleted the connection and re-did and it works :smiley: :brain: hurts now.

1 Like
#7

IMO the Noip system works, but frequently has issues with resolution. I found I had to run the DUC update every 5 minutes, from both ends of the connection, in order to maintain the resolution.

1 Like
#8

DUC update?

#9

https://www.noip.com/download?page=linux

#10

Strange - so far for me it has worked perfectly (AFAIK) - and allows me to run 2 separate mirrors on the NoIP address. It even changed over more quickly than I expected when ISP troubles actually changed my IP (DUC at work). I wonder if I just hit on magic settings - but no special tricks were needed…

#11

Yeah, maybe Noip provides more resources for first-world countries, not banana republics like New Zealand or the UK :rofl:

1 Like
#12

You have BANANAS?? Here I though it might be what you were, not what you had… :duck:

Actually - I don’t see how/why it would differ from one place to another - still Linux and still DUC. Are you sure DUC is configured properly - and set to frequent enough? Jus’ wondering…

1 Like
#13

I didn’t say we had bananas; rather that we are bananas.

#14

Good on you, then. Looking at the world upside down can’t but help these days! Be glad you’re still in a republic, anyway… :grin:

The worst of these challenges we all face is that I’ll probably not make it down there after all - always wanted to (even before the LOTR). Bananas not required.

1 Like