sendnrw/netbird-docs
2
0
Fork 0
mirror of https://github.com/netbirdio/docs.git synced 2026-04-22 02:16:37 +00:00
Code Issues Packages Projects Releases Wiki Activity

improves initial new routes documentation

Browse Source
This commit is contained in:
Marco Garcês
2024-12-16 11:12:02 +00:00
parent 965a078524
commit 707b5d487d
1 changed files with 18 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
src/pages/how-to/new-network-concept.mdx
View File

@@ -4,6 +4,8 @@ On `v0.35.0` we've introduced a new concept for the Network object, where we've
You can now create a **Network** which contain access to other resources, such as single IP addresses, full subnets addresses and domain names. This new concept allows you to manage all the network configurations in a single place, making it easier to manage and understand your network resources.
**TO REVIEW** other old concept still supports site to site, exit routes. It will be deprecated in the future, and the new concept will take precedence. Also, older routes created in the old concept will be migrated to the new concept.
## Concepts
### Networks
Networks allow you to group multiple resources in the same location. You can create a network and add multiple resources to it, such as single IP addresses, full subnets addresses and domain names. This is also the place where you can assign routing peers to your network, allowing you to route packets between your NetBird peers and your other networks.
@@ -12,10 +14,23 @@ Networks allow you to group multiple resources in the same location. You can cre
### Routing Peers
**Routing Peers** are the peers that will route packets between your NetBird peers and your other networks. You can assign a routing peer to a **Network**, and all the peers connected to this routing peer will be able to send traffic to all the **Resources** in this **Network**.
## Practical examples
Let's say you your company has 2 Office locations, one in Berlin (subnet `10.10.0.0/16`) and another in London (subnet '10.20.0.0/16'), a database running on a AWS EC2 instance, with internal IP address of 172.20.0.46 (inside VPC subnet `172.20.0.0/22`) and finally a domain name `intranet.mycompany.com` that you want to route through a specific location.
## Practical example
### Scenario
Let's say you your company has two office locations, one in Berlin (subnet `10.10.0.0/16`) and another in London (subnet `10.20.0.0/16`), a database running on a AWS EC2 instance, with internal IP address of `172.20.0.46` (inside VPC subnet `172.20.0.0/22`) and finally a domain name `intranet.mycompany.com` that is only accessible from within the offices.
In order to create an object that contains all these resources, you'll need to make sure you have at least one NetBird peer in each of your locations; these peers will be assigned as routing peers to your **Network**. Let's assume these peers are named `berlin-router-1`, `london-router-1` and `aws-router-1`, and they are inside their respective subnets and belong the the Peer Group `mycompany-routers`.
### Steps
1. Create a new **Network** object named `MyCompany Access`.
Navigate to `Networks` > `Networks`, and click `Add Network`. Fill in the name and description of the network, and click `Add Network`.
2. A pop-up will show up, asking to "Add a router to 'MyCompany Access'", You can add an individual `Routing Peer` or a `Peer Group`. In this case, you can select the `mycompany-routers` group in `Peer Group`. Click `Add Router`.
3. Now a pop-up will show up, asking to "Add a resource to 'MyCompany Access'". You can add a single IP address, a subnet or a domain name. In this case, you can add the following resources:
- `10.10.0.0/16`
- `10.20.0.0/16`
- `172.20.0.46`
- `intranet.mycompany.com`
In order to create a network that contains all these resources, you'll need to make sure you have at least one NetBird peer in each of your locations; these peers will be assigned as routing peers to your **Network**.
{/*
NetBird provides fast and reliable end-to-end encryption between peers in your network. You can install the agent on every desktop, VM, container, or physical server and have a fast, secure peer-to-peer mesh network. That is the desired configuration, but some cases do not allow for agent installation or can slow down migration from legacy systems: