From: Radu CUGUT <rcugut@gmail.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Re: LARTC Digest, Vol 4, Issue 9
Date: Fri, 03 Jun 2005 19:49:37 +0000 [thread overview]
Message-ID: <18ebe9d305060312491b0282d9@mail.gmail.com> (raw)
Daniel Lopes wrote:
> Ping a client you surely know should be connected to the switch. ARP
> will take the part to find out the hardware address so the packet can be
> delivered. If the switch is on it should find a hardware address and ARP
> should put it in your ARP cache. It´s independet from ICMP blocks and
> similar. So after trying to ping you should have an entry in your ARP
> table which you can control with "arp" command.
>
>
It seems that I didn't make myself quite clear ...
I want to know if there is a way to find out if a switch is working ok or not.
If there is something like a small device, that I plug into the
switch, ant then if that device "reports in" ok, then I know the
switch is working.
Like on a router... if you want to know if a router is doing it's job,
than you send an ICMP echo request to a host on the other side of the
router.
ME ----> ROUTER -----> testing host
well, I want the same thing but on an inferior layer, on a switch.
ME -----> SWITCH ----> testing device
I want to know if thare can be such thing as a "testing device".
I thought of an ethernet card, that i plug in the switch, power the
card up, and then somehot arping the card, from witch I know the MAC.
... but i don't think it works just like that :(.
Hope I was specific enough this time ....
Thanks for the (possible) answers.
Best regards,
Radu.
--
Radu Cugut
mobile: +40 742 045686
web: http://rcugut.has.it
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next reply other threads:[~2005-06-03 19:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-03 19:49 Radu CUGUT [this message]
2005-06-03 20:26 ` [LARTC] Re: LARTC Digest, Vol 4, Issue 9 Daniel Lopes
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=18ebe9d305060312491b0282d9@mail.gmail.com \
--to=rcugut@gmail.com \
--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.