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,
	Jonathan Haws <Jonathan.Haws@sdl.usu.edu>
Subject: Re: [B.A.T.M.A.N.] [PATCH v4] alfred: IPv4 multicast distribution support.
Date: Tue, 24 Jan 2017 17:05:17 +0100	[thread overview]
Message-ID: <1595128.WQAW59UAnQ@prime> (raw)
In-Reply-To: <1485272731.2398.15.camel@sdl.usu.edu>

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

Hey Jonathan,

On Tuesday, January 24, 2017 3:45:31 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?
> 
> I'd be happy to answer questions, but it would be best if those
> questions are directed to the list and my address is in the CC field.
>  That way I'll definitely see it and can answer.  If it just goes to
> the list in general I'll very likely miss the message.  Is that
> someting that could be added to the Wiki?

Hmm, you can add anything you want in the wiki, but it's unlikely someone will 
read it before asking here on the mailing list, at least to my personal 
experience. ;)

But if you commit to look into these issues, just try to catch the mails sent 
here to this mailing list - if you don't i'll try to forward them to you. :)

> > 
> >  * Do you plan to provide OpenWRT support as well? (This is more out
> > of 
> > curiosity)
> 
> I wasn't planning on OpenWRT support. What would be entailed? When I
> hear OpenWRT, I think of the firmware I can load onto my old Linksys
> WRT54G AP.  Would it simply be testing these changes on that device?

Basically we already have an OpenWRT/LEDE integration [1] which provides 
configuration options in a config file, which are parsed and applied etc.

Not sure if the ancient WRT54G is still even properly supported, but there are 
dozens of cheap and more moderns APs you can use it. But if you are not 
familiar with OpenWRT, don't worry, someone else can provide the integration 
if they need it. :)

Cheers,
     Simon

[1] https://github.com/openwrt-routing/packages/tree/master/alfred

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

  reply	other threads:[~2017-01-24 16:05 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
2017-01-24 15:45   ` Jonathan Haws
2017-01-24 16:05     ` Simon Wunderlich [this message]
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=1595128.WQAW59UAnQ@prime \
    --to=sw@simonwunderlich.de \
    --cc=Jonathan.Haws@sdl.usu.edu \
    --cc=b.a.t.m.a.n@lists.open-mesh.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox