Hi Mike,
> Mina, do you care about epair, or is the behavior I described sufficient
> for your purposes?
I do deeply care about epair, but for me, ifinfo does the
right thing for me:
root@irc:~ # ifinfo | grep Interface
Interface vnet0 (epair30):
Interface lo0 (lo0):
for one. For the other.
> I have a proof of concept that makes the presumed original name
> (driver name + unit number) available to ifconfig, which prints
> the string with everything else in the standard output format.
> I don't think that is the right solution, but the other details
> should be easy. I'm tempted to
Hi Zhenlei,
> Since it is just for physical devices, may I propose to have the driver name
> in their groups ?
>
> So an if_ure interface ue0 will look like:
>
> ```
> ue0: flags=1008843 metric 0
> mtu 1500
>
> options=60009b
>
> ether 00:e0:4c:xx:xx:xx
> media: Ethernet autoselect
Hi Mike,
> The kernel has a driver name for each interface, which looks like it
> doesn't change currently in most cases. There is a kernel accessor
> function, but I don't think it is exported to user space now. It could
> be, though. Would this be sufficient for your purposes? There is also
> a
Hi Özkan,
> It would be better if FreeBSD could have "interface altname feature"
> like Linux has.
even tho I'm writing this email from a Linux laptop, and often
have to understand Linux specific code to see how I can (or if I
need to) replicate that on FreeBSD, I'm not familiar enough
with
> > FreeBSD currently does not preserve the old ( original ) name of
> > interfaces if it is renamed ( either physical or cloned ones ).
> > While there's an attempt https://reviews.freebsd.org/D28247
> > to get the device name (physical
> > ones) but it is not perfect and not completed.
> >
>
sily accessible from Python,
and which we already use to figure out the uptime (or rather, the boottime):
https://github.com/canonical/cloud-init/blob/5496745b394f9b7b9eaf57fd619330d484ce2da8/cloudinit/util.py#L2073-L2105
Looking forward to reading your ideas.
Kind regards,
Mina Galić
> On 4/18/23 11:44, Mina Galić wrote:
>
> > Hi HPS,
> >
> > i don't see those sysctl entries for regular devices?
> > is this infiniband specific?
> > or is there anything I need to enable to get these sysctls?
> >
> > Kind regards,
>
&
Hi HPS,
i don't see those sysctl entries for regular devices?
is this infiniband specific?
or is there anything I need to enable to get these sysctls?
Kind regards,
Mina
Original Message
On 18 Apr 2023, 10:32, Hans Petter Selasky wrote:
> Hi, All the `/sys/class/net//*`
and, speaking of ifconfig limitations…
…why is it so hard to tell what if a device has been renamed?
and what its original name was?
at least we have this Diff trying to reconcile some of that…
https://reviews.freebsd.org/D28247
Kind regards,
Mina
?
Kind regards,
Mina Galić
Don't Try *my* PkgBase Repository: https://alpha.pkgbase.live/ — until i have a
new hardware sponsor…
11 matches
Mail list logo
