This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
advanced-routing [2022/01/21 03:14] – clarity, formatting hogwild | advanced-routing [2024/10/13 00:41] (current) – -Tag relevant subheads as Head2 hogwild | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ===== Routing ===== | + | ====== Routing |
- | The Routing page allows | + | In this menu, you can view the current routing table. You can also define the output interface for specific |
\\ | \\ | ||
- | {{: | + | ===== Current Routing Table ===== |
- | \\\\ The Current Routing Table displays the output from the '' | + | {{: |
- | A default table entry should be present which indicates traffic going towards the Internet.\\ | + | \\ |
- | {{: | + | The Current Routing Table displays the output from the '' |
+ | |||
+ | A default table entry should be present that indicates traffic going towards the Internet. | ||
+ | |||
+ | \\ | ||
+ | |||
+ | ===== Static Routing Table ===== | ||
+ | |||
+ | {{: | ||
+ | |||
+ | \\ The Static Routing Table is manually created. Here, you can define static routes (with their netmask/ | ||
+ | |||
+ | ===== Miscellaneous ===== | ||
+ | |||
+ | {{: | ||
+ | |||
+ | \\ | ||
+ | |||
+ | If the WAN interface receives an IP address via DHCP, this specifies whether to accept routing information from the DHCP server. Such information is sent usually via DHCP option 33 or 121. | ||
+ | |||
+ | \\ | ||
- | The Static Routing Table is manually created. Here, you can would define static routes (with their netmask and gateway) towards specific destinations. While this is not normally needed, it might be useful for advanced setups such as like intranets, VPN, and so on.\\ \\ | + | |
- | {{: | + | |
- | If the WAN interface is assigned IP addressing via DHCP, this options specfies whether or not to accept routing information from the DHCP server. Such routing information is usually sent via DHCP option 33 or 121. | + | \\ \\ |