> I would be happier knowing what it says rather than what it
> "essentially"
> says. Also what "it" is (what browser is reporting the
> error). From here,
> Netscape (on Win95) gets the right translated address from
> DynDNS, but times
> out with its standard "The server is not responding ..." message.
>
Noted.
> >Here is the data for analysis:
>
> Where in the config file are you setting up the port
> forwarding? If I look
> at the section on port forwarding, all I see is a
> commented-out line to
> specify the port-forwarding link:
>
> >#INTERN_SERVERS="tcp_${EXTERN_IP}_8080_192.168.1.200_80"
>
> (You do uncomment the line to identify the internal WWW
> server, but that
> doesn't include any port-8080 information.)
>
> >INTERN_WWW_SERVER=192.168.1.200 # Internal WWW server to make
> >available
I've been trying out various ways to make port-forwarding work. Thus the
reason why you see so many commented out lines.
>
> You might want to check if the port-forwarding rule you
> desire is actually
> in place. I always forget this command, but I think it is --
>
> ipmasqadm mfw -L -n
Here it is.
# ipmasqadm mfw -L -n
fwmark rediraddr rport pcnt pref
Looks like there isn't any port-forwarding rules in place? What do I need to
do then? Would uncommenting the "INTERN_SERVERS" line listed above open port
8080 for forwarding to port 80 on 192.168.1.200?
~Doug
_______________________________________________
Leaf-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
