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: <20181206162131.GG18674@lunn.ch>
Date:   Thu, 6 Dec 2018 17:21:31 +0100
From:   Andrew Lunn <andrew@...n.ch>
To:     Joakim Tjernlund <Joakim.Tjernlund@...inera.com>
Cc:     "claudiu.manoil@....com" <claudiu.manoil@....com>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: [PATCH] gianfar: Add gfar_change_carrier()

> > Hi Joakim
> > 
> > Please could you explain the use case for this.
> 
> I have an eth I/F connected to an internal (on board) switch which has an external port to a mgmt network.
> Whenever the external link is broken I want inform linux IP stack that the link is down on the internal eth
> I/F as well. The two interfaces are isolated from the rest of the switch ports using VLANs. 

Hi Jockim

What type of switch is it?

What i would expect is you use a switch driver, and that driver would
allow access to the switches PHYs. When the external port goes down,
the Linux interface for that port would go down. There is no need to
change the carrier on the master interface.

       Andrew

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ