On Sep 1, 2010, at 6:01 AM, Michael wrote: > Michael Keuter wrote: > >> Within Server mode in the "push section" you just need to add the >> route and DNS for your local network, e.g.: >> >> route 192.168.1.0 255.255.255.0 >> dhcp-option DOMAIN local >> dhcp-option DNS 192.168.1.1 >> >> > > I have these options. Looks like this in my case: > > dhcp-option DNS 172.17.2.1 > route 172.17.2.0 255.255.255.128 > dhcp-option DOMAIN local > > And they are correctly transferred to the client-Laptop. > > When I try to ping a LAN-IP address I do see on the *astlinux* box the pings > on the tun device. So the pings on the client-Laptop are correctly routed to > the tunnel and do arrive at the astlinux box. > > But then the pings are not routed from the tun to the LAN on the astlinux > box, which is strange to me. Maybe it is the firewall blocking traffic from > tun to LAN. But that would be strange as it allows traffic from tun to WAN.
Michael, In the Network -> Firewall sub-tab, you need to check the option: _x_ Allow OpenVPN Server tunnel to the [ 1st LAN Interface ] and restart the firewall. (assuming your br1 is defined as the 1st LAN Interface) By default, the firewall isolates all LAN subnets from each other, including the OpenVPN tun0 subnet. Lonnie ------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ Astlinux-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [email protected].
