Hi Frank, hi all > I'm not sure that David's suggestion of running an internal DNS server > would help. That is, it looks like the complex.wox.org name helps in > his case, but I have no such name to put in my external web page to use > as a link to my home network. Instead, I edit the external web page > each time I restart my DSL connection to update it to the currently > assigned external IP, e.g. http://209.142.160.132:8888/whatever, so > there would be nothing for a local DNS server to work with, right?
Ahh, sorry, I didn't realize that you don't use a DNS name for your website! Instead of manually update your IP on the website and adding a second link (which works of course), I'd suggest to use a Dynamic DNS service like DynDNS. This is the best solution which covers all your needs. There is .lrp package for LEAF (ez-ipupdate) which monitors your external IP and updates the DNS record. I'd do the following: 1. register a DynDNS account. (www.dyndns.org) 2. install .lrp package (from Jacques Nilo's or my package directory: http://leaf.sourceforge.net/devel/sminola/packages) 3. use your new DNS name for the link on the webpage (<a href="http://newname.dyndns.org";>My Server at home</a>) 4. add a entry to your hosts file for this DNS name (in the system32 directory) This solution is much cooler because you don't have to care about the IP anymore. It's done automatically. --- Sandro Minola | LEAF Developer (http://leaf.sourceforge.net) mailto:[EMAIL PROTECTED] | mailto:[EMAIL PROTECTED] http://www.minola.ch | http://leaf.sourceforge.net/devel/sminola > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Frank > Sergeant > Sent: Sunday, February 24, 2002 8:22 PM > To: [EMAIL PROTECTED] > Subject: RE: [Leaf-user] How to reach my internal web server from an > internal machine via an external web page? > > > Thank you, Sandro and David. > > > "Sandro Minola" <[EMAIL PROTECTED]> wrote: > > > 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. > > > This issue was discussed some days ago in the thread > "[Leaf-user] DCD port > > forwarding [second attempt]". > > I had read that thread but didn't quite make the connection as I thought > in that case the problem was that external machines could not access his > internal web server. In my case, external machines can access my > internal web server. But, looking further, I now see how the point > about portscanning the external IP from within the network is related. > > > As you can see from the pasted text, another possiblity to > solve the problem > > would be to add a third NIC to your Firewall (DMZ interface). > > Yes, I'd prefer not to add another NIC. > > > David said to add an internal DNS server to your Firewall. This > is the best > > and cleanest solution if you don't want to buy/add hardware. > > Ok, I would not mind trying this, but as I mentioned above, would it > work with just the raw IP of my external IP, rather than an actual name? > I don't have an actual name to put in the link on the external web > page. > > > or ... , you also may add > > an entry for your website in the "hosts" file of your internal clients. > > Linux: /etc/hosts > > Windows NT: C:\WINNT\SYSTEM32\DRIVERS\ETC > > Windows 9x: C:\windows\system32\ (I'm not sure about Win9x, > but I think the > > hosts file is in system32, use Filesearch) > > Ok, I've started trying this, but no luck yet. I would be doing the web > browsing from bed (192.168.1.40) (a W2K machine). My current external > IP is 209.142.160.132. The internal web server is on liv (192.168.1.10) > (a Linux machine). I added the second line to the > C:\WINNT\system32\drivers\etc\hosts file: > > 192.168.1.10 liv.home.net liv > 209.142.160.132 liv.home.net liv > > I think that doesn't help? > > Then, I added a route on bed to say: > > route add 209.142.160.132 MASK 255.255.255.255 192.168.1.10 > > I guess (?) that helps. I suppose when bed makes the http request to > the external IP, the route will cause it to be addressed to liv rather > than directly to the firewall machine. Then, I guess liv will say, well > that's not my address! I'll just pass it along to my default gateway > (the firewall machine). > > Maybe I then need a port forwarding/masquerading command on liv to say > if anything comes in from bed for port 8888 on 209.142.160.132, then > port forward that to 192.168.1.10. > > Well, that's my latest thinking but I may just be thoroughly confused. > I may just live with not being able to browse the internal web site from > a link on the external web page. This is not a serious problem. I just > thought it would be better for me to see my external web site (including > its link to my internal web site) exactly the same way that an external > machine would see it. > > Thanks again. > > > -- Frank > > _______________________________________________ > 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
