On Wed, 2002-10-09 at 11:27, Joseph A Nagy Jr wrote: > > > > My external IP as DynDNS.org has it is 24.158.191.171, but it only > > brings up my routers admin page instead of the web site I'm trying to > > host off my system and no one EXTERNAL of me can connect at all. > > Apparently this is NOT my real IP, > > Let me rephrase that. The url http://omega-fleet.homelinux.org (which > DynDNS bound to the IP given above) brings up the routers admin page > instead of the site as defined by my server and v-host configuration for > Apache.
I suspect that the issue is indeeed in the router setup. I have no direct experience with these devices, but I would think at a minimum you will need to forward port 80 to the internal box and (I hope ) poke a hole in the router's firewall enabling port 80 to get through. If you are still concerned about the ipaddress, what's his name had a good solution, go the the chicken whatever site he suggested and see where your internal boxes are being masqueraded from. That IP address will be your router's external interface. This should tell you for sure what the ip address is if you don't trust the admin page. I am relieved for you that connections coming in from the external interface do not see your admin page. google a bit on the linksys port forwarding feature that I am assuming your router has. I DOES do portforwarding doesn't it? In my experience, DMZs are routeble ip addresses (not private ip like 192.168.*.*) but with a firewall protecting both inputs from the untrusted external network as well as the connections into the trusted nework from the DMZ based hosts. Therefore; when you say you enabled the dmz feature, I think of allowing connections to a routable ipaddressed host through the router rather than portforwarding to a private ipaddressed host. If I am way off let me know. my two cents. Bret -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
