This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
advanced-routing [2022/01/21 03:14] – clarity, formatting hogwild | advanced-routing [2023/06/21 01:52] – -formatting hogwild | ||
---|---|---|---|
Line 5: | Line 5: | ||
\\ | \\ | ||
- | {{: | + | {{: |
- | \\\\ The Current Routing Table displays the output from the '' | + | \\ |
+ | |||
+ | The Current Routing Table displays the output from the '' | ||
A default table entry should be present which indicates traffic going towards the Internet.\\ | A default table entry should be present which indicates traffic going towards the Internet.\\ | ||
- | {{: | + | \\ |
- | 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.\\ \\ | + | {{: |
- | {{: | + | \\ The Static Routing Table is manually created. Here, you can define static routes (with their netmask/ |
+ | |||
+ | \\ | ||
+ | |||
+ | {{: | ||
+ | |||
+ | \\ | ||
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. | 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. | ||
+ | |||
+ | \\ | ||
+ | |||
+ | \\ | ||
+ | |||
+ | \\ | ||