Ipv4
[Node]
Access to the Ipv4 forwarding table, interfaces, and configuration.
More...
Collaboration diagram for Ipv4:
|
This class defines the API to manipulate the following aspects of the Ipv4 implementation:
- set/get an Ipv4RoutingProtocol
- register a NetDevice for use by the Ipv4 layer (basically, to create Ipv4-related state such as addressing and neighbor cache that is associated with a NetDevice)
- manipulate the status of the NetDevice from the Ipv4 perspective, such as marking it as Up or Down,
- adding, deleting, and getting addresses associated to the Ipv4 interfaces.
- exporting Ipv4 configuration attributes
Each NetDevice has conceptually a single Ipv4 interface associated with it (the corresponding structure in the Linux Ipv4 implementation is struct in_device). Each interface may have one or more Ipv4 addresses associated with it. Each Ipv4 address may have different subnet mask, scope, etc., so all of this per-address information is stored in an Ipv4InterfaceAddress class (the corresponding structure in Linux is struct in_ifaddr)
Ipv4 attributes such as whether IP forwarding is enabled and disabled are also stored in this class
TO DO: Add API to allow access to the Ipv4 neighbor table
- See also:
- Ipv4RoutingProtocol
