Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
non-existing interface problem
101 views
Skip to first unread message
ghe2001
Mar 12, 2021, 6:10:05 PM3/12/21
to
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
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. I have eth0 and eth0:1 static, and wlan0 DHCP interfaces in the interfaces file. Everything works properly. The box is on two nets and acts as I expect it to.
ifconfig shows eth1 and wwan0 (yes wwan0, not wlan<n>) as existing, but down, interfaces. It claims eth1 has an Ethernet address (10:05:01:49:64:9d) -- similar to eth0's (10:05:01:40:f4:43). Neither eth1 or wwan0 exist, as far as I know. They aren't mentioned in my interfaces file, and there's just one Ethernet hole on the computer. On the outside, anyway. Webmin shown them in its list of existing interfaces, but they're greyed out and I can't access them (Webmin also says they're down).
root@gobook3:/# ifconfig eth1 up
doesn't complain, but afterward, it says it's not up:
root@gobook3:/# ifconfig eth1
eth1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 10:05:01:49:64:9d txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
ifconfig assigns eth1 an address if asked to:
root@gobook3:/# ifconfig eth1 42.42.42.42
root@gobook3:/# ifconfig eth1
eth1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 42.42.42.42 netmask 255.0.0.0 broadcast 42.255.255.255
...
And Webmin shows eth1 with the IP and up. And it's accessible now.
But ifup:
root@gobook3:/# ifup eth1
ifup: unknown interface eth1
They don't really seem to hurt anything because they're never expected to be active (and they certainly aren't), but I'd like to get rid of them. They're a little sloppy in my configs, and they might bite me in the ass someday.
I've looked for several things on the web, and grepped for wwan on the disk to no avail. This confusion doesn't exist on the Supermicro desktop.
Any help or suggestions would be appreciated. Or maybe just an explanation of what's going on so I can quit worrying about it.
--
Glenn English
-----BEGIN PGP SIGNATURE-----
Version: ProtonMail
wsBzBAEBCAAGBQJgS+5bACEJEObKK1bRaqt3FiEExEbtoeXBeE9fruv35sor
VtFqq3eS5ggAgdwJPgPrDZYYrcTgFLG40nH4NsVDeropIJIf7zdvwoBSZfVI
rJ4tmrvha8fgs+SNeztId3P3ab91wxIUgP2nANGQrs8aH4kABKXlNU2pcNFs
lnxYs33C+Lkm53MJyeaJW8l3JHkOIHSt2RTg+vaItTRAcRqM1eCq3FAEcfnP
oXWBtD0JmN5NcJV1Qrw8yZi11hYMYUF1K6RBYk9AEyXvTe00y+VS1qWPYSZ/
BgNyKNIn1SLrnr3YEYjZBhkz8fqEC0H8hvoV3pVtQZvm3Gsu9xuWD5pR0V4o
RiKRpPOI3en5Gft+zPD5gc9YCurxpwRx3/tyxWnbKCKASfdYXhMyKw==
=5St2
-----END PGP SIGNATURE-----
Hash: SHA256
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. I have eth0 and eth0:1 static, and wlan0 DHCP interfaces in the interfaces file. Everything works properly. The box is on two nets and acts as I expect it to.
ifconfig shows eth1 and wwan0 (yes wwan0, not wlan<n>) as existing, but down, interfaces. It claims eth1 has an Ethernet address (10:05:01:49:64:9d) -- similar to eth0's (10:05:01:40:f4:43). Neither eth1 or wwan0 exist, as far as I know. They aren't mentioned in my interfaces file, and there's just one Ethernet hole on the computer. On the outside, anyway. Webmin shown them in its list of existing interfaces, but they're greyed out and I can't access them (Webmin also says they're down).
root@gobook3:/# ifconfig eth1 up
doesn't complain, but afterward, it says it's not up:
root@gobook3:/# ifconfig eth1
eth1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 10:05:01:49:64:9d txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
ifconfig assigns eth1 an address if asked to:
root@gobook3:/# ifconfig eth1 42.42.42.42
root@gobook3:/# ifconfig eth1
eth1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 42.42.42.42 netmask 255.0.0.0 broadcast 42.255.255.255
...
And Webmin shows eth1 with the IP and up. And it's accessible now.
But ifup:
root@gobook3:/# ifup eth1
ifup: unknown interface eth1
They don't really seem to hurt anything because they're never expected to be active (and they certainly aren't), but I'd like to get rid of them. They're a little sloppy in my configs, and they might bite me in the ass someday.
I've looked for several things on the web, and grepped for wwan on the disk to no avail. This confusion doesn't exist on the Supermicro desktop.
Any help or suggestions would be appreciated. Or maybe just an explanation of what's going on so I can quit worrying about it.
--
Glenn English
-----BEGIN PGP SIGNATURE-----
Version: ProtonMail
wsBzBAEBCAAGBQJgS+5bACEJEObKK1bRaqt3FiEExEbtoeXBeE9fruv35sor
VtFqq3eS5ggAgdwJPgPrDZYYrcTgFLG40nH4NsVDeropIJIf7zdvwoBSZfVI
rJ4tmrvha8fgs+SNeztId3P3ab91wxIUgP2nANGQrs8aH4kABKXlNU2pcNFs
lnxYs33C+Lkm53MJyeaJW8l3JHkOIHSt2RTg+vaItTRAcRqM1eCq3FAEcfnP
oXWBtD0JmN5NcJV1Qrw8yZi11hYMYUF1K6RBYk9AEyXvTe00y+VS1qWPYSZ/
BgNyKNIn1SLrnr3YEYjZBhkz8fqEC0H8hvoV3pVtQZvm3Gsu9xuWD5pR0V4o
RiKRpPOI3en5Gft+zPD5gc9YCurxpwRx3/tyxWnbKCKASfdYXhMyKw==
=5St2
-----END PGP SIGNATURE-----
David
Mar 12, 2021, 7:50:04 PM3/12/21
to
On Sat, 13 Mar 2021 at 10:00, ghe2001 <ghe...@pm.me> 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
> Buster, Dell laptop
> I've got what might be two ghost interfaces, and I think I'd like to get rid of them.
starting suggestions:
1) Look or grep to see if there's anything relevant under /etc/udev/rules.d
2) Can you show the output of 'ip a' (ifconfig is deprecated)
3) webmin probably isn't helping
ghe2001
Mar 12, 2021, 8:40:04 PM3/12/21
to
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
Hash: SHA256
On Friday, March 12, 2021 5:41 PM, David <bounci...@gmail.com> 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 under /etc/udev/rules.d
> Hi, other people here know far more about networks than I do, but here's some
> starting suggestions:
>
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 misbehaving interfaces.
> 2. Can you show the output of 'ip a'
root@sbox:~# ssh gb ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 10:05:01:40:f4:43 brd ff:ff:ff:ff:ff:ff
inet 216.17.134.203/24 brd 216.17.134.255 scope global eth0
valid_lft forever preferred_lft forever
inet 10.200.184.3/24 brd 10.200.184.255 scope global eth0:1
valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST> 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: <BROADCAST,MULTICAST,NOARP> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 92:3c:c5:6c:84:27 brd ff:ff:ff:ff:ff:ff
5: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether f4:8c:50:17:bc:0e brd ff:ff:ff:ff:ff:ff
(I rebooted the machine, so the IP that ifconfig put on eth1 isn't there.)
> (ifconfig is deprecated)
I know it is, but it's still available, it works, and I know how to use it. And it (pretty much) does one thing, and does it (reasonably) well.
> 3. webmin probably isn't helping
It's not the first thing to go to, but it backs up a lot of what the CLI software says.
--
Glenn English
-----BEGIN PGP SIGNATURE-----
Version: ProtonMail
MYKsjDJ7NAgAsW1Ad7M/jOIadq4k+LLou/A6IDkeRwrslHTE/abQe2Idy4fG
fEUBKagK3+Gbqwh9ut33u6SUuLg79UIbVMrOV4zJ20BKOaKWKcUM3rsdTZ55
iRlZyhM/JIlkhoIMBnp8ENpsptL6A9OVNC5dIk49k9v7ZnF106x8xV5XAUM1
3tQKKKUYlA8O5VWDNjZU/VTM1arvxhxsPU3/phGrny2mP3Ms19xeuujo52JI
VRZXsRGhRZSfrh11mYG8vamlTJhfQV8EFhmYH60TLkcYWRTDcMi5ipgh2O5I
+aYydKpvxVOT49k4Y6m1fgY4ENmNwGI7YS4aw+eSEKBzcSETP4rGlQ==
=BxOA
-----END PGP SIGNATURE-----
David
Mar 12, 2021, 9:10:04 PM3/12/21
to
On Sat, 13 Mar 2021 at 12:35, ghe2001 <ghe...@protonmail.com> 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 misbehaving interfaces.
I have 2 machines here running Debian 10.8, they're both empty
> > 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 misbehaving interfaces.
like yours, so I don't think that's any problem.
I remember that udev used to manage interface names, but it seems that
it is not involved here, so we eliminated that possibility.
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 someone who knows more
to answer :)
[1] https://wiki.archlinux.org/index.php/Network_manager
[2] https://www.debian.org/doc/manuals/debian-reference/ch05.en.html
[3] https://wiki.debian.org/NetworkConfiguration
The Wanderer
Mar 12, 2021, 9:20:04 PM3/12/21
to
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 someone who knows more
> to answer :)
>
> [1] https://wiki.archlinux.org/index.php/Network_manager
> [2] https://www.debian.org/doc/manuals/debian-reference/ch05.en.html
> [3] https://wiki.debian.org/NetworkConfiguration
I wouldn't say that I particularly know more; in fact I may know less.
> 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 someone who knows more
> to answer :)
>
> [1] https://wiki.archlinux.org/index.php/Network_manager
> [2] https://www.debian.org/doc/manuals/debian-reference/ch05.en.html
> [3] https://wiki.debian.org/NetworkConfiguration
However, if I were encountering such symptoms and had (as has apparently
happened here) searched the system for mention of the key term 'wwan'
without finding it, the next places I'd look for clues would be A: dmesg
and B: the contents of /var/log/. (If running systemd, I'd probably also
want to investigate the contents of the journal, but I don't know proper
syntax for that beyond the name 'journalctl'.)
It might be necessary to make sure you're booting with appropriate
message verbosity; IIRC, systemd may default to a quieter boot than
sysvinit does, so you may have to adjust some grub parameters and
reboot. In principle, however, I'd expect that if such devices are being
set up at boot time there'd have to be some details about that logged
during the boot process, and such logging would have to go to one or
more of those three places.
--
The Wanderer
The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw
David Wright
Mar 12, 2021, 9:30:04 PM3/12/21
to
Googling linux kernel wwan device throws up
https://lore.kernel.org/netdev/20200225105149.59963c95aa29.Id0e40565452d0d5bb9ce5cc00b8755ec96db8559@changeid/
which suggests a mobilephone-type device.
BTW /etc/udev/rules.d will only be populated if you put your own stuff
there (like I do); it belongs to the sysadmin. The system uses /lib
and /run.
Cheers,
David.
David
Mar 12, 2021, 10:50:04 PM3/12/21
to
> 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
> 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.
configuration files in the /etc/network/interfaces.d directory?
Andrei POPESCU
Mar 13, 2021, 3:00:05 AM3/13/21
to
On Sb, 13 mar 21, 01:35:35, ghe2001 wrote:
>
> 3: eth1: <BROADCAST,MULTICAST> 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: <BROADCAST,MULTICAST,NOARP> mtu 1500 qdisc noop state DOWN group default qlen 1000
> link/ether 92:3c:c5:6c:84:27 brd ff:ff:ff:ff:ff:ff
These look like real hardware to me.
>
> 3: eth1: <BROADCAST,MULTICAST> 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: <BROADCAST,MULTICAST,NOARP> mtu 1500 qdisc noop state DOWN group default qlen 1000
> link/ether 92:3c:c5:6c:84:27 brd ff:ff:ff:ff:ff:ff
Anything interesting in the output of 'lspci -nn', 'lsusb' and 'dmesg'?
Kind regards,
Andrei
--
http://wiki.debian.org/FAQsFromDebianUser
ghe2001
Mar 13, 2021, 1:00:05 PM3/13/21
to
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
Hash: SHA256
On Friday, March 12, 2021 8:42 PM, David <bounci...@gmail.com> wrote:
> Another possibility to check/eliminate: are there any additional
> configuration files in the /etc/network/interfaces.d directory?
Nope. Empty. Thanks for the thought.
> Another possibility to check/eliminate: are there any additional
> configuration files in the /etc/network/interfaces.d directory?
--
Glenn English
-----BEGIN PGP SIGNATURE-----
Version: ProtonMail
MYKsjDJbRgf9Gn3lUVcFLIlx5ji/UUr6jJBlqpmB3+S5+rXbSQJ8c+nUd9mo
1TugbcZc5YPexmSEdvpzQTvnGnSq/WK5oM41d2yegK2Pn/XjnAZQR6ahdG/b
357roFC5zXyxRVGRzmCs+E15ruD9X10bHmXErm9b3Q6xC5pj34GHRbssJt4J
qTYbMRYMfBIR1aEdvSGw1JrKnc+cg665fNJEQfeHcSw3HhSXjHsHusoN38xw
303oh7qPTebYXcUZzGpbqPjlj9FQDBdLTdFOrWoMGS+oJ9xzzHDCnE94IFYJ
2SWhuu/iB/5Q19t9CCUJH9DGbP6ssHWLVZ4PqzE4AIe3o5n2wnZ+Lw==
=7vT6
-----END PGP SIGNATURE-----
ghe2001
Mar 13, 2021, 1:20:04 PM3/13/21
to
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
Hash: SHA256
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Saturday, March 13, 2021 12:58 AM, Andrei POPESCU <andreim...@gmail.com> wrote:
> These look like real hardware to me.
They do to me too. Sometimes. But they're a bit suspect in places.
> These look like real hardware to me.
>
> Anything interesting in the output of 'lspci -nn', 'lsusb' and 'dmesg'?
lines from lspci -nn:
> Anything interesting in the output of 'lspci -nn', 'lsusb' and 'dmesg'?
00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection I219-LM [8086:156f] (rev 21)
01:00.0 Network controller [0280]: Intel Corporation Wireless 8260 [8086:24f3] (rev 3a)
Only one of each, but they could be chips with 2 ports -- nope Intel's web says on it says there's just one port on the Ethernet chip.
There's nothing I can make much sense of from lsub. Nothing labeled Network or Wireless or Ethernet. there's one line that might be relevant:
Bus 001 Device 006: ID 8087:0a2b Intel Corp.
dmesg (grepped a little -- did I ask for the wrong things?):
root@gobook3:~# dmesg | egrep -i network
[ 1.694000] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
[ 1.874625] e1000e 0000:00:1f.6 eth0: Intel(R) PRO/1000 Network Connection
root@gobook3:~# dmesg | egrep -i ethernet
[ 5.380441] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
root@gobook3:~# dmesg | egrep -i wireless
[ 2.747290] usb 1-2: Product: Dell Wireless 5808e Gobi™ 4G LTE Mobile Broadband Card
[ 2.747292] usb 1-2: Manufacturer: Sierra Wireless, Incorporated
[ 4.571427] input: DELL Wireless hotkeys as /devices/virtual/input/input12
[ 4.832877] Intel(R) Wireless WiFi driver for Linux
[ 5.042981] iwlwifi 0000:01:00.0: Detected Intel(R) Dual Band Wireless AC 8260, REV=0x208
--
Glenn English
-----BEGIN PGP SIGNATURE-----
Version: ProtonMail
MYKsjDLLcAgAkbRnd2pz9Bx4KYdNxn8D2f/bUigpZOVgGjZB4Hd5r+Bznsoc
YVtzXzZNcpP6UAbSvt30/MfPxOAy2vbKGgENKPors7r0VfD+t46BWDQrnXrY
1VD/+ZEsUDrZBv2FOo0z+OgPf2ilgkrKJJpDEBbxp9q0Qy5GHvtJrs6vicRL
vQNmots4Jr+oJdHxgYKB1Kc6Wkq89YhpzjkxI5yjTnAqCLvYrAqU2EoSpWKr
rkxWmniiFFUFagANT/v5J9Z6d3hSNbRmjag4mEqzSZjE/9ISdPIwzGpi3IYo
H/BawC11BXNqgT7H/jOp+ogn8Sct6D+7ZUVSy/iHv5xscFu+DMmOGg==
=RFmi
-----END PGP SIGNATURE-----
Andrei POPESCU
Mar 13, 2021, 4:30:05 PM3/13/21
to
On Sb, 13 mar 21, 18:13:12, ghe2001 wrote:
>
>
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Saturday, March 13, 2021 12:58 AM, Andrei POPESCU <andreim...@gmail.com> 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 'lspci -nn', 'lsusb' and 'dmesg'?
>
> lines from lspci -nn:
>
> 00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection I219-LM [8086:156f] (rev 21)
> 01:00.0 Network controller [0280]: Intel Corporation Wireless 8260 [8086:24f3] (rev 3a)
>
> Only one of each, but they could be chips with 2 ports -- nope Intel's web says on it says there's just one port on the Ethernet chip.
>
> There's nothing I can make much sense of from lsub. Nothing labeled Network or Wireless or Ethernet. there's one line that might be relevant:
>
> Bus 001 Device 006: ID 8087:0a2b Intel Corp.
>
> dmesg (grepped a little -- did I ask for the wrong things?):
>
> root@gobook3:~# dmesg | egrep -i network
Well, you could try grepping for 'eth' and 'wwan' ;)
>
>
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Saturday, March 13, 2021 12:58 AM, Andrei POPESCU <andreim...@gmail.com> 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 'lspci -nn', 'lsusb' and 'dmesg'?
>
> lines from lspci -nn:
>
> 00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection I219-LM [8086:156f] (rev 21)
> 01:00.0 Network controller [0280]: Intel Corporation Wireless 8260 [8086:24f3] (rev 3a)
>
> Only one of each, but they could be chips with 2 ports -- nope Intel's web says on it says there's just one port on the Ethernet chip.
>
> There's nothing I can make much sense of from lsub. Nothing labeled Network or Wireless or Ethernet. there's one line that might be relevant:
>
> Bus 001 Device 006: ID 8087:0a2b Intel Corp.
>
> dmesg (grepped a little -- did I ask for the wrong things?):
>
> root@gobook3:~# dmesg | egrep -i network
Some context might help as well (as in '-C 5' or so).
ghe2001
Mar 14, 2021, 5:50:05 PM3/14/21
to
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
Hash: SHA256
On Saturday, March 13, 2021 2:25 PM, Andrei POPESCU <andreim...@gmail.com> wrote:
> Well, you could try grepping for 'eth' and 'wwan' ;)
>
> Some context might help as well (as in '-C 5' or so).
Bingo:
> Well, you could try grepping for 'eth' and 'wwan' ;)
>
> Some context might help as well (as in '-C 5' or so).
root@gobook3:~# dmesg | egrep -i wwan
[ 5.089737] cdc_mbim 1-2:1.12 wwan0: register 'cdc_mbim' at usb-0000:00:14.0-2, CDC MBIM, 8e:2c:c2:16:4d:2f
root@gobook3:~# dmesg | egrep -i eth
[ 1.685235] wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found
[ 1.687781] ACPI Error: Method parse/execution failed \_TZ.TZ00._TMP, AE_NOT_FOUND (20180810/psparse-516)
[ 1.688172] ACPI Error: Method parse/execution failed \_TZ.TZ00._TMP, AE_NOT_FOUND (20180810/psparse-516)
[ 1.688494] ACPI Error: Method parse/execution failed \_TZ.TZ01._TMP, AE_NOT_FOUND (20180810/psparse-516)
[ 1.688806] ACPI Error: Method parse/execution failed \_TZ.TZ01._TMP, AE_NOT_FOUND (20180810/psparse-516)
[ 1.874623] e1000e 0000:00:1f.6 eth0: (PCI Express:2.5GT/s:Width x1) 10:05:01:40:f4:43
[ 1.874625] e1000e 0000:00:1f.6 eth0: Intel(R) PRO/1000 Network Connection
[ 1.874682] e1000e 0000:00:1f.6 eth0: MAC: 12, PHY: 12, PBA No: FFFFFF-0FF
[ 4.692597] usbcore: registered new interface driver cdc_ether
[ 4.939278] r8152 1-1.2:1.0 eth1: v1.09.9
[ 5.380441] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 28.519062] e1000e 0000:00:1f.6 eth0: 10/100 speed: disabling TSO
Thank you, Andrei. But I'm afraid this means next to nothing to me. Other than that Control Data seems to be in the Wireless Wide Area Network business :-)
Education anyone?
--
Glenn English
-----BEGIN PGP SIGNATURE-----
Version: ProtonMail
MYKsjDLuDwf+L2w0bFbnNkmF/2qYc+iK4pHrSTXE4vjL6LYly0If4wp8KrDh
tbgrjp/nbhJWFJwdaAAP7RgoRGV/VDbEH0dVWvo0RrZ19oI/Arz1HE7sJz2e
Aa7VWgvMWMgGjGWhzRoFeSRr0z51SRoHA6gjVn06kp4tYklwZ6/PCIJQsUNr
7YgbFF2OmV3RgEwpEQURvujdpJQ6DVZSSJj88iYDaUiuqbUAXNseOx0thVkw
NTqVlwnzM+QukXfx04WHkY5Z8NB2KKJPktlDijxseF9UEgOvTeREgK9XhqpQ
TCidc2cFKtmvhn3HNlFrOBCRZ45jdaBwzeRx5cMIBF32VGeAWPmBQg==
=mPJB
-----END PGP SIGNATURE-----
David Wright
Mar 14, 2021, 6:10:04 PM3/14/21
to
On Sun 14 Mar 2021 at 21:41:11 (+0000), ghe2001 wrote:
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Saturday, March 13, 2021 2:25 PM, Andrei POPESCU <andreim...@gmail.com> 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 -i wwan
> [ 5.089737] cdc_mbim 1-2:1.12 wwan0: register 'cdc_mbim' at usb-0000:00:14.0-2, CDC MBIM, 8e:2c:c2:16:4d:2f
> root@gobook3:~# dmesg | egrep -i eth
> [ 1.685235] wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found
> [ 1.687781] ACPI Error: Method parse/execution failed \_TZ.TZ00._TMP, AE_NOT_FOUND (20180810/psparse-516)
> [ 1.688172] ACPI Error: Method parse/execution failed \_TZ.TZ00._TMP, AE_NOT_FOUND (20180810/psparse-516)
> [ 1.688494] ACPI Error: Method parse/execution failed \_TZ.TZ01._TMP, AE_NOT_FOUND (20180810/psparse-516)
> [ 1.688806] ACPI Error: Method parse/execution failed \_TZ.TZ01._TMP, AE_NOT_FOUND (20180810/psparse-516)
> [ 1.874623] e1000e 0000:00:1f.6 eth0: (PCI Express:2.5GT/s:Width x1) 10:05:01:40:f4:43
> [ 1.874625] e1000e 0000:00:1f.6 eth0: Intel(R) PRO/1000 Network Connection
> [ 1.874682] e1000e 0000:00:1f.6 eth0: MAC: 12, PHY: 12, PBA No: FFFFFF-0FF
> [ 4.692597] usbcore: registered new interface driver cdc_ether
>
> [ 4.939278] r8152 1-1.2:1.0 eth1: v1.09.9
>
> [ 5.380441] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
> [ 28.519055] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
> [ 28.519062] e1000e 0000:00:1f.6 eth0: 10/100 speed: disabling TSO
>
> Thank you, Andrei. But I'm afraid this means next to nothing to me. Other than that Control Data seems to be in the Wireless Wide Area Network business :-)
>
> Education anyone?
As I said, I reckon it's a mobilephone-type device. Anyway, I googled
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Saturday, March 13, 2021 2:25 PM, Andrei POPESCU <andreim...@gmail.com> 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 -i wwan
> [ 5.089737] cdc_mbim 1-2:1.12 wwan0: register 'cdc_mbim' at usb-0000:00:14.0-2, CDC MBIM, 8e:2c:c2:16:4d:2f
> root@gobook3:~# dmesg | egrep -i eth
> [ 1.685235] wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found
> [ 1.687781] ACPI Error: Method parse/execution failed \_TZ.TZ00._TMP, AE_NOT_FOUND (20180810/psparse-516)
> [ 1.688172] ACPI Error: Method parse/execution failed \_TZ.TZ00._TMP, AE_NOT_FOUND (20180810/psparse-516)
> [ 1.688494] ACPI Error: Method parse/execution failed \_TZ.TZ01._TMP, AE_NOT_FOUND (20180810/psparse-516)
> [ 1.688806] ACPI Error: Method parse/execution failed \_TZ.TZ01._TMP, AE_NOT_FOUND (20180810/psparse-516)
> [ 1.874623] e1000e 0000:00:1f.6 eth0: (PCI Express:2.5GT/s:Width x1) 10:05:01:40:f4:43
> [ 1.874625] e1000e 0000:00:1f.6 eth0: Intel(R) PRO/1000 Network Connection
> [ 1.874682] e1000e 0000:00:1f.6 eth0: MAC: 12, PHY: 12, PBA No: FFFFFF-0FF
> [ 4.692597] usbcore: registered new interface driver cdc_ether
>
> [ 4.939278] r8152 1-1.2:1.0 eth1: v1.09.9
>
> [ 5.380441] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
> [ 28.519055] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
> [ 28.519062] e1000e 0000:00:1f.6 eth0: 10/100 speed: disabling TSO
>
> Thank you, Andrei. But I'm afraid this means next to nothing to me. Other than that Control Data seems to be in the Wireless Wide Area Network business :-)
>
> Education anyone?
r8152 wwan (from your output) which hits
https://android.googlesource.com/kernel/common.git/+/bcmdhd-3.10/drivers/net/usb/Kconfig
on which r8152 tells you about Realtek RTL8152 Based USB 2.0 Ethernet Adapters
and wwan tells you about Sierra Wireless USB-to-WWAN device.
Sierra wwan then gives you stuff about 2/3/4G broadband.
(Of not much interest to me.)
Cheers,
David.
David
Mar 14, 2021, 6:20:04 PM3/14/21
to
On Mon, 15 Mar 2021 at 08:41, ghe2001 <ghe...@protonmail.com> wrote:
> On Saturday, March 13, 2021 2:25 PM, Andrei POPESCU <andreim...@gmail.com> 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 Saturday, March 13, 2021 2:25 PM, Andrei POPESCU <andreim...@gmail.com> wrote:
>
> > Well, you could try grepping for 'eth' and 'wwan' ;)
> >
> > Some context might help as well (as in '-C 5' or so).
>
> Bingo:
dmesg | grep -E 'eth|wlan|wwan|cdc_|e1000e|r8152|0000:00:1f.6|0000:00:14.0-2'
0 new messages