Hello, Is there a way from a CLI to tell if the computer is connected to the network at a 100tx or 1000? Thank you, James
On Friday 19 May 2006 06:16 pm, James D. Parra wrote:
Hello,
Is there a way from a CLI to tell if the computer is connected to the network at a 100tx or 1000?
Use the tcpdump utility. It isn't just for teh l33t h4xx0rs. :) Run as root: tcpdump -c xx -i eth(n) xx is the number of packets you want to capture - this can be really small. (n) is the ethernet port you're running. Here's an example from my machine showing I'm running 10MB/S yoda:/home/kai # tcpdump -c 10 -i eth1 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth1, link-type EN10MB (Ethernet), capture size 96 bytes -- kai - www.perfectreign.com www.filesite.org - the filenet community forum 43...for those who require slightly more than the answer to life, the universe and everything.
On Fri, 2006-05-19 at 19:08 -0700, kai wrote:
On Friday 19 May 2006 06:16 pm, James D. Parra wrote:
Hello,
Is there a way from a CLI to tell if the computer is connected to the network at a 100tx or 1000?
Use the tcpdump utility. It isn't just for teh l33t h4xx0rs. :)
Run as root: tcpdump -c xx -i eth(n)
xx is the number of packets you want to capture - this can be really small.
(n) is the ethernet port you're running. Here's an example from my machine showing I'm running 10MB/S
yoda:/home/kai # tcpdump -c 10 -i eth1 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth1, link-type EN10MB (Ethernet), capture size 96 bytes
Kai, is this cat5(100) or coax(10)?
On Friday 19 May 2006 09:08 pm, Mike McMullin wrote: <snip>
yoda:/home/kai # tcpdump -c 10 -i eth1 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth1, link-type EN10MB (Ethernet), capture size 96 bytes
Kai, is this cat5(100) or coax(10)?
Neither, actually. I did this on my laptop. It is 802.11g 54mbps. I think it doesn't know how to handle that. But it does give an indication. -- k
On Saturday 20 May 2006 09:08, kai wrote:
On Friday 19 May 2006 06:16 pm, James D. Parra wrote:
Hello,
Is there a way from a CLI to tell if the computer is connected to the network at a 100tx or 1000?
Use the tcpdump utility. It isn't just for teh l33t h4xx0rs. :)
Run as root: tcpdump -c xx -i eth(n)
xx is the number of packets you want to capture - this can be really small.
(n) is the ethernet port you're running. Here's an example from my machine showing I'm running 10MB/S
yoda:/home/kai # tcpdump -c 10 -i eth1 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth1, link-type EN10MB (Ethernet), capture size 96 bytes
-- Dear kai, Found this an interesting command line and tried it at once out on my system. I do not get one line but following lines which make me wonder what they tell me. Could you shine some light in this flux of information?
# tcpdump -c 10 -i eth0
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
16:44:31.907646 IP 10.0.0.11.8065 > pop-qmail.indo.net.id.imap: P
1575050632:1575050663(31) ack 3606448495 win 3712
On Saturday 20 May 2006 02:49 am, C. Brouerius van Nidek wrote:
On Saturday 20 May 2006 09:08, kai wrote: <snip>
yoda:/home/kai # tcpdump -c 10 -i eth1 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth1, link-type EN10MB (Ethernet), capture size 96 bytes
Dear kai, Found this an interesting command line and tried it at once out on my system. I do not get one line but following lines which make me wonder what they tell me. Could you shine some light in this flux of information?
I'm not very good at tcpdump, since I mostly play with ethereal and nmap these days. Basically, without the -c xx command, tcpdump will go on forever capturing tcp/ip information. You can also save that to a file. -- k
participants (5)
-
C. Brouerius van Nidek -
James D. Parra -
kai -
Mike McMullin -
Per Jessen