-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I don't know what to say. I rebooted the box, yet again, last evening. This
morning, I tried yesterday's last suggestion (a big grep of dmesg), and there
was no mention of wwan0 or eth1. I ran the others too (dmesg (with several
greps), ifconfi
On Mon, 15 Mar 2021 at 08:41, ghe2001 wrote:
> On Saturday, March 13, 2021 2:25 PM, Andrei POPESCU
> wrote:
>
> > Well, you could try grepping for 'eth' and 'wwan' ;)
> >
> > Some context might help as well (as in '-C 5' or so).
>
> Bingo:
There might be a bit more useful info to be seen with:
On Sun 14 Mar 2021 at 21:41:11 (+), ghe2001 wrote:
> ‐‐‐ Original Message ‐‐‐
> On Saturday, March 13, 2021 2:25 PM, Andrei POPESCU
> wrote:
>
> > Well, you could try grepping for 'eth' and 'wwan' ;)
> >
> > Some context might help as well (as in '-C 5' or so).
>
> Bingo:
>
> root@
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
‐‐‐ Original Message ‐‐‐
On Saturday, March 13, 2021 2:25 PM, Andrei POPESCU
wrote:
> Well, you could try grepping for 'eth' and 'wwan' ;)
>
> Some context might help as well (as in '-C 5' or so).
Bingo:
root@gobook3:~# dmesg | egrep
On Sb, 13 mar 21, 18:13:12, ghe2001 wrote:
>
>
> ‐‐‐ Original Message ‐‐‐
> On Saturday, March 13, 2021 12:58 AM, Andrei POPESCU
> wrote:
>
> > These look like real hardware to me.
>
> They do to me too. Sometimes. But they're a bit suspect in places.
> >
> > Anything interesting in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
‐‐‐ Original Message ‐‐‐
On Saturday, March 13, 2021 12:58 AM, Andrei POPESCU
wrote:
> These look like real hardware to me.
They do to me too. Sometimes. But they're a bit suspect in places.
>
> Anything interesting in the output of '
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
‐‐‐ Original Message ‐‐‐
On Friday, March 12, 2021 8:42 PM, David wrote:
> Another possibility to check/eliminate: are there any additional
> configuration files in the /etc/network/interfaces.d directory?
Nope. Empty. Thanks for the
On Sb, 13 mar 21, 01:35:35, ghe2001 wrote:
>
> 3: eth1: mtu 1500 qdisc noop state DOWN group
> default qlen 1000
> link/ether 10:05:01:49:64:9d brd ff:ff:ff:ff:ff:ff
> 4: wwan0: mtu 1500 qdisc noop state DOWN group
> default qlen 1000
> link/ether 92:3c:c5:6c:84:27 brd ff:ff:ff:ff:ff:f
On Sat, 13 Mar 2021 at 10:00, ghe2001 wrote:
> Buster, Dell laptop
> I've got what might be two ghost interfaces, and I think I'd like to get rid
> of them.
> I use /etc/network/interfaces to configure interfaces.
Another possibility to check/eliminate: are there any additional
configuration
On Fri 12 Mar 2021 at 21:14:34 (-0500), The Wanderer wrote:
> On 2021-03-12 at 21:05, David wrote:
>
> > So I guess the answer is either in the kernel, or systemd,
> > but I don't know, and I found no further clues about that in
> > either the Arch Linux wiki [1] or the Debian Reference [2]
> > or
On 2021-03-12 at 21:05, David wrote:
> So I guess the answer is either in the kernel, or systemd,
> but I don't know, and I found no further clues about that in
> either the Arch Linux wiki [1] or the Debian Reference [2]
> or the Debian wiki [3].
>
> So I will stay silent now and wait for someon
On Sat, 13 Mar 2021 at 12:35, ghe2001 wrote:
> > 1. Look or grep to see if there's anything relevant under /etc/udev/rules.d
>
> root@gobook3:~# ls /etc/udev/rules.d/
> root@gobook3:~#
>
> Hmm. Kinda looks like nothing's there. If that's true,
> I may have problems a lot worse than a couple mis
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
‐‐‐ Original Message ‐‐‐
On Friday, March 12, 2021 5:41 PM, David wrote:
> Hi, other people here know far more about networks than I do, but here's some
> starting suggestions:
>
> 1. Look or grep to see if there's anything relevant unde
On Sat, 13 Mar 2021 at 10:00, ghe2001 wrote:
> Buster, Dell laptop
> I've got what might be two ghost interfaces, and I think I'd like to get rid
> of them.
Hi, other people here know far more about networks than I do, but here's some
starting suggestions:
1) Look or grep to see if there's an
14 matches
Mail list logo
