RARP - Reverse Address Resolution Protocol¶
pcapkit.protocols.application.rarp.protocol contains
RARP only,
which implements an extractor for Reverse Address
Resolution Protocol (RARP) [*], whose structure is:
Octets |
Bits |
Name |
Description |
|---|---|---|---|
0 |
0 |
|
Hardware Type |
2 |
16 |
|
Protocol Type |
4 |
32 |
|
Hardware Address Length |
5 |
40 |
|
Protocol Address Length |
6 |
48 |
|
Operation |
8 |
64 |
|
Sender Hardware Address |
14 |
112 |
|
Sender Protocol Address |
18 |
144 |
|
Target Hardware Address |
24 |
192 |
|
Target Protocol Address |
Added in version 1.5.0: Moved here from pcapkit.protocols.link.rarp.
RARP and
DRARP derive from
Application as well as
ARP, so their layer is
'Application' (#719).
Removed in version 1.5.0: pcapkit.protocols.link.rarp, and the RARP and DRARP names
that pcapkit.protocols.link exported, with no alias (#719).
Removed in version 1.6.0: pcapkit.protocols.application.rarp.DRARP, with no alias. The class
moved to pcapkit.protocols.application.drarp.protocol, since a module holds
one protocol class, named after it (#2529).
- class pcapkit.protocols.application.rarp.protocol.RARP(file=None, length=None, **kwargs)[source]¶
Bases:
Application,ARPThis class implements Reverse Address Resolution Protocol.
RFC 1122 Section 1.1.3 lists RARP in the application layer, among the “support protocols, used for host name mapping, booting, and management”, while putting ARP in the Link Layer chapter at RFC 1122 Section 2.3.2 – two sibling protocols sharing one frame format, placed on function alone. Hence the two bases: the layer base
Applicationfirst, forlayer == 'Application', then the protocol family baseARPfor the shared parser. See Protocol Layer Placement.Note
The order is load-bearing, not stylistic.
ARP’s chain reachesLink, which owns__layer__, soclass RARP(ARP, Application)would report'Link'.The subpackage does not track the dispatch tier: RARP is dispatched from
Link.__proto__atReverse_Address_Resolution_Protocol, since an Ethernet frame is what carries it.
Footnotes