Relier 2 reseaux local de plus de 20 km

APIGO Messages postés 13 Statut Membre -  
frizouille44 Messages postés 83 Statut Membre -
Bonjour,
voila mon bleme
je voudrais relier 2 reseaux local separe de plus de 20km, alors j'aimerai savoir quel materiel acheter pour faire sa
merci
Configuration: Windows XP sp3
Internet Explorer 7.0

18 réponses

  1. cocoche95 Messages postés 1187 Statut Contributeur 543
     
    Salut !

    Le VPN est ton ami !! Via deux connections internet et deux routeurs.

    Voilà !
    0
  2. APIGO Messages postés 13 Statut Membre
     
    salut
    merci pour l'info mais pourais tu me donner une lien sur une tuto pour relier 2 routeurs en vpn via internet?
    et est ce possible de relier ces 2 routeurs avec des antennes (WIMAX)
    0
  3. cocoche95 Messages postés 1187 Statut Contributeur 543
     
    Voilà un exemple parmi plein d'autres : http://www.netgear-forum.com/forum/index.php?showtopic=38478

    ou sinon : http://www.kogik.com/docs/vpn.php

    Avec du WIMAX ça doit être possible mais ne l'ayant pas fait moi même je préfère ne pas donner d'avis pour ne pas dire de conneries !

    N'oublies pas : google est ton ami !
    0
  4. APIGO Messages postés 13 Statut Membre
     
    merci cocoche95

    mais j'ai oublier de te dire que moi j'utilise des routeurs vpn linksys wrv200
    0
    1. cocoche95 Messages postés 1187 Statut Contributeur 543
       
      Regarde sur mon deuxième lien, c'est un exemple avec un linksys. Les menus se ressemblent, non ? Essaye de naviguer dans tous les menus et de bidouiller un peu ^^ (voir quels menu se ressemblent ou peuvent correspondre).

      Je vais essayer de chercher un peu.
      0
  5. Vous n’avez pas trouvé la réponse que vous recherchez ?

    Posez votre question
  6. APIGO Messages postés 13 Statut Membre
     
    salut
    ouai jvais remarquer que les menu se ressemblaient
    je te tien au courant poour la suite merci
    0
    1. cocoche95 Messages postés 1187 Statut Contributeur 543
       
      Tiens j'ai trouvé ça sur le site de linksys : http://linksys-fr.custhelp.com/cgi-bin/linksys_fr.cfg/php/enduser/std_adp.php?p_faqid=6609&lid=2185302593B08

      On peux pas faire mieux je crois !
      0
  7. APIGO Messages postés 13 Statut Membre
     
    merci cocoche c'est trop cool de ta part
    0
  8. APIGO Messages postés 13 Statut Membre
     
    salut
    jai fini de configurer les routeur et je pense qque jai tout bien fait mais j'arrive toujours pas a etablir un connection entre les 2 routeur (mes 2 routeurs sont directement connecter a internet il ne passe pas par un modem j'espere que c'est pas sa le bleme?)

    et le log affiche sa!!!

    000 [Sun 14:23:41] "TunnelA": deleting connection
    001 [Sun 14:23:41] "TunnelA" #10: deleting state (STATE_QUICK_R2)
    002 [Sun 14:23:41] "TunnelA" #9: deleting state (STATE_QUICK_I2)
    003 [Sun 14:23:41] "TunnelA" #8: deleting state (STATE_MAIN_I4)
    004 [Sun 14:23:47] added connection description "TunnelA"
    005 [Sun 14:23:47] "TunnelA" #11: initiating Main Mode
    006 [Sun 14:23:47] "TunnelA" #11: [WRV210 Response:] ISAKMP SA (Main Mode) Initiation
    007 [Sun 14:23:47] "TunnelA" #11: received Vendor ID payload [Openswan (this version) 2.4.5dr3 X.509-1.5.4 PLUTO_SENDS_VENDORID PLUTO_USES_KEYRR]
    008 [Sun 14:23:47] "TunnelA" #11: received Vendor ID payload [Dead Peer Detection]
    009 [Sun 14:23:47] "TunnelA" #11: received Vendor ID payload [RFC 3947] method set to=109
    010 [Sun 14:23:47] "TunnelA" #11: enabling possible NAT-traversal with method 3
    011 [Sun 14:23:48] "TunnelA" #11: transition from state STATE_MAIN_I1 to state STATE_MAIN_I2
    012 [Sun 14:23:48] "TunnelA" #11: STATE_MAIN_I2: sent MI2, expecting MR2
    013 [Sun 14:23:48] "TunnelA" #11: I did not send a certificate because I do not have one.
    014 [Sun 14:23:48] "TunnelA" #11: NAT-Traversal: Result using 3: no NAT detected
    015 [Sun 14:23:48] "TunnelA" #11: transition from state STATE_MAIN_I2 to state STATE_MAIN_I3
    016 [Sun 14:23:48] "TunnelA" #11: STATE_MAIN_I3: sent MI3, expecting MR3
    017 [Sun 14:23:49] "TunnelA" #11: Main mode peer ID is ID_IPV4_ADDR: '196.200.92.247'
    018 [Sun 14:23:49] "TunnelA" #11: transition from state STATE_MAIN_I3 to state STATE_MAIN_I4
    019 [Sun 14:23:49] "TunnelA" #11: [WRV210 Response:] ISAKMP SA established
    020 [Sun 14:23:49] "TunnelA" #11: STATE_MAIN_I4: ISAKMP SA established {auth=OAKLEY_PRESHARED_KEY cipher=oakley_3des_cbc_192 prf=oakley_md5 group=modp1024}
    021 [Sun 14:23:49] "TunnelA" #11: Dead Peer Detection (RFC 3706): enabled
    022 [Sun 14:23:49] "TunnelA" #12: [WRV210 Response:] IPSec SA (Quick Mode) Initiation
    023 [Sun 14:23:49] "TunnelA" #12: initiating Quick Mode PSK+ENCRYPT+TUNNEL+PFS+UP {using isakmp#11}
    024 [Sun 14:23:52] "TunnelA" #12: Dead Peer Detection (RFC 3706): enabled
    025 [Sun 14:23:52] "TunnelA" #12: transition from state STATE_QUICK_I1 to state STATE_QUICK_I2
    026 [Sun 14:23:52] "TunnelA" #12: [WRV210 Response:] IPSec SA established
    027 [Sun 14:23:52] "TunnelA" #12: STATE_QUICK_I2: sent QI2, IPsec SA established {ESP=>0x77bbc6b8 <0x258e927b xfrm=3DES_0-HMAC_MD5 NATD=none DPD=enabled}
    028 [Sun 14:23:53] "TunnelA" #13: responding to Quick Mode {msgid:166cbb2e}
    029 [Sun 14:23:53] "TunnelA" #13: transition from state STATE_QUICK_R0 to state STATE_QUICK_R1
    030 [Sun 14:23:53] "TunnelA" #13: STATE_QUICK_R1: sent QR1, inbound IPsec SA installed, expecting QI2
    031 [Sun 14:23:53] "TunnelA" #13: Dead Peer Detection (RFC 3706): enabled
    032 [Sun 14:23:53] "TunnelA" #13: transition from state STATE_QUICK_R1 to state STATE_QUICK_R2
    033 [Sun 14:23:53] "TunnelA" #13: [WRV210 Response:] IPSec SA established
    034 [Sun 14:23:53] "TunnelA" #13: STATE_QUICK_R2: IPsec SA established {ESP=>0x77bbc6b9 <0x258e927c xfrm=3DES_0-HMAC_MD5 NATD=none DPD=enabled}
    035 [Sun 14:24:01] "TunnelA" #11: ignoring Delete SA payload: PROTO_IPSEC_ESP SA(0x77bbc6b7) not found (maybe expired)
    036 [Sun 14:24:01] "TunnelA" #11: received and ignored informational message
    0
  9. cocoche95 Messages postés 1187 Statut Contributeur 543
     
    Franchement, je vois rien d'anormal, essayes de contacter un techos de linksys. Moi je suis plutôt netgear ! lol

    Là franchement, je vois pas... Désolé !
    0
  10. APIGO Messages postés 13 Statut Membre
     
    maintenant ca me donne sa

    000 [Sun 08:50:04] packet from 196.200.87.23:500: received Vendor ID payload [Openswan (this version) 2.4.5dr3 X.509-1.5.4 PLUTO_SENDS_VENDORID PLUTO_USES_KEYRR]
    001 [Sun 08:50:04] packet from 196.200.87.23:500: received Vendor ID payload [Dead Peer Detection]
    002 [Sun 08:50:04] packet from 196.200.87.23:500: received Vendor ID payload [RFC 3947] method set to=109
    003 [Sun 08:50:04] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-03] meth=108, but already using method 109
    004 [Sun 08:50:04] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02] meth=107, but already using method 109
    005 [Sun 08:50:04] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-00]
    006 [Sun 08:50:04] packet from 196.200.87.23:500: initial Main Mode message received on 196.200.83.226:500 but no connection has been authorized
    007 [Sun 08:50:12] packet from 196.200.87.23:500: received Vendor ID payload [Openswan (this version) 2.4.5dr3 X.509-1.5.4 PLUTO_SENDS_VENDORID PLUTO_USES_KEYRR]
    008 [Sun 08:50:12] packet from 196.200.87.23:500: received Vendor ID payload [Dead Peer Detection]
    009 [Sun 08:50:12] packet from 196.200.87.23:500: received Vendor ID payload [RFC 3947] method set to=109
    010 [Sun 08:50:12] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-03] meth=108, but already using method 109
    011 [Sun 08:50:12] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02] meth=107, but already using method 109
    012 [Sun 08:50:12] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-00]
    013 [Sun 08:50:12] packet from 196.200.87.23:500: initial Main Mode message received on 196.200.83.226:500 but no connection has been authorized
    014 [Sun 08:50:22] packet from 196.200.87.23:500: received Vendor ID payload [Openswan (this version) 2.4.5dr3 X.509-1.5.4 PLUTO_SENDS_VENDORID PLUTO_USES_KEYRR]
    015 [Sun 08:50:22] packet from 196.200.87.23:500: received Vendor ID payload [Dead Peer Detection]
    016 [Sun 08:50:22] packet from 196.200.87.23:500: received Vendor ID payload [RFC 3947] method set to=109
    017 [Sun 08:50:22] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-03] meth=108, but already using method 109
    018 [Sun 08:50:22] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02] meth=107, but already using method 109
    019 [Sun 08:50:22] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-00]
    020 [Sun 08:50:22] packet from 196.200.87.23:500: initial Main Mode message received on 196.200.83.226:500 but no connection has been authorized
    021 [Sun 08:50:42] packet from 196.200.87.23:500: received Vendor ID payload [Openswan (this version) 2.4.5dr3 X.509-1.5.4 PLUTO_SENDS_VENDORID PLUTO_USES_KEYRR]
    022 [Sun 08:50:42] packet from 196.200.87.23:500: received Vendor ID payload [Dead Peer Detection]
    023 [Sun 08:50:42] packet from 196.200.87.23:500: received Vendor ID payload [RFC 3947] method set to=109
    024 [Sun 08:50:42] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-03] meth=108, but already using method 109
    025 [Sun 08:50:42] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02] meth=107, but already using method 109
    026 [Sun 08:50:42] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-00]
    027 [Sun 08:50:42] packet from 196.200.87.23:500: initial Main Mode message received on 196.200.83.226:500 but no connection has been authorized
    028 [Sun 08:51:22] packet from 196.200.87.23:500: received Vendor ID payload [Openswan (this version) 2.4.5dr3 X.509-1.5.4 PLUTO_SENDS_VENDORID PLUTO_USES_KEYRR]
    029 [Sun 08:51:22] packet from 196.200.87.23:500: received Vendor ID payload [Dead Peer Detection]
    030 [Sun 08:51:22] packet from 196.200.87.23:500: received Vendor ID payload [RFC 3947] method set to=109
    031 [Sun 08:51:22] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-03] meth=108, but already using method 109
    032 [Sun 08:51:22] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02] meth=107, but already using method 109
    033 [Sun 08:51:22] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-00]
    034 [Sun 08:51:22] packet from 196.200.87.23:500: initial Main Mode message received on 196.200.83.226:500 but no connection has been authorized
    035 [Sun 08:51:40] packet from 196.200.87.23:500: received Vendor ID payload [Openswan (this version) 2.4.5dr3 X.509-1.5.4 PLUTO_SENDS_VENDORID PLUTO_USES_KEYRR]
    036 [Sun 08:51:40] packet from 196.200.87.23:500: received Vendor ID payload [Dead Peer Detection]
    037 [Sun 08:51:40] packet from 196.200.87.23:500: received Vendor ID payload [RFC 3947] method set to=109
    038 [Sun 08:51:40] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-03] meth=108, but already using method 109
    039 [Sun 08:51:40] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02] meth=107, but already using method 109
    040 [Sun 08:51:40] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-00]
    041 [Sun 08:51:40] packet from 196.200.87.23:500: initial Main Mode message received on 196.200.83.226:500 but no connection has been authorized
    042 [Sun 08:52:00] packet from 196.200.87.23:500: received Vendor ID payload [Openswan (this version) 2.4.5dr3 X.509-1.5.4 PLUTO_SENDS_VENDORID PLUTO_USES_KEYRR]
    043 [Sun 08:52:00] packet from 196.200.87.23:500: received Vendor ID payload [Dead Peer Detection]
    044 [Sun 08:52:00] packet from 196.200.87.23:500: received Vendor ID payload [RFC 3947] method set to=109
    045 [Sun 08:52:00] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-03] meth=108, but already using method 109
    046 [Sun 08:52:00] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02] meth=107, but already using method 109
    047 [Sun 08:52:00] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-00]
    048 [Sun 08:52:00] packet from 196.200.87.23:500: initial Main Mode message received on 196.200.83.226:500 but no connection has been authorized
    049 [Sun 08:52:40] packet from 196.200.87.23:500: received Vendor ID payload [Openswan (this version) 2.4.5dr3 X.509-1.5.4 PLUTO_SENDS_VENDORID PLUTO_USES_KEYRR]
    050 [Sun 08:52:40] packet from 196.200.87.23:500: received Vendor ID payload [Dead Peer Detection]
    051 [Sun 08:52:40] packet from 196.200.87.23:500: received Vendor ID payload [RFC 3947] method set to=109
    052 [Sun 08:52:40] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-03] meth=108, but already using method 109
    053 [Sun 08:52:40] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02] meth=107, but already using method 109
    054 [Sun 08:52:40] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-00]
    055 [Sun 08:52:40] packet from 196.200.87.23:500: initial Main Mode message received on 196.200.83.226:500 but no connection has been authorized
    056 [Sun 08:52:50] packet from 196.200.87.23:500: received Vendor ID payload [Openswan (this version) 2.4.5dr3 X.509-1.5.4 PLUTO_SENDS_VENDORID PLUTO_USES_KEYRR]
    057 [Sun 08:52:50] packet from 196.200.87.23:500: received Vendor ID payload [Dead Peer Detection]
    058 [Sun 08:52:50] packet from 196.200.87.23:500: received Vendor ID payload [RFC 3947] method set to=109
    059 [Sun 08:52:50] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-03] meth=108, but already using method 109
    060 [Sun 08:52:50] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02] meth=107, but already using method 109
    061 [Sun 08:52:50] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-00]
    062 [Sun 08:52:50] packet from 196.200.87.23:500: initial Main Mode message received on 196.200.83.226:500 but no connection has been authorized
    063 [Sun 08:52:59] packet from 196.200.87.23:500: received Vendor ID payload [Openswan (this version) 2.4.5dr3 X.509-1.5.4 PLUTO_SENDS_VENDORID PLUTO_USES_KEYRR]
    064 [Sun 08:52:59] packet from 196.200.87.23:500: received Vendor ID payload [Dead Peer Detection]
    065 [Sun 08:52:59] packet from 196.200.87.23:500: received Vendor ID payload [RFC 3947] method set to=109
    066 [Sun 08:52:59] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-03] meth=108, but already using method 109
    067 [Sun 08:52:59] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02] meth=107, but already using method 109
    068 [Sun 08:52:59] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-00]
    069 [Sun 08:52:59] packet from 196.200.87.23:500: initial Main Mode message received on 196.200.83.226:500 but no connection has been authorized
    070 [Sun 08:53:19] packet from 196.200.87.23:500: received Vendor ID payload [Openswan (this version) 2.4.5dr3 X.509-1.5.4 PLUTO_SENDS_VENDORID PLUTO_USES_KEYRR]
    071 [Sun 08:53:19] packet from 196.200.87.23:500: received Vendor ID payload [Dead Peer Detection]
    072 [Sun 08:53:19] packet from 196.200.87.23:500: received Vendor ID payload [RFC 3947] method set to=109
    073 [Sun 08:53:19] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-03] meth=108, but already using method 109
    074 [Sun 08:53:19] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02] meth=107, but already using method 109
    075 [Sun 08:53:19] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-00]
    076 [Sun 08:53:19] packet from 196.200.87.23:500: initial Main Mode message received on 196.200.83.226:500 but no connection has been authorized
    077 [Sun 08:53:42] forgetting secrets
    078 [Sun 08:53:42] loading secrets from "/etc/ipsec.secrets"
    079 [Sun 08:53:42] "TunnelA": deleting connection
    080 [Sun 08:53:47] added connection description "TunnelA"
    081 [Sun 08:53:47] "TunnelA": We cannot identify ourselves with either end of this connection.
    082 [Sun 08:54:00] packet from 196.200.87.23:500: received Vendor ID payload [Openswan (this version) 2.4.5dr3 X.509-1.5.4 PLUTO_SENDS_VENDORID PLUTO_USES_KEYRR]
    083 [Sun 08:54:00] packet from 196.200.87.23:500: received Vendor ID payload [Dead Peer Detection]
    084 [Sun 08:54:00] packet from 196.200.87.23:500: received Vendor ID payload [RFC 3947] method set to=109
    085 [Sun 08:54:00] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-03] meth=108, but already using method 109
    086 [Sun 08:54:00] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02] meth=107, but already using method 109
    087 [Sun 08:54:00] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-00]
    088 [Sun 08:54:00] packet from 196.200.87.23:500: initial Main Mode message received on 196.200.83.226:500 but no connection has been authorized
    089 [Sun 08:54:09] packet from 196.200.87.23:500: received Vendor ID payload [Openswan (this version) 2.4.5dr3 X.509-1.5.4 PLUTO_SENDS_VENDORID PLUTO_USES_KEYRR]
    090 [Sun 08:54:09] packet from 196.200.87.23:500: received Vendor ID payload [Dead Peer Detection]
    091 [Sun 08:54:09] packet from 196.200.87.23:500: received Vendor ID payload [RFC 3947] method set to=109
    092 [Sun 08:54:09] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-03] meth=108, but already using method 109
    093 [Sun 08:54:09] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02] meth=107, but already using method 109
    094 [Sun 08:54:09] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-00]
    095 [Sun 08:54:09] packet from 196.200.87.23:500: initial Main Mode message received on 196.200.83.226:500 but no connection has been authorized
    096 [Sun 08:54:18] packet from 196.200.87.23:500: received Vendor ID payload [Openswan (this version) 2.4.5dr3 X.509-1.5.4 PLUTO_SENDS_VENDORID PLUTO_USES_KEYRR]
    097 [Sun 08:54:18] packet from 196.200.87.23:500: received Vendor ID payload [Dead Peer Detection]
    098 [Sun 08:54:18] packet from 196.200.87.23:500: received Vendor ID payload [RFC 3947] method set to=109
    099 [Sun 08:54:18] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-03] meth=108, but already using method 109
    100 [Sun 08:54:18] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02] meth=107, but already using method 109
    101 [Sun 08:54:18] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-00]
    102 [Sun 08:54:18] packet from 196.200.87.23:500: initial Main Mode message received on 196.200.83.226:500 but no connection has been authorized
    103 [Sun 08:54:38] packet from 196.200.87.23:500: received Vendor ID payload [Openswan (this version) 2.4.5dr3 X.509-1.5.4 PLUTO_SENDS_VENDORID PLUTO_USES_KEYRR]
    104 [Sun 08:54:38] packet from 196.200.87.23:500: received Vendor ID payload [Dead Peer Detection]
    105 [Sun 08:54:38] packet from 196.200.87.23:500: received Vendor ID payload [RFC 3947] method set to=109
    106 [Sun 08:54:38] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-03] meth=108, but already using method 109
    107 [Sun 08:54:38] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02] meth=107, but already using method 109
    108 [Sun 08:54:38] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-00]
    109 [Sun 08:54:38] packet from 196.200.87.23:500: initial Main Mode message received on 196.200.83.226:500 but no connection has been authorized
    110 [Sun 08:55:09] packet from 196.200.87.23:500: received Vendor ID payload [Dead Peer Detection]
    111 [Sun 08:55:09] packet from 196.200.87.23:500: received Vendor ID payload [RFC 3947] method set to=109
    112 [Sun 08:55:09] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-03] meth=108, but already using method 109
    113 [Sun 08:55:09] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02] meth=107, but already using method 109
    114 [Sun 08:55:09] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-00]
    115 [Sun 08:55:09] packet from 196.200.87.23:500: initial Aggressive Mode message from 196.200.87.23 but no (wildcard) connection has been configured
    116 [Sun 08:55:19] packet from 196.200.87.23:500: received Vendor ID payload [Dead Peer Detection]
    117 [Sun 08:55:19] packet from 196.200.87.23:500: received Vendor ID payload [RFC 3947] method set to=109
    118 [Sun 08:55:19] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-03] meth=108, but already using method 109
    119 [Sun 08:55:19] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02] meth=107, but already using method 109
    120 [Sun 08:55:19] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-00]
    121 [Sun 08:55:19] packet from 196.200.87.23:500: initial Aggressive Mode message from 196.200.87.23 but no (wildcard) connection has been configured
    122 [Sun 08:55:39] packet from 196.200.87.23:500: received Vendor ID payload [Dead Peer Detection]
    123 [Sun 08:55:39] packet from 196.200.87.23:500: received Vendor ID payload [RFC 3947] method set to=109
    124 [Sun 08:55:39] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-03] meth=108, but already using method 109
    125 [Sun 08:55:39] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02] meth=107, but already using method 109
    126 [Sun 08:55:39] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-00]
    127 [Sun 08:55:39] packet from 196.200.87.23:500: initial Aggressive Mode message from 196.200.87.23 but no (wildcard) connection has been configured
    128 [Sun 08:56:29] packet from 196.200.87.23:500: received Vendor ID payload [Dead Peer Detection]
    129 [Sun 08:56:29] packet from 196.200.87.23:500: received Vendor ID payload [RFC 3947] method set to=109
    130 [Sun 08:56:29] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-03] meth=108, but already using method 109
    131 [Sun 08:56:29] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02] meth=107, but already using method 109
    132 [Sun 08:56:29] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-00]
    133 [Sun 08:56:29] packet from 196.200.87.23:500: initial Aggressive Mode message from 196.200.87.23 but no (wildcard) connection has been configured
    134 [Sun 08:56:47] packet from 196.200.87.23:500: received Vendor ID payload [Dead Peer Detection]
    135 [Sun 08:56:47] packet from 196.200.87.23:500: received Vendor ID payload [RFC 3947] method set to=109
    136 [Sun 08:56:47] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-03] meth=108, but already using method 109
    137 [Sun 08:56:47] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02] meth=107, but already using method 109
    138 [Sun 08:56:47] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-00]
    139 [Sun 08:56:47] packet from 196.200.87.23:500: initial Aggressive Mode message from 196.200.87.23 but no (wildcard) connection has been configured
    140 [Sun 08:57:17] packet from 196.200.87.23:500: received Vendor ID payload [Dead Peer Detection]
    141 [Sun 08:57:17] packet from 196.200.87.23:500: received Vendor ID payload [RFC 3947] method set to=109
    142 [Sun 08:57:17] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-03] meth=108, but already using method 109
    143 [Sun 08:57:17] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02] meth=107, but already using method 109
    144 [Sun 08:57:17] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-00]
    145 [Sun 08:57:17] packet from 196.200.87.23:500: initial Aggressive Mode message from 196.200.87.23 but no (wildcard) connection has been configured
    146 [Sun 08:58:05] packet from 196.200.87.23:500: received Vendor ID payload [Dead Peer Detection]
    147 [Sun 08:58:05] packet from 196.200.87.23:500: received Vendor ID payload [RFC 3947] method set to=109
    148 [Sun 08:58:05] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-03] meth=108, but already using method 109
    149 [Sun 08:58:05] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02] meth=107, but already using method 109
    150 [Sun 08:58:05] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-00]
    151 [Sun 08:58:05] packet from 196.200.87.23:500: initial Aggressive Mode message from 196.200.87.23 but no (wildcard) connection has been configured
    152 [Sun 08:58:15] packet from 196.200.87.23:500: received Vendor ID payload [Dead Peer Detection]
    153 [Sun 08:58:15] packet from 196.200.87.23:500: received Vendor ID payload [RFC 3947] method set to=109
    154 [Sun 08:58:15] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-03] meth=108, but already using method 109
    155 [Sun 08:58:15] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02] meth=107, but already using method 109
    156 [Sun 08:58:15] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-00]
    157 [Sun 08:58:15] packet from 196.200.87.23:500: initial Aggressive Mode message from 196.200.87.23 but no (wildcard) connection has been configured
    158 [Sun 08:58:35] packet from 196.200.87.23:500: received Vendor ID payload [Dead Peer Detection]
    159 [Sun 08:58:35] packet from 196.200.87.23:500: received Vendor ID payload [RFC 3947] method set to=109
    160 [Sun 08:58:35] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-03] meth=108, but already using method 109
    161 [Sun 08:58:35] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02] meth=107, but already using method 109
    162 [Sun 08:58:35] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-00]
    163 [Sun 08:58:35] packet from 196.200.87.23:500: initial Aggressive Mode message from 196.200.87.23 but no (wildcard) connection has been configured
    164 [Sun 08:59:22] packet from 196.200.87.23:500: received Vendor ID payload [Dead Peer Detection]
    165 [Sun 08:59:22] packet from 196.200.87.23:500: received Vendor ID payload [RFC 3947] method set to=109
    166 [Sun 08:59:22] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-03] meth=108, but already using method 109
    167 [Sun 08:59:22] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02] meth=107, but already using method 109
    168 [Sun 08:59:22] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-00]
    169 [Sun 08:59:22] packet from 196.200.87.23:500: initial Aggressive Mode message from 196.200.87.23 but no (wildcard) connection has been configured
    170 [Sun 08:59:32] packet from 196.200.87.23:500: received Vendor ID payload [Dead Peer Detection]
    171 [Sun 08:59:32] packet from 196.200.87.23:500: received Vendor ID payload [RFC 3947] method set to=109
    172 [Sun 08:59:32] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-03] meth=108, but already using method 109
    173 [Sun 08:59:32] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02] meth=107, but already using method 109
    174 [Sun 08:59:32] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-00]
    175 [Sun 08:59:32] packet from 196.200.87.23:500: initial Aggressive Mode message from 196.200.87.23 but no (wildcard) connection has been configured
    176 [Sun 08:59:52] packet from 196.200.87.23:500: received Vendor ID payload [Dead Peer Detection]
    177 [Sun 08:59:52] packet from 196.200.87.23:500: received Vendor ID payload [RFC 3947] method set to=109
    178 [Sun 08:59:52] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-03] meth=108, but already using method 109
    179 [Sun 08:59:52] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02] meth=107, but already using method 109
    180 [Sun 08:59:52] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-00]
    181 [Sun 08:59:52] packet from 196.200.87.23:500: initial Aggressive Mode message from 196.200.87.23 but no (wildcard) connection has been configured
    182 [Sun 09:00:40] packet from 196.200.87.23:500: received Vendor ID payload [Dead Peer Detection]
    183 [Sun 09:00:40] packet from 196.200.87.23:500: received Vendor ID payload [RFC 3947] method set to=109
    184 [Sun 09:00:40] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-03] meth=108, but already using method 109
    185 [Sun 09:00:40] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02] meth=107, but already using method 109
    186 [Sun 09:00:40] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-00]
    187 [Sun 09:00:40] packet from 196.200.87.23:500: initial Aggressive Mode message from 196.200.87.23 but no (wildcard) connection has been configured
    188 [Sun 09:00:50] packet from 196.200.87.23:500: received Vendor ID payload [Dead Peer Detection]
    189 [Sun 09:00:50] packet from 196.200.87.23:500: received Vendor ID payload [RFC 3947] method set to=109
    190 [Sun 09:00:50] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-03] meth=108, but already using method 109
    191 [Sun 09:00:50] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02] meth=107, but already using method 109
    192 [Sun 09:00:50] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-00]
    193 [Sun 09:00:50] packet from 196.200.87.23:500: initial Aggressive Mode message from 196.200.87.23 but no (wildcard) connection has been configured
    194 [Sun 09:01:10] packet from 196.200.87.23:500: received Vendor ID payload [Dead Peer Detection]
    195 [Sun 09:01:10] packet from 196.200.87.23:500: received Vendor ID payload [RFC 3947] method set to=109
    196 [Sun 09:01:10] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-03] meth=108, but already using method 109
    197 [Sun 09:01:10] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02] meth=107, but already using method 109
    198 [Sun 09:01:10] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-00]
    199 [Sun 09:01:10] packet from 196.200.87.23:500: initial Aggressive Mode message from 196.200.87.23 but no (wildcard) connection has been configured
    200 [Sun 09:01:57] packet from 196.200.87.23:500: received Vendor ID payload [Dead Peer Detection]
    201 [Sun 09:01:57] packet from 196.200.87.23:500: received Vendor ID payload [RFC 3947] method set to=109
    202 [Sun 09:01:57] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-03] meth=108, but already using method 109
    203 [Sun 09:01:57] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02] meth=107, but already using method 109
    204 [Sun 09:01:57] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-00]
    205 [Sun 09:01:57] packet from 196.200.87.23:500: initial Aggressive Mode message from 196.200.87.23 but no (wildcard) connection has been configured
    206 [Sun 09:02:27] packet from 196.200.87.23:500: received Vendor ID payload [Dead Peer Detection]
    207 [Sun 09:02:27] packet from 196.200.87.23:500: received Vendor ID payload [RFC 3947] method set to=109
    208 [Sun 09:02:27] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-03] meth=108, but already using method 109
    209 [Sun 09:02:27] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-02] meth=107, but already using method 109
    210 [Sun 09:02:27] packet from 196.200.87.23:500: received Vendor ID payload [draft-ietf-ipsec-nat-t-ike-00]
    0
  11. cocoche95 Messages postés 1187 Statut Contributeur 543
     
    Je vois toujours pas ! Désolé !

    Essayes de contacter Brupala https://www.commentcamarche.net/communaute/profil-brupala , peut être qu'il saura faire ou t'aider mieux que moi !
    0
  12. APIGO Messages postés 13 Statut Membre
     
    ok merci pour l'info tu ma vrai aide je te remerci 123445890 fois
    0
  13. APIGO Messages postés 13 Statut Membre
     
    Cet utilisateur n'est pas membre de CommentCaMarche.net
    0
    1. cocoche95 Messages postés 1187 Statut Contributeur 543
       
      je viens de corrigé mon lien ! Je me suis loupé la première fois !

      La ça marche pour moi !
      0
  14. frizouille44 Messages postés 83 Statut Membre 11
     
    Concernant le Wimax, pour l'avoir déjà installé, je peux te dire que ça dépote.

    Evidemment, il faut faire une petite étude préalable pour vérifier la visée directe entre les deux sites (pas d'obstacles)

    pas besoin de VPN, ce lien se comportera comme un cable RJ45
    et un débit de 100Mbs!!! et un ping équivalent à un cordon..

    La marque leader : www.alvarion.fr (voir le produit breezeNetBee)

    Distribué par connectdata en france

    Des sociétés sont spécialisées pour l'instal et la mise en servive (par ex www.qostelecom.fr )

    voilou
    0
    1. APIGO Messages postés 13 Statut Membre
       
      salut
      merci frizouille44 pour ton info mais est ce que a la place du alvarion breezenetbee je pourais utiliser le Cisco Aironet® 1300
      merci
      0
  15. frizouille44 Messages postés 83 Statut Membre 11
     
    Oui, mais ne t'attends pas à un débit important.
    A mon avis, à 20km, tu n'atteindras que difficilement 5 ou 6 mbits et encore, je suis tres optimiste.
    De plus, la régularité du lien sera plus que douteuse, le wifi étant du best effort...
    En plus, il faudra prier pour qu'il n'y est pas de perturbations le long de la liaison...
    Bref, le WIFI sur 20km, c'est pô gagné...

    Pour info, si ça t'interresse, je peux t'aider à faire un profil topographique de ta liaison (on a tout ce qu'il faut à la boite ;) et ainsi, vérifier si c'est réalisable ... (à moins que tu ai une visée directe avec tes jumelles!)

    hop..
    0
    1. APIGO Messages postés 13 Statut Membre
       
      Salut
      ouai ta raison sur les 20 km il ya plein d'obstacle, mais t'es sur qu'avec le ALVARION j'aurai pas de bleme sur les 20km malgrer les obstacle?
      merci
      0
    2. APIGO Messages postés 13 Statut Membre
       
      et tu poura me trouver un tuto pour l'installation des Alvarion?
      0
  16. frizouille44 Messages postés 83 Statut Membre 11
     
    Normalement, il ne faut pas d'obstacles....
    Concernant l'installation des alvarions, il n'y aura qu'à configurer la clé, et la fréquence. Rien à faire sur tes réseaux locaux...

    C'est vraiment très simple, la doc est livrée avec.

    Je pourrais t'aider, de toutes façon.

    Si tu veux qu'on fasse un essai topo, envoi moi juste les coordonnées de tes sites (en Lambert II si possible)
    Si tu ne les a pas, trouves les sur www.geoportail.fr
    0
  17. Maestro HF
     
    Idées recues ....

    il est inutile de compliquer les choses en matière de distance, de portée, etc, entre 2 points dits A et B qui peuvent être imaginés de composition quelconque, 2 PC éloignés, 1 camara Wifi distance avec routeur, 2 routeurs séparés, 1 box avec un serveur, avec une clée, on s'en fout de la configuration particulière ...

    Ce qui compte c'est que les accessoires Wifi choisis soient dotés d'un connecteur SMA pour y brancher une antenne exterieure, gain de 10 à 25 dB, gain à définir notamment en fonction de la distance et la nature du trajet. Les radiommateurs connaissent et appliquent ce principe depuis bien longtemps, ignoré, le plus souvent, pas les "simples" wifistes..

    2 Antennes identiques doubleront le gain dans le bilan de liaison, ce qui a rien à voir avec le doublage de la distance entre A et B. Chaque fois que l'on double la distance, il faut 6 dB de plus au système, soit sur l'antenne A ou B, soit la moitié sur l A1 et l'autre moitié sur A 2, en ne perdant pas de vue que l'on multiplie aussi par 2 les problemes potentiels fréquents en 2.4 Ghz car cette bande ISM est de type partagée...on est pas les seuls, il y a aussi les radiamateurs et autres colocataires.

    En wifi il est recommandé que les liaisons ( antenne à antenne) soient "à vue", car si obstacle les atténuations peuvent parfois être violentes, mais tout dépendra de nombreux facteurs, comme l'emplacement et la composition de l 'obstacle dans le trajet..

    Voici ce qui compte et ce qu'il faut privilégier avant tout, en évitant les amplificateurs ( aspect spectral impur). On pourra toutefois envisager un répéteur.

    On utilisera une ( ou 2) antenne directive ( ex plate ou parabole en polarisation verticale) et surtout un coaxial de bonne qualité, faible perte, et le plus court possible, 10 m c'est déjà pas mal , jusqu' - 4 dB .( à déduire du gain d'antenne). On soigne la connectique, attention aux raccords..

    Etablir des liaisons wifi sur 10 ou 20 km ce n'est pas dans le domaine de l'inimaginable, toutefois il faut que la liaison soit ensuite perenne......, chute du débit avec l'arrivée d'un autre sytème 2.4 Ghz dans le secteur...
    0