linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Michal Kazior <michal.kazior@tieto.com>, Felix Fietkau <nbd@openwrt.org>
Cc: Grzegorz Bajorski <grzegorz.bajorski@tieto.com>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [RFC] mac80211: add extap functionality
Date: Tue, 19 Apr 2016 11:11:43 +0200	[thread overview]
Message-ID: <1461057103.2766.15.camel@sipsolutions.net> (raw)
In-Reply-To: <CA+BoTQnf953+s++Wiug=BgEw2Ahu7cN1fbatmgyWi_6iAg_v2Q@mail.gmail.com> (sfid-20160418_132353_986196_638EA8F9)

On Mon, 2016-04-18 at 13:23 +0200, Michal Kazior wrote:

> You can't really implement complete IPv6 support in relayd though.
> Link-local routing is forbidden by the spec explicitly and a patch
> I've cooked up was rejected[1].
> 
> I guess this leaves either the kernel's wireless stack to take up the
> task or a special link device (for which I'm soliciting feedback now
> [2]).
> 

I think you'll probably have to cook up a simple patch to get that
question in [2] taken seriously :)

How much of that could be done with nftables btw?

johannes

  reply	other threads:[~2016-04-19  9:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-17 11:55 [RFC] mac80211: add extap functionality Grzegorz Bajorski
2016-02-17 16:55 ` Felix Fietkau
2016-02-18 13:36   ` Grzegorz Bajorski
2016-02-18 14:08     ` Felix Fietkau
2016-02-19 12:05       ` Grzegorz Bajorski
2016-02-19 16:24         ` Felix Fietkau
2016-02-22 13:50           ` Grzegorz Bajorski
2016-04-18 11:23   ` Michal Kazior
2016-04-19  9:11     ` Johannes Berg [this message]
2016-04-19 10:22       ` Michal Kazior
2016-04-19 11:02         ` Johannes Berg
2016-04-19 11:30           ` Michal Kazior

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=1461057103.2766.15.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=grzegorz.bajorski@tieto.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=michal.kazior@tieto.com \
    --cc=nbd@openwrt.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;
as well as URLs for NNTP newsgroup(s).