|
|
Enable remote access with TCP wrappers from dynamic IPs
I wondered that too. I suspect the issue would be similar, though, because hosts.allow and hosts.deny are accessed by inetd, and inetd does three things: it gets the IP of the incoming host (say, 123.456.78.90), resolves it (say, 78-90.yourISP.com), and then checks to see whether either 123.456.78.90 or 78-90.yourISP.com is in hosts.allow. If you use no-IP, you're given a "fake" domain (say, foo.noip.net) which always resolves to your current IP, which is great, but when inetd checks hosts.allow, it doesn't translate foo.noip.net into 123.456.78.90 before comparing it to the incoming host. So, it compares the first two addresses to the third, finds no match, and rejects. That's why putting foo.noip.net into hosts.allow won't work but looking it up with nslookup and *then* putting it in hosts.allow will. |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:Hints1 new Hints in the last 24 hoursComments last 2 daysNo new commentsLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.24 seconds |
|