ifconfig data interpretation

[colin davidson]

"Frame" means framing error. On Ethernet, this can be a number of different
things. If a packet is started sooner than allowed by the mandatory Inter
Packet Gap, you have a framing error. If the packet is longer than the
maximum allowed length, you have a framing error. If the packet is not a
multiple of eight bit times in lenght, you have a framing error. There are
probably other conditions as well - anything that isn't a valid ethernet
frame will cause this error.

On Thu, Apr 2, 2009 at 11:47 AM, William Muriithi <
william.muriithi-Re5JQEeQqe8AvxtiuMwx3w at public.gmane.org> wrote:

> Morning,
>
> I have noticed that the ifconfig tool is being deprecated and will be
> replaced by the ip tool. However, so far I have not been able to find
> a way of getting all the information generated by ifconfig from ip
> tool. By that I mean details like packets received, packet sent out,
> collision statistics and sent/receive errors are impossible to get
> from /sbin/ip.  Now, is that a tool limitation or is it me who have
> not done my homework well?
>
> Second, I have noticed one details that is not straight forward to
> understand as I thought - frame. When I googled, I got the feeling its
> a flag raised when the NIC can not detect connectivity. That is not
> the case though as none of the network based seem affected. It could
> also be the frame is larger than 1500, but I have not seen it in any
> other system. It make no sense to assert that only one system is
> experiencing giant frames.
>
> That got me thinking that I may actually be misinterpretation what the
> word frame mean and therefore the post. Any idea why the frame counter
> keep going up?
>
> Link encap:Ethernet  HWaddr 00:14:22:3E:8F:79
>          inet addr:172.16.1.139  Bcast:172.16.3.255  Mask:255.255.252.0
>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>          RX packets:37156044 errors:172679 dropped:0 overruns:0
> frame:172678
>          TX packets:54908637 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:1000
>          RX bytes:313517308 (298.9 MiB)  TX bytes:2734438868 (2.5 GiB)
>          Base address:0xecc0 Memory:fe6e0000-fe700000
>
>
> - Interesting dmesg information
> * e1000: eth0: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex
> * Intel(R) PRO/1000 Network Driver - version 6.0.54-k2-NAPI
>
> The nic card is:
> lspci output
> * 06:07.0 Ethernet controller: Intel Corp. 82541GI/PI Gigabit Ethernet
> Controller (rev 05)
>
> ethtool output
>
> Settings for eth0:
>        Supported ports: [ TP ]
>        Supported link modes:   10baseT/Half 10baseT/Full
>                                100baseT/Half 100baseT/Full
>                                1000baseT/Full
>        Supports auto-negotiation: Yes
>        Advertised link modes:  10baseT/Half 10baseT/Full
>                                100baseT/Half 100baseT/Full
>                                1000baseT/Full
>        Advertised auto-negotiation: Yes
>        Speed: 1000Mb/s
>        Duplex: Full
>        Port: Twisted Pair
>        PHYAD: 0
>        Transceiver: internal
>        Auto-negotiation: on
>        Supports Wake-on: umbg
>        Wake-on: d
>        Current message level: 0x00000007 (7)
>        Link detected: yes
>
>
> Regards,
>
> William
> --
> The Toronto Linux Users Group.      Meetings: http://gtalug.org/
> TLUG requests: Linux topics, No HTML, wrap text below 80 columns
> How to UNSUBSCRIBE: http://gtalug.org/wiki/Mailing_lists
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gtalug.org/pipermail/legacy/attachments/20090402/e50fcbe7/attachment.html>