All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gert Doering <gert@...1296...>
To: Vladimir Kamarzin <vvk@...1868...>
Cc: "openvpn-devel@lists.sourceforge.net"
	<openvpn-devel@lists.sourceforge.net>
Subject: Re: [Openvpn-devel] [PATCH] Extract MAC addresses from ARP packets
Date: Wed, 5 Mar 2014 13:21:13 +0100	[thread overview]
Message-ID: <20140305122113.GT16637@...1296...> (raw)
In-Reply-To: <283911394015829@...1871...>

[-- Attachment #1: Type: text/plain, Size: 900 bytes --]

Hi,

On Wed, Mar 05, 2014 at 04:37:09PM +0600, Vladimir Kamarzin wrote:
> 5. Switch (S) does not know where is 00:00:00:22:22:22, so it sends this packet to all ports

Yeah, I think that's the difference.  We don't do unicast flooding ("send
frames to unknown unicast destinations to every single port") because
bandwidth on the VPN is limited & more expensive.

Adding it would solve the issue at hand, but I'm not convinced that you'll
be happy with the end - it might actually end up saturating VPN links and
making users unhappy if you have "much flooded traffic" (which happens in
some of the networks).

gert
-- 
USENET is *not* the non-clickable part of WWW!
                                                           //www.muc.de/~gert/
Gert Doering - Munich, Germany                             gert@...1296...
fax: +49-89-35655025                        gert@...1297...

[-- Attachment #2: Type: application/pgp-signature, Size: 305 bytes --]

  reply	other threads:[~2014-03-05 12:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-04 10:37 [Openvpn-devel] [PATCH] Extract MAC addresses from ARP packets Vladimir V. Kamarzin
2014-03-04 10:44 ` Vladimir Kamarzin
2014-03-04 19:56 ` Gert Doering
2014-03-04 20:49 ` Arne Schwabe
2014-03-05  5:53   ` Gert Doering
2014-03-05 10:37   ` Vladimir Kamarzin
2014-03-05 12:21     ` Gert Doering [this message]
2014-03-05 12:44       ` Vladimir Kamarzin
2014-03-05 14:55         ` Gert Doering

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=20140305122113.GT16637@...1296... \
    --to=openvpn-devel@lists.sourceforge.net \
    /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.