public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Simon Wunderlich <sw@simonwunderlich.de>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: Jonathan Haws <jhaws@sdl.usu.edu>
Subject: Re: [B.A.T.M.A.N.] [PATCH v4] alfred: IPv4 multicast distribution support.
Date: Tue, 24 Jan 2017 12:44:38 +0100	[thread overview]
Message-ID: <4448368.uV4yijacOc@prime> (raw)
In-Reply-To: <1484884864-7315-1-git-send-email-jhaws@sdl.usu.edu>

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

On Thursday, January 19, 2017 9:01:04 PM CET Jonathan Haws wrote:
> Enabled via -4 expert option where multicast group address is specified.
> This option will disable IPv6 communication and is intended for use in
> networks which do not support IPv6 addressing.
> 
> When this option is enabled, all IPv6 communication is disabled. Combining
> IPv4 and IPv6 alfred nodes is unsupported.
> 
> Hardware address handling done by submitting queries to the local ARP
> cache rather than forcing an ARP request.

Thanks Jonathan for your patch! I've just looked through the patch and 
discussed the matter with Sven yesterday. We are both not too big fans of 
supporting IPv4, but since it helps your scenario and you supplied a well 
written patch which properly abstracts the address mode and has separate IPv4/
IPv6 functions, I think we can adopt it.

Just two general questions/remarks:

 * I do not want to give support for IPv4-related questions of users. Would 
you be available to maintain and answer questions regarding the IPv4 support?
 * Do you plan to provide OpenWRT support as well? (This is more out of 
curiosity)

Thank you,
     Simon

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2017-01-24 11:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-20  4:01 [B.A.T.M.A.N.] [PATCH v4] alfred: IPv4 multicast distribution support Jonathan Haws
2017-01-20  4:04 ` Jonathan Haws
2017-01-24 11:44 ` Simon Wunderlich [this message]
2017-01-24 15:45   ` Jonathan Haws
2017-01-24 16:05     ` Simon Wunderlich
2017-01-24 16:07       ` Jonathan Haws
2017-01-24 13:05 ` Sven Eckelmann
2017-01-24 15:35   ` Jonathan Haws
2017-01-24 16:09     ` Simon Wunderlich
2017-01-24 16:19     ` Sven Eckelmann

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=4448368.uV4yijacOc@prime \
    --to=sw@simonwunderlich.de \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=jhaws@sdl.usu.edu \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox