-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Bump releases to version v0.7.2 (#69)
* Bump releases to version v0.7.2 * Auto generate Co-authored-by: metal-stack <[email protected]> Co-authored-by: Gerrit91 <[email protected]>
- Loading branch information
1 parent
0a24bfd
commit d22ea6a
Showing
2 changed files
with
3 additions
and
4 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -168,9 +168,8 @@ consolepassword: ... | |
If you want to access the firewall with SSH or have internet connectivity from the firewall and machine, you'll need to have a static route configured that points to the vagrant boxes of the leaf switches: | ||
|
||
```bash | ||
make route # shows you the route needed to access the network internet-vagrant-lab | ||
add this route to communicate with the virtual internet network 100.255.254.0/24 over leaf01 and leaf02 | ||
sudo ip r a 100.255.254.0/24 nexthop via 192.168.121.120 dev virbr0 nexthop via 192.168.121.132 dev virbr0 | ||
# Add the route to the network internet-vagrant-lab 100.255.254.0/24 via leaf01 and leaf02, whose IPs are dynamically allocated. Make sure there's no old route before execution. | ||
make route | ||
|
||
# Connect to the firewall | ||
ssh [email protected] | ||
|