Tomato Weird OpenVPN Issue

Discussion in 'Tomato Firmware' started by dfrandin, Jun 21, 2014.

  1. dfrandin

    dfrandin Addicted to LI Member

    I'm running Tomato 1.28.0000 MIPSR2-115 K26 Max on a Asus RT-N12D. Everything was working perfectly up till yesterday when my local power company did one of its cute little "lets cut the power off to our customers for about 30 seconds" that they do so well in my neighborhood in the summertime.. And no, I don't currently have a UPS on the router, but if these start happening often, I'll bite the bullet and get one... Anyway, after the power came back on, I noticed that I could not reach my remote servers that have tunnels hosted by the Asus router's openvpn server. Initial checking found that - for some reason - the Tomato Openvpn server/basic tab was showing a blank for the port.. Of course this is supposed to be 1194 in this configuration, so I entered that and hit save and the gui told me it was an invalid port. Huh? So I ssh'ed into the console of the router and checked the /tmp/etc/openvpn/server1/config.ovpn.. it was showing "port 0".. hmmm.. Oh well, fired up vi and edited the file and set "port 1194"... For some reason the Tomato gui keeps changing it back to port 0. Since I have the keys etc. to completely recreate the server config, I'd love to be able to do that, but for some reason, I can't remove the complete "server1" configuration.. it keeps coming back.. even when I delete the entire /tmp/etc/openvpn/server1 directory, and copious reboots... Never had any trouble like this with Tomato in the years that I've been running it on both Linksys and Asus routers... HELP!!

    Update: Further troubleshooting finds that when I try and add a port in the port forwarding/basic tab, to allow me to run openvpn on one of my other systems, I get an "invalid port" error from the tomato gui.. That power-outage really borked up this router... Any pointers to what I can do to recover from this would be appreciated...
    Last edited: Jun 21, 2014
  2. Grimson

    Grimson Networkin' Nut Member

    Sounds like the NVRAM got corrupted, clear it and reconfigure the router from scratch.
  3. dfrandin

    dfrandin Addicted to LI Member

    Yeah.. Thats what I did.. BIG pain in the a$$.. Fortuantly, the router was otherwise operational, so I took screenshots of all of the pertinent screens to make reconfig easier.. This shibby build doesnt seem to have the capability (or at least I can't find it) of backing up nvram to a .cfg file like the old 1.27vpn I used on my old WRT54GL. In fact, as far as I can tell, this shibby build only allows wiping nvram when you're upgrading. So, I wound up "upgrading" to the same version that was installed, simply so I could wipe nvram.. Please advise if I'm missing the nvram backup and ability to wipe it w/o doing an upgrade...
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice