All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Oester <kernel@linuxace.com>
To: Mitchell Blank Jr <mitch@sfgoth.com>
Cc: shemminger@osdl.org, linux-net@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: Recent select() handling change breaks Poptop
Date: Mon, 6 Dec 2004 20:53:02 -0800	[thread overview]
Message-ID: <20041207045302.GA23746@linuxace.com> (raw)
In-Reply-To: <20041207025218.GB61527@gaz.sfgoth.com>

On Mon, Dec 06, 2004 at 06:52:18PM -0800, Mitchell Blank Jr wrote:
> That's very strange.  It would be helpful if you could gather:
>   1. strace of the server, both working and broken

Will work on it

>   2. a "tcpdump -nvv" of its udp traffic (ideally captured from a seperate
>      server, but from the server would probably be OK too)

PPTP uses TCP 1723 and GRE (proto 47), so there is no udp traffic involved.
I suspect the change was made to all datagram traffic with the assumption 
that UDP was the only protocol impacted.  Perhaps GRE was not considered?

Phil

  reply	other threads:[~2004-12-07  4:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-07  0:35 Recent select() handling change breaks Poptop Phil Oester
2004-12-07  2:52 ` Mitchell Blank Jr
2004-12-07  4:53   ` Phil Oester [this message]
2004-12-07  5:48     ` Mitchell Blank Jr
2004-12-07 15:08       ` [PATCH] fix select() for SOCK_RAW sockets Mitchell Blank Jr
2004-12-07 17:28         ` Phil Oester
2004-12-07 17:35         ` YOSHIFUJI Hideaki / 吉藤英明
2004-12-07 18:01           ` [PATCH] fix select() for SOCK_RAW sockets (ipv6) Stephen Hemminger
2004-12-07 18:48             ` David S. Miller
2004-12-07 18:56               ` Stephen Hemminger
2004-12-08  7:58               ` YOSHIFUJI Hideaki / 吉藤英明
2004-12-07 17:45         ` [PATCH] fix select() for SOCK_RAW sockets Stephen Hemminger
2004-12-08  5:28         ` David S. Miller

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=20041207045302.GA23746@linuxace.com \
    --to=kernel@linuxace.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@vger.kernel.org \
    --cc=mitch@sfgoth.com \
    --cc=shemminger@osdl.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.