> If I understand the setup right, you are referring here to > hosts.allow and > hosts.deny on the LEAF router. But the actual Web server runs > on a different > host, on its port 80, and gets (or is supposed to get, once everything > works) traffic forwarded from port 8080 on the LEAF router's > external interface. > > If I have all of that right, then the entries you describe > will have no > effect on this problem. Only the port-forwarding code in the kernel is > involved on the LEAF router, and that makes no use fo these > files, which are > used by inetd (and a few other server processes). > > If I have any of my assumptions wrong, then please clarify > appropriately.
No, you've got it right. Ok, ruling out one thing then... I still can't access the web server via http://www.cybersampson.com!!! #$%#!& I'm beginning to think it's the web server that is denying access. I'm thinking that the web server does accept requests from the private network but is *somehow* denying requests that pass through the DCD router. Would that be possible even though the forwarded packets are now inside the private network? I do not know enough about TCP/IP packet structure to be able to answer this question adequately. Can someone verify or debunk this? ~Doug _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
