From: Daniel Lopes <lopsch@lopsch.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] how can I monitor a (dumb) switch ?
Date: Fri, 03 Jun 2005 13:15:01 +0000 [thread overview]
Message-ID: <42A057D5.7050201@lopsch.com> (raw)
In-Reply-To: <51095.194.102.203.14.1117786690.squirrel@194.102.203.14>
Radu CUGUT schrieb:
> Hello there,
>
> Can anyone help me with a problem i have....
>
> I have an ethernet LAN, made over dumb fast-ethernet switches
> (10/100mbit) without management, so there is no IP for the switches.
>
> What I want, if possible, is to find out if a switch is down or not.
>
> It's like with routers... if you want to find out if a router is OK,
> either you send ICMP directly to the router, or to a host "behind" the
> router.
>
> Is there any device, or ANY OTHER possibility that I can find out if a
> switch is unplugged or broken. Users on my LAN aren't reliable (they
> have firewalls, closed computers, etc.), so pinging users that are
> linked to a switch to find out is out of the question.
>
> I have got an ideea that if I take an ehernet card, and somehow manage
> to put power in it, than I would have a device with MAC addres to
> arping ... is this correct ?
>
> MANY thanks in advance, and SORRY for being a bit out of topic.
>
>
> Best regards,
> Radu.
>
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.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2005-06-03 13:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-03 8:18 [LARTC] how can I monitor a (dumb) switch ? cristian_dimache
2005-06-03 8:24 ` Radu CUGUT
2005-06-03 13:15 ` Daniel Lopes [this message]
2005-06-03 15:34 ` Dmytro O. Redchuk
2005-06-03 17:03 ` Jay Vosburgh
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=42A057D5.7050201@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.