Viscosity will not route to lan devices on a Tomato server
Posted: Tue Sep 25, 2018 6:56 pm
My Viscosity to version 1.7.11.
My Tomato Router Version is 1.28.
My home LAN is 10.100.1.0/24 with the router at 10.100.1.1.
OpenVPN subnet/netmask is 10.8.0.0 and 255.255.255.0.
I followed Sparklab's instructions about how to configure the Tomato's OpenVPN Server and a Viscosity Client:
https://www.sparklabs.com/support/k...n ... viscosity/
My OpenVPN clients are able to connect with Viscosity to my Tomato's OpenVPN Server. They get an IP number 10.8.0.6. Tomato's -> VPN Tunneling -> OpenVPN Server -> Server 1 -> Status will register a client when connected. However, there is NO ROUTING across the OpenVPN connection!
At first, I focused on the Tomato Router as the problem. Unlike GLuDeRo's post here:
http://www.linksysinfo.org/index.php?th ... ice.72806/
My clients cannot ping 10.100.1.1 nor any other device on 10.100.1.0/24.
When I connect a second client at 10.8.0.10, neither client can ping each other.
I tried configuring a Tomato -> Administration -> Scripts -> Firewall script like GLuDeRo suggested. It didn't make a difference for me:
iptables -t nat -I POSTROUTING -s 10.8.0.0/24 -o br0 -j SNAT --to $(nvram get lan_ipaddr)
Based on someone else's post somewhere, I tried this firewall script without success:
iptables -I FORWARD -s 10.8.0.0/24 -d 10.100.1.0/24 -j DROP
Here is my Tomato Routing Table. Everything looks reasonable:
https://drive.google.com/file/d/1AqsvMd ... sp=sharing
From Tomato's -> Tools -> Ping, I cannot ping a client like 10.8.0.6. However, I can ping 10.8.0.1.
From the client, I cannot Ping 10.8.0.1 nor can it even ping itself, 10.8.0.6.
Based on this one small but unreliable test, I tend to think the problem is with Viscosity.
The problem occurs whether Viscosity is running on a Mac or PC.
"Send all traffic over VPN connection" doesn't make a difference.
I have entered my Lan's Default Gateway in Viscosity without routing success.
Can someone make some suggestions for me as to a possible solution to this routing problem? Maybe I need to set a static route in Viscosity?
I'll be happy to provide more information if requested.
Rob
My Tomato Router Version is 1.28.
My home LAN is 10.100.1.0/24 with the router at 10.100.1.1.
OpenVPN subnet/netmask is 10.8.0.0 and 255.255.255.0.
I followed Sparklab's instructions about how to configure the Tomato's OpenVPN Server and a Viscosity Client:
https://www.sparklabs.com/support/k...n ... viscosity/
My OpenVPN clients are able to connect with Viscosity to my Tomato's OpenVPN Server. They get an IP number 10.8.0.6. Tomato's -> VPN Tunneling -> OpenVPN Server -> Server 1 -> Status will register a client when connected. However, there is NO ROUTING across the OpenVPN connection!
At first, I focused on the Tomato Router as the problem. Unlike GLuDeRo's post here:
http://www.linksysinfo.org/index.php?th ... ice.72806/
My clients cannot ping 10.100.1.1 nor any other device on 10.100.1.0/24.
When I connect a second client at 10.8.0.10, neither client can ping each other.
I tried configuring a Tomato -> Administration -> Scripts -> Firewall script like GLuDeRo suggested. It didn't make a difference for me:
iptables -t nat -I POSTROUTING -s 10.8.0.0/24 -o br0 -j SNAT --to $(nvram get lan_ipaddr)
Based on someone else's post somewhere, I tried this firewall script without success:
iptables -I FORWARD -s 10.8.0.0/24 -d 10.100.1.0/24 -j DROP
Here is my Tomato Routing Table. Everything looks reasonable:
https://drive.google.com/file/d/1AqsvMd ... sp=sharing
From Tomato's -> Tools -> Ping, I cannot ping a client like 10.8.0.6. However, I can ping 10.8.0.1.
From the client, I cannot Ping 10.8.0.1 nor can it even ping itself, 10.8.0.6.
Based on this one small but unreliable test, I tend to think the problem is with Viscosity.
The problem occurs whether Viscosity is running on a Mac or PC.
"Send all traffic over VPN connection" doesn't make a difference.
I have entered my Lan's Default Gateway in Viscosity without routing success.
Can someone make some suggestions for me as to a possible solution to this routing problem? Maybe I need to set a static route in Viscosity?
I'll be happy to provide more information if requested.
Rob