XORP click Configuration

Chapter 5 translation of XORP User Manual

Tag: xorp fea click

5.1 forwarding engine (forwarding engine)

The forwarding engine is an integral part of a router. It collects packets and forwards the packets from one interface to another. In XORP, the forwarding engine can be the forwarding engine, click forwarding engine, or hardware forwarding engine in UNIX systems.

In any vro, enabling or disabling the forwarding function is always desirable. For example, a vro can be set to forward only IPv6 packets instead of IPv4 packets, or to forward only unicast packets instead of multicast packets. XORP provides the function of configuring the diversity of forwarding functions.

In XORP, the term 'fea' refers to forwarding engine processing action. The term 'mfea' refers

Multicast forwarding engine modify action. The term 'Transport action' indicates a high-level configuration interface, which does not need to consider whether the forwarding engine is provided (including software in the operating system or hardware ).

5.2 forwarding engine configuration

In XORP routers, the forwarding function must be explicitly used; otherwise, packets cannot be forwarded. Forwarding can be divided into unicast and multicast packets, IPv4 and IPv6 forwarding. Additionally, multicast interfaces/vifs need to be explicitly enabled

Individually, and certain special-purpose forwarding functionality
Can also be enabled for multicast. (I don't know how to translate ...)

5.2.1 configuration syntax

FEA {
Targetname: TXT // The Name Of The FEA instance. The default value is fea. Do not modify it.
Unicast-forwarding4 {
Disable: bool // The default value is false.
Table-ID: u32 // specifies the ID of the IPv4 unicast forwarding table. If this item is not specified, FEA uses the default table ID. note: not all systems support multiple forwarding tables. Currently, multiple forwarding tables only exist in Linux.
Forwarding-entries {// specify attributes of IPv4 forwarding objects
Retain-on-startup: bool // when FEA is started, whether to delete XORP's IPv4 unicast forwarding entity (if it exists after the previous operation) defaults to false.
Retain-on-Shutdown: bool // when FEA is disabled, the same as above

// Note: retain-on-startup and retain-on-Shutdown only prevent FEA from deleting the forwarding entity. They cannot be deleted by rib or any unicast routing protocol.
}
}
Unicast-forwarding6 {// same as IPv4
Disable: bool
Table-ID: u32
Forwarding-entries {
Retain-on-startup: bool
Retain-on-Shutdown: bool
}
}
Click {// configure the forwarding path of the click
Disable: bool // The default value is false.
Duplicate-routes-to-kernel: bool // controls whether the XORP route table added to the click operation is also added to the system kernel. The default value is false.
Kernel-click {// used to configure the kernel-level click
Disable: bool // whether to enable kernel-level click forwarding. The default value is false.
Install-on-startup: bool // specifies whether to install kernel-level click at startup. The default value is false.
Kernel-click-modules: Text // list of the modules specified for click, which are separated by colons. These modules must have been loaded to the kernel. By default, the list of modules required by the Linux system is:"

"/Usr/local/click/linuxmodule/proclikefs. O:/usr/local/click/linuxmodule/click. O"

", For the FreeBSD system, the only required module is click. Ko, so this item is"/path/to/click. Ko"
Mount-Directory: Text // directory address, used to mount the click File System. The default value is/click.
Kernel-click-config-generator-file: Text // The default value is "/usr/local/XORP/FEA/xorp fea click config generator ". Program It is used to generate kernel-level click Configuration from XORP configuration.
}
User-click {// configure user-level click
Disable: bool // configure whether to enable user-level click forwarding. The default value is false.
Command-file: Address of the text // click binary program. The default value is "/usr/local/bin/click"
Command-extra-arguments: Text // specifies the running parameters of the preceding program. The default value is-R. Note: do not include-P <port>, because it will conflict with extra FEA Parameters
Command-execute-on-startup: bool // run the preceding command at startup. The default value is false.
Control-Address: IPv4-addr // an IPv4 address used to accept connections with the configured click, 127.0.0.1 by default
Control-socket-Port: uint (1 .. 65535) // configure the click port. The default value is 13000.
Startup-config-file: Address of the text // click configuration file. The default value is "/dev/null"
User-click-config-generator-file: Text // program address. This program can generate user-level click Configuration Based on XORP configuration, the default value is "/usr/local/XORP/FEA/xorp fea click config generator"
} // Note: kernel-level and user-level click operations can be performed simultaneously. In this case, kernel-click-config-generator-file and user-click-config-generator-file must point to different files.
}
}

// User-level click does not require a File System

plumbing {//
mfea4 {// configure IPv4 multicast packet forwarding
Disable: bool // whether to enable IPv4 multicast packet forwarding, the default value is false
interface text {// specify an interface for forwarding IPv4 multicast packets. Each used interface must be explicitly listed. Additionally, when configuring the PIM-SM, register_vif needs to be configured with
VIF text {// an interface for forwarding IPv4 multicast packets
Disable: bool // The default value is false
}< BR >}< br> interface register VIF {
VIF register VIF {
Disable: bool
}< BR >}< br> traceoptions {// configure the debug option
flag all {
Disable: bool // The default value is false
}< BR >}< br> mfea6 {// IPv6, which is the same as IPv4
Disable: bool
interface text {
VIF text {
Disable: bool
}< BR >}< br> interface register VIF {
VIF register VIF {
Disable: bool
}< BR >}< br> traceoptions {
flag {
all {
Disable: bool
}< BR >}