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]
Message-Id: <20120326.174216.151181141269420661.davem@davemloft.net>
Date:	Mon, 26 Mar 2012 17:42:16 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	david.ward@...mit.edu
Cc:	jorge@...2.net, netdev@...r.kernel.org
Subject: Re: [PATCH] net/vlan: withdraw VLAN ID attribute from GVRP on VLAN
 device stop

From: "Ward, David - 0663 - MITLL" <david.ward@...mit.edu>
Date: Mon, 26 Mar 2012 11:50:16 -0400

> If I create an interface that is initially down, then bring it up, and
> finally bring it back down, I think it should return to the state it
> was in initially.  So in my opinion, either the GVRP attribute should
> exist while the interface is down, or it shouldn't.

You're whole argument breaks down because we definitely don't do this
for IPv4 addresses, we'll keep receiving traffic for IPv4 addresses
configured on that interface when received on other interfaces which
are still up, even when you bring that interface down.

Really, if you want to leave GVRP, unconfigure it.

I'm not applying this patch.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ