troubeshooting: fix lint errors

This commit is contained in:
rebortg 2020-12-11 22:44:17 +01:00
parent ac19aa7518
commit 74b8c6d63a

View File

@ -160,9 +160,12 @@ Neighbor Discovery
Interface names
***************
If you find the names of your interfaces have changed, this could be because your MAC addresses have changed.
If you find the names of your interfaces have changed, this could be because
your MAC addresses have changed.
* For example, you have a VyOS VM with 4 Ethernet interfaces named eth0, eth1, eth2 and eth3. Then, you migrate your VyOS VM to a different host and find your interfaces now are eth4, eth5, eth6 and eth7.
* For example, you have a VyOS VM with 4 Ethernet interfaces named
eth0, eth1, eth2 and eth3. Then, you migrate your VyOS VM to a different
host and find your interfaces now are eth4, eth5, eth6 and eth7.
One way to fix this issue **taking control of the MAC addresses** is:
@ -174,18 +177,24 @@ If you find the names of your interfaces have changed, this could be because you
Take note of MAC addresses.
Now, in order to update a MAC address in the configuration, run this command specifying the interface name and MAC address you want.
Now, in order to update a MAC address in the configuration, run this command
specifying the interface name and MAC address you want.
.. code-block:: none
set interfaces eth0 hw-id 00:0c:29:da:a4:fe
If it is a VM, go into the settings of the host and set the MAC address to the settings found in the config.boot file. You can also set the MAC to static if the host allows so.
If it is a VM, go into the settings of the host and set the MAC address to
the settings found in the config.boot file. You can also set the MAC to
static if the host allows so.
* Another example could be when cloning VyOS VMs in GNS3 and you get into the same issue: interface names have changed.
* Another example could be when cloning VyOS VMs in GNS3 and you get into the
same issue: interface names have changed.
And **a more generic way to fix it** is just deleting every MAC address at the configuration file of the cloned machine. They will be correctly regenerated automatically.
And **a more generic way to fix it** is just deleting every MAC address at
the configuration file of the cloned machine. They will be correctly
regenerated automatically.
**********
@ -436,6 +445,8 @@ These are the boot steps for VyOS 1.2
11. Finally it runs the post-config script
``/config/scripts/vyos-postconfig-bootup.script``
.. stop_vyoslinter
.. _Quagga: https://www.quagga.net/
.. _`GNU Zebra`: https://www.gnu.org/software/zebra/
.. _FRR: https://frrouting.org/
@ -444,3 +455,5 @@ These are the boot steps for VyOS 1.2
.. _`Debian Jessie`: https://www.debian.org/releases/jessie/
.. _tshark: https://www.wireshark.org/docs/man-pages/tshark.html
.. _`PCAP filter expressions`: http://www.tcpdump.org/manpages/pcap-filter.7.html
.. start_vyoslinter