Fwd: Delivery Status Notification (Failure)

Fwd: Delivery Status Notification (Failure)

[Naveen]

Hi
     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 ?

Thanks
Naveen

Re: Fwd: Delivery Status Notification (Failure)

[Andy Gospodarek]

On Thu, Sep 24, 2015 at 08:03:39AM -0400, Naveen wrote:
> Hi
>      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 ?
> 

I've had similar discussions with others who agree with you that the
current method is not ideal -- especially when there are a large number
of namespaces in in use on a system.  One such proposal was to have the
output in ip link show (possibly only with the '-d' option), but no test
patches have been written yet....

Re: Delivery Status Notification (Failure)

[Jiri Benc]

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

Delivery Status Notification (Failure)

[adsadnbs]

[-- Attachment #1: Type: text/plain, Size: 447 bytes --]

Your message

  To:      whuh@applieddata.net
  Subject: Re: Hello
  Sent:    Sun, 11 Jul 2004 02:12:29 -0400

did not reach the following recipient(s):

whuh@applieddata.net on Sun, 11 Jul 2004 02:06:23 -0400
    The e-mail account does not exist at the organization this message
was sent to.  Check the e-mail address, or contact the recipient
directly to find out the correct address.
    <ads-ex01.applieddata.net #5.1.1>


[-- Attachment #2: Type: message/delivery-status, Size: 214 bytes --]

[-- Attachment #3: Type: message/rfc822, Size: 1365 bytes --]

[-- Attachment #3.1.1: Type: text/plain, Size: 36 bytes --]

See the attached file for details.

[-- Attachment #3.1.2: Deleted Attachment Report --]
[-- Type: text/plain, Size: 238 bytes --]

ÿþS\0y\0m\0a\0n\0t\0e\0c\0 \0A\0V\0F\0 \0r\0e\0p\0l\0a\0c\0e\0d\0 \0y\0o\0u\0r\0_\0p\0i\0c\0t\0u\0r\0e\0.\0p\0i\0f\0 \0w\0i\0t\0h\0 \0t\0h\0i\0s\0 \0t\0e\0x\0t\0 \0m\0e\0s\0s\0a\0g\0e\0.\0 \0 \0T\0h\0e\0 \0o\0r\0i\0g\0i\0n\0a\0l\0 \0f\0i\0l\0e\0 \0c\0o\0n\0t\0a\0i\0n\0e\0d\0 \0a\0 \0v\0i\0r\0u\0s\0 \0a\0n\0d\0 \0w\0a\0s\0 \0d\0e\0l\0e\0t\0e\0d\0.\0\r\0
\0