[OpenVPN home] [Date Prev] [Date Index] [Date Next]
[OpenVPN mailing lists] [Thread Prev] [Thread Index] [Thread Next]
Google
 
Web openvpn.net

Re: [Openvpn-users] After connecting to OpenVPN server unable to browse internet...


  • Subject: Re: [Openvpn-users] After connecting to OpenVPN server unable to browse internet...
  • From: toby <toby711@xxxxxxxxx>
  • Date: Fri, 30 Nov 2007 06:54:25 -0600

Yep, as soon as I talk to a computer on the VPN side internet goes down. Same subnet must be the issue. I'm going to change the network their and we should be good.

Thanks all!

Toby

On Nov 30, 2007 6:51 AM, Jan Just Keijser <janjust@xxxxxxxxx> wrote:
the fact that your subnet is the same as your clients remote subnet is
bound to cause this sort of problems; I had expected that as soon as you
make the openvpn connection you would lose all internet access...
another thing to try is to webex in again, test internet access, then do
a single 'ping 192.168.1.117' and then try internet access again...

cheers,

JJK

toby wrote:
> One more thing, while webex'd in I noticed I could connect to OpenVPN
> server and browse web at the same time. The only time internet
> browsing, dns resolution, etc was broken was when I went to My
> Computer -> Mapped network drive (Samba) This drive is only accessible
> by VPN connection. Again, this is due to remote users LAN being on
> same subnet I'm pushing correct?
>
> Toby.
>
> On Nov 30, 2007 6:32 AM, toby < toby711@xxxxxxxxx
> <mailto:toby711@xxxxxxxxx>> wrote:
>
>     Well the OpenVPN server LAN is on 192.168.1.0 <http://192.168.1.0>
>     on next maintenance window I can change it to 10.10.0.0/24
>     < http://10.10.0.0/24> network and it should resolve this problem
>     as well.
>
>     Toby.
>
>
>     On Nov 30, 2007 6:26 AM, Rob MacGregor < rob.macgregor@xxxxxxxxx
>     <mailto:rob.macgregor@xxxxxxxxx>> wrote:
>
>         On Nov 30, 2007 12:23 PM, toby < toby711@xxxxxxxxx
>         <mailto:toby711@xxxxxxxxx>> wrote:
>         > I'm going to change the LAN on remote users side to
>         192.168.2.0 <http://192.168.2.0> and
>         > hopefully this will do the trick.
>
>         Be more creative, to avoid having to do this again next week
>         when you
>         come across a home user/WiFi hotspot using 192.168.2.0/24
>         <http://192.168.2.0/24 >.  Pick a
>         random /24 from the 10.0.0.0/8 <http://10.0.0.0/8> range, say
>         10.142.52.0/8 <http://10.142.52.0/8>.
>
>         -
>