On Mon, Mar 21, 2011 at 10:02 AM, Shachar Shemesh wrote:
> On 21/03/11 02:41, Etzion Bar-Noy wrote:
>
>> It is common that the VPN provider policy *prevents* you from connecting
>> to multiple networks (theirs and someone else's). The logic behind it is to
>> prevent data leak, especially accident
On 21/03/11 02:41, Etzion Bar-Noy wrote:
It is common that the VPN provider policy *prevents* you from
connecting to multiple networks (theirs and someone else's). The logic
behind it is to prevent data leak, especially accidental, by combining
somehow their network with someone else's.
You ha
On 21/03/11 09:43, Baruch Siach wrote:
Hi Shachar,
On Mon, Mar 21, 2011 at 04:51:43AM +0200, Shachar Shemesh wrote:
I think so.
Instead of me trying to explain it to you, why don't you just try to
draw the network topology you think will solve the problem. I
believe that will give you the
Hi Shachar,
On Mon, Mar 21, 2011 at 04:51:43AM +0200, Shachar Shemesh wrote:
> On 20/03/11 23:49, Elazar Leibovich wrote:
> >Yeah, but as your probably know, VPN is used in practice to
> >connect to your workstation from your laptop
> >
> >And VPN solution could offer NAT, in fact a shallow Google
On 20/03/11 23:49, Elazar Leibovich wrote:
Yeah, but as your probably know, VPN is used in practice to connect to
your workstation from your laptop
And VPN solution could offer NAT, in fact a shallow Google search[1]
offers exactly the same solution.
Is there something I'm missing here?
It is common that the VPN provider policy *prevents* you from connecting to
multiple networks (theirs and someone else's). The logic behind it is to
prevent data leak, especially accidental, by combining somehow their network
with someone else's.
So - this poses no problem to be dealt with. The co
On Sun, Mar 20, 2011 at 9:54 PM, Shachar Shemesh wrote:
>
> On another side note, what does it do if I'm having a 192.168.4.* internal
>> network?
>>
> Then you are @!#*%!@#$@!)(!@#&%@#! !@(%!@#()#!@$!@%#.
Wow, I'm not sure I know any adjective that long in English ;-)
VPN is designed to conne
On 20/03/11 21:40, Elazar Leibovich wrote:
On a side note, the VPN client on windows shoves entries to the
routing table which seems to depend on the actual network I'm
connecting to (192.18.4.* for instance, I don't think it does so for
all networks), how does it know the destination network
Anyone have experience connecting to Checkpoint VPN using Checkpoint
Endpoint security with Linux? The windows client is called "Checkpoint
Endpoint Security" and looks like a yellow lock in the taskbar.
They seem to have a client, but I'm not sure which one to download, and the
one I tried doesn't
