Hi Greg,

The best solution that i found for this problem, and i used it currently is 
by, adding your local server name to your host file..

example.

192.168.11.40       greg.dyndns.org

if your add something like that u'll be up and running, that's how i do it, 
and have no problems whatsoever, if it's one pc u should have no problem, if 
u have many pc's then u'll probably want to have a general host file, and 
have it copied to each pc during logon

regards


>From: Greg Brown <gregbrown at mindspring dot com>
>To: m0n0wall at lists dot m0n0 dot ch
>Subject: [m0n0wall] m0n0, dyndns, and nat
>Date: Thu, 27 Jan 2005 21:45:42 -0500
>
>My network is on a cable modem and my routeable IP address is grabbed by 
>m0n0 (as it should be).  My internal "LAN" is on 192.168.11.x/24 range.  I 
>forward ports 80, 22, and 443 to 192.168.11.40, my primary server.  How can 
>I, while connected to my internal LAN, update my blog and other software 
>associated with my dyndns name?  If I try to force the connection to 
>192.168.11.40/blog (running Drupal) I cannot add stories to my page.  My 
>lame work-around has been to ssh to my buddy's house then use his squid 
>proxy to redirect back out on the Internet.  Obviously this is not ideal.
>
>There must be a way to set up a rule on m0n0 to allow this?  I've google, 
>hacked around, etc, but nothing seems to work like I'd like it to.  Is 
>there a quick m0n0 rule fix to allow this?
>
>Greg
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
>For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch
>

_________________________________________________________________
Talk with your online friends with MSN Messenger http://messenger.msn.nl/