From: Jamal Hadi Salim <jhs@mojatatu•com>
To: Antonio Quartulli <antonio@open-mesh•com>
Cc: "David S. Miller" <davem@davemloft•net>,
"netdev@vger•kernel.org" <netdev@vger•kernel.org>
Subject: Re: Using skb->mark outside netfilter
Date: Tue, 07 May 2013 09:30:04 -0400 [thread overview]
Message-ID: <518901DC.2050100@mojatatu.com> (raw)
In-Reply-To: <20130507132326.GB2729@open-mesh.com>
On 13-05-07 09:23 AM, Antonio Quartulli wrote:
> The mark is not really encoded in the batman header.
>
> Each node is configured with a mark value (the values have to be the same on
> everynode in order to make the mechanism work correctly), then batman-adv will
> advertise to the rest of the mesh which host is sending marked packets.
>
[..]
> Receiving nodes will then restore the mark in the skb each time it is coming from
> one of those advertised hosts.
>
I see - so some control "protocol" will be used to advertise the mark
and which host will use such a mark? Or are you saying some admin is
going around and configuring 100 batman nodes? ;->
Note: I have no freaking clue in regards to batman or its usage.
> A future feature may consists in carrying the mark directly into the header so
> that batman-adv itself does not have to take care about the meaning of such
> value but will just carry it (we still have to think about it...it is just an
> idea now)
>
I think that may be more interesting because it may allow you to use
many different marks with many different meanings. It doesnt disqualify
a control protocol advertising the mark.
cheers,
jamal
next prev parent reply other threads:[~2013-05-07 13:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 17:41 [PATCH 0/3] bridge: implement restricted forwarding policy Antonio Quartulli
2013-04-08 17:41 ` [PATCH 1/3] if.h: add IFF_BRIDGE_RESTRICTED flag Antonio Quartulli
2013-04-08 18:58 ` Stephen Hemminger
2013-04-09 6:33 ` Antonio Quartulli
2013-04-09 7:56 ` Antonio Quartulli
2013-04-09 12:57 ` Jamal Hadi Salim
2013-04-09 13:51 ` Antonio Quartulli
2013-04-09 15:49 ` Jamal Hadi Salim
2013-04-10 16:54 ` Antonio Quartulli
2013-04-10 20:46 ` Stephen Hemminger
2013-04-11 10:56 ` Antonio Quartulli
2013-04-11 11:03 ` Jamal Hadi Salim
2013-04-08 17:41 ` [PATCH 2/3] sk_buff: add bridge_restricted flag Antonio Quartulli
2013-04-08 17:41 ` [PATCH 3/3] bridge: implement restricted port forwarding policy Antonio Quartulli
2013-05-06 18:48 ` Using skb->mark outside netfilter (was: [PATCH 0/3] bridge: implement restricted forwarding policy) Antonio Quartulli
2013-05-07 13:04 ` Using skb->mark outside netfilter Jamal Hadi Salim
2013-05-07 13:23 ` Antonio Quartulli
2013-05-07 13:30 ` Jamal Hadi Salim [this message]
2013-05-07 14:17 ` Antonio Quartulli
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=518901DC.2050100@mojatatu.com \
--to=jhs@mojatatu$(echo .)com \
--cc=antonio@open-mesh$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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