From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Lopes Date: Fri, 03 Jun 2005 20:26:40 +0000 Subject: Re: [LARTC] Re: LARTC Digest, Vol 4, Issue 9 Message-Id: <42A0BD00.6020303@lopsch.com> List-Id: References: <18ebe9d305060312491b0282d9@mail.gmail.com> In-Reply-To: <18ebe9d305060312491b0282d9@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: lartc@vger.kernel.org Radu CUGUT schrieb: > Daniel Lopes wrote: >=20 >>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=B4s 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. >> >> >=20 >=20 > It seems that I didn't make myself quite clear ... >=20 > I want to know if there is a way to find out if a switch is working ok or= not. >=20 It seems you can=B4t read. To ping someone you exactly know is connected=20 to the switch is the easiest way to get an arp cache entry. If you don=B4t = get an entry the switch is not working or the other one is blocking arp=20 what shouldn=B4t happen because he wouldn=B4t be able to receive any=20 packets. Just try what I said. Blocking protocols like ICMP doesn=B4t have = an impact on the work of arp respectively ethernet. Exactly spoken no=20 impact of getting the hardware address. _______________________________________________ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc