Hi,
I would like to model a veth pair in YANG, preferrably without proprietary
models.
In Linux, these veth pairs are basically just this:
+--+ +--+
|Socket| |Socket|
+--+ +--+
Dear NETMODers,
I'm on site at the annual EANTC interop-event in Berlin, and came across an
interesting case relating to import and deviations that I'd like the views of
the list on.
According to RFC 7950:
There MUST NOT be any circular chains of imports. For example, if
module "a"
Hi Florian,
Some very quick thoughts on this:
I’m assuming that these Virtual Ethernet interfaces are really only Ethernet
emulations at layer 2 rather than layer 1. I.e., I presume that there is no
configuration for speed, duplex, flow-control, etc? But they would each have
their own a MAC
Could we add this case to the intf-ext work?
We could use this as an example. If a new module is what is desired, I will
support that too.
Regards,
-scott.
From: Rob Wilton (rwilton)
Sent: Tuesday, February 27, 2024 8:55 AM
To: Florian Kauer ; netmod@ietf.org
Cc: Scott Mansfield
Subject:
Yes possibly. Florian would you be interested in helping if we were to do that?
Regards,
Rob
From: Scott Mansfield
Date: Tuesday, 27 February 2024 at 14:16
To: Rob Wilton (rwilton) , Florian Kauer
, netmod@ietf.org
Subject: RE: Modeling of veth pairs
Could we add this case to the intf-ext
Hi Network Modeling WG
In ietf-hardware.yang, /hardware/component/class is configurable. But in
RFC8348, this node is mapped to ENTITY-MIB object entPhysicalClass and
entPhysicalVendorType which are read only.
As my understanding, this node is expected to be set by device vendor. And for
device
Hi,
comments inline.
On 27.02.24 16:11, Rob Wilton (rwilton) wrote:
> Yes possibly. Florian would you be interested in helping if we were to do
> that?
Yes, of course! Let me know how I can help with that.
> *From: *Scott Mansfield
> *Date: *Tuesday, 27 February 2024 at 14:16
> *To: *Rob
