From: Simon Oosthoek <simon.oosthoek@ti-wmc.nl>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Herman Elfrink <herman.elfrink@ti-wmc.nl>
Subject: Re: [ANNOUNCE] FLAME: external kernel module for L2.5 meshing
Date: Tue, 23 May 2006 16:41:48 +0200 [thread overview]
Message-ID: <44731F2C.2010109@ti-wmc.nl> (raw)
In-Reply-To: <1148395738.25255.68.camel@localhost.localdomain>
Alan Cox wrote:
> On Maw, 2006-05-23 at 16:07 +0200, Herman Elfrink wrote:
>> FLAME uses an unofficial protocol number (0x4040), any tips on how to
>> get an official IANA number would be highly appreciated.
>>
>
> Ethernet protocol number I assume you mean. If so this at least used to
> be handled by the IEEE, along with ethernet mac address ranges.
>
Yes ethernet protocol (it's below IP level), I didn't realise that IEEE
also handled the portnumbers. I'll check the ieee website to see how it
works, tnx!
/Simon
next prev parent reply other threads:[~2006-05-23 14:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-23 14:07 [ANNOUNCE] FLAME: external kernel module for L2.5 meshing Herman Elfrink
2006-05-23 14:38 ` Stephen Hemminger
2006-05-23 14:51 ` Simon Oosthoek
2006-05-23 15:09 ` Steven Rostedt
2006-05-23 15:20 ` Alan Cox
2006-05-23 14:48 ` Alan Cox
2006-05-23 14:41 ` Simon Oosthoek [this message]
2006-05-23 14:55 ` Erik Mouw
2006-05-23 15:00 ` Simon Oosthoek
2006-05-23 15:14 ` Alan Cox
2006-05-30 6:42 ` Herman Elfrink
2006-05-30 8:43 ` Herman Elfrink
2006-05-23 16:43 ` Stephen Hemminger
2006-05-23 17:43 ` Simon Oosthoek
2006-05-24 18:43 ` jamal
2006-05-25 10:53 ` Simon Oosthoek
2006-05-25 15:38 ` jamal
2006-05-30 7:01 ` Herman Elfrink
2006-05-24 20:50 ` Pavel Machek
2006-05-25 9:36 ` Simon Oosthoek
2006-05-30 8:29 ` Herman Elfrink
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=44731F2C.2010109@ti-wmc.nl \
--to=simon.oosthoek@ti-wmc.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=herman.elfrink@ti-wmc.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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.