From: "John A. Sullivan III" <jsullivan@opensourcedevel.com>
To: Dave Beach <drbeach@rogers.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: Networking question
Date: Sat, 24 Dec 2005 13:53:58 -0500 [thread overview]
Message-ID: <1135450438.2584.4.camel@localhost> (raw)
In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAqrTb2LYes02Oflamihm4wwL6DwAQAAAAdIdG2rUYq0C89CEWuAaQWwEAAAAA@rogers.com>
On Sat, 2005-12-24 at 13:34 -0500, Dave Beach wrote:
> This is undoubtedly off-topic in oh-so-many ways; I'd be quite happy to be
> redirected to another, more appropriate mailing list should someone be so
> kind as to suggest one.
>
> Internal, home, private network, WinXP boxen and a Squid proxy, connecting
> through an iptables box to my router and cable modem. Everything works
> peachy.
>
> While trying to poke bittorrent holes through my iptables setup (see? Some
> vague evidence of relevance), I encountered problems and decided to take the
> proxy out of the picture. VERY much to my surprise, when I reconfigured IE
> to not use the proxy (and configured iptables to allow for a direct
> connection), I see no HTTP traffic whatsoever leaving the XP box destined
> for the firewall. In fact, no TCP traffic either (all traffic analysis done
> with ethereal on the XP box). I can ping to/from the XP box, and see THAT
> via ethereal.
>
> I am considerably confused by this. My presumption was that IE would just
> happily send HTTP traffic directly to the firewall, but this is NOT the
> behaviour I'm seeing.
>
> I know it's Christmas Eve day, and I was out a bit late last night, but
> there's clearly something VERY obvious I'm missing.
>
>
If the problem is on the XP station (no packets egressing), could there
be an XP personal firewall problem? - John
--
John A. Sullivan III
Open Source Development Corporation
+1 207-985-7880
jsullivan@opensourcedevel.com
Financially sustainable open source development
http://www.opensourcedevel.com
next prev parent reply other threads:[~2005-12-24 18:53 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-24 18:11 [LARTC] Simple routing configuration Paul Lewis
2005-12-24 18:11 ` Paul Lewis
2005-12-24 18:32 ` John A. Sullivan III
2005-12-24 18:34 ` Networking question Dave Beach
2005-12-24 18:53 ` John A. Sullivan III [this message]
2005-12-24 18:56 ` /dev/rob0
2005-12-24 18:58 ` Edmundo Carmona
2005-12-24 19:02 ` Dave Beach
-- strict thread matches above, loose matches on Subject: below --
2022-06-21 0:29 Networking Question Ryan P. Nicholl
2022-06-21 7:02 ` Bernd Petrovitsch
2022-06-21 15:43 ` Ryan P. Nicholl
2013-03-14 10:55 networking question devendra.aaru
2013-03-14 18:11 ` Rami Rosen
2013-03-15 7:19 ` devendra.aaru
[not found] <65aa6af90512241106v5e49da74jc54fa7821960ed28@mail.gmail.com>
2005-12-24 19:09 ` Networking question Dave Beach
2005-12-24 19:17 ` Edmundo Carmona
2005-12-24 20:00 ` Dave Beach
2005-12-24 20:16 ` Edmundo Carmona
2004-04-01 17:15 Tony Gogoi
2004-04-01 18:09 ` Adam Lang
2004-04-01 18:24 ` Tony Gogoi
2004-04-01 18:39 ` Adam Lang
2004-04-01 22:50 ` Glynn Clements
2002-07-18 15:11 Bloch, Jack
2002-07-18 15:17 ` kuznet
2002-07-16 15:34 Bloch, Jack
2002-07-16 17:00 ` kuznet
2002-07-17 22:32 ` Maksim (Max) Krasnyanskiy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1135450438.2584.4.camel@localhost \
--to=jsullivan@opensourcedevel.com \
--cc=drbeach@rogers.com \
--cc=netfilter@lists.netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.