[vpn-help] Problem with iked, a bridge and xen

Alexis La Goutte alexis.lagoutte at gmail.com
Wed Dec 17 09:13:24 CST 2014


On Tue, Dec 16, 2014 at 7:00 PM, Stéphane PERON <s.peron at free.fr> wrote:
>
>  Bonjour Alexy,
>
> My VPN gateway as you see is the ip of my shrew client : 192.168.35.64
>
My question is what the type/marque of your VPN Gateway

>
> For the install on windows ... I have windows 2000 ..And I am afraid it is
> too old ...
>

> Can we use shrew on windows 2000 ?
>
Yes but Shrew is old too ;-)
and it is compatible with Windows 2000 (2K) see OS support of
https://www.shrew.net/download/vpn

>
> thanks a lot
>
De rien

>
> Stéphane
>
> Le 16/12/2014 18:07, Alexis La Goutte a écrit :
>
>   Bonjour Stéphane,
>
>  What is your VPN Gateway ?
>
>  Why don't install Shrew directly on Windows VM ? (VPN Client don't like
> share connection...)
>
> Regards,
>
>
> On Tue, Dec 16, 2014 at 3:34 PM, Stéphane PERON <s.peron at free.fr> wrote:
>>
>> Hi all,
>>
>> I have installed xen on my linux computer ... and started, on this
>> computer, a xen virtual machine on windows ...
>>
>> iked works very well ... creating a tap0 connection, when I want to use
>> an IPSec connection
>> My windows VM can go on the web ... no problem !
>>
>> So, what's wrong ?
>>
>> When I want my VM Windows use the "tap0" IPSec connection  ... I does not
>> work !
>> I can't join any computer on the other side of the IPSec connection ...
>> althougth I do it on linux.
>>
>> Please find my configuration :
>>
>> =================================================
>>
>> moua at SPE-FIXE:~$ cat /etc/network/interfaces
>>
>> auto lo
>> iface lo inet loopback
>>
>> auto eth0
>> iface eth0 inet manual
>>
>> auto xenbr0
>> iface xenbr0 inet dhcp
>>     bridge_ports eth0
>>         bridge_fd 9
>>         bridge_hello 2
>>         bridge_maxage 12
>>         bridge_stp off
>>
>> =================================================
>>
>> moua at SPE-FIXE:~$ route -n
>> Table de routage IP du noyau
>> Destination     Passerelle      Genmask         Indic Metric Ref Use Iface
>> 0.0.0.0         192.168.1.254   0.0.0.0         UG    1 0        0 xenbr0
>> 95.141.100.6    192.168.1.254   255.255.255.255 UGH   0 0        0 xenbr0
>> 169.254.0.0     0.0.0.0         255.255.0.0     U     1000 0        0
>> xenbr0
>> 192.168.1.0     0.0.0.0         255.255.255.0   U     0 0        0 xenbr0
>> 192.168.35.0    0.0.0.0         255.255.255.0   U     0 0        0 tap0
>> 192.168.201.0   192.168.35.64   255.255.255.0   UG    0 0        0 tap0
>>
>> ==================================================
>>
>> When I try to ping the ip 192.168.201.88 from the windows machine, it
>> does not work
>>
>> First, I don't understand why the default route is on the first line ...
>> Could it be the problem ?
>>
>> Any idea that could fix the problem ?
>>
>> Thanks a lot for your help
>>
>> Stéphane
>> _______________________________________________
>> vpn-help mailing list
>> vpn-help at lists.shrew.net
>> https://lists.shrew.net/mailman/listinfo/vpn-help
>>
>
>
> _______________________________________________
> vpn-help mailing list
> vpn-help at lists.shrew.net
> https://lists.shrew.net/mailman/listinfo/vpn-help
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.shrew.net/pipermail/vpn-help/attachments/20141217/5cd5161f/attachment.html>


More information about the vpn-help mailing list