# US 2005/0030906 A1 · System and method for configuring a computer network route

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2005/0030906 A1
- Document ID: US20050030906A1
- Status: Published application
- Kind: A1
- Application number: 10/830,199
- Filed: 2004-04-21
- Published: 2005-02-10
- Earliest claimed: 2003-08-08
- Inventors: Changjian Lou; Tang He
- Web page: https://patentgrep.com/patent/US20050030906A1

## CPC

- H04L 41/0879: {Manual configuration through operator}
- H04L 41/18: Delegation of network management function, e.g. customer network management [CNM]
- H04L 45/00: Routing or path finding of packets in data switching networks (routing or path finding in wireless networks H04W40/00)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A system (5) for configuring a computer network route includes a user interface for providing a configuration interface for a user, a configuration manager (52) for providing configuration services for the user interface, a routing information protocol (RIP) interface (54), a Zebra daemon (56) for managing a route, an RIP daemon (57) for performing RIP, and a kernel routing table (58) for recording routing information of the system. The daemon communicates with the configuration manager through the RIP interface, and communicates with the RIP daemon by exchanging information. The RIP daemon communicates with the configuration manager through the RIP interface. A related method for configuring a route is also provided.

## Claims

### Claim 1

A system for configuring a computer network route, the system comprising:
a user interface for providing a configuration interface for a user;
a configuration manager for providing configuration services for the user interface;
a routing information protocol (RIP) interface;
a managing daemon for managing a route, the managing daemon communicating with the configuration manager through the RIP interface;
an RIP daemon for performing RIP, the RIP daemon communicating with the configuration manager through the RIP interface; and
a kernel routing table for recording routing information of the system;
wherein the managing daemon communicates with the RIP daemon by exchanging information.

### Claim 2 (depends on 1)

The system as claimed in claim 1, wherein the user interface is a command line interface or a web interface.

### Claim 3 (depends on 1)

The system as claimed in claim 1, wherein the managing daemon is a Zebra daemon or a Gated daemon.

### Claim 4 (depends on 3)

The system as claimed in claim 3, wherein the managing daemon is used for updating the kernel routing table.

### Claim 5 (depends on 4)

The system as claimed in claim 4, wherein the managing daemon is used for redistributing the routes among different routing protocols.

### Claim 6 (depends on 1)

The system as claimed in claim 1, wherein the RIP daemon comprises a routing table.

### Claim 7 (depends on 6)

The system as claimed in claim 6, wherein the RIP daemon is used for transmitting updating route information periodically.

### Claim 8 (depends on 1)

The system as claimed in claim 1, wherein the RIP interface, the managing daemon and the RIP daemon communicate with one another through a UNIX domain socket.

### Claim 9

A method for configuring a computer network route, the method comprising the following steps:
(a) transmitting a command line to a configuration manager;
(b) determining whether there is a match between the command line and any of command lines registered in the configuration manager;
(c) ordering a routing information protocol (RIP) interface to transmit a message to a managing daemon or an RIP daemon if there is a match;
(d) receiving the message, and generating a response to the message; and
(e) returning an acknowledgement message to the RIP interface.

### Claim 10 (depends on 9)

The method as claimed in claim 9, further comprising the step of returning error information to a user interface if there is no match.

### Claim 11 (depends on 9)

The method as claimed in claim 9, further comprising the following steps before step (d):
(1) determining whether the managing daemon or the RIP daemon is free; and
(2) monitoring the managing daemon or the RIP daemon if the managing daemon or the RIP daemon is not free.

### Claim 12 (depends on 9)

The method as claimed in claim 9, further comprising after step (e) the step of obtaining acknowledgement information from the acknowledgement message, and forwarding the acknowledgement information to a user interface.
