mirror of
https://github.com/knorrie/network-examples
synced 2025-08-29 21:48:22 +00:00
Link pages to each other
This commit is contained in:
parent
e763a2ac4b
commit
3b7fc81658
@ -116,3 +116,5 @@ To finish this tutorial:
|
||||
* Create a third container, the webshop server, and configure it. Confirm you can reach it from weaver, by running a SimpleHTTPServer with python (`python -m SimpleHTTPServer`) and pointing wget to it from weaver. You should see the outside IPv4 address of sparrow as source address of the request because of the NAT. Also, because of the NAT, the webshop server does not need to know a route to the `10.1.60.0/24` network, because it's hidden behind sparrow.
|
||||
|
||||
That's basically it. As you can see, when you get the hang of this, it's instantly also getting extremely boring to do the configuration every time. For later tutorials, I'll make sure all files that make up the starting point of the configuration are available to simply copy into the newly cloned containers.
|
||||
|
||||
Next up: [Meanwhile at the Birdhouse Factory...](/birdhouse-vlans-vpn/README.md)
|
||||
|
@ -295,3 +295,5 @@ Finally, we can check that git only wants to store our bird and network configur
|
||||
[...]
|
||||
|
||||
Right! As you might notice, there are "end-hosts" in the drawing on top of this page, and we just configured the base container to start bird and enable IP forwarding. While this is not needed, or wanted for the end host containers, I don't really care, because it will not influence the working of the test environment, as bird has no configuration, end hosts will not attract traffic that's not for themselves. However, if you like, you can create two different containers to clone from, one for a router, and one for an end host.
|
||||
|
||||
Let's head over to the next page to [meet the Birdhouse Factory network](/birdhouse-intro/README.md)!
|
||||
|
Loading…
x
Reference in New Issue
Block a user