Skip to content
This repository has been archived by the owner on Dec 13, 2024. It is now read-only.

Commit

Permalink
Merge pull request #16 from HAW-RN/routing-protocol
Browse files Browse the repository at this point in the history
Routing protocol
  • Loading branch information
AnnsAnns authored Jun 10, 2024
2 parents f04fbdf + 8b1f7f8 commit c5911ef
Show file tree
Hide file tree
Showing 2 changed files with 7 additions and 8 deletions.
15 changes: 7 additions & 8 deletions protocol/04_routing_protocol.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Routing protocol (participants)
Bastian Basler, Tim Hagedorn, Ruben Marin Grez, Eike Balling
## Requirements
## Requirements (Bastian Basler)
#### Prerequisites
- Participants have to be in the same Network
- Participants must be able to send and receive packages via IPv4
Expand All @@ -16,7 +16,7 @@ Participants must be able to forward Messages
- The participants must form any partially meshed network
- Participants may send Messages to themselves

## Packet format
## Packet format (Tim Hagedorn)
### Header
See "Shared Header" section

Expand Down Expand Up @@ -50,8 +50,7 @@ See "Shared Header" section
]
}
```

## Packet Types
## Packet Types (Ruben Marin Grez)

Defined within the `type_id` field of the common header.

Expand All @@ -63,16 +62,16 @@ Defined within the `type_id` field of the common header.
| 5 | SCCR | Connection Check Reply |
| 6 | STU | Send Table Update (Send Routingtable) |

## Procedure
1. Participant A starts the Application and sets internal Table update Timer to 30 seconds
## Procedure (Eike Balling)
1. Participant A starts the Application and sets internal Table update Timer to 10 seconds
2. Participant B sends CR to Participant A and sends current Routingtable
3. Participant A accepts CR from Participant B and answers CRR and sends current Routingtable
4. Participant A updates Routingtable based on the received Table
5. After A´s Timer expired A sends SCC to all next entrances in its Routingtable
6. Participant A updates Routingtable based on received SCCRs
1. If SCCR isn´t received after one second Participant A sets Hop Count to 16 (Poison Reverse)
1. If SCCR isn´t received after one second Participant A sets Hop Count to 32 (Poison Reverse)
7. Participant A sends STU to all active Participants
8. Participant A resets Timer to 30 seconds
8. Participant A resets Timer to 10 seconds

## Example
![Logo](./images/Routing_Protokoll_Sequenz_Diagram.png)
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

0 comments on commit c5911ef

Please sign in to comment.