David Wright writes:
> If you look at how the package iwd keeps the kernel's choice of name,
> you'll see it installs:
[...]
Interesting. I can't say I'm convinced by the systemd.link manpage that
this is the correct configuration but let's assume the iwd peeps know
what they're doing. I set
On Fri 02 Sep 2022 at 13:44:24 (+0300), Anssi Saari wrote:
>
> I have an LTE module in my Debian router for failover in case my fiber
> goes down. It has this occasional issue that mostly its interface is
> wwan0 but sometimes it's wwx0a697e2d934f.
>
> When that happens I have something like
Tixy writes:
> The number in the name looks like a MAC address and its value is in the
> 'locally administered' range, i.e. not something baked into the device
> by the manufacturer.
It's an LTE device so it doesn't have a MAC address even though it
presents an ethernet-like interface. Or I
On Fri, 2022-09-02 at 13:44 +0300, Anssi Saari wrote:
> I have an LTE module in my Debian router for failover in case my fiber
> goes down. It has this occasional issue that mostly its interface is
> wwan0 but sometimes it's wwx0a697e2d934f.
>
> When that happens I have something like this in my
On Fri 02 Sep 2022 at 13:44:24 +0300, Anssi Saari wrote:
>
> I have an LTE module in my Debian router for failover in case my fiber
> goes down. It has this occasional issue that mostly its interface is
> wwan0 but sometimes it's wwx0a697e2d934f.
>
> When that happens I have something like this
I have an LTE module in my Debian router for failover in case my fiber
goes down. It has this occasional issue that mostly its interface is
wwan0 but sometimes it's wwx0a697e2d934f.
When that happens I have something like this in my syslog:
Sep 1 08:34:40 animus kernel: [8.150781]
6 matches
Mail list logo
