Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| en:hw:01-axon:lte [2025/04/07 08:53] – avsetula | en:hw:01-axon:lte [2025/05/16 09:55] (current) – [Autoswitch feature] typo ofojt | ||
|---|---|---|---|
| Line 44: | Line 44: | ||
| By default, the unipi-lte Linux service provides automatic handling with the default network gateway according to the WAN availability on both main and backup network interfaces. The main network adapter is usually wired ethernet (eth0) while the backup is realized by the LTE modem. In the Linux routing table, the default GW routes for both of these interfaces should be always present. When a " | By default, the unipi-lte Linux service provides automatic handling with the default network gateway according to the WAN availability on both main and backup network interfaces. The main network adapter is usually wired ethernet (eth0) while the backup is realized by the LTE modem. In the Linux routing table, the default GW routes for both of these interfaces should be always present. When a " | ||
| - | 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/ | + | 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 ///etc/ |
| Then, the /// | Then, the /// | ||
