Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
en:hw:01-axon:lte [2021/08/06 14:13] avsetula |
en:hw:01-axon:lte [2023/07/11 15:09] avsetula [Autoswitch feature] |
||
---|---|---|---|
Line 25: | Line 25: | ||
- Insert a micro-sim supporting LTE data into the slot. | - Insert a micro-sim supporting LTE data into the slot. | ||
- | - Log-in to the unit via SSH (or SCP). | + | - Log-in to the unit via SSH. |
- Install unipi-lte package:<code> | - Install unipi-lte package:<code> | ||
sudo su | sudo su | ||
Line 42: | Line 42: | ||
Therefore, it is necessary to continually keep the metrics as positive non-zero values. This is ensured by a DHCP client when DHCP is active on the main network interface but **it must be assured manually if static IP is configured on the main interface** (as static routes have zero metrics as default). As an example, you can put a constant to the interface’s configuration file at ///etw/network/interfaces.d//. | Therefore, it is necessary to continually keep the metrics as positive non-zero values. This is ensured by a DHCP client when DHCP is active on the main network interface but **it must be assured manually if static IP is configured on the main interface** (as static routes have zero metrics as default). As an example, you can put a constant to the interface’s configuration file at ///etw/network/interfaces.d//. | ||
- | Then, the ///etw/network/interfaces.d/**eth0**// file for static IP configuration may look like: | + | Then, the ///etc/network/interfaces.d/**eth0**// file for static IP configuration may look like: |
<code> | <code> | ||
# Example static IP configuration for unit belonging to LAN | # Example static IP configuration for unit belonging to LAN |