From: Johannes Berg <johannes@sipsolutions.net>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: Felix Fietkau <nbd@openwrt.org>,
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 13:02:27 +0200 [thread overview]
Message-ID: <1461063747.2766.22.camel@sipsolutions.net> (raw)
In-Reply-To: <CA+BoTQ=Nw_pW3xk_zkRGw=kTXcfin8Py_xo+WMGsdLcgUiNV4Q@mail.gmail.com> (sfid-20160419_122209_567227_77BEBD32)
> > How much of that could be done with nftables btw?
> I'm not sure if I follow. Do you mean what I've been able to do with
> relayd until now? Without link-local ipv6 routing DHCPv6 is broken
> (could probably addressed with DHCPv6 Relay to a certain degree) and
> RS/RA may not work (if it propagates fe80:: routes). Also apps that
> rely on fe80:: socket binding/addressing will fail.
Ok, so that makes sense I guess - but you were speaking of some packet
mangling etc. and I was wondering if the nftables virtual machine could
actually do something like that.
johannes
next prev parent reply other threads:[~2016-04-19 11:02 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
2016-04-19 10:22 ` Michal Kazior
2016-04-19 11:02 ` Johannes Berg [this message]
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=1461063747.2766.22.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 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.