- This topic is empty.
September 27, 2009 at 5:54 am #41942dqqjzMember
MANY THX FOR ANY Help form ANY BODY !!
Great Work Zeroshell!!
Tried to setup a Host-to-Lan OpenVpn
Moible connected Laptop (VPNClient)
laptop (connect from 3G mobile phone) 220.127.116.11
Zeroshell (eth1) 114. 36.7.30
Zeroshell (eth0) 192.168.0.75
VPN99 VPN RANGE 192.168.250.1-253(default)
OPENVPN Gateway /DNS 192.168.250.254 (default)
Source NAT : YES
Net button: 192.168.250.0/24
Password only authentication
followed exactly as the documents on the website configure server/client
client connect successfully!
from client VPN IP 192.168.250.1
ping : 192.168.250.254 OK (can even visit web GUI of zeroshell)
ping : 192.168.0.75 NO response (time out)
ping : 192.168.0.10 time out (Desktop connected with zeroshell router eth0)
from desktop in the intranet
ping 192.168.0.75 OK
I searched and findout the “”bridge” method afte create a new bridge
for VPN99 Eth00
The desktop can access to 192.168.250.254
still can not access 192.168.250.1 (laptop vpn client )
BUT I need VPN Client able to ACCESS the LAN eg.Desktop(192.168.0.10)
and I can not even ping the gateway 192.168.0.75
What Shall i add ? WHERE
Hope anybody tell me ~ & it is kind of UrgentSeptember 28, 2009 at 3:07 am #48819dqqjzMember
Any one can help, it is kind of urgent?September 28, 2009 at 8:18 am #48820yumMember
Have you enabled NAT on LAN interface of ZeroShell (ETH00)?
What is your firewall configuration, routing table?September 28, 2009 at 3:15 pm #48821
Remove the Source NAT on the ZS openvpn webpage.
Add a static Route on every client upon connection
route 192.168.0.0 255.255.255.0 192.168.250.254 1September 1, 2010 at 11:38 pm #48822
I had this working before without having to add the route on the client end. Is there anyway to get it done from within the zeroshell interface?
btw in win7
route ADD 192.0.0.0 MASK 255.0.0.0 192.168.250.254 METRIC 1September 2, 2010 at 6:28 am #48823
Yes you can add this subnet in the list that pops up when you hit the “Net” button.September 2, 2010 at 9:27 pm #48824
but I still can’t ping anything behind the router’s ip.
I still had to add the route in a command shell.
I tried 192.168.0.0/255.255.0.0September 8, 2010 at 8:19 pm #48825
I was thinking 192.0.0.0 would include 192.168.3.0
what I needed to do was specify
192.0.0.0/255.0.0.0September 9, 2010 at 6:55 am #48826
It does include it, but it is wrong to use the whole 192.0.0.0 network cause only the 192.168.0.0/255.255.0.0 is private. The rest is public and you may need to access it.
- You must be logged in to reply to this topic.