|
Home > Archive > VPN > February 2005 > My first VPN - and it "almost" works - BEFVP41 V2
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
My first VPN - and it "almost" works - BEFVP41 V2
|
|
| wardellcastles 2005-01-30, 7:45 am |
| I have successfully set up a tunnel between a computer outsi=ADde my
network and my LAN at home. (No small feat for a network new=ADbie, I
have to admit).
The VPN Gateway at home is a LinkSys BEFVP41 Router with Firmware=AD
Version 1.00.12
The remote VPN Client software is TheGreenbowVPN (In trial mode)
The good news is that both the client and VPN Gateway agree =ADa tunnel
has been created. The log on the Gateway is reporting "IKE[=AD1] Set up
ESP tunnel with aaa.bbb.ccc.ddd Success!" (aaa.bbb.ccc.ddd=AD is the
address of the remote client).
The bad news is that the remote machine cannot ping the mach=ADines on
the other end of the VPN nor does it have any access to the shared
reso=ADurces on the remote LAN.
I do have one thing that confuses me even more. The client =ADas well
as the VPN Gateway is on LAN that has local addresses of
192.16=AD8.1.xxx So how does the client differentiate between machine
192.168=AD.1.100 (for example) on his network and a machine on the local
LAN with =ADthe same address?
Thanks in advance for all replies.=20
Wardell Castles
| |
| CoolUncle 2005-01-30, 5:45 pm |
| wardellcastles wrote:
> I have successfully set up a tunnel between a computer outsi_de my
> network and my LAN at home. (No small feat for a network new_bie, I
> have to admit).
>
> The VPN Gateway at home is a LinkSys BEFVP41 Router with Firmware_
> Version 1.00.12
>
> The remote VPN Client software is TheGreenbowVPN (In trial mode)
>
> The good news is that both the client and VPN Gateway agree _a tunnel
> has been created. The log on the Gateway is reporting "IKE[_1] Set up
> ESP tunnel with aaa.bbb.ccc.ddd Success!" (aaa.bbb.ccc.ddd_ is the
> address of the remote client).
>
> The bad news is that the remote machine cannot ping the mach_ines on
> the other end of the VPN nor does it have any access to the shared
> reso_urces on the remote LAN.
>
> I do have one thing that confuses me even more. The client _as well
> as the VPN Gateway is on LAN that has local addresses of
> 192.16_8.1.xxx So how does the client differentiate between machine
> 192.168_.1.100 (for example) on his network and a machine on the local
> LAN with _the same address?
> Thanks in advance for all replies.
>
> Wardell Castles
>
Hi,
the answer is unfortunately that it doesn't. The two ends have usually
to be in two different subnets. For some top-of-the-range routers fudges
can be made, but don't go there unless you have to. Be a coward and put
one of the LANs at 192.168.2.xxx for example.
HTH,
Colin
| |
| Ken Endeley 2005-02-02, 8:45 pm |
| CoolUncle wrote:
> wardellcastles wrote:
>
> Hi,
>
> the answer is unfortunately that it doesn't. The two ends have usually
> to be in two different subnets. For some top-of-the-range routers fudges
> can be made, but don't go there unless you have to. Be a coward and put
> one of the LANs at 192.168.2.xxx for example.
>
> HTH,
>
> Colin
Static routes for both remote networks should resolve your problems
Ken
|
|
|
|
|