PROBLEMAS CON VPN DESPUES DE ACTUALIZAR



  • Saludos, he actualizado la version de pfsense y al conectar un cliente a la vpn conecta y le asigna una direccion pero no conecta a internet y sii hago un ping a la puerta de enlace no responde.
    Otro  punto es que cuando veo equipos de la red solo aparece la pc de mi casa.

    Microsoft Windows [Version 6.1.7601]
    Copyright © 2009 Microsoft Corporation.  All rights reserved.

    C:\Users\Klaus Salazar>ping google.com

    Pinging google.com [173.194.37.136] with 32 bytes of data:
    Reply from 173.194.37.136: bytes=32 time=118ms TTL=251
    Reply from 173.194.37.136: bytes=32 time=89ms TTL=251
    Reply from 173.194.37.136: bytes=32 time=118ms TTL=251
    Reply from 173.194.37.136: bytes=32 time=89ms TTL=251

    Ping statistics for 173.194.37.136:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 89ms, Maximum = 118ms, Average = 103ms

    C:\Users\Klaus Salazar>ping 192.168.129.1

    Pinging 192.168.129.1 with 32 bytes of data:
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.

    Ping statistics for 192.168.129.1:
        Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

    C:\Users\Klaus Salazar>ping google.com

    Pinging google.com [173.194.37.132] with 32 bytes of data:
    Reply from 173.194.37.132: bytes=32 time=117ms TTL=251
    Reply from 173.194.37.132: bytes=32 time=118ms TTL=251
    Reply from 173.194.37.132: bytes=32 time=118ms TTL=251
    Reply from 173.194.37.132: bytes=32 time=118ms TTL=251

    Ping statistics for 173.194.37.132:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 117ms, Maximum = 118ms, Average = 117ms

    C:\Users\Klaus Salazar>tracert 192.168.129.1

    Tracing route to 192.168.129.1 over a maximum of 30 hops

    1    3 ms    1 ms    1 ms  192.168.2.1
      2    *        *        *    Request timed out.
      3    26 ms    24 ms    25 ms  10.111.112.25
      4    *        *        *    Request timed out.
      5    28 ms    30 ms    31 ms  10.111.3.153
      6    *        *        *    Request timed out.
      7    *        *        *    Request timed out.
      8    *        *        *    Request timed out.
      9    *        *        *    Request timed out.
    10    *        *        *    Request timed out.
    11    *        *        *    Request timed out.
    12    *        *        *    Request timed out.
    13    *        *        *    Request timed out.
    14    *        *        *    Request timed out.
    15    *        *        *    Request timed out.
    16    *        *        *    Request timed out.
    17    *        *        *    Request timed out.
    18    *        *        *    Request timed out.
    19    *        *        *    Request timed out.
    20    *        *        *    Request timed out.
    21    *        *        *    Request timed out.
    22    *        *        *    Request timed out.
    23    *        *        *    Request timed out.
    24    *        *        *    Request timed out.
    25    *        *        *    Request timed out.
    26    *        *        *    Request timed out.
    27    *        *        *    Request timed out.
    28    *        *        *    Request timed out.
    29    *        *        *    Request timed out.
    30    *        *        *    Request timed out.

    Trace complete.

    C:\Users\Klaus Salazar>tracert peru.com

    Tracing route to peru.com [174.129.223.60]
    over a maximum of 30 hops:

    1    1 ms    1 ms    1 ms  192.168.4.1
      2    *        *        *    Request timed out.
      3    36 ms    25 ms    25 ms  10.111.97.29
      4    *        *        *    Request timed out.
      5    31 ms    32 ms    30 ms  10.111.2.153
      6    *        *        *    Request timed out.
      7    87 ms  140 ms    87 ms  Xe5-1-3-0-grtmiabr4.red.telefonica-wholesale.net
    [84.16.15.62]
      8    89 ms    91 ms    89 ms  BE1-grtmiabr5.red.telefonica-wholesale.net [94.1
    42.121.126]
      9    88 ms    87 ms    88 ms  et2-0-0-0-grtmiana2.red.telefonica-wholesale.net
    [84.16.14.189]
    10    89 ms    89 ms    89 ms  xe-0-3-0-23.r04.miamfl02.us.bb.gin.ntt.net [129.
    250.9.21]
    11    89 ms    88 ms    88 ms  ae-1.amazon.miamfl02.us.bb.gin.ntt.net [129.250.
    201.190]
    12  116 ms  114 ms  116 ms  54.240.229.46
    13  115 ms  114 ms  114 ms  54.240.229.32
    14  114 ms  116 ms  117 ms  54.240.229.144
    15    *        *        *    Request timed out.
    16  116 ms  113 ms  113 ms  205.251.244.4
    17  114 ms  115 ms  116 ms  72.21.220.31
    18  113 ms  114 ms  113 ms  205.251.245.55
    19    *        *        *    Request timed out.
    20    *        *        *    Request timed out.
    21    *        *        *    Request timed out.
    22  121 ms  125 ms  115 ms  216.182.224.193
    23    *        *        *    Request timed out.
    24    *        *        *    Request timed out.
    25    *        *        *    Request timed out.
    26    *        *        *    Request timed out.
    27    *        *        *    Request timed out.
    28    *        *        *    Request timed out.
    29    *        *        *    Request timed out.
    30    *        *        *    Request timed out.

    Trace complete.



  • Explica, por favor, brevemente tu topología (qué VPN, rangos usados…)

    Tantos logs marean y no aclaran mucho.


Log in to reply