netstat -i output

Question

netstat -i output

gunhu opened this issue 6 years ago · comments

Hi everyone,

I wanted to point out something on netstat -i output:

$ netstat -i
Kernel Interface table
Iface MTU RX-OK RX-ERR RX-DRP RX-OVR TX-OK TX-ERR TX-DRP TX-OVR Flg
lo 65536 2 0 0 0 2 0 0 0 LRU

When I'm debugging network issues I want to have all information about a network card.

I mean all relevant timers to see if something wrong is going on.

I don't see any RX-FRAME or TX-FRAME field, I need to add -e option.

Can I make a PR to have an output like this:

$ netstat -i
Kernel Interface table
Iface MTU RX-OK RX-ERR RX-DRP RX-FRAME RX-OVR TX-OK TX-ERR TX-DRP TX-FRAME TX-OVR Flg
lo 65536 2 0 0 0 0 2 0 0 0 0 LRU

Thanks for your kind advice about it.

Regards,

Bernd · Answer 1 · Fri Nov 30 2018 02:14:18 GMT+0800 (China Standard Time)

Hello Alexis, Thanks for the report. I think the columns selected are designed to fit into 80 colums. So if we want to add more we should I guess either have a new Option or make it sensitive to terminal width (and Show all coluimns for pipes). This would also reduce compliations with scripts parsing the Output (which is most likely not a good idea…) So what do you think, new option or detecting terminal width? Gruss Bernd -- http://bernd.eckenfels.net Von: Alexis VACHETTE Gesendet: Donnerstag, 29. November 2018 17:52 An: ecki/net-tools Cc: Subscribed Betreff: [ecki/net-tools] netstat -i output (#10) Hi everyone, I wanted to point out something on netstat -i output: $ netstat -i Kernel Interface table Iface MTU RX-OK RX-ERR RX-DRP RX-OVR TX-OK TX-ERR TX-DRP TX-OVR Flg lo 65536 2 0 0 0 2 0 0 0 LRU I don't see any RX-FRAME or TX-FRAME field, I need to add -e option. Can I make a PR to have an output like this: $ netstat -i Kernel Interface table Iface MTU RX-OK RX-ERR RX-DRP RX-FRAME RX-OVR TX-OK TX-ERR TX-DRP TX-FRAME TX-OVR Flg lo 65536 2 0 0 0 0 2 0 0 0 0 LRU Thanks for your kind advice about it. Regards, — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

Alexis Vachette · Answer 2 · Fri Nov 30 2018 06:25:38 GMT+0800 (China Standard Time)

Hello Bernd,

I will add a new option (PR) to not break backward compability (with scripts).

Man page(s) will be updated accordingly.

Is it fine with you ?

Regards,

Alexis Vachette · Answer 3 · Mon Dec 03 2018 00:12:06 GMT+0800 (China Standard Time)

I came with a new idea.

Add CRC / Frame errors to RX counter.

No breaking change in the output.

Regards,

Alexis Vachette · Answer 4 · Mon Dec 03 2018 00:28:25 GMT+0800 (China Standard Time)

Here is the relevant PR:

#11

Regards,

Bernd · Answer 5 · Tue Dec 04 2018 04:15:11 GMT+0800 (China Standard Time)

Thanks, adding the numbers actually looks like a good compromise. Will have to make sure to document that in manpage and release notes.

Alexis Vachette · Answer 6 · Tue Dec 04 2018 05:26:15 GMT+0800 (China Standard Time)

Do you want me to clarify this on the man page ?

Regards,

Bernd · Answer 7 · Tue Dec 04 2018 07:57:36 GMT+0800 (China Standard Time)

It would be great if you could. Can you also squash your commits, so its a single one with the sum (of the right fields) and the man adoption.

Alexis Vachette · Answer 8 · Sun Dec 09 2018 01:29:59 GMT+0800 (China Standard Time)

Hi Bernd,

I added manpage details on my PR.

I'm only French native speaker and I can write/speak English too.

Feel free to review German and Portuguese part if it's not correct.

Regards,

Bernd · Answer 9 · Tue Aug 23 2022 02:38:38 GMT+0800 (China Standard Time)

Marged here: 6cd5159