Hi Roderick, hi all

>You could do one of two things. Either forward 8080 -> 8080 like
>above and open the destination 8080 using some of the comments others
>have made, or, you could simply forward 8080 -> 80 by changing your
>port forwarding

Hmm, his config is okay. Not clean, but ok.
He's doing the following things:
EXTERN_TCP_PORTS
-Port 80 is opened. This is not necessary cause Cox is blocking Port 80.
It's just there because he was trying to get it running and left it.
-Port 8080 is opened. This is necessary cause he wants to run his webserver
on port 8080

Portforwarding:
-Port 80 is forwarded to 192.168.1.1. This is not necessary cause there is
nothing listening on port 80 on 192.168.1.1 because his webserver is on
8080. (It's *still* there cause he didn't removed it)

-Port 8080 is forwarded to 192.168.1.1. This is necessary.

His config *should* work. No, I'd say it the other way arround: His config
*will* work if his webserver is properly configured.

---
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 Roderick
Scott Corporation
Sent: Thursday, February 14, 2002 6:25 PM
To: [EMAIL PROTECTED]
Subject: Re: [Leaf-user] DCD port forwarding [second attempt]


Hi Doug,

I'm a little late in diving in here but I think the primary error in
your config is in this section from what I can tell.

>###########################################################################
###
>#
># Port Forwarding
>###########################################################################
###
>#
># Remember to open appropriate holes in the firewall rules, above
>
># Uncomment following for port-forwarded internal services.
># The following is an example of what should be put here.
># Tuples are as follows:
>#       <protocol>_<local-ip>_<local-port>_<remote-ip>_<remote-port>
>#INTERN_SERVERS="tcp_${EXTERN_IP}_ftp_192.168.1.1_ftp
>tcp_${EXTERN_IP}_smtp_192.
>INTERN_SERVERS="tcp_${EXTERN_IP}_8080_192.168.1.1_8080"

Here you are forwarding 8080 to 8080

># These lines use the primary external IP address...if you need to
>port-forward
># an aliased IP address, use the INTERN_SERVERS setting above
>#INTERN_FTP_SERVER=192.168.1.1   # Internal FTP server to make available
>INTERN_WWW_SERVER=192.168.1.1   # Internal WWW server to make available
>#INTERN_SMTP_SERVER=192.168.1.1 # Internal SMTP server to make available
>#INTERN_POP3_SERVER=192.168.1.1 # Internal POP3 server to make available
>#INTERN_IMAP_SERVER=192.168.1.1  # Internal IMAP server to make available
>#INTERN_SSH_SERVER=192.168.1.1   # Internal SSH server to make available
>#EXTERN_SSH_PORT=24              # External port to use for internal SSH
>access

But here you are opening  www (80) so it is not connectin.

You could do one of two things. Either forward 8080 -> 8080 like
above and open the destination 8080 using some of the comments others
have made, or, you could simply forward 8080 -> 80 by changing your
port forwarding to:

        INTERN_SERVERS="tcp_${EXTERN_IP}_8080_192.168.1.1_80"

And now that I look closer at it, the line

        NTERN_WWW_SERVER=192.168.1.1   # Internal WWW server to make available

defaults to ${EXTERN_IP} at port 80.... which is not what you want.

I hope this helps,

Scott

_______________________________________________
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

Reply via email to