How do I write a RIP routing information protocol code where is the standard format content defined?

[bit57]

I want to write a project on the IP Routing Information Protocol, but I don't know the format and format definitions of RIP (Routing Information Protocol), OSPF (Open Shortest Path First) and BGP (Border Gateway Protocol) and the official definition of the protocol content. Find a https://www.ietf.org/rfc/rfc2082.txt but there is no detailed format content, how to write one? In which directory and file the code of the Linux routing protocol can you refer to the trouble and recommend some open source projects of this IP information protocol routing

Я хочу написать проект по протоколу IP Routing Information Protocol, но я не знаю формата и определения формата RIP (Routing Information Protocol), OSPF (Open Shortest Path First) и BGP ( Border Gateway Protocol) и официальное определение содержания протокола. Найти https://www.ietf.org/rfc/rfc2082.txt но нет подробного форматного контента, как его написать? В каком каталоге и файле код протокола маршрутизации Linux вы можете сослаться на проблему и порекомендовать некоторые проекты с открытым исходным кодом этой маршрутизации информационного протокола IP

 

[weaver]

These RFCs documents contain the detailed format and format definitions of the protocols.

• RIP: https://www.ietf.org/rfc/rfc2082.txt
• OSPF: https://www.ietf.org/rfc/rfc2328.txt
• BGP: https://www.ietf.org/rfc/rfc4271.txt

/usr/src/linux/net/ipv4/route.c

GitHub - gtungatkar/RIPv1: Routing Information Protocol version 1

Routing Information Protocol version 1. Contribute to gtungatkar/RIPv1 development by creating an account on GitHub.

github.com

Look

GitHub - fingon/bird-ext-lsa: Experimental BIRD version with support for OSPFv3 LSA types that are managed externally. As a proof of concept, OSPFv3 autoconfiguration and OSPFv3 prefix assignment drafts are implemented using that idea.

Experimental BIRD version with support for OSPFv3 LSA types that are managed externally. As a proof of concept, OSPFv3 autoconfiguration and OSPFv3 prefix assignment drafts are implemented using th...

github.com

RIP

bird-ext-lsa/proto/rip at master · fingon/bird-ext-lsa

Experimental BIRD version with support for OSPFv3 LSA types that are managed externally. As a proof of concept, OSPFv3 autoconfiguration and OSPFv3 prefix assignment drafts are implemented using th...

github.com

OSPF

bird-ext-lsa/proto/ospf at master · fingon/bird-ext-lsa

Experimental BIRD version with support for OSPFv3 LSA types that are managed externally. As a proof of concept, OSPFv3 autoconfiguration and OSPFv3 prefix assignment drafts are implemented using th...

github.com

BGP

bird-ext-lsa/proto/bgp at master · fingon/bird-ext-lsa

Experimental BIRD version with support for OSPFv3 LSA types that are managed externally. As a proof of concept, OSPFv3 autoconfiguration and OSPFv3 prefix assignment drafts are implemented using th...

github.com

and

Build software better, together

GitHub is where people build software. More than 100 million people use GitHub to discover, fork, and contribute to over 330 million projects.

github.com

Build software better, together

GitHub is where people build software. More than 100 million people use GitHub to discover, fork, and contribute to over 330 million projects.

github.com

Build software better, together

GitHub is where people build software. More than 100 million people use GitHub to discover, fork, and contribute to over 330 million projects.

github.com

enjoy

 

[Dread Pirate Roberts]

you could check source of the routing tools such as quagga.net

 

[bit57]

这些 RFC 文档包含协议的详细格式和格式定义。

• 撕裂：https://www.ietf.org/rfc/rfc2082.txt
• OSPF：https://www.ietf.org/rfc/rfc2328.txt
• BGP： https://www.ietf.org/rfc/rfc4271.txt

https://github.com/gtungatkar/RIPv1
看
https://github.com/fingon/bird-ext-lsa

把
https://github.com/fingon/bird-ext-lsa/tree/master/proto/rip

奥普夫
https://github.com/fingon/bird-ext-lsa/tree/master/proto/ospf

边界网关协议
https://github.com/fingon/bird-ext-lsa/tree/master/proto/bgp

和
[URL un展开=“true”]https://github.com/search?q=Routing+Information+Protocol&type=[/URL]
https://github.com/search?q=Open+Shortest+Path+First
[URL un展开=“true”]https://github.com/search?q=Border+Gateway+Protocol[/URL]


享受

谢谢

 

[W8ve]

To write a RIP (Routing Information Protocol) code, you can start by understanding the standard format and content defined for RIP. Since you mentioned that the provided link does not have detailed format content, we will need to refer to other resources.

Here's a step-by-step plan to help you proceed:

1. Research RIP Protocol:
   
   • Gather information on RIP from multiple sources, including RFC documents, networking textbooks, and online tutorials.
   • Study the basic principles, message formats, packet structures, and algorithms used in RIP.
2. Analyze Existing Implementations:
   
   • Look for existing open-source projects that implement RIP, OSPF, or BGP.
   • Explore their code repositories to understand how they handle routing protocols.
   • Analyze the relevant files and directories that deal with routing protocols.
3. Determine Project Scope:
   
   • Decide on the scope of your project, such as building a RIP implementation from scratch or extending an existing implementation.
   • Define the specific features and functionalities you plan to include in your project.
4. Choose Programming Language:
   
   • Select a programming language suitable for network programming. Common choices include C, C++, Python, or Java.
   • Consider the availability of libraries or frameworks that can assist with network-related tasks.
5. Plan Code Organization:
   
   • Decide on the directory and file structure for your project.
   • Identify the files that will handle RIP-specific functionality and routing-related operations.
   • Define modules or classes to encapsulate different aspects of the protocol.
6. Define Data Structures:
   
   • Determine the data structures required to store routing tables, neighbor information, and routing updates.
   • Design data structures that can efficiently represent and manipulate routing information.
7. Implement RIP Protocol:
   
   • Start coding the RIP protocol according to the specifications you gathered.
   • Implement the message formats, packet parsing, and generation of routing updates.
   • Handle the exchange of RIP messages with neighboring routers.
8. Test and Debug:
   
   • Create test cases to verify the correctness and efficiency of your implementation.
   • Test the RIP code by simulating network scenarios and evaluating the routing behavior.
   • Debug any issues or errors encountered during testing.
9. Document and Refine:
   
   • Document your code to make it easier for others (and yourself) to understand.
   • Refine your implementation based on feedback, performance analysis, and additional research.
   • Consider optimizing the code for better performance if necessary.