VMG1312-B10A: Static Routes: Difference between revisions

(9 intermediate revisions by 3 users not shown)

Line 1:

=Important=

==Important==

'''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.

'''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, e.g.

The notes below are the steps to set up a static route, but you may find it does not work.

⚫

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, eg

INTERNET <--> ZyXEL <--> ROUTER <--> LAN

(Note, some people may prefer to set the ZyxEL to Bridge mode, and then have your own Router use PPP to log in. This has the advantage of keeping the ZyXEL config simpler and giving your own router more control over the Internet access.)

== Config via CLI ==

route add [network] [subnet] metric -1 gw [LAN side route] dev br0

e.g., if your block is 192.0.2.0/27 and the internal router is 198.51.100.2, then:

route add 192.0.2.0 255.255.255.240 metric -1 gw 198.51.100.2 dev br0

save

⚫

Again, from the CLI you can view the route table with:

⚫

route show

⚫

The list should display immediately, if there are pauses between showing the default routes and the new static then this could be an indication of a problem with DNS look-ups and should not affect the actual routing.

=== IPv6 ===

The ''route'' command from the CLI isn't IPv6 aware. You'll have to login as ''supervisor'', enter ''sh'' to get a root shell prompt and then use the native ''route'' command:

route -A inet6 add 2001:8b0:xxx:yyyy::/64 gw 2001:8b0:xxx:zzzz::3

== Config via Web Interface ==

The static route can be added via the web interface:

Line 42:

Line 59:

Security --> Firewall

==CLI==

⚫

~~From~~ the CLI ~~(telnet/SSH)~~ you can view the route table with:

⚫

route show

⚫

The list should display immediately, if there are pauses between showing the default routes and the new static then this could be an indication of a problem with DNS look-ups and should not affect the actual routing.

[[Category:~~ZyXEL_VMG1312~~|Static]]

[[Category:ZyXEL VMG1312-B10A|Static Routes]]

[[Category:ZyXEL VMG1312 B10D|Static Routes]]

[[Category:ZyXEL VMG3925 B10C|Static Routes]]