From: Patrick McHardy <kaber@trash.net>
To: Greg Scott <GregScott@InfraSupportEtc.com>
Cc: netfilter-devel@lists.netfilter.org,
Mike McRae <Mike_McRae@schneidermans.com>
Subject: Re: Troubeleshooting a PPTP conversation
Date: Mon, 04 Sep 2006 18:12:05 +0200 [thread overview]
Message-ID: <44FC5055.10802@trash.net> (raw)
In-Reply-To: <925A849792280C4E80C5461017A4B8A206FA78@mail733.InfraSupportEtc.com>
Greg Scott wrote:
>>I didn't notice any error .. are there still gre connection tracking
>
> entries when this error occurs?
>
> Yes. Searching for "1723" in the output I posted from
> /proc/net/ip_conntrack, I see three entries. The first two are from my
> end user. The third ons is from somewhere else - not sure where.
> Curiously, all the IP Addresses on that third entry are internal. I
> wonder why anyone would do a PPTP connection when they are already part
> of the network? Here they are:
>
> [...]
>
> It looks like everything in here shows TCP traffic. I don't see
> anything that mentions GRE specifically or protocol 47. But that may be
> normal.
Depending on the state of the connection, yes. I'm currently cleaning
the helper up and noticed a few bugs. Not sure how they could lead
to something like this but I'll prepare a patch for 2.6.17 when I'm
done if you want to test it.
next prev parent reply other threads:[~2006-09-04 16:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-04 15:46 Troubeleshooting a PPTP conversation Greg Scott
2006-09-04 16:12 ` Patrick McHardy [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-09-04 16:22 Greg Scott
2006-09-04 16:26 ` Patrick McHardy
2006-08-29 12:23 Greg Scott
2006-08-29 12:54 ` Patrick McHardy
2006-09-04 14:46 ` Patrick McHardy
2006-08-29 2:24 Greg Scott
2006-08-28 19:14 Greg Scott
2006-08-28 13:30 Greg Scott
2006-08-28 15:14 ` Patrick McHardy
2006-08-27 0:13 Greg Scott
2006-08-28 9:23 ` Patrick McHardy
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=44FC5055.10802@trash.net \
--to=kaber@trash.net \
--cc=GregScott@InfraSupportEtc.com \
--cc=Mike_McRae@schneidermans.com \
--cc=netfilter-devel@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.