All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Taylor <gtaylor@riverviewtech.net>
To: lartc@vger.kernel.org
Subject: [LARTC] To broadcast or not to broadcast...
Date: Mon, 09 Jul 2007 06:26:55 +0000	[thread overview]
Message-ID: <4691D52F.7080908@riverviewtech.net> (raw)

I'm looking to refine / re-use my recently discussed "Redundant internet 
connections" 
(http://mailman.ds9a.nl/pipermail/lartc/2007q2/thread.html#21015) in 
such a way that I will not be sure of returning traffic, thus I must 
monitor the connection my self and not rely on inbound traffic to update 
the kernel counters.

I'm considering using arping to ping the upstream gateway.  I think this 
will work just fine.  However arping has an option to always send 
broadcasts verses starting with broadcast packets and then falling back 
to unicast packets.  My fear is that if I use arpings default method of 
broadcast and then unicast once a MAC is known, this will fail if the 
upstream router is doing something where the MAC address would change.

So, my question / request for thoughts and / or opinions, is should I 
always send out broadcasts so that any and all stations on the subnet 
see the ARP, thus allowing the arping to function even if the MAC 
address of the default gateway is changed, say if the provider decides 
to do an upgrade and / or maintenance?



Grant. . . .
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

                 reply	other threads:[~2007-07-09  6:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4691D52F.7080908@riverviewtech.net \
    --to=gtaylor@riverviewtech.net \
    --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.