all,
I guess my ISP is blocking port 80. I configured the web server to use
port 8080 and configured my rules the same as before but used port 8080 and
it worked. thanks for all of the help!
----- Original Message -----
From: "Stewart Thompson" <[EMAIL PROTECTED]>
To: "Big Daddy" <[EMAIL PROTECTED]>; "Antony Stone"
<[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Monday, July 08, 2002 4:11 PM
Subject: RE: HTTP Port forwarding issues
> Perhaps you should publish your entire rule set. Trying to help you with
> piecemeal rules is pretty tough.
> The order of the rules is important. Logging is also useful as recommended
> in an earlier post. What does
> a TCPDUMP show for port 80 on the External and Internal Interfaces. Also,
> what are you using to test
> your port 80? Internal machines will act very different than machines
coming
> in from the Internet.
>
> Stu........
>
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Big Daddy
> Sent: July 8, 2002 1:04 PM
> To: Antony Stone; [EMAIL PROTECTED]
> Subject: Re: HTTP Port forwarding issues
>
> i have the following rule as well.
>
> iptables -A FORWARD -i eth0 -m state --state RELATED,ESTABLISHED -j ACCEPT
>
> ----- Original Message -----
> From: "Antony Stone" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Monday, July 08, 2002 3:57 PM
> Subject: Re: HTTP Port forwarding issues
>
>
> > On Monday 08 July 2002 8:51 pm, Big Daddy wrote:
> >
> > > It worked when I was using a Linksys router. However maybe they have
> > > changed it since then. Do my rules look fine?
> >
> > Well, I hope these are not your *only* rules ? I mean, like Stewart
> > suggested, what about the ESTABLISHED packets as well as the NEW ones ?
> >
> >
> >
> > Antony.
> >
>
>
>
