https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275228
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|j...@freebsd.org
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275251
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
--
You are receiv
Mike Karels wrote:
> Here, interface-name was a placeholder for the current name of the
> interface. My newer code prints "drivername: igb1" at the end of
> the list of values for "ifconfig $interface-name" or "ifconfig -a"
> if the -D option is given. I decided that it was better to be able
>
On 21 Nov 2023, at 19:35, Jamie Landeg-Jones wrote:
> Mike Karels wrote:
>
>> 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
Kristof Provost wrote:
>
> I believe a similar solution has been proposed before, and it failed to cope
> with things like epair interfaces.
>
> I’d look in the direction of just adding a field to struct ifnet with the
> original interface name (likely easily done in if_attach()), along with a n
Mike Karels wrote:
> 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 eas
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275225
--- Comment #2 from Reid Linnemann ---
Correction to my previous comment - both believe that have the lowest advskew,
not advbase
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275225
Reid Linnemann changed:
What|Removed |Added
CC||linnema...@gmail.com
--- Comment
On 21 Nov 2023, at 12:16, Mina Galić wrote:
> 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
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. Fo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275225
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
--
You are receiv
On 21 Nov 2023, at 0:43, Franco Fichtner wrote:
>> On 20. Nov 2023, at 23:06, Mike Karels wrote:
>>
>> On 20 Nov 2023, at 15:16, Franco Fichtner wrote:
>>
>>> All that is really missing is a way to print it via ifconfig command.
>>
>> That is trivial to add; I just tested it. It also has problem
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275228
Michael Osipov changed:
What|Removed |Added
CC||dte...@freebsd.org,
> On 21. Nov 2023, at 10:51, Ronald Klop wrote:
>
> Interesting.
>
> Is this: /usr/src/tools/tools/ifinfo ?
Yes.
Interesting.
Is this: /usr/src/tools/tools/ifinfo ?
Regards,
Ronald.
Van: Franco Fichtner
Datum: maandag, 20 november 2023 22:23
Aan: Kristof Provost
CC: Mike Karels , "Mina Galic" , Zhenlei Huang
, Kyle Evans , freebsd-net@freebsd.org
Onderwerp: Re: How to tell if a network interface was re
15 matches
Mail list logo
