netdev - Re: Delivery Status Notification (Failure)

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] [day] [month] [year] [list]

Message-ID: <20150924150906.067bba62@griffin>
Date:	Thu, 24 Sep 2015 15:09:06 +0200
From:	Jiri Benc <jbenc@...hat.com>
To:	Naveen <dear.chap@...il.com>
Cc:	netdev@...r.kernel.org
Subject: Re: Delivery Status Notification (Failure)

On Thu, 24 Sep 2015 08:03:39 -0400, Naveen wrote:
>      Right now the only way to detect if an interface has a peer(veth)
> is touse ethtool -S. Instead I was thinking of adding it to device
> attributes as a peer_ifndex entry. In drivers/net/veth.c I could add
> an entry to
> dev->groups for a veth specific group. Would that be acceptable ?

Recent kernels announce the peer in IFLA_LINK, including its netnsid
(thus it's finally possible to track peers across net namespaces).
Just try "ip a" with a recent kernel.

 Jiri

-- 
Jiri Benc
--
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