What's new

Github snapshot test builds (Updated 30-May-2015)

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Status
Not open for further replies.
Connected to a VPN provider, in routing policy mode, block routed clients if tunnel goes down set to yes. Everything working properly.

All I have to do is switch to all traffic mode and click apply to reproduce the problem of LAN clients routed through tunnel being blocked even though the tunnel is indeed up.

As the tunnel goes down rules are put in place to prohibit the default route. However when the tunnel comes back up in all traffic mode that rule is not cleaned up because, as the log explicitly says, it's not in routing policy mode anymore.

Thanks, fixed with this commit. Additionally, now if you change between All and Policy routing while the tunnel is already down, the routing tables will also be properly updated with this commit.

I'm currently looking into making the tunnel enforcement also be applied at boot time.
 
Last edited:
I'm currently uploading fresh builds for people to tinker with. Not many changes since last week, mostly the fixes to UPNP and policy-based routing.
 
OK, just tested alpha 4 with the openvpn routing switches and it's all working well. I also tested a change while the openvpn client is off and it cleaned up the rules/routes as desired.

edit: thanks for working on applying the rules on boot too. a power blip causing reboot has been the only time my router was off VPN and I didn't know it. of course, I got a new battery backup after that too. :)
 
Have been testing 378.54_alpha3 and 378.54_alpha4 both works good regarding Ipvanish openvpn using Strict DNS Configuration and no problems from other configuration settings that I use. Thx Merlin :)
 
Alpha 4 working great

Fisrt time a saw this in the logs and i have no disks at all attached to the router

May 31 02:00:04 disk_monitor: Got SIGALRM... o_O

yeah, I've seen that several times with alpha 3 and 4.
 
Have been testing 378.54_alpha3 and 378.54_alpha4 both works good regarding Ipvanish openvpn using Strict DNS Configuration and no problems from other configuration settings that I use. Thx Merlin :)

Note that there is one gotcha with DNS servers set on Strict while in policy mode: it will also force those DNS servers to all your other clients, regardless of whether they are routed through the tunnel or not.

I couldn't find any simple way to implement rule-based DNS handling at this point (short of re-implementing a whole system similar to DNSFilter but tied to VPN routing), so my recommendation for anyone using policy routing for now is to leave this to Relaxed or Disabled, and configure instead a DNSFilter rule for those clients you wish to force through the VPN tunnel, with the custom DNS being set to one of those provided by the VPN tunnel provider.
 
OpenVPN seems to run fine with .54 alpha 4 on my RT-AC66U.

Unfortunately the problem I had with .53 is still present: my WeMo switches won't connect anymore.
 
I dont know if it is just me but the cpu utilization would go up every 30 seconds even when there is no internet activity or external drive pluged in. I dont think previous version does this
 

Attachments

  • Screenshot_2015-06-03-11-33-55.png
    Screenshot_2015-06-03-11-33-55.png
    228.9 KB · Views: 520
I dont know if it is just me but the cpu utilization would go up every 30 seconds even when there is no internet activity or external drive pluged in. I dont think previous version does this

Check with "top" to determine what's causing the CPU spikes.
 
Is it possible to reload the /etc/hosts file from /jffs/config/hosts.add with out restarting the router ??
 
Is it possible to reload the /etc/hosts file from /jffs/config/hosts.add with out restarting the router ??

Just manually copy the content of it to /etc/hosts . Linux will automatically notice the changes.
 
I have noticed some wierd things in alpha-4. make sure you have 2 openvpn clients configured and reboot the machine. I have noticed the one open vpn client (client 2) starts up automatically ( It was switched off before reboot )
 
I have noticed some wierd things in alpha-4. make sure you have 2 openvpn clients configured and reboot the machine. I have noticed the one open vpn client (client 2) starts up automatically ( It was switched off before reboot )

Check the state of the "Start with WAN" setting.
 
Status
Not open for further replies.

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top