Agreed - usually means there’s no route on the VPN server to handle outside traffic to the world.
> On Dec 10, 2014, at 1:26 PM, Vick Khera <vi...@khera.org> wrote: > > did you configure tunnelblick to send *all* traffic to the vpn? if so, you > have to add allow rules to the openvpn interface to permit that traffic, and > probably set up a NAT on there as well. > > it is easiest to not send all traffic there unless that is your goal to mask > your origin. my goal is to access internal resources to my office network, so > i do not configure tunnelblick that way. > > On Wed, Dec 10, 2014 at 2:11 PM, Kostas Backas <kos...@i-system.gr > <mailto:kos...@i-system.gr>> wrote: > Hello, > > We are using openvpn with tunnelblick and viscosity clients in OS X. > > Our main issue is that when the users are connected to the vpn, the cannot > access the Internet. > > I have tried to forward traffic through vpn, add DNS servers etc, but nothing > worked. > > How can I determine what keeps it from working? > > Best regards > > Kostas > > Sent from my iPhone > _______________________________________________ > List mailing list > List@lists.pfsense.org <mailto:List@lists.pfsense.org> > https://lists.pfsense.org/mailman/listinfo/list > <https://lists.pfsense.org/mailman/listinfo/list> > > _______________________________________________ > List mailing list > List@lists.pfsense.org > https://lists.pfsense.org/mailman/listinfo/list
_______________________________________________ List mailing list List@lists.pfsense.org https://lists.pfsense.org/mailman/listinfo/list
