Hi,<br><br>The (client) router is may be bugged, <span id="result_box" class="short_text" lang="en"><span style="color: rgb(0, 0, 0);" title="">you have tested disable</span></span> NAT Traversal ?<br><br>Regards,<br><br><div class="gmail_quote">
On Sat, Nov 20, 2010 at 5:09 PM, <span dir="ltr"><<a href="mailto:kpickard@simplyc.com">kpickard@simplyc.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
It probably does but it has no way of knowing who to pass the packet to as it came back on the wrong port. It has nothing to<br>
match on. There is no way for it to know that the reply it receives on port 500 corresponds to the request that was sent out on<br>
port 26891.<br>
<div class="im"><br>
-----------------------------------~~~~~~~-----------------------------<br>
Doing what you love is Freedom. | o o | Kevin Pickard<br>
Loving what you do is Happiness. | ^ | <a href="mailto:kpickard@simplyc.com">kpickard@simplyc.com</a><br>
------------------------------^^^-----------^^^------------------------<br>
<br>
<br>
</div>On Sat 10/11/20 10:59 AM , Alexis La Goutte <a href="mailto:alexis.lagoutte@gmail.com">alexis.lagoutte@gmail.com</a> sent:<br>
<div class="im">> Hi,<br>
><br>
> No VPN pass through in your router ?<br>
</div><div class="im">> On Sat, Nov 20, 2010 at 4:54 PM, wrote:<br>
> Hi Alexis. My client is behind a router (it is *not*<br>
> connected directly to the internet). So the router has to route the<br>
> return packet. It therefore must come back to the originating port<br>
> (namely 26891 in this example).<br>
><br>
> -----------------------------------~~~~~~~-----------------------------<br>
> Doing what you love is Freedom. | o o | Kevin Pickard<br>
> Loving what you do is Happiness. | ^ | <br>
><br>
</div>> ------------------------------^^^-----------^^^------------------------<br>
> On Sat 10/11/20 10:42 AM , Alexis La Goutte sent:<br>
<div><div></div><div class="h5">> > Hi Kevin,<br>
> ><br>
> > Your Client is between a router ? or directly connected to<br>
> Internet ?<br>
> ><br>
> > Regards,<br>
> ><br>
> > On Fri, Nov 19, 2010 at 7:07 PM, wrote:<br>
> > Thanks for the response Alexis.<br>
> > I can not easily test from another location but I did<br>
> > identify where there is a problem. I managed to run a<br>
> > Wireshark trace outside of the router at the client side and I see<br>
> > that the Netgear *is* responding. The problem is<br>
> > that it is responding to port 500 when it received the request<br>
> from<br>
> > port 26891! So the router here rightly does not<br>
> > route the response. So the flow is as follows.<br>
> > Client SrcPort(26891) -> DstPort(500) ISAKMP Req<br>
> <br>
> > Netgear<br>
> > Client DstPort(500) Hi kevin,<br>
> > ><br>
> > > I received your message, have you tested from another Internet<br>
> > > access?<br>
> > > Because it is very strange to not receive answer from router<br>
> > > Regards,<br>
> > > On Thu, Nov 18, 2010 at 7:12 PM, wrote:<br>
> > > Hello Alexis. Sorry to bother you. I was just wondering if<br>
> > you<br>
> > > received the message below sent yesterday (and<br>
> > > followup with Netgear config) and if you had any further ideas?<br>
> > You<br>
> > > helped me get to the point where it is almost<br>
> > > negotiating. Thank you very much for that.<br>
> > ><br>
> > ><br>
> ><br>
> -----------------------------------~~~~~~~-----------------------------<br>
> > > Doing what you love is Freedom. | o o | Kevin Pickard<br>
> > > Loving what you do is Happiness. | ^ | <br>
> > ><br>
> > ><br>
> ><br>
> ------------------------------^^^-----------^^^------------------------<br>
> > > ----- Original Message -----<br>
> > > From:<br>
> > > To: "Alexis La Goutte"<br>
> > > Sent: Wed 10/11/17 2:46 PM<br>
> > > Subject: Fwd: Re: Re: [vpn-help] Netgear<br>
> > > FVS318<br>
> > > Hi Alexis. I have not included the Shrew debug before<br>
> > because<br>
> > > it just shows the retry of the ISAKMP packet<br>
> > > send (last few lines). I have now included it below. I also am<br>
> > > running Wireshark on the client side and all I see<br>
> > > is the ISAKMP packet going out with no response coming back in<br>
> as<br>
> > > well. So everything important right now is<br>
> > > happening on the Netgear router side. Based on my earlier logs<br>
> > from<br>
> > > the Netgear it looks like it is trying to send<br>
> > > a response but for whatever reason it is not getting back to the<br>
> > > client. As I said, my client is also behind a NAT<br>
> > > router. Is there something else that I need to setup in the<br>
> > Netgear<br>
> > > so it knows how to reach the client behind the<br>
> > > router or is there something else I need to configure on the<br>
> > client<br>
> > > so it can tell the Netgear how to get back to<br>
> > > it?<br>
> > > Once again thanks for all your help.<br>
> > > 10/11/17 14:37:39 ## : IKE Daemon, ver 2.1.7<br>
> > > 10/11/17 14:37:39 ## : Copyright 2010 Shrew Soft Inc.<br>
> > > 10/11/17 14:37:39 ## : This product linked OpenSSL 0.9.8h 28 May<br>
> > > 2008<br>
> > > 10/11/17 14:37:39 ii : opened 'C:Program FilesShrewSoftVPN<br>
> > > Clientdebugiked.log'<br>
> > > 10/11/17 14:37:39 ii : rebuilding vnet device list ...<br>
> > > 10/11/17 14:37:40 ii : device ROOTVNET000 disabled<br>
> > > 10/11/17 14:37:40 ii : network process thread begin ...<br>
> > > 10/11/17 14:37:40 ii : pfkey process thread begin ...<br>
> > > 10/11/17 14:37:40 ii : ipc server process thread begin ...<br>
> > > 10/11/17 14:37:43 ii : ipc client process thread begin ...<br>
> > > 10/11/17 14:37:43 > : key exchange payload<br>
> > > 10/11/17 14:37:43 >> : nonce payload<br>
> > > 10/11/17 14:37:43 >> : identification payload<br>
> > > 10/11/17 14:37:43 >> : vendor id payload<br>
> > > 10/11/17 14:37:43 ii : local supports nat-t ( draft v00 )<br>
> > > 10/11/17 14:37:43 >> : vendor id payload<br>
> > > 10/11/17 14:37:43 ii : local supports nat-t ( draft v01 )<br>
> > > 10/11/17 14:37:43 >> : vendor id payload<br>
> > > 10/11/17 14:37:43 ii : local supports nat-t ( draft v02 )<br>
> > > 10/11/17 14:37:43 >> : vendor id payload<br>
> > > 10/11/17 14:37:43 ii : local supports nat-t ( draft v03 )<br>
> > > 10/11/17 14:37:43 >> : vendor id payload<br>
> > > 10/11/17 14:37:43 ii : local supports nat-t ( rfc )<br>
> > > 10/11/17 14:37:43 >> : vendor id payload<br>
> > > 10/11/17 14:37:43 ii : local supports FRAGMENTATION<br>
> > > 10/11/17 14:37:43 >> : vendor id payload<br>
> > > 10/11/17 14:37:43 ii : local supports DPDv1<br>
> > > 10/11/17 14:37:43 >> : vendor id payload<br>
> > > 10/11/17 14:37:43 ii : local is SHREW SOFT compatible<br>
> > > 10/11/17 14:37:43 >> : vendor id payload<br>
> > > 10/11/17 14:37:43 ii : local is NETSCREEN compatible<br>
> > > 10/11/17 14:37:43 >> : vendor id payload<br>
> > > 10/11/17 14:37:43 ii : local is SIDEWINDER compatible<br>
> > > 10/11/17 14:37:43 >> : vendor id payload<br>
> > > 10/11/17 14:37:43 ii : local is CISCO UNITY compatible<br>
> > > 10/11/17 14:37:43 >= : cookies 7b05d12fcf86a8d3:0000000000000000<br>
> > > 10/11/17 14:37:43 >= : message 00000000<br>
> > > 10/11/17 14:37:43 -> : send IKE packet MAILFILTERGATEWAY<br>
> WARNING:<br>
</div></div>> > > NUMERICAL LINKS ARE OFTEN MALICIOUS: MAILFILTERGATEWAY WARNING:<br>
> NUMERICAL LINKS ARE OFTEN MALICIOUS: <a href="http://192.168.1.83:500" target="_blank">192.168.1.83:500</a> [4] [4] [5] -><br>
<div class="im">> > > MAILFILTERGATEWAY WARNING: NUMERICAL LINKS ARE OFTEN MALICIOUS:<br>
> > > MAILFILTERGATEWAY WARNING: NUMERICAL LINKS ARE OFTEN MALICIOUS:<br>
</div>> <a href="http://206.248.160.8:500" target="_blank">206.248.160.8:500</a> [5] [5] [6] ( 554 bytes )<br>
<div class="im">> > > 10/11/17 14:37:43 DB : phase1 resend event scheduled ( ref count<br>
> =<br>
> > 2<br>
> > > )<br>
> > > 10/11/17 14:37:48 -> : resend 1 phase1 packet(s)<br>
> MAILFILTERGATEWAY<br>
</div>> > > WARNING: NUMERICAL LINKS ARE OFTEN MALICIOUS: MAILFILTERGATEWAY<br>
> WARNING: NUMERICAL LINKS ARE OFTEN MALICIOUS: <a href="http://192.168.1.83:500" target="_blank">192.168.1.83:500</a> [6] [6]<br>
<div class="im">> > [7] -><br>
> > > MAILFILTERGATEWAY WARNING: NUMERICAL LINKS ARE OFTEN MALICIOUS:<br>
> > > MAILFILTERGATEWAY WARNING: NUMERICAL LINKS ARE OFTEN MALICIOUS:<br>
</div>> <a href="http://206.248.160.8:500" target="_blank">206.248.160.8:500</a> [7] [7] [8]<br>
<div><div></div><div class="h5">> > ><br>
> > ><br>
> ><br>
> -----------------------------------~~~~~~~-----------------------------<br>
> > > Doing what you love is Freedom. | o o | Kevin Pickard<br>
> > > Loving what you do is Happiness. | ^ | <br>
> > ><br>
> > ><br>
> ><br>
> ------------------------------^^^-----------^^^------------------------<br>
> > > On Wed 10/11/17 2:12 PM , Alexis La Goutte sent:<br>
> > > > Hi,<br>
> > > ><br>
> > > > No, the communications never use TCP, ISAKMP use UDP (Port<br>
> 500).<br>
> > > ><br>
> > > > No trace in Shrew Debug ?<br>
> > > ><br>
> > > > Regards,<br>
> > > > On Wed, Nov 17, 2010 at 7:51 PM, wrote:<br>
> > > > Hi Alexis. Thanks again for your help.<br>
> > > > Well I noticed that there was a mismatch in the Key<br>
> Group<br>
> > so<br>
> > > I<br>
> > > > changed my Netgear to use DH Group 2 as this is<br>
> > > > what the Shrew client was using for DH exchange. I also<br>
> > explicitly<br>
> > > > specified 3DES as the cipher algorithm on the<br>
> > > > client side rather than auto because I was seeing a lot of<br>
> > trying<br>
> > > > the different options on the Netgear side until<br>
> > > > it settled on 3DES anyway.<br>
> > > > So now things are looking like they are getting further<br>
> > > along<br>
> > > > (see Netgear log below). It looks though like<br>
> > > > the Netgear is trying to send back a response (the TX >> AM_R1<br>
> > > line)<br>
> > > > but I am not seeing it at the client side. Is<br>
> > > > there something else I should be doing as the client is behind<br>
> a<br>
> > > NAT<br>
> > > > router? Should the communications from the<br>
> > > > client not be over TCP rather than UDP to make this work?<br>
> > > > Again thanks for all your help.<br>
> > > > Wed, 11/17/2010 13:43:00 - TekSavvy IPsec:Receive Packet<br>
> > > > address:0x1396850 from 216.254.149.98<br>
> > > > Wed, 11/17/2010 13:43:00 - TekSavvy IKE:Peer Initialized IKE<br>
> > > > Aggressive Mode<br>
> > > > Wed, 11/17/2010 13:43:00 - TekSavvy IKE:RX > AM_R1 :<br>
> > > 216.254.149.98<br>
> > > > Wed, 11/17/2010 13:43:00 - TekSavvy IPsec:inserting event<br>
> > > > EVENT_RETRANSMIT, timeout in 10 seconds for #4<br>
> > > > Wed, 11/17/2010 13:43:04 - TekSavvy IPsec:event after this is<br>
> > > > EVENT_RETRANSMIT in 4 seconds<br>
> > > > Wed, 11/17/2010 13:43:04 - TekSavvy IPsec:handling event<br>
> > > > EVENT_RETRANSMIT for d8fe9562 "Client_Shrew_tmp2" #3<br>
> > > > Wed, 11/17/2010 13:43:04 - TekSavvy IPsec:inserting event<br>
> > > > EVENT_RETRANSMIT, timeout in 20 seconds for #3<br>
> > > ><br>
> > > ><br>
> > ><br>
> ><br>
> -----------------------------------~~~~~~~-----------------------------<br>
> > > > Doing what you love is Freedom. | o o | Kevin Pickard<br>
> > > > Loving what you do is Happiness. | ^ | <br>
> > > ><br>
> > > ><br>
> > ><br>
> ><br>
> ------------------------------^^^-----------^^^------------------------<br>
> > > > On Wed 10/11/17 12:31 PM , Alexis La Goutte sent:<br>
> > > > > Hi Kevin,<br>
</div></div>> > > > > The identifier Information (<a href="http://fvs_remote.com" target="_blank">fvs_remote.com</a> [8] [8] [11] [4]<br>
> [1]<br>
> > and<br>
> > > > <a href="http://fvs_local.com" target="_blank">fvs_local.com</a> [9] [9] [12] [5] [2])<br>
<div><div></div><div class="h5">> > > > > are actual values to be used, not need to resolve this<br>
> > address.<br>
> > > > > Check your phase1 parameter (ISAKMP)<br>
> > > > ><br>
> > > > > Regards,<br>
> > > > ><br>
> > > > > On Wed, Nov 17, 2010 at 6:25 PM, wrote:<br>
> > > > > Thank you Alexis. I went through the VPN Wizard again<br>
> > and<br>
> > > > > followed the steps at the link you provided. I then<br>
> > > > > rebooted my router to make sure it was starting with the<br>
> > proper<br>
> > > > > configuration. Now it appears that my router is no<br>
> > > > > longer flagging the ISAKMP packets as suspicious and tossing<br>
> > > them<br>
> > > > > (which is good). In fact it looks like my router<br>
> > > > > is actually trying to process the packets now. But it is<br>
> > having<br>
> > > > > trouble with what it is seeing, based on its own<br>
> > > > > internal logs (below)...and a response is not being sent<br>
> back<br>
> > to<br>
> > > > the<br>
> > > > > Shrew client.<br>
> > > > > My question now is, according to the link you<br>
> provided,<br>
> > I<br>
> > > > was<br>
> > > > > to set the Identifier information fields to<br>
</div></div>> > > > > <a href="http://fvs_remote.com" target="_blank">fvs_remote.com</a> [10] [10] [13] [6] [4] and <a href="http://fvs_local.com" target="_blank">fvs_local.com</a> [11]<br>
<div class="im">> [11] [14]<br>
> > [7] [5]. Are<br>
> > > these just<br>
> > > > examples or<br>
> > > > > are they the actual values to be used? Should these<br>
> > > > > not resolve to real addresses? As can be seen below the FQDN<br>
> > of<br>
</div>> > > > > <a href="http://fvs_remote.com" target="_blank">fvs_remote.com</a> [12] [12] [15] [8] [6] is being sent by the<br>
<div><div></div><div class="h5">> Shrew<br>
> > client in<br>
> > > > > the ISAKMP packet. The Netgear then complains about not<br>
> having<br>
> > a<br>
> > > > > connection. Is this because this address does not<br>
> > > > > resolve?<br>
> > > > > By the way, the Shrew client is on a network behind a<br>
> > > router<br>
> > > > > so is NAT.<br>
> > > > > Anyway, below is the log from my Netgear. On the Shrew<br>
> > > side<br>
> > > > I<br>
> > > > > only see the ISAKMP packets being sent out every<br>
> > > > > 5 seconds without any response coming back.<br>
> > > > > Wed, 11/17/2010 10:44:22 - TekSavvy IKE:Trying Dynamic IP<br>
> > > > Searching<br>
> > > > > Wed, 11/17/2010 10:44:28 - TekSavvy IPsec:Receive Packet<br>
> > > > > address:0x1396850 from 216.254.149.98<br>
> > > > > Wed, 11/17/2010 10:44:28 - TekSavvy IKE:Peer Initialized IKE<br>
> > > > > Aggressive Mode<br>
> > > > > Wed, 11/17/2010 10:44:28 - TekSavvy IKE:RX Hi Kevin,<br>
> > > > > ><br>
> > > > > > There is a VPN wizard in your FVS318v1 ?<br>
> > > > > ><br>
> > > > > > Because use VPN Wizard and information in this blog<br>
> > > > > ><br>
> > > > ><br>
> > > ><br>
> > ><br>
> ><br>
> <a href="http://blog.igut.fr/post/2009/02/07/Client-VPN-IPSec-Shrew-avec-Routeur-VPN" target="_blank">http://blog.igut.fr/post/2009/02/07/Client-VPN-IPSec-Shrew-avec-Routeur-VPN</a><br>
> [13]<br>
> > [13]<br>
> > > [16]<br>
> > > > [9]<br>
> > > > > [9]<br>
> > > > > > -NETGEAR[1]<br>
> > > > > > And it should work !<br>
> > > > > ><br>
> > > > > > Regards,<br>
> > > > > ><br>
> > > > > > On Mon, Nov 15, 2010 at 2:05 PM, Kevin Pickard wrote:<br>
> > > > > > Thanks for the response Alexis. So have you<br>
> > managed<br>
> > > > to<br>
> > > > > > get a FVS318v1 to work? Do you know what configuration I<br>
> > > should<br>
> > > > > use?<br>
> > > > > > As I said in my initial post, my attempts at<br>
> > > > > configuring<br>
> > > > > > it have failed (see below).<br>
> > > > > > At 03:59 AM 2010-11-15, Alexis La Goutte wrote:<br>
> > > > > > >Hi Kevin,<br>
> > > > > > ><br>
> > > > > > >Yes, it work but you should not use the Xauth &<br>
> ModeConfig<br>
> > > (no<br>
> > > > > > available in FVS318v1)<br>
> > > > > > ><br>
> > > > > > >Regards,<br>
> > > > > > ><br>
> > > > > > ><br>
> > > > > > >On Sat, Nov 13, 2010 at 11:19 PM, Kevin Pickard wrote:<br>
> > > > > > > I take it no-one else has any experience with<br>
> > this?<br>
> > > > > > Andreas was the only one to respond but his FVS318 appears<br>
> > to<br>
> > > be<br>
> > > > a<br>
> > > > > > newer version and is completely different from mine. I<br>
> have<br>
> > > the<br>
> > > > > older<br>
> > > > > > v1 hardware (FVS318v1). Anyone?<br>
> > > > > > >At 16:59:21 2010-10-26, wrote:<br>
> > > > > > >>Message: 2<br>
> > > > > > >>Date: Tue, 26 Oct 2010 16:59:21 +0200<br>
> > > > > > >>From:<br>
> > > > > > >>Subject: Re: [vpn-help] Netgear FVS318<br>
> > > > > > >>To:<br>
> > > > > > >>Message-ID:<br>
> > > > > > >>Content-Type: text/plain; charset="iso-8859-1";<br>
> > > > Format="flowed";<br>
> > > > > > >> DelSp="Yes"<br>
> > > > > > >><br>
> > > > > > >>Zitat von :<br>
> > > > > > >><br>
> > > > > > >>> Hello. Does anyone know if the Shrew client<br>
> will<br>
> > > > work<br>
> > > > > > with the<br>
> > > > > > >>> Netgear FVS318 router?<br>
> > > > > > >>><br>
> > > > > > >>> I have scanned the archives and I have found<br>
> > > > > references<br>
> > > > > > to the<br>
> > > > > > >>> FVG318 but nothing specific about the FVS318. I have<br>
> > seen<br>
> > > > > > references<br>
> > > > > > >>> to needing Mode and Xauth enabled to get the FVS318 to<br>
> > > work<br>
> > > > > but<br>
> > > > > > >>> neither of those options exist on the FVS318 (that I<br>
> can<br>
> > > > > find).<br>
> > > > > > So I<br>
> > > > > > >>> think those people are confusing the FVS318 with<br>
> another<br>
> > > > > model.<br>
> > > > > > >>><br>
> > > > > > >>> Has anyone been able to get the Netgear FVS318<br>
> > (V1<br>
> > > > > > hardware<br>
> > > > > > >>> running V2.4 firmware) to work with the Shrew client?<br>
> > > > > > >>><br>
> > > > > > >>> My initial attempts at trying various<br>
> > > configurations<br>
> > > > > > have only<br>
> > > > > > >>> resulted in security warnings on my FVS318 indicating<br>
> > that<br>
> > > > UDP<br>
> > > > > > >>> packets (from the Shrew Client) are being tossed<br>
> because<br>
> > > > they<br>
> > > > > > >>> contain 'Suspicious UDP Data'. I have<br>
> configured<br>
> > > to<br>
> > > > > use<br>
> > > > > > PSK. On the<br>
> > > > > > >>> client<br>
> > > > > > >>> side, via Wireshark, I only see the ISAKMP packet<br>
> being<br>
> > > sent<br>
> > > > > out<br>
> > > > > > >>> (this is the one being tossed by the FVS318) at 5<br>
> second<br>
> > > > > > intervals.<br>
> > > > > > >>> The<br>
> > > > > > >>> Shrew client itself shows "bringing up tunnel ...",<br>
> then<br>
> > > > > > eventually<br>
> > > > > > >>> followed by "negotiation timout [sic] occurred" after<br>
> > the<br>
> > > > > ISAKMP<br>
> > > > > > >>> packet has been sent 4 times.<br>
> > > > > > >><br>
> > > > > > >>Only some guess:<br>
> > > > > > >>If the netgear has some form of firewall you maybe need<br>
> to<br>
> > > > allow<br>
> > > > > > >>inbound UDP port 500 and if using UDP encapsulation port<br>
> > > 4500<br>
> > > > as<br>
> > > > > > well<br>
> > > > > > >>to get the tunnel up.<br>
> > > > > > >><br>
> > > > > > >>Regards<br>
> > > > > > >><br>
> > > > > > >>Andreas<br>
> > > > > > >><br>
> > > > > > >><br>
> > > > > > >>-------------- next part --------------<br>
> > > > > > >>A non-text attachment was scrubbed...<br>
> > > > > > >>Name: smime.p7s<br>
> > > > > > >>Type: application/pkcs7-signature<br>
> > > > > > >>Size: 6046 bytes<br>
> > > > > > >>Desc: S/MIME Cryptographic Signature<br>
> > > > > > >>URL:<br>
> > > > > > >><br>
> > > > > > >>------------------------------<br>
> > > > > > >><br>
> > > > > > >>_______________________________________________<br>
> > > > > > >>vpn-help mailing list<br>
> > > > > > >><br>
> > > > > > >><a href="http://lists.shrew.net/mailman/listinfo/vpn-help" target="_blank">http://lists.shrew.net/mailman/listinfo/vpn-help</a> [14]<br>
> [14] [17]<br>
> > [10]<br>
> > > [10]<br>
> > > > [19]<br>
> > > > > > >><br>
> > > > > > >><br>
> > > > > > >>End of vpn-help Digest, Vol 49, Issue 25<br>
> > > > > > >>****************************************<br>
> > > > > ><br>
> > > > > ><br>
> > > > ><br>
> > > ><br>
> > ><br>
> ><br>
> >-----------------------------------~~~~~~~-----------------------------<br>
> > > > > > > Doing what you love is Freedom. | o o | Kevin<br>
> Pickard<br>
> > > > > > > Loving what you do is Happiness. | ^ |<br>
> > > > > ><br>
> > > > > ><br>
> > > > ><br>
> > > ><br>
> > ><br>
> ><br>
> >------------------------------^^^-----------^^^------------------------<br>
> > > > > > >_______________________________________________<br>
> > > > > > >vpn-help mailing list<br>
> > > > > > ><br>
> > > > > > ><a href="http://lists.shrew.net/mailman/listinfo/vpn-help" target="_blank">http://lists.shrew.net/mailman/listinfo/vpn-help</a> [15]<br>
> [15] [18]<br>
> > [11]<br>
> > > [11] [24]<br>
> > > > > ><br>
> > > > > ><br>
> > > > ><br>
> > > ><br>
> > ><br>
> ><br>
> -----------------------------------~~~~~~~-----------------------------<br>
> > > > > > Doing what you love is Freedom. | o o | Kevin<br>
> Pickard<br>
> > > > > > Loving what you do is Happiness. | ^ |<br>
> > > > > ><br>
> > > > > ><br>
> > > > ><br>
> > > ><br>
> > ><br>
> ><br>
> ------------------------------^^^-----------^^^------------------------<br>
> > > > > ><br>
> > > > > ><br>
> > > > > > Links:<br>
> > > > > > ------<br>
> > > > > > [1]<br>
> > > > > ><br>
> > > > ><br>
> > > ><br>
> > ><br>
> ><br>
> <a href="http://blog.igut.fr/post/2009/02/07/Client-VPN-IPSec-Shrew-avec-Routeur-VPN" target="_blank">http://blog.igut.fr/post/2009/02/07/Client-VPN-IPSec-Shrew-avec-Routeur-VPN</a><br>
> [16]<br>
> > [16]<br>
> > > [19]<br>
> > > > [12]<br>
> > > > > [12]<br>
> > > > > > -NETGEAR[15]<br>
> > ><br>
> > ><br>
> > > Links:<br>
> > > ------<br>
</div></div>> > > [5] MAILFILTERGATEWAY WARNING: NUMERICAL LINKS ARE OFTEN<br>
> MALICIOUS: <a href="http://192.168.1.83:500" target="_blank">http://192.168.1.83:500</a> [17] [17]<br>
> > > [6] MAILFILTERGATEWAY WARNING: NUMERICAL LINKS ARE OFTEN<br>
> MALICIOUS: <a href="http://206.248.160.8:500" target="_blank">http://206.248.160.8:500</a> [18] [18]<br>
<div class="im">> > > [7] MAILFILTERGATEWAY WARNING: NUMERICAL LINKS ARE OFTEN<br>
</div>> MALICIOUS: <a href="http://192.168.1.83:500" target="_blank">http://192.168.1.83:500</a> [19] [19]<br>
> > > [8] MAILFILTERGATEWAY WARNING: NUMERICAL LINKS ARE OFTEN<br>
> MALICIOUS: <a href="http://206.248.160.8:500" target="_blank">http://206.248.160.8:500</a> [20] [20]<br>
> > > [11] <a href="http://fvs_remote.com" target="_blank">http://fvs_remote.com</a> [21] [21]<br>
> > > [12] <a href="http://fvs_local.com" target="_blank">http://fvs_local.com</a> [22] [22]<br>
> > > [13] <a href="http://fvs_remote.com" target="_blank">http://fvs_remote.com</a> [23] [23]<br>
> > > [14] <a href="http://fvs_local.com" target="_blank">http://fvs_local.com</a> [24] [24]<br>
> > > [15] <a href="http://fvs_remote.com" target="_blank">http://fvs_remote.com</a> [25] [25]<br>
<div class="im">> > > [16]<br>
> > ><br>
> ><br>
> <a href="http://blog.igut.fr/post/2009/02/07/Client-VPN-IPSec-Shrew-avec-Routeur-VPN" target="_blank">http://blog.igut.fr/post/2009/02/07/Client-VPN-IPSec-Shrew-avec-Routeur-VPN</a><br>
> [26]<br>
> > [26]<br>
</div>> > > [17] <a href="http://lists.shrew.net/mailman/listinfo/vpn-help" target="_blank">http://lists.shrew.net/mailman/listinfo/vpn-help</a> [27] [27]<br>
> > > [18] <a href="http://lists.shrew.net/mailman/listinfo/vpn-help" target="_blank">http://lists.shrew.net/mailman/listinfo/vpn-help</a> [28] [28]<br>
<div class="im">> > > [19]<br>
> > ><br>
> ><br>
> <a href="http://blog.igut.fr/post/2009/02/07/Client-VPN-IPSec-Shrew-avec-Routeur-VPN" target="_blank">http://blog.igut.fr/post/2009/02/07/Client-VPN-IPSec-Shrew-avec-Routeur-VPN</a><br>
> [29]<br>
</div>> > [29]<br>
> > ><br>
> > ><br>
> ><br>
> ><br>
> > Links:<br>
> > ------<br>
> > [4] MAILFILTERGATEWAY WARNING: NUMERICAL LINKS ARE OFTEN<br>
> MALICIOUS: <a href="http://192.168.1.83:500" target="_blank">http://192.168.1.83:500</a> [30]<br>
<div class="im">> > [5] MAILFILTERGATEWAY WARNING: NUMERICAL LINKS ARE OFTEN<br>
</div>> MALICIOUS: <a href="http://206.248.160.8:500" target="_blank">http://206.248.160.8:500</a> [31]<br>
> > [6] MAILFILTERGATEWAY WARNING: NUMERICAL LINKS ARE OFTEN<br>
> MALICIOUS: <a href="http://192.168.1.83:500" target="_blank">http://192.168.1.83:500</a> [32]<br>
<div class="im">> > [7] MAILFILTERGATEWAY WARNING: NUMERICAL LINKS ARE OFTEN<br>
</div>> MALICIOUS: <a href="http://206.248.160.8:500" target="_blank">http://206.248.160.8:500</a> [33]<br>
> > [8] <a href="http://fvs_remote.com" target="_blank">http://fvs_remote.com</a> [34]<br>
> > [9] <a href="http://fvs_local.com" target="_blank">http://fvs_local.com</a> [35]<br>
> > [10] <a href="http://fvs_remote.com" target="_blank">http://fvs_remote.com</a> [36]<br>
> > [11] <a href="http://fvs_local.com" target="_blank">http://fvs_local.com</a> [37]<br>
> > [12] <a href="http://fvs_remote.com" target="_blank">http://fvs_remote.com</a> [38]<br>
<div class="im">> > [13]<br>
> ><br>
> <a href="http://blog.igut.fr/post/2009/02/07/Client-VPN-IPSec-Shrew-avec-Routeur-VPN" target="_blank">http://blog.igut.fr/post/2009/02/07/Client-VPN-IPSec-Shrew-avec-Routeur-VPN</a><br>
</div>> [39]<br>
> > [14] <a href="http://lists.shrew.net/mailman/listinfo/vpn-help" target="_blank">http://lists.shrew.net/mailman/listinfo/vpn-help</a> [40]<br>
> > [15] <a href="http://lists.shrew.net/mailman/listinfo/vpn-help" target="_blank">http://lists.shrew.net/mailman/listinfo/vpn-help</a> [41]<br>
<div class="im">> > [16]<br>
> ><br>
> <a href="http://blog.igut.fr/post/2009/02/07/Client-VPN-IPSec-Shrew-avec-Routeur-VPN" target="_blank">http://blog.igut.fr/post/2009/02/07/Client-VPN-IPSec-Shrew-avec-Routeur-VPN</a><br>
</div>> [42]<br>
> > [17] MAILFILTERGATEWAY WARNING: NUMERICAL LINKS ARE OFTEN<br>
> MALICIOUS: <a href="http://192.168.1.83:500" target="_blank">http://192.168.1.83:500</a> [43]<br>
> > [18] MAILFILTERGATEWAY WARNING: NUMERICAL LINKS ARE OFTEN<br>
> MALICIOUS: <a href="http://206.248.160.8:500" target="_blank">http://206.248.160.8:500</a> [44]<br>
> > [19] MAILFILTERGATEWAY WARNING: NUMERICAL LINKS ARE OFTEN<br>
> MALICIOUS: <a href="http://192.168.1.83:500" target="_blank">http://192.168.1.83:500</a> [45]<br>
> > [20] MAILFILTERGATEWAY WARNING: NUMERICAL LINKS ARE OFTEN<br>
> MALICIOUS: <a href="http://206.248.160.8:500" target="_blank">http://206.248.160.8:500</a> [46]<br>
> > [21] <a href="http://fvs_remote.com" target="_blank">http://fvs_remote.com</a> [47]<br>
> > [22] <a href="http://fvs_local.com" target="_blank">http://fvs_local.com</a> [48]<br>
> > [23] <a href="http://fvs_remote.com" target="_blank">http://fvs_remote.com</a> [49]<br>
> > [24] <a href="http://fvs_local.com" target="_blank">http://fvs_local.com</a> [50]<br>
> > [25] <a href="http://fvs_remote.com" target="_blank">http://fvs_remote.com</a> [51]<br>
<div class="im">> > [26]<br>
> ><br>
> <a href="http://blog.igut.fr/post/2009/02/07/Client-VPN-IPSec-Shrew-avec-Routeur-VPN" target="_blank">http://blog.igut.fr/post/2009/02/07/Client-VPN-IPSec-Shrew-avec-Routeur-VPN</a><br>
</div>> [52]<br>
> > [27] <a href="http://lists.shrew.net/mailman/listinfo/vpn-help" target="_blank">http://lists.shrew.net/mailman/listinfo/vpn-help</a> [53]<br>
> > [28] <a href="http://lists.shrew.net/mailman/listinfo/vpn-help" target="_blank">http://lists.shrew.net/mailman/listinfo/vpn-help</a> [54]<br>
<div class="im">> > [29]<br>
> ><br>
> <a href="http://blog.igut.fr/post/2009/02/07/Client-VPN-IPSec-Shrew-avec-Routeur-VPN" target="_blank">http://blog.igut.fr/post/2009/02/07/Client-VPN-IPSec-Shrew-avec-Routeur-VPN</a><br>
</div>> [55]<br>
<div><div></div><div class="h5">> ><br>
> ><br>
><br>
><br>
> Links:<br>
> ------<br>
> [4] <a href="http://192.168.1.83:500" target="_blank">http://192.168.1.83:500</a><br>
> [5] <a href="http://206.248.160.8:500" target="_blank">http://206.248.160.8:500</a><br>
> [6] <a href="http://192.168.1.83:500" target="_blank">http://192.168.1.83:500</a><br>
> [7] <a href="http://206.248.160.8:500" target="_blank">http://206.248.160.8:500</a><br>
> [8] <a href="http://fvs_remote.com" target="_blank">http://fvs_remote.com</a><br>
> [9] <a href="http://fvs_local.com" target="_blank">http://fvs_local.com</a><br>
> [10] <a href="http://fvs_remote.com" target="_blank">http://fvs_remote.com</a><br>
> [11] <a href="http://fvs_local.com" target="_blank">http://fvs_local.com</a><br>
> [12] <a href="http://fvs_remote.com" target="_blank">http://fvs_remote.com</a><br>
> [13]<br>
> <a href="http://blog.igut.fr/post/2009/02/07/Client-VPN-IPSec-Shrew-avec-Routeur-VPN" target="_blank">http://blog.igut.fr/post/2009/02/07/Client-VPN-IPSec-Shrew-avec-Routeur-VPN</a><br>
> [14] <a href="http://lists.shrew.net/mailman/listinfo/vpn-help" target="_blank">http://lists.shrew.net/mailman/listinfo/vpn-help</a><br>
> [15] <a href="http://lists.shrew.net/mailman/listinfo/vpn-help" target="_blank">http://lists.shrew.net/mailman/listinfo/vpn-help</a><br>
> [16]<br>
> <a href="http://blog.igut.fr/post/2009/02/07/Client-VPN-IPSec-Shrew-avec-Routeur-VPN" target="_blank">http://blog.igut.fr/post/2009/02/07/Client-VPN-IPSec-Shrew-avec-Routeur-VPN</a><br>
> [17] <a href="http://192.168.1.83:500" target="_blank">http://192.168.1.83:500</a><br>
> [18] <a href="http://206.248.160.8:500" target="_blank">http://206.248.160.8:500</a><br>
> [19] <a href="http://192.168.1.83:500" target="_blank">http://192.168.1.83:500</a><br>
> [20] <a href="http://206.248.160.8:500" target="_blank">http://206.248.160.8:500</a><br>
> [21] <a href="http://fvs_remote.com" target="_blank">http://fvs_remote.com</a><br>
> [22] <a href="http://fvs_local.com" target="_blank">http://fvs_local.com</a><br>
> [23] <a href="http://fvs_remote.com" target="_blank">http://fvs_remote.com</a><br>
> [24] <a href="http://fvs_local.com" target="_blank">http://fvs_local.com</a><br>
> [25] <a href="http://fvs_remote.com" target="_blank">http://fvs_remote.com</a><br>
> [26]<br>
> <a href="http://blog.igut.fr/post/2009/02/07/Client-VPN-IPSec-Shrew-avec-Routeur-VPN" target="_blank">http://blog.igut.fr/post/2009/02/07/Client-VPN-IPSec-Shrew-avec-Routeur-VPN</a><br>
> [27] <a href="http://lists.shrew.net/mailman/listinfo/vpn-help" target="_blank">http://lists.shrew.net/mailman/listinfo/vpn-help</a><br>
> [28] <a href="http://lists.shrew.net/mailman/listinfo/vpn-help" target="_blank">http://lists.shrew.net/mailman/listinfo/vpn-help</a><br>
> [29]<br>
> <a href="http://blog.igut.fr/post/2009/02/07/Client-VPN-IPSec-Shrew-avec-Routeur-VPN" target="_blank">http://blog.igut.fr/post/2009/02/07/Client-VPN-IPSec-Shrew-avec-Routeur-VPN</a><br>
</div></div>> [30] <a href="http://192.168.1.83:500" target="_blank">http://192.168.1.83:500</a><br>
> [31] <a href="http://206.248.160.8:500" target="_blank">http://206.248.160.8:500</a><br>
> [32] <a href="http://192.168.1.83:500" target="_blank">http://192.168.1.83:500</a><br>
> [33] <a href="http://206.248.160.8:500" target="_blank">http://206.248.160.8:500</a><br>
> [34] <a href="http://fvs_remote.com" target="_blank">http://fvs_remote.com</a><br>
> [35] <a href="http://fvs_local.com" target="_blank">http://fvs_local.com</a><br>
> [36] <a href="http://fvs_remote.com" target="_blank">http://fvs_remote.com</a><br>
> [37] <a href="http://fvs_local.com" target="_blank">http://fvs_local.com</a><br>
> [38] <a href="http://fvs_remote.com" target="_blank">http://fvs_remote.com</a><br>
> [39]<br>
<div class="im">> <a href="http://blog.igut.fr/post/2009/02/07/Client-VPN-IPSec-Shrew-avec-Routeur-VPN" target="_blank">http://blog.igut.fr/post/2009/02/07/Client-VPN-IPSec-Shrew-avec-Routeur-VPN</a><br>
</div>> [40] <a href="http://lists.shrew.net/mailman/listinfo/vpn-help" target="_blank">http://lists.shrew.net/mailman/listinfo/vpn-help</a><br>
> [41] <a href="http://lists.shrew.net/mailman/listinfo/vpn-help" target="_blank">http://lists.shrew.net/mailman/listinfo/vpn-help</a><br>
> [42]<br>
<div class="im">> <a href="http://blog.igut.fr/post/2009/02/07/Client-VPN-IPSec-Shrew-avec-Routeur-VPN" target="_blank">http://blog.igut.fr/post/2009/02/07/Client-VPN-IPSec-Shrew-avec-Routeur-VPN</a><br>
</div>> [43] <a href="http://192.168.1.83:500" target="_blank">http://192.168.1.83:500</a><br>
> [44] <a href="http://206.248.160.8:500" target="_blank">http://206.248.160.8:500</a><br>
> [45] <a href="http://192.168.1.83:500" target="_blank">http://192.168.1.83:500</a><br>
> [46] <a href="http://206.248.160.8:500" target="_blank">http://206.248.160.8:500</a><br>
> [47] <a href="http://fvs_remote.com" target="_blank">http://fvs_remote.com</a><br>
> [48] <a href="http://fvs_local.com" target="_blank">http://fvs_local.com</a><br>
> [49] <a href="http://fvs_remote.com" target="_blank">http://fvs_remote.com</a><br>
> [50] <a href="http://fvs_local.com" target="_blank">http://fvs_local.com</a><br>
> [51] <a href="http://fvs_remote.com" target="_blank">http://fvs_remote.com</a><br>
> [52]<br>
<div class="im">> <a href="http://blog.igut.fr/post/2009/02/07/Client-VPN-IPSec-Shrew-avec-Routeur-VPN" target="_blank">http://blog.igut.fr/post/2009/02/07/Client-VPN-IPSec-Shrew-avec-Routeur-VPN</a><br>
</div>> [53] <a href="http://lists.shrew.net/mailman/listinfo/vpn-help" target="_blank">http://lists.shrew.net/mailman/listinfo/vpn-help</a><br>
> [54] <a href="http://lists.shrew.net/mailman/listinfo/vpn-help" target="_blank">http://lists.shrew.net/mailman/listinfo/vpn-help</a><br>
> [55]<br>
<div class="im">> <a href="http://blog.igut.fr/post/2009/02/07/Client-VPN-IPSec-Shrew-avec-Routeur-VPN" target="_blank">http://blog.igut.fr/post/2009/02/07/Client-VPN-IPSec-Shrew-avec-Routeur-VPN</a><br>
><br>
><br>
<br>
</div><div class="im">_______________________________________________<br>
vpn-help mailing list<br>
<a href="mailto:vpn-help@lists.shrew.net">vpn-help@lists.shrew.net</a><br>
</div><div><div></div><div class="h5"><a href="http://lists.shrew.net/mailman/listinfo/vpn-help" target="_blank">http://lists.shrew.net/mailman/listinfo/vpn-help</a><br>
</div></div></blockquote></div><br>