Re: [netfilter] Re: iptables help

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: netfilter@xxxxxxxxxxxxxxxxxxx
Subject: Re: [netfilter] Re: iptables help
From: "Ashley M. Kirchner" <ashley@xxxxxxxxxx>
Date: Thu, 29 Jul 2004 15:35:02 -0600
In-reply-to: <200407292220.39022.Antony@Soft-Solutions.co.uk>
Organization: Photo Craft Laboratories, Inc.
References: <Pine.LNX.4.44.0407291026030.2121-100000@ivanhoe.pcraft.com> <200407291928.48974.Antony@Soft-Solutions.co.uk> <410966F6.3020206@pcraft.com> <200407292220.39022.Antony@Soft-Solutions.co.uk>
Sender: netfilter-admin@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)

Antony Stone wrote:

You're missing the fact that 192.168.1.253 connects to 66.218.75.184 on destination port 80, not the other way round.

   Yeah, I noticed that after sending the message.

References:
- Re: [netfilter] Re: iptables help
  - From: Ashley M. Kirchner
- Re: [netfilter] Re: iptables help
  - From: Antony Stone
- Re: [netfilter] Re: iptables help
  - From: Ashley M. Kirchner
- Re: [netfilter] Re: iptables help
  - From: Antony Stone

Prev by Date: Re: [netfilter] Re: iptables help
Next by Date: RE: [netfilter] Re: iptables help
Previous by thread: Re: [netfilter] Re: iptables help
Next by thread: Re: [netfilter] Re: iptables help
Index(es):
- Date
- Thread

[Index of Archives] [Linux Netfilter Development] [Linux Kernel Networking Development] [Netem] [Berkeley Packet Filter] [Linux Kernel Development] [Advanced Routing & Traffice Control] [Bugtraq]

Powered by Linux