You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: netbox-discovery-quickstart/README.md
+9-5Lines changed: 9 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,11 +21,7 @@ You will be able to run simple scripts to use both features of NetBox Discovery:
21
21
22
22
> [!TIP]
23
23
>
24
-
> The workshop assumes it is running on an internet accessible machine and it relies on the public IP for a lot of functionality
25
-
> This means that **it will not work on your local machine**, but we aim to add that possibility at a later stage. Please use a cloud VM for now.
26
-
27
-
> [!TIP]
28
-
>
24
+
> - The workshop can be ran on a server or virtual machine with a public or private ip. Please see the additional step for the latter option
29
25
> - We recommend using a machine with at least 4GB of RAM and 2 cores. If you're using a discount cloud or are going to run Cisco IOS images, we recommend at least 8GB of RAM and 4 cores.
30
26
> - The workshop has only been tested on Ubuntu 22.04. It _should_ work on other Linux distros but if you hit any problems please create an [issue](https://github.com/netboxlabs/netbox-learning/issues) in GitHub
31
27
> - Unfortunately MacOS is not supported. The workshop relies heavily on ContainerLab which does not have native support for MacOS
@@ -57,6 +53,14 @@ su - quickstart
57
53
58
54
### Generate and export the necessary environment variables for the quickstart
59
55
56
+
Optionally set a private IP. If this machine does not have a public ipv4 address assigned on a local interface, this option should be used.
57
+
58
+
Replace <myipaddress> with an ip address assigned to the local machine - eg: 10.1.1.1
59
+
60
+
```
61
+
export MY_EXTERNAL_IP=<ip address>
62
+
```
63
+
60
64
> [!TIP]
61
65
>
62
66
> `1_set_envvars.sh` writes the variables it generates to a file in the root directory called `environment`
0 commit comments