2.4/2.6 local TCP connect oddity
- From: Tal Kelrich <tal@xxxxxxxxxxxxxxx>
- Date: Sun, 21 Oct 2007 17:53:37 +0200
Hi,
I've run into a problem where a process trying to connect to a local
port within the local port range eventually ends up connected to itself,
with source port = dest port.
similar behavior can be gotten by running netcat as follows:
nc -p 1025 localhost 1025
I'm not really sure if that's a bug, but the original case was at least
unexpected.
Regards,
Tal Kelrich
--
Tal Kelrich
PGP fingerprint: 3EDF FCC5 60BB 4729 AB2F CAE6 FEC1 9AAC 12B9 AA69
Key Available at: http://www.hasturkun.com/pub.txt
----
Administration: An ingenious abstraction in politics, designed to
receive the kicks and cuffs due to the premier or president.
-- Ambrose Bierce
----
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: 2.4/2.6 local TCP connect oddity
- From: Willy Tarreau
- Re: 2.4/2.6 local TCP connect oddity
- Prev by Date: Re: [PATCH 1/4 resend] [x86] Add generic GPIO support to x86
- Next by Date: Re: [PATCH 17/17] RTC interrupt handling cleanups
- Previous by thread: Why are ipmi modules being loaded?
- Next by thread: Re: 2.4/2.6 local TCP connect oddity
- Index(es):
Relevant Pages
|
