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/10 19:23] – rs232 | advanced-routing [2023/06/24 19:43] – -add point to intro about displaying current table hogwild | ||
---|---|---|---|
Line 1: | Line 1: | ||
===== Routing ===== | ===== Routing ===== | ||
- | The Routing page allows you to define the output interface for specific | + | The Routing page allows you to view the current routing table. It also allows you to define the output interface for specific |
- | {{: | + | \\ |
- | The Current Routing Table is displaying | + | |
+ | {{: | ||
+ | |||
+ | \\ | ||
+ | |||
+ | The Current Routing Table displays | ||
+ | |||
+ | A default | ||
+ | |||
+ | \\ | ||
+ | |||
+ | {{: | ||
+ | |||
+ | \\ 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 specifies whether to accept routing information from the DHCP server. Such routing information is usually sent via DHCP option 33 or 121. | ||
+ | |||
+ | \\ NOTE: On older FreshTomato versions, there was an obsolete setting in this menu that suggested FreshTomato can operate in Gateway mode or Router mode. Ignore this, and leave it set to " | ||
+ | |||
+ | \\ | ||
+ | |||
+ | [[https:// | ||
+ | |||
+ | \\ | ||
- | {{: | ||
- | The Static Routing Table is created by human interaction/ | ||
- | {{: | ||
- | In case the WAN interface is obtaining IP information via DHCP, with this option we can control whether to accept routing information (usually sent as a DHCP option 33 or 121) from the DHCP server or not. |