>> For reference, here's the valies I've managed to identify...
> Where do these numbers come from? (other than
> /usr/src/linux/include/linux/socket.h and
> /usr/include/socketbits.h...by-the-way, why are they defined,
> sometimes differently, in the two files?) Do we get numbers
> from IANA, or are these implementation specific?
Most of these were obtained from socket.h specifically, in which I
have used the identifier provided. I chose to label these 'possible
identifier' because I have seen conflicting identifiers for some of
them in the past.
The ones I listed under the 'identifier' column are those defined on
the system I am currently using, plus ax25 which I use regularly at
home, and that is all that separates the two columns.
>> Q> Modprobe Identifier Possible Identifier
>> Q> ~~~~~~~~~~~~ ~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~
>> Q> net-pf-1 unix
>> Q> net-pf-2 ipv4
>> Q> net-pf-3 ax25
>> Q> net-pf-4 ipx
>> Q> net-pf-5 appletalk
>> Q> net_pf_6 netrom
>> Q> net_pf_8 atmpvc
>> Q> net_pf_9 x25
>> Q> net_pf_10 ipv6
>> Q> net_pf_11 rose
>> Q> net_pf_12 decnet
>> Q> net_pf_13 netbeui
>> Q> net_pf_16 netlink
>> Q> net-pf-17 packet
>> Q> net_pf_18 ash
>> Q> net_pf_19 econet
>> Q> net_pf_20 atmsvc
>> Q> net_pf_22 sna
>> Q> net_pf_23 irda
> Additionally, I have seen and am using PF_KEY=15 (RFC2367).
> Currently, our PF_KEYv2 is part of the 'ipsec' module, but
> should be separated at some point into 'key' since it is a
> generic keying interface.
I deliberately omitted that one as it appears to have at least three
different names in the kernel sources, and I didn't plan on guessing
which was the correct one.
>> The 'possible identifier' column is where I have identified the
>> protocol being referred to, but have no info as to the actual
>> protocol identifier to use. Basically, if you have the relevant
>> protocol as a module for your current kernel, look for a module
>> with a name similar to those given, probably to be found in...
>> /lib/modules/`uname -r`/net/
> or: /lib/modules/`uname -r`/misc/
Quite possibly...
Best wishes from Riley.
+----------------------------------------------------------------------+
| There is something frustrating about the quality and speed of Linux |
| development, ie., the quality is too high and the speed is too high, |
| in other words, I can implement this XXXX feature, but I bet someone |
| else has already done so and is just about to release their patch. |
+----------------------------------------------------------------------+
* ftp://ftp.MemAlpha.cx/pub/rhw/Linux
* http://www.MemAlpha.cx/kernel.versions.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/