Skip navigation
Banner: skynetworks

RIPv1,v2 Interface Usage

RIPv1,v2 Interface Usage

 

Contents

 [hide]

 

[edit]

IkarusOS RIPv1,v2 Interface Usage


You will need 1 device setted up with latest Ikarus O.S version(no bridge mode).

[edit]

INMS Configuration Field Screenshots

Below you can see 2 screenshots of the INMS containing all possible configuration fields:

Main Tab - Protocol Tab:

 

Main Tab - Redistribute Tab:

 
[edit]

INMS Configuration Field Usage

Below you can find an explanation of the INMS RIP configuration fields.

Main Tab:

INMS field: Enable... Usage: Enables the overall RIPd process.

INMS field: State: Usage: Assigns the RIPd deamon onto the selected interface.

INMS field: Send Version: Usage: Selects the version of RIP to send RIP requests.

INMS field: Receive Version: Usage: Selects the version of RIP to reply to RIP requests.

INMS field: Connectivity: Usage: Selects the operation mode of RIPd deamon.
Hint: RIP classifies routers as active and passive (silent). Active routers advertise their routes (reachability information) to others. Passive routers listen and update their routes based on advertisements but do not advertise. Typically, routers run RIP in active mode, while hosts use passive mode.

INMS field: Auth Type: Usage(RIPv2 only): Allows packets to be authenticated via either an insecure plain text password, included with the packet, or via a more secure MD5 based HMAC (keyed-Hashing for Message AuthentiCation).
Hint: Enabling authentication prevents routes being updated by unauthenticated remote routers, but still can allow routes (I.e. the entire RIP routing table) to be queried remotely, potentially by anyone on the internet, via RIPv1.

INMS field: Password: Usage: Password input text field.

INMS field: Split Horizon Usage: Enables the Split Horizon option.
Hint: This is simply data suppression. It works by not sending updates about networks it learned out the interface through which it learned those networks.

INMS field: Poison Reverse Usage: Configures the Split Horizon option to operate with Poison Reverse option as well.
Hint: When sending updates out an interface, designate any networks you learned from that interface unreachable.

In particular, it is never useful to claim reachability for a destination network to the neighbor(s) from which the route was learned. Split horizon is a scheme for avoiding problems caused by including routes in updates sent to the router from which they were learned. The simple split horizon scheme omits routes learned from one neighbor in updates sent to that neighbor whileSplit horizon with poisoned reverse includes such routes in updates, but sets their metrics to infinity.

Protocol Tab:

INMS field: Update Usage: Sets the autoupdate timer.
Hint: The router will send its entire route table to every neighbor it has.

INMS field: Timeout Usage: Sets the expiration timer.
Hint: If a route gets to a certain configurable age, the router will think the device from which it learned that route has gone away, thus we flush it. Note, when a route expires, it is NOT removed from the table. It has its metric set to 16 or unreachable.

INMS field: Garbager Usage: Sets the garbage collection timer.
Hint: When a route hits this timer, it is indeed removed from the table.

INMS field: IP (neighbors) Usage: Inserts/removes neighbors' IP addresses 
Hint: When a neighbor doesn't understand multicast, this command is used to specify neighbors. In some cases, not all routers will be able to understand multicasting, where packets are sent to a network or a group of addresses. In a situation where a neighbor cannot process multicast packets, it is necessary to establish a direct link between routers. The neighbor command allows the network administrator to specify a router as a RIP neighbor.

Redistribute Tab:

INMS field: Connected Usage: Redistributes connected routes into the RIP tables. This command redistributes connected of the interface which RIP is disabled. The connected route on RIP enabled interface is announced by default.

INMS field: Static Usage: Redistributes routing information from static route entries into the RIP tables.

INMS field: Connected Usage: Redistributes routing information from kernel route entries into the RIP tables.