due to the one-way nature of the ipforwarding rules, you cannot take advantage of the portforwarding your firewall does... i.e. htting http://external.ip:8888 will not show you what you see when you go to http://192.168.1.10:8888 ... to test your firewall rules, you need a net connection that isn't behind your firewall. or what i do, since my discussion board gets twitchy whenever you try to view it from anything other than the domain name, is i run an internal dns server, and map complex.wox.org to 192.168.1.11, my webserver. the other computers get dns entries, but those are name.complex.wox.org ... it's more of a workaround than a fix, but eh, what can ya do? :] having an internal dns server is helpful anyway... keeps you from having to type in ip's or update hosts files every time a computer gets added. -david
On Sun, 2002-02-24 at 01:24, Frank Sergeant wrote: > I have a basic Dachstein-PPPoE floppy firewall setup with port 8888 > opened on the firewall and forwarded to port 8888 on an internal > machine (192.168.1.10) which is running a web server on that port. > > Sitting at another internal machine (192.168.1.40), I can access the web > server via its local network address, e.g. http://192.168.1.10:8888. > > However, I have a web page hosted on an external site that has a > link to my internal web server via my firewall's external IP. From > a machine outside my network, that link works fine, reaching my > internal web server. However, if I connect to the external web page > from the internal network (e.g. 192.168.1.40), clicking on the link to > my internal web page fails. > > Can anyone suggest what I should do or where I should look in order > to solve this? > > > -- Frank > [EMAIL PROTECTED] > > _______________________________________________ > Leaf-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/leaf-user _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
