initial klm description
fix link to display filter reference
|Deletions are marked like this.||Additions are marked like this.|
|Line 7:||Line 7:|
|This protocol was developed at the same time as ["NLM"] and is very similar to ["NLM"].||This protocol was developed at the same time as ["NLM"] and is semi-similar to ["NLM"].|
|Line 28:||Line 28:|
|XXX - Add a simple example capture file to the SampleCaptures page and link from here. Keep it short, it's also a good idea to gzip it to make it even smaller, as Ethereal can open gzipped files automatically. Since this protocol only exists ontop of loopback one will have to create it on a host that allows capturing of loopback such as Linux.||attachment:SampleCaptures/klm.pcap.gz|
|Line 31:||Line 31:|
|A complete list of PROTO display filter fields can be found in the [http://www.ethereal.com/docs/dfref/PROTO/PROTO.html display filter reference]||A complete list of KLM display filter fields can be found in the [http://www.ethereal.com/docs/dfref/k/klm.html display filter reference]|
Kernel Lock Manager Protocol (KLM)
The KLM protocol is used to manage lock requests between the VFS layer in the kernel of a ["NFS"] host and the userspace lock manager daemon. This protocol is only used across the loopback interface and will never bee seen on a network.
This protocol was developed at the same time as ["NLM"] and is semi-similar to ["NLM"].
- ["UDP"]: KLM uses ["UDP"] as its transport protocol. There is no well known UDP port for KLM.
XXX - Add example traffic here as plain text or Ethereal screenshot).
The KLM dissector is fully functional.
There are no preferences for the KLM protocol itself, but since it shares the filehandle structure with ["NFS"] there are some ["NFS"] preferences related to filehandles that do affect the dissection of KLM. BR See ["NFS Preferences"]
Example capture file
A complete list of KLM display filter fields can be found in the [http://www.ethereal.com/docs/dfref/k/klm.html display filter reference]
Show only the KLM based traffic:
You cannot directly filter KLM while capturing. However, if you know the ["UDP"] port used (see above), you can filter on that one. KLM only exists ontop of the loopback interface so one can only capture KLM on a host that allows capturing of loopback.
A KLM specification does not exist, however most unixen do have an interface specification for the protocol in /usr/include/rpcsvc