linux-kernel - Re: Killing a network connection

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:	Tue, 16 Oct 2007 00:12:46 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Stefan Monnier <monnier@....umontreal.ca>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Killing a network connection

Stefan Monnier <monnier@....umontreal.ca> writes:
>
> The main use for me is to deal with dangling connections due to taking
> network interfaces up&down with different IP addresses (typically the wlan0
> interface where the IP is different because I've modes from an AP to
> another).  Of course, maybe there's another way to solve this particular
> problem, in case I'd like to hear about it as well.

Long ago I did a 2.4 patch that solved exactly this problem. It introduced
a new ifconfig flag "dynamic" and when a dynamic address went down
all TCP connections originating from it were killed. It's still available
in older SUSE releases. I might post a forward port later.

-Andi
-
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/