editor
698
edits
VMG1312-B10A: Static Routes: Difference between revisions
m
clean up, typos fixed: eg → e.g. (2)
m (→Config via CLI) |
m (clean up, typos fixed: eg → e.g. (2)) |
||
|
'''IMPORTANT NOTE!''' Some customers have reported static routes not working. This issue is being looked in to (July 2015). It has been suggested that disabling QoS helped, but this has yet to be verified with other setups. At the moment, we can't really suggest using static routes. Instead, we'd suggest using the ZyXEL as a bridge and perform PPPoE on your internal router/firewall. This issue is on our [[VMG1312-Bugs|Bugs Page]] as of July 2015 and has been escalated to ZyXEL. In these cases rather than using the Web interface to add the static route you can use the telnet/ssh CLI to add it. An example is below.
Static routes can be applied manually. This allows a second block of IP addresses allocated by AAISP to be routed to a router on your LAN on the inside of the ZyXEL router,
INTERNET <--> ZyXEL <--> ROUTER <--> LAN
route add [network] [subnet] metric -1 gw [LAN side route] dev br0
route add 192.0.2.0 255.255.255.240 metric -1 gw 198.51.100.2 dev br0
save
[[Category:
| |||