inxi/pinxi - RAM/Memory + partitions, file systems, and drive use

h2-1 · 07-28-2023, 01:46 AM

babydr, what data is lacking? It's not obvious to me just looking at it. Note that -n activates the more advanced network interface options, and -i adds the device and wan ips.

-F only activates -N, the basic network device rows.

Thus: -Nz has less data than -nz which has less data than -iz, but all activate the main -N network device rows. -x, -xx, -xxx, and -a add more verbosity.

babydr · 07-31-2023, 04:45 PM

@h2-1 , Hopefully the below will answer the Question ,

ie: This line out of the report I sent ...

" IF-ID-1: ppp0 state: unknown speed: N/A duplex: N/A mac: N/A"

Shouldn't it at least show an interface UP state ?

It is created by PPPoE thru eth1 from /etc/rd.local

Code:

# Start pppoe on eth1 ...
pppoe-start

I am not aware of how one would acquire it's speed , Tho maybe thru ...
Note: The "nic-xxx" in the output that this , I am assuming , s/b the ether device it is connected thru . As that is what I have it configure to use .

Code:

# ps -auxww | grep ppp | grep -v grep
root      1312  0.0  0.0   3920  2884 ?        S    May10   0:00 /bin/sh /usr/sbin/pppoe-connect
root      1333  0.0  0.0   8988  4420 ?        Ss   May10   1:05 /usr/sbin/pppd plugin /etc/ppp/plugins/rp-pppoe.so nic-eth1 noipdefault noauth default-asyncmap defaultroute hide-password nodetach mtu 1492 mru 1492 noaccomp nodeflate nopcomp novj novjccomp user dslZZZZZ@sillyprovider.net lcp-echo-interval 20 lcp-echo-failure 3

Code:

# ifconfig ppp0
ppp0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST>  mtu 1492
        inet xxx.yyy.zzz.128  netmask 255.255.255.255  destination xxx.yyy.zzz.232
        ppp  txqueuelen 3  (Point-to-Point Protocol)
        RX packets 116213782  bytes 79063350986 (73.6 GiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 56067195  bytes 5981549843 (5.5 GiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

# ifconfig eth1
eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        ether zz:zz:zz:zz:zz:zz  txqueuelen 1000  (Ethernet)
        RX packets 116805087  bytes 82097800576 (76.4 GiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 56658518  bytes 7232768543 (6.7 GiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

# ip -a -d link show ppp0
7: ppp0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1492 qdisc pfifo_fast state UNKNOWN mode DEFAULT group default qlen 3
    link/ppp  promiscuity 0 minmtu 0 maxmtu 0 
    ppp numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535 

# ip -a -d link show eth1
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
    link/ether zz:zz:zz:zz:zz brd ff:ff:ff:ff:ff:ff promiscuity 0 minmtu 68 maxmtu 9194 numtxqueues 1 numrxqueues 1 gso_max_size 64000 gso_max_segs 64 parentbus pci parentdev 0000:03:00.0

h2-1 · 07-31-2023, 10:11 PM

IF-ID-1: ppp0

I don't think inxi knows about PPoE.

I know I don't know anything about it, it's been probably 20 years since I've dealt with it, maybe 15, can't remember.

inxi has to have a way to match the IF device to the IF, many times no such way exists, that's also the case for vm IFs, and several other types.

Basically that IF has to be detectable in /sys, and to see what is happening there, I need to see a full --debug 22 dataset, otherwise I'd just be guessing.

I doubt there will be a way to link them, and it looks like there was no network data found for ppp0, at least that's what it looks like to me. Unless there's some regex blocking it for some reason.

Completely unknown scenarios usually require full data, otherwise it's largely impossible to do the guessing required, and takes forever.

h2-1 · 07-31-2023, 10:14 PM

I'd need to see ip address and ifconfig -a
to see what is going on there, that's a different syntax, which inxi knows nothing about, for ip, which is what it defaults to.

I can run some local data tests on those short term, but in terms of looking for any advanced data in /sys, I'd have to see a lot more data.

h2-1 · 07-31-2023, 10:36 PM

I did a quick check, inxi doesn't know anything about ppoe, and unfortunatley, neither do I.

That's using the "ip addr" data.

I don't have any real debugging or --force switches running, which is an oversight, so I'll add those, at least so that inxi -iz --force ifconfig would work.

It's odd I never added debugger switches there, though technically, that area is very difficult to debug since most of the data comes from /sys in this case, ip or ifconfig provide only the IP and scope, and a few other related things.

It looks to me like ifconfig should be supplying the IP address at least, but for some reason, ip address isn't showing, unless that command doesn't show it.

Has to be either:

ip addr
or
ifconfig

full output.

note that when obfuscating ip addresses, make sure to use valid syntax, otherwise I have to replace it:

zz:zz bad, ab:ab good.

xxx.yyy. bad, 2.3. good.

I won't be able to do much on this one, but I will add --force switches, which I am amazed I never did before, and I will add some local debuggers so I can at least see what is going on.

If ip addr for ppp0 does not show inet, and some other values in that main line, then inxi can't get any data about pppoe using ip, might get some with ifconfig.

But that's why, never seen this data type before, don't have any real data on it, and don't have full debugger data.

I could check my stored debugger datasets for a ppoe value, but I'd have to find one that I can search for that is always there, ideally in /sys network section.

babydr · 08-03-2023, 06:50 PM

@h2-1 , Sorry about not checking back ...

Latest (afaia) , gives the below error for --force ifconfig

"Error 10: Unsupported value: ifconfig for option: force"

Please see more below ...

Code:

# /usr/local/sbin/pinxi -V
pinxi 3.3.28-09 (2023-07-31)

Copyright (C) 2008-2023 Harald Hope aka h2
Forked from Infobash 3.02: Copyright (C) 2005-2007 Michiel de Boer aka locsmif.
Using Perl version: 5.034000
Program Location: 
Started via symbolic link: /usr/local/sbin/pinxi

Website: https://github.com/smxi/inxi or https://smxi.org/
IRC: irc.oftc.net channel: #smxi
Forums: https://techpatterns.com/forums/forum-33.html

This program is free software; you can redistribute it and/or modify it under the terms of the GNU 
General Public License as published by the Free Software Foundation; either version 3 of the 
License, or (at your option) any later version. (https://www.gnu.org/licenses/gpl.html)

Code:

# /usr/local/sbin/pinxi -iz --force ifconfig
Error 10: Unsupported value: ifconfig for option: force
Check -h for correct parameters.

h2-1 · 08-03-2023, 07:10 PM

Sorry, typo, that's fixed now, forgot to test it when I added that switch. My test case was also incomplete, so it would have run ip anyway, that's also fixed.

Code:

pinxi -iz --force ifconfig
Network:
  Device-1: Intel I211 Gigabit Network driver: igb
  IF: enp7s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IP v4: <filter> scope: N/A
  IP v6: <filter> scope: link
  IP v6: <filter> scope: global
  Device-2: Ralink MT7601U Wireless Adapter driver: mt7601u type: USB
  IF: wlx000f007025bd state: down mac: <filter>
  Device-3: NetGear WNDA3100v1 802.11abgn [Atheros AR9170+AR9104]
    driver: carl9170 type: USB
  IF: wlx001f33efd968 state: down mac: <filter>
  IF-ID-1: vboxnet0 state: down mac: <filter>
  WAN IP: <filter>

pinxi -iz --force ip
Network:
  Device-1: Intel I211 Gigabit Network driver: igb
  IF: enp7s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IP v4: <filter> scope: global
  IP v6: <filter> type: dynamic mngtmpaddr scope: global
  IP v6: <filter> scope: link
  Device-2: Ralink MT7601U Wireless Adapter driver: mt7601u type: USB
  IF: wlx000f007025bd state: down mac: <filter>
  Device-3: NetGear WNDA3100v1 802.11abgn [Atheros AR9170+AR9104]
    driver: carl9170 type: USB
  IF: wlx001f33efd968 state: down mac: <filter>
  IF-ID-1: vboxnet0 state: down mac: <filter>
  WAN IP: <filter>

babydr · 08-04-2023, 11:04 PM

@h2-1 , Yay , ppp0 (ie: a pppoe) , I am seeing some further descriptive info .
Tho most is of minimal value , It says yes ppp0 exists tho nothing more .
I've done a very cursory scan of the --help , Tho am not certain which options I would need is order to have inxi dump as much info as it knows howto acquire about the Networked interfaces .
An example would help me I believe . Maybe it's because the device is a Software item not hardware ?

Tia , JimL

Code:

# /usr/local/sbin/pinxi -iz --force ifconfig
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IP v4: <filter> scope: N/A
  IP v4: <filter> virtual: eth0:0 scope: N/A
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169
  IF: eth1 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-3: Intel Wireless 3165 driver: iwlwifi
  IF: wlan0 state: down mac: <filter>
  Device-4: Intel Bluetooth wireless interface driver: btusb type: USB
  Device-5: Realtek RTL8152 Fast Ethernet Adapter driver: r8152 type: USB
  IF: eth3 state: up speed: 100 Mbps duplex: full mac: <filter>
  Message: Output throttled. IPs: 1; Limit: 10; Override: --limit [1-x;-1 all]
  Device-6: ASIX AX88772 driver: asix type: USB
  IF: eth2 state: down mac: <filter>
  Message: Output throttled. IPs: 1; Limit: 10; Override: --limit [1-x;-1 all]
  IF-ID-1: ppp0 state: unknown speed: N/A duplex: N/A mac: N/A
  Message: Output throttled. IPs: 1; Limit: 10; Override: --limit [1-x;-1 all]
  WAN IP: <filter>

h2-1 · 08-05-2023, 12:51 AM

It looks like you may have tripped some internal bug, you should not be seeing that:

Code:

Message: Output throttled. IPs: 1; Limit: 10; Override: --limit [1-x;-1 all]

since there is only 1 IP.

It's supposed to, and does, work like this:

Code:

Network:
  Device-1: Intel I350 Gigabit Network driver: igb
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IP v4: <filter> scope: global
  IP v4: <filter> type: deprecated scope: global
  IP v4: <filter> type: deprecated scope: global
  IP v4: <filter> type: deprecated scope: global
  IP v4: <filter> type: deprecated scope: global
  IP v4: <filter> type: deprecated scope: global
  IP v4: <filter> type: deprecated scope: global
  IP v4: <filter> type: deprecated scope: global
  Message: Output throttled. IPs: 379; Limit: 10; Override: --limit [1-x;-1 all]
  Device-2: Intel I350 Gigabit Network driver: igb
  IF: eth1 state: down mac: <filter>
  WAN IP: <filter>

Mostly for servers with a lot of IPs on the Device, but that will never show unless you have > 10 IPs attached to that device, but your result shows 1, but it has that message, which in theory can't happen, but appears to have happened.

Actually there too the count is off, I'll have to check that, the limit is supposed to show up to that limit, but that one is showing only 8, hmm.

h2-1 · 08-05-2023, 01:10 AM

That was a bug, I was using the wrong thing to count the limit. Corrected now.

Code:

pinxi -iz
Network:
  Device-1: Intel I350 Gigabit Network driver: igb
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IP v4: <filter> scope: global
  IP v4: <filter> type: deprecated scope: global
  IP v4: <filter> type: deprecated scope: global
  IP v4: <filter> type: deprecated scope: global
  IP v4: <filter> type: deprecated scope: global
  IP v4: <filter> type: deprecated scope: global
  IP v4: <filter> type: deprecated scope: global
  IP v4: <filter> type: deprecated scope: global
  IP v4: <filter> type: deprecated scope: global
  IP v4: <filter> type: deprecated scope: global
  Message: Output throttled. IPs: 379; Limit: 10; Override: --limit [1-x;-1 all]
  Device-2: Intel I350 Gigabit Network driver: igb
  IF: eth1 state: down mac: <filter>
  WAN IP: <filter>

Not sure how I missed this one, I think on those servers I don't often run -i so don't trip the limiter.

Glad you had a bunch of devices however.

Code:

Device-4: Intel Bluetooth wireless interface driver: btusb type: USB

that's a bug too, that's not supposed to be in the Network report, it's supposed to be in the -E/--bluetooth report, there must be messed up regex again somewhere in there.

h2-1 · 08-05-2023, 01:41 AM

There were even more bugs in that usb type detection logic, a series of them, which led to that device falling through instead of getting caught as a bluetooth device before it hit the network device test.

This should be corrected, I hope.

This section has had a lot of bugs, I must have been having an off day when I redid that logic judging by the way the bugs and glitches are.

Most of that should be cleaned up now, I think.

The bluetooth device should now be out of the output, hopefully, unless there are even more bugs in there hiding.

There were some incorrectly nested test conditions, failed to use parentheses properly, so I redid that code to make it much more obvious what is ending and starting each test condition.

babydr · 08-05-2023, 07:16 PM

@h2-1 , The "ouput throttled" are now gone .
Am now , when using "-iZ" options , seeing ppp0's ip address Which is big improvement to me :-) .

Tho the Bluetooth items is still present using the option line as in the below .
Tho NOT when using the one below that . It is actually in the BlueTooth section . Very odd to me .

Tia , JimL

Code:

# pinxi -xxxiz --force ifconfig 2>&1 

Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 v: kernel pcie:
    speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 02:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IP v4: <filter> scope: N/A broadcast: <filter>
  IP v4: <filter> virtual: eth0:0 scope: N/A broadcast: <filter>
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 v: kernel pcie:
    speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: eth1 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-3: Intel Wireless 3165 driver: iwlwifi v: kernel pcie: speed: 2.5 GT/s lanes: 1
    bus-ID: 04:00.0 chip-ID: 8086:3165 class-ID: 0280
  IF: wlan0 state: down mac: <filter>
  Device-4: Intel Bluetooth wireless interface driver: btusb type: USB rev: 2.0 speed: 12 Mb/s
    lanes: 1 bus-ID: 1-5.2:7 chip-ID: 8087:0a2a class-ID: e001
  Device-5: Realtek RTL8152 Fast Ethernet Adapter driver: r8152 type: USB rev: 2.1
    speed: 480 Mb/s lanes: 1 bus-ID: 1-5.3:9 chip-ID: 0bda:8152 class-ID: 0000 serial: <filter>
  IF: eth3 state: up speed: 100 Mbps duplex: full mac: <filter>
  IP v4: <filter> scope: N/A broadcast: <filter>
  IP v4: <filter> virtual: eth3:0 scope: N/A broadcast: <filter>
  Device-6: ASIX AX88772 driver: asix type: USB rev: 2.0 speed: 480 Mb/s lanes: 1
    bus-ID: 1-5.4:10 chip-ID: 0b95:7720 class-ID: ff00 serial: <filter>
  IF: eth2 state: down mac: <filter>
  IP v4: <filter> scope: N/A broadcast: <filter>
  IF-ID-1: ppp0 state: unknown speed: N/A duplex: N/A mac: N/A
  IP v4: <filter> scope: N/A
  WAN IP: <filter>

Code:

# pinxi -Fxxxriz --force ifconfig 2>&1 
System:
  Kernel: 5.15.94 arch: x86_64 bits: 64 compiler: gcc v: 2.37-slack15 clocksource: tsc
    Console: pty pts/1 Distro: Slackware 15.0
Machine:
  Type: Unknown Mobo: ZOTAC model: ZBOX-CI325NANO v: XX serial: <filter> UEFI: American Megatrends
    v: B301P021 date: 03/07/2017
CPU:
  Info: quad core model: Intel Celeron N3160 bits: 64 type: MCP smt: <unsupported> arch: Airmont
    rev: 4 cache: L1: 224 KiB L2: 2 MiB
  Speed (MHz): avg: 1800 high: 2240 min/max: 480/2240 volts: 1.2 V ext-clock: 80 MHz cores:
    1: 1361 2: 1360 3: 2240 4: 2240 bogomips: 12800
  Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics
    vendor: ZOTAC driver: i915 v: kernel arch: Gen-8 ports: active: none empty: DP-1, DP-2,
    HDMI-A-1, HDMI-A-2, HDMI-A-3 bus-ID: 00:02.0 chip-ID: 8086:22b1 class-ID: 0300
  Display: server: X.org v: 1.20.14 with: Xwayland v: 21.1.4 driver: X: loaded: modesetting
    unloaded: vesa alternate: fbdev dri: i965 gpu: i915 tty: 180x48
  API: OpenGL Message: GL data unavailable in console for root.
Audio:
  Device-1: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series High Definition Audio
    vendor: ZOTAC driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:2284 class-ID: 0403
  API: ALSA v: k5.15.94 status: kernel-api with: aoss type: oss-emulator
  Server-1: EsounD v: 0.2.41 status: off
  Server-2: PipeWire v: 0.3.44 status: off with: 1: pipewire-pulse status: off
    2: pipewire-media-session status: off
  Server-3: PulseAudio v: 15.0 status: off
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 v: kernel pcie:
    speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 02:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IP v4: <filter> scope: N/A broadcast: <filter>
  IP v4: <filter> virtual: eth0:0 scope: N/A broadcast: <filter>
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 v: kernel pcie:
    speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: eth1 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-3: Intel Wireless 3165 driver: iwlwifi v: kernel pcie: speed: 2.5 GT/s lanes: 1
    bus-ID: 04:00.0 chip-ID: 8086:3165 class-ID: 0280
  IF: wlan0 state: down mac: <filter>
  Device-4: Realtek RTL8152 Fast Ethernet Adapter driver: r8152 type: USB rev: 2.1
    speed: 480 Mb/s lanes: 1 bus-ID: 1-5.3:9 chip-ID: 0bda:8152 class-ID: 0000 serial: <filter>
  IF: eth3 state: up speed: 100 Mbps duplex: full mac: <filter>
  IP v4: <filter> scope: N/A broadcast: <filter>
  IP v4: <filter> virtual: eth3:0 scope: N/A broadcast: <filter>
  Device-5: ASIX AX88772 driver: asix type: USB rev: 2.0 speed: 480 Mb/s lanes: 1
    bus-ID: 1-5.4:10 chip-ID: 0b95:7720 class-ID: ff00 serial: <filter>
  IF: eth2 state: down mac: <filter>
  IP v4: <filter> scope: N/A broadcast: <filter>
  IF-ID-1: ppp0 state: unknown speed: N/A duplex: N/A mac: N/A
  IP v4: <filter> scope: N/A
  WAN IP: <filter>
Bluetooth:
  Device-1: Intel Bluetooth wireless interface driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 bus-ID: 1-5.2:7 chip-ID: 8087:0a2a class-ID: e001
  Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 4.2 lmp-v: 8
    sub-v: 1000 hci-v: 8 rev: 1000
Drives:
  Local Storage: total: 447.13 GiB used: 28.47 GiB (6.4%)
  ID-1: /dev/sda vendor: SanDisk model: SSD PLUS 480GB size: 447.13 GiB speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 04RL scheme: GPT
Partition:
  ID-1: / size: 398.69 GiB used: 28.25 GiB (7.1%) fs: ext4 dev: /dev/sda3
  ID-2: /boot/efi size: 7.98 GiB used: 226.4 MiB (2.8%) fs: vfat dev: /dev/sda1
Swap:
  ID-1: swap-1 type: partition size: 33 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda2
Sensors:
  System Temperatures: cpu: 34.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Repos:
  Packages: pm: pkgtool pkgs: 1606
  slackpkg mirror in: /etc/slackpkg/mirrors
    1: file://home/archive/slackware-15_X
Info:
  Processes: 144 Uptime: 87d 7h 49m wakeups: 1 Memory: total: 8 GiB available: 7.67 GiB
  used: 542.5 MiB (6.9%) igpu: 32 MiB Init: SysVinit v: 3.01 runlevel: 3 default: 3 Compilers:
  gcc: 11.2.0 clang: 13.0.0 Shell: Bash v: 5.1.16 running-in: pty pts/1 (SSH) pinxi: 3.3.28-15

h2-1 · 08-05-2023, 08:35 PM

I think I can see where/why it's failing, the tests require the feature be active in one case, so if bluetooth is not activated, it's still falling back to the network item.

Bluetooth was sort of tacked on quite late in this game, and this is a corner case it didn't handle.

I'll check the tests again, and run your data through though I can't fully emulate it, but maybe I can more or less.

Thanks, I should have this fixed fairly soon now that I see the actual trigger, which wouldn't be obvious if -F is used, which trips -E/--bluetooth, which then trips the filter case.

h2-1 · 08-05-2023, 09:21 PM

The bluetooth issue is now corrected, I tested it against your literal string on a device, and now it works, with -n, it does not show, and with -nE it shows only as bluetooth.

The cause here in a sense was optimization, but in a good cause, the goal was to avoid doing 3 layers of regex tests to determine if a device is a certain type if that type item has not been requested for output, but in this case, inxi needs to always capture bluetooth if network is called, since there's a regex with 'wireless' as a last fallback. My initial inclination was to remove that, but it's quite useful for catching wireless devices that might otherwise fail to get detected, just have to catch bluetooth always prior to network if bluetooth OR network.

Added shortcut for --force ifconfig --ifconfig, why not? Maybe will add a configuration item too for that, never considered the utility but this example shows a clear example of that.

This lets me get back to your original issue, which I'm now seeing more on since I can focus on it instead of inxi's glitches in this area.

Thanks for your patience in helping to track down these various issues. These were all generic issues which could have, and probably have, caught others.

This gets us back to your pppoe issue, which I can now see more clearly. Note that ip is used as first IF source, and ifconfig is a fallback, since it was deprecated a long time ago, or that's what was said, though still default on bsds, so it's still alive and kicking, but 'ip addr' is first source, and inxi won't know the device is a pppoe connection until after the tool runs, so it can't really change its behavior. having to use --force ifconfig is not ideal, though I can also make an --ifconfig shortcut flag to trip that, inxi uses many of those shortcut force options. But it's not a solution since the user should not have to know to use it.

Code:

7: ppp0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1492 qdisc pfifo_fast state UNKNOWN mode DEFAULT group default qlen 3
    link/ppp  promiscuity 0 minmtu 0 maxmtu 0 
    ppp numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535

I'm confused why ip addr does not show IP for ppo0, but ifconfig does.

I'll look to see if I can find if /sys is any help with ppoe devices.

h2-1 · 08-05-2023, 09:50 PM

Code:

7: ppp0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1400 qdisc pfifo_fast state 
UNKNOWN group default qlen 3
    link/ppp 
    inet 192.168.1.12 peer 192.168.1.14/32 scope global ppp0 
      valid_lft forever preferred_lft forever
    inet6 fe80::1ca6:d5a4:8b3c:31bc peer fe80::b0:45/128 scope link 
      valid_lft forever preferred_lft forever

This from another dataset, with a link/ppp, that's 'ip addr' though this instance for some reason added linebreaks, which then of course broke inxi parsing.

I'll have to see if this is a standard behavior for ip, if so, that's extremely unfortunate.

Can you verify that: ip addr

does not wrap its output, and does not include the inet address?

I have a few pppoe datasets, but not very many. I've never seen ip output wrap the way the above did, that is bad behavior. Hmm, actually checking that system output, it was doing bad wrapping all over, so probably not a great test case, there may have been some other silliness going on there.