linux-kernel - Re: Feedback on TCP: Make TCP_RTO

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 16 Jun 2008 17:03:06 +0930
From:	David Newall <davidn@...idnewall.com>
To:	Stephen Hemminger <shemminger@...tta.com>
CC:	OBATA Noboru <noboru.obata.ar@...achi.com>,
	"David S. Miller" <davem@...emloft.net>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-net@...r.kernel.org
Subject: Re: Feedback on TCP: Make TCP_RTO_MAX a variable

Stephen Hemminger wrote:
> On Mon, 16 Jun 2008 06:27:35 +0930
> David Newall <davidn@...idnewall.com> wrote:
>   
>> ... caused by floods of packets directed towards the internet
>> link at one end or the other
> Why are you letting them through. Use proper firewalling.
>   

They didn't get through the router.  These floods congested the border
links (devices).

> A real VPN with IPSEC would have stopped the problem.
>   

No, it wouldn't.  If you don't see this, ask and I'll explain, again.


> I wouldn't put a mission critical system exposed directly to the Internet.
>   

I didn't.  Standard NAT appliances protect all ends.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/