On 21 Nov 2023, at 0:43, Franco Fichtner wrote:
>> On 20. Nov 2023, at 23:06, Mike Karels <m...@karels.net> 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 problems with
>> epair. Maybe that isn't an issue for this purpose.
>
> Two things to consider:
>
> Does epair do it the "right way"? And does it even matter given that this
> behaviour hasn't had any exposure and is likely ever going to be used
> as input for another tool?
epair arguably does it wrong; it doesn't follow the convention of using the
driver name followed by an integer. However, what it does is practical, and
clearly we don't want to change it now. Using the driver name as returned
by ifconfig_get_orig_addr displays "epair0" for two interfaces. If they have
been renamed, the new names will hopefully be suggestive of which is which.
Mina, do you care about epair, or is the behavior I described sufficient
for your purposes?
Mike
> I mean it still tracks the origin in the driver. This way you can even find
> the epair belonging together. It looks like it should given the design
> choices.
>
>
> Cheers,
> Franco
