Open main menu

AAISP Support Site β

Changes

VMG1312-B10A: Static Routes

2,380 bytes added, 08:24, 7 October 2020
m
no edit summary
==Important==
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
'''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, ege.g.
INTERNET --> ZyXEL --> ROUTER --> LAN
 
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
 
FromAgain, 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.
 
=== 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:
 
Network Setting -> Routing -> Add new static route
 
The settings would typically be:
{| class="wikitable"
|-
| Enabled || Ticked for this to be on
|-
| Name || LAN, or whatever you want
|-
| IP Type || IP4 for IP4 blocks, IP6 for IP6 blocks!
|-
| Destination IP Address: || The ''Network'' address of your routed block
|-
| Subnet || The subnet mask of your routed block
|-
| Gateway Address: || The IP of the router on the LAN side of the ZyXEL
|-
| Use Interface || Default/br0 for the LAN side
|}
 
Here is an example:
[[File:ZyXEL-staticroute.png|frame|none|The new Static route, as shown on the routes page]]
 
==Firewall Needs to be Disabled==
==CLI==
It seems that the firewall will be unaware of the static route, and adding firewall entries to allow the traffic will be ignored. Disabling the firewall will allow the traffic through the ZyXEL to your router. This is normally required anyway, as customers would typically use the firewall features on the internal router. The setting for this is found under:
From the CLI (telnet/SSH) you can view the route table with:
Security --> Firewall
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_VMG1312ZyXEL VMG1312-B10A|Static Routes]]
[[Category:ZyXEL VMG1312 B10D|Static Routes]]
[[Category:ZyXEL VMG3925 B10C|Static Routes]]