As intimated earlier, my Vigor 130 modem is not accessible as it sits behind a router. The 130’s address range is 192.168.2.1/24, while my LAN sits on a 192.168.1.1/24 range.

Try 1

Although Draytek have an article about using tagged & untagged VLANs to access these modems behind routers, the setup didn’t work for me (I suspect their use of the ‘0’ VLAN tag as shorthand for an untagged VLAN didn’t work for the particular router I have).

Try 2

Instead, I want to set up a route policy and any requests for the address range of the modem should be passed back through the WAN2 interface to be resolved there. At least I think that is how it is done. Using Routing / Load-Balancing Route Policy I setup a policy so that any requests on the 192.168.2.1/24 range go via WAN2, and should go to the modem. However it doesn’t work.

Try 3

I think I have the wrong concept about the route policy and have to instead use a virtual WLAN such as WLAN5? An excellent article explained it better, however it was for another type of modem. Dantheperson’s explanation was that by adding a secondary static route and pointing that at the WAN interface, “Now when your PC routes the request for 192.168.0.1 to the router, the router knows it can access that address via the WAN interface, instead of forwarding it to the default “internet” interface.” This is what I want to do, however I think that the Vigor router uses the permanent virtual circuit (PVC) idea to do the same thing. So my current setup is Route Policy –> virtual WAN5 which sets up a VLAN on the WAN2 interface. It still doesn’t work.

Argggggh!