From: Daniel Lopes <lopsch@lopsch.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Re: LARTC Digest, Vol 4, Issue 9
Date: Fri, 03 Jun 2005 20:26:40 +0000 [thread overview]
Message-ID: <42A0BD00.6020303@lopsch.com> (raw)
In-Reply-To: <18ebe9d305060312491b0282d9@mail.gmail.com>
Radu CUGUT schrieb:
> 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.
>
It seems you can´t read. To ping someone you exactly know is connected
to the switch is the easiest way to get an arp cache entry. If you don´t
get an entry the switch is not working or the other one is blocking arp
what shouldn´t happen because he wouldn´t be able to receive any
packets. Just try what I said. Blocking protocols like ICMP doesn´t have
an impact on the work of arp respectively ethernet. Exactly spoken no
impact of getting the hardware address.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2005-06-03 20:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-03 19:49 [LARTC] Re: LARTC Digest, Vol 4, Issue 9 Radu CUGUT
2005-06-03 20:26 ` Daniel Lopes [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=42A0BD00.6020303@lopsch.com \
--to=lopsch@lopsch.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.