|
|
"Leonard Isham" <leonard.isham@xxxxxxxxx> wrote in message news:1e6368e804110314366586d520@xxxxxxxxxxxxxxxxx > Unless Imissed it I did not see rout tables for the worksatations on > the 192.168.1.0 subnet. These have to have a way to route back to > the OpenVPN server or that will never reach the remote site. What do you mean "worksatations"? +If you mean the client side PC (a road warrior), then I have add the route to that PC for the server. > 10.1.1.n > OpenVNP Client > 66.42.xxx.xxx Dialup So I have to add route 64.42.xxx.0 Netmask 10.1.1.n at my server 192.168.1.25 The problem is I don't realy know 64.42.xxx.0 and the Netmask. It is dynamic IP (dialup) That is something confusing me. I thought the command "client-to-client" in config-file would handle that. Actually I don't need "client-to-client" since the client is a road warrior only. +If you mean PC1 and PC2 on the server side, then yes, there are the routes: 192.168.1.0 255.255.255.0 192.168.1.25 and 10.1.1.0 255.255.255.0 192.168.1.25 at the Gatway router 192.168.1.1 I still wonder what is wrong with my config-file. Ben > > ------- > > Route table on server side > > Active Routes: > > Network Destination Netmask Gateway Interface > > Metric > > 0.0.0.0 0.0.0.0 192.168.1.1 > > 192.168.1.25 1 > > 10.1.1.0 255.255.255.252 10.1.1.1 > > 10.1.1.1 1 > > 10.1.1.0 255.255.255.0 10.1.1.2 > > 10.1.1.1 1 > > 10.1.1.1 255.255.255.255 127.0.0.1 > > 127.0.0.1 1 > > 10.255.255.255 255.255.255.255 10.1.1.1 10.1.1.1 > > 1 > > 127.0.0.0 255.0.0.0 127.0.0.1 > > 127.0.0.1 1 > > 192.168.1.0 255.255.255.0 192.168.1.25 > > 192.168.1.25 1 > > 192.168.1.25 255.255.255.255 127.0.0.1 > > 127.0.0.1 1 > > 192.168.1.255 255.255.255.255 192.168.1.25 > > 192.168.1.25 1 > > 224.0.0.0 224.0.0.0 10.1.1.1 > > 10.1.1.1 1 > > 224.0.0.0 224.0.0.0 192.168.1.25 > > 192.168.1.25 1 > > 255.255.255.255 255.255.255.255 10.1.1.1 10.1.1.1 > > 1 > > Default Gateway: 192.168.1.1 > > =========================================================================== > > I don't have a route table on client side for now. However I already checked > > it. There are the routes to 192.168.1.0 via 10.1.1.1 > > That why Client is able to ping 192.168.1.25 > > > > Thank you for your review, > > > > Ben > > > > Unless Imissed it I did not see rout tables for the worksatations on > the 192.168.1.0 subnet. These have to have a way to route back to > the OpenVPN server or that will never reach the remote site. > -- > Leonard Isham, CISSP > Ostendo non ostento. > > > ------------------------------------------------------- > This SF.Net email is sponsored by: > Sybase ASE Linux Express Edition - download now for FREE > LinuxWorld Reader's Choice Award Winner for best database on Linux. > http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click ____________________________________________ Openvpn-users mailing list Openvpn-users@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/openvpn-users |