I have installed shabby AIO on an E4200, after fiddling around unsuccessfully with dd-wrt for the last fortnight. After seeing how stable and easy to use Tomato is, I cannot help but feeling that the last fortnight of my life was wasted!
The main reason I require firmware is to connect to an online VPN server (service).
WAN (ISP) = 97.140.xx.xx Router = 192.168.2.1 NAS = 192.168.2.20 (routed through VPN) E.g. Laptop = 192.168.2.3 (Not routed through VPN, routed through WAN).
I successfully set-up the VPN client on my router to my requirements, i.e. my NAS is tunnelled through the VPN but all other devices on my network (e.g. my laptop) are directed through the normal ISP route (WAN). I did this following this provided tutorial openvpn-via-password-authentication (sorry I am not allowed to post the link but it is in the tomato tutorial section). This is working seamlessly.
My issue is that my NAS contains a webserver for my domain. As soon as the VPN client connects I lose the ability to access the webserver from outside the network, i.e. by typing in my address www.’mydomain’.com. I can see that my nameservers are still pointing to my WAN IP, so the connection is obviously still coming through my WAN but not making it to the webserver on the NAS as the NAS thinks it is exclusively connected to the VPN route only.
I note that the OpenVPN route-up script directs all traffic for my NAS IP using the vpn_gateway function.
My question is – how do I maintain the functionality I have at present but also allow the NAS to receive traffic from the WAN as well as the connect VPN route. i.e. how do I make my NAS direct traffic through the VPN route and listen on the WAN concurrently.
Any suggestions would be greatly appreciated.