NETWORK: udp_port_rover reluctant to rove (unlike tcp_port_rover)
From: John Dahlstrom (jd_at_freeshell.org)
Date: 01/16/05
- Previous message: Erik Steffl: "Re: SATA disk dead? ATA: abnormal status 0x59 on port 0xE407"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sat, 15 Jan 2005 20:37:39 -0600 (CST) To: linux-kernel@vger.kernel.org
Regarding udp_port_rover (of linux/net/ipv4/udp.c):
In Linux 2.4 or 2.6, I noticed that selected local port numbers for UDP
resist roaming, unlike TCP ports numbers (tcp_port_rover) that appear
to steadily increase irrespective of concurrent local port usage.
What is the advantage of this lack of parallel behavior? (Other than
exacerbating broken behavior of certain firewalls that insist on fixed
UDP source port blocking?)
Aesthetically peculiar it seems, that the kernel reins in port roving
for the connectionless protocol unless a UDP stampede unleashes itself,
while allowing the TCP ports to range free across the local ports
regardless.
Kind regards,
- John
-- http://jodarom.sdf1.org/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Previous message: Erik Steffl: "Re: SATA disk dead? ATA: abnormal status 0x59 on port 0xE407"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|