All of lore.kernel.org
 help / color / mirror / Atom feed
From: Srikanth <srikanth_w@naturesoft.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] How to find the NIC Capacity / Bandwidth ?
Date: Thu, 01 May 2003 07:01:40 +0000	[thread overview]
Message-ID: <marc-lartc-105177337822380@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105170164615078@msgid-missing>

Dear Martin,

Thanks for the quickest response.
I've downloaded ethtool-1.6.tar.gz from the freshmeat.net, and 
customized the "ethtool.c"
It's giving the Speed of 10Mb/s. 

regards,
Srikanth.

Martin A. Brown wrote:

>Srikanth,
>
> : Any body having idea to find the NIC Capacity / BW (10 / 100 Mbps) ?
> : Whether the interface may be eth0/eth1/ppp0 or some other. Is there any
> : related IOCTL avialable, if so just give the linux-2.4.18 file path.
>
>For ethernet interfaces (devices), you should be able to determine the
>negotiated speed with either a device specific diagnostic utility
>(e.g., tulip-diag), or, with recent kernels and drivers, mii-diag,
>mii-tool, and the preferred ethtool.
>
>You can find the source to ethtool here:
>
>  http://freshmeat.net/projects/ethtool/?topic_id\x146%2C150
>
>If this doesn't provide your answer, you may find a faster (if terser)
>answer from linux-net....as for determining speed of a serial link from
>the interface or device--I have no idea!  Maybe somebody else on the list?
>
>Best of luck,
>
>-Martin
>
>  
>


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      parent reply	other threads:[~2003-05-01  7:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-30 11:28 [LARTC] How to find the NIC Capacity / Bandwidth ? Srikanth
2003-05-01  4:25 ` Martin A. Brown
2003-05-01  7:01 ` Srikanth [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-lartc-105177337822380@msgid-missing \
    --to=srikanth_w@naturesoft.net \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.