mir/network-examples
2
0
Fork 0
mirror of https://github.com/knorrie/network-examples synced 2025-08-30 14:08:36 +00:00
Code Issues Releases Wiki Activity

Copy paste some changed output of commands...

Browse Source 
...so that it's more look-a-like again.
This commit is contained in:
Hans van Kranenburg
2021-01-27 21:13:44 +01:00
parent 8a57ef7303
commit bda997f48f
2 changed files with 6 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
birdhouse-intro/README.md
View File

@@ -19,12 +19,8 @@ Since the Birdhouse Factory people also like internet technology, they combined
After following the [tutorial to set up a lab environment](/lxcbird/README.md) we end up with the first container, "birdbase". Make sure this birdbase container is stopped (by using `lxc-stop`, or typing `halt` on the container prompt after using `lxc-attach`), so it can be cloned into new ones. After following the [tutorial to set up a lab environment](/lxcbird/README.md) we end up with the first container, "birdbase". Make sure this birdbase container is stopped (by using `lxc-stop`, or typing `halt` on the container prompt after using `lxc-attach`), so it can be cloned into new ones.
lxcbird:/var/lib/lxc 0-# lxc-ls --fancy lxcbird:/var/lib/lxc 0-# lxc-ls --fancy
NAME STATE IPV4 IPV6 AUTOSTART NAME STATE AUTOSTART GROUPS IPV4 IPV6 UNPRIVILEGED
---------------------------------------- birdbase STOPPED 0 - - - false
.git STOPPED - - NO
birdbase STOPPED - - NO
Heh, `lxc-ls` is not that clever, and also thinks my git repository is a container. Oh well...
Let's create some of the systems shown in the network picture: Let's create some of the systems shown in the network picture:

8
lxcbird/README.md
View File

@@ -194,19 +194,19 @@ Now, let's try to start it and see what happens!
lxcbird:/var/lib/lxc/birdbase 0-# lxc-attach -n birdbase lxcbird:/var/lib/lxc/birdbase 0-# lxc-attach -n birdbase
root@birdbase:/# root@birdbase:/#
root@birdbase:/# ip a root@birdbase:/# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever valid_lft forever preferred_lft forever
inet6 ::1/128 scope host inet6 ::1/128 scope host
valid_lft forever preferred_lft forever valid_lft forever preferred_lft forever
215: vlan10: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 7: vlan10@if8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 02:00:c6:33:64:fe brd ff:ff:ff:ff:ff:ff link/ether ce:21:b1:f4:b8:c5 brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet 198.51.100.254/24 brd 198.51.100.255 scope global vlan10 inet 198.51.100.254/24 brd 198.51.100.255 scope global vlan10
valid_lft forever preferred_lft forever valid_lft forever preferred_lft forever
inet6 2001:db8:1998::fe/120 scope global inet6 2001:db8:1998::fe/120 scope global
valid_lft forever preferred_lft forever valid_lft forever preferred_lft forever
inet6 fe80::c6ff:fe33:64fe/64 scope link inet6 fe80::cc21:b1ff:fef4:b8c5/64 scope link
valid_lft forever preferred_lft forever valid_lft forever preferred_lft forever
Let's verify if we have proper outgoing network connectivity! Let's verify if we have proper outgoing network connectivity!