Forum Discussion

spoulson's avatar
spoulson
On our wavelength
3 months ago
Solved

Routing problems

You have a problem with routing - zayo.com is not forwarding your packets for certain IPs. This is causing me much pain and I am considering cancelling my contract

 

Compare the following traceroutes:

Virgin:

```traceroute -I amsvpn.vrt.sourcefire.com

traceroute to amsvpn.vrt.sourcefire.com (172.110.205.185), 64 hops max, 48 byte packets

1  192.168.0.1 (192.168.0.1)  8.055 ms  71.147 ms  139.188 ms

2  * * *

3  80.255.200.164 (80.255.200.164)  10.555 ms  14.502 ms  9.166 ms

4  * * *

5  aor.uk-lon03a-ri1.network.virginmedia.net (62.254.42.174)  21.328 ms  11.761 ms  29.426 ms

6  * * *

7  uk-lon01b-ri1-ae-25-0.aorta.net (84.116.136.102)  70.679 ms  156.305 ms  15.548 ms

8  * * *

9  ae3.cr1.lhr15.uk.eth.zayo.com (64.125.28.150)  76.189 ms  20.585 ms  18.454 ms

10  * * *

11  * * *

packets get lost here

 

Compare with another ISP

 

traceroute -I amsvpn.vrt.sourcefire.com

traceroute to amsvpn.vrt.sourcefire.com (172.110.205.185), 64 hops max, 48 byte packets

1  192.168.113.114 (192.168.113.114)  140.808 ms  34.309 ms  3.259 ms

2  255.0.0.0 (255.0.0.0)  76.861 ms  44.147 ms  55.541 ms

3  * * *

4  109.249.132.9 (109.249.132.9)  43.484 ms  53.890 ms  47.197 ms

5  * * *

6  * 109.249.132.123 (109.249.132.123)  59.909 ms *

7  core6-hu0-7-0-15.faraday.ukcore.bt.net (195.99.127.50)  62.828 ms * *

8  * 166-49-209-194.gia.bt.net (166.49.209.194)  39.966 ms  51.990 ms

9  ae15.mpr1.lhr15.uk.above.net (195.66.224.76)  48.269 ms  49.551 ms  52.558 ms

10  ae3.cr1.lhr15.uk.eth.zayo.com (64.125.28.150)  49.399 ms  46.367 ms  54.104 ms

11  213.161.83.239 (213.161.83.239)  50.270 ms  59.591 ms  92.833 ms

12  vl2803.amscore2.vrt.sourcefire.com (172.110.205.57)  49.739 ms  57.692 ms  43.337 ms

13  amsvpn.vrt.sourcefire.com (172.110.205.185)  49.761 ms  41.806 ms  56.170 ms

  • spoulson's avatar
    spoulson
    3 months ago

    It turns out this isn't a routing problem. I think the zayo.com switch has been configured to drop packets sourced from 86.14.162.0/24 or more specific. I switched to modem mode which reallocated my IP out of this range and I can get to sourcefire.com now.  Thanks to the community for support. However, during this process I must say I found Virgin Media's support poor and I will consider this when the contract runs out.

20 Replies

Sort By
  • Carley_S's avatar
    Carley_S
    Icon for Forum Team rankForum Team
    3 months ago

    Hi spoulson 

    Welcome to the Community Forums. 

    Sorry to hear that you've not been able to access zayo.com. 

    Are you able to access this through a Virgin Media service without the VPN enabled? 

    • spoulson's avatar
      spoulson
      On our wavelength
      3 months ago

      Everything works otherwise except can't connect to amsvpn.vrt.sourcefire.com. I've also seen the same problem at another location that uses Virgin but works fine with other ISPs. The packet is meant to route to amsvpn.vrt.sourcefire.com (172.110.205.185)  but doesn't go beyond ae3.cr1.lhr15.uk.eth.zayo.com (64.125.28.150) either this server is dead or is rejecting packets from VM, another route is needed. See traceroute. This looks like something that should be raised with your network team like I've seen in other discussions here.

       

       

  • Client62's avatar
    Client62
    Alessandro Volta
    3 months ago

    On our VM connection we can reach : amsvpn.vrt.sourcefire.com

    > ping  amsvpn.vrt.sourcefire.com

    Pinging amsvpn.vrt.sourcefire.com [172.110.205.185] with 32 bytes of data:
    Reply from 172.110.205.185: bytes=32 time=25ms TTL=240
    Reply from 172.110.205.185: bytes=32 time=25ms TTL=240
    Reply from 172.110.205.185: bytes=32 time=22ms TTL=240
    Reply from 172.110.205.185: bytes=32 time=23ms TTL=240

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

    • cje85's avatar
      cje85
      Wise owl
      3 months ago

      It's working for me too:

      tracert amsvpn.vrt.sourcefire.com

      Tracing route to amsvpn.vrt.sourcefire.com [172.110.205.185]
      over a maximum of 30 hops:

        1     1 ms     1 ms     1 ms  RT-AX86U-9080 [192.168.1.1]
        2    17 ms    13 ms    14 ms  10.53.39.9
        3    15 ms    35 ms    12 ms  80.255.195.242
        4     *        *        *     Request timed out.
        5    34 ms    30 ms    30 ms  86.85-254-62.static.virginmediabusiness.co.uk [62.254.85.86]
        6     *        *        *     Request timed out.
        7    23 ms    31 ms    41 ms  uk-lon01b-ri1-ae-23-0.aorta.net [84.116.135.30]
        8     *        *        *     Request timed out.
        9    25 ms    26 ms    24 ms  ae3.cr1.lhr15.uk.eth.zayo.com [64.125.28.150]
       10    26 ms    25 ms    26 ms  213.161.83.239
       11    27 ms    24 ms    23 ms  vl2803.amscore2.vrt.sourcefire.com [172.110.205.57]
       12    27 ms    26 ms    25 ms  amsvpn.vrt.sourcefire.com [172.110.205.185]

      • spoulson's avatar
        spoulson
        On our wavelength
        3 months ago

        You have a different route:

        Yours: uk-lon01b-ri1-ae-23-0.aorta.net [84.116.135.30] -> 64.125.28.150

        Mine: uk-lon01b-ri1-ae-25-0.aorta.net (84.116.136.102) -> 64.125.28.150

        64.125.28.150 has an ACL entry to drop packets from 84.116.136.102  ¯\_(ツ)_/¯

    • spoulson's avatar
      spoulson
      On our wavelength
      3 months ago

      @Client62 can you do the traceroute for that. My hypothesis is the 84.116.135.30- > 64.125.28.150 hop is the problem.

      • Client62's avatar
        Client62
        Alessandro Volta
        3 months ago

        First I would like to see your result of a ping test.

        Unless you are also near Colchester, Essex my routing would differ from yours.

         

  • spoulson's avatar
    spoulson
    On our wavelength
    3 months ago

    @ Carley_S  see https://community.virginmedia.com/discussions/Wireless/routing-problems-to-google-dns/5531299

    • Client62's avatar
      Client62
      Alessandro Volta
      3 months ago

      Routing to dns.google works perfectly :- 

      > nslookup hp.com 8.8.8.8
      Server:  dns.google
      Address:  8.8.8.8

      Non-authoritative answer:
      Name:    hp.com
      Addresses:  15.72.80.135
                15.73.145.56


  • Roger_Gooner's avatar
    Roger_Gooner
    Alessandro Volta
    3 months ago

    It works for me.

    C:\>tracert amsvpn.vrt.sourcefire.com

Tracing route to amsvpn.vrt.sourcefire.com [172.110.205.185]
over a maximum of 30 hops:

  1     2 ms     1 ms     1 ms  192.168.0.1
  2     *        *        *     Request timed out.
  3     8 ms    11 ms     8 ms  80.255.195.134
  4     8 ms     8 ms     7 ms  haye-core-2a-ae1-0.network.virginmedia.net [80.3.176.177]
  5     *        *        *     Request timed out.
  6    44 ms    11 ms    16 ms  aor.uk-lon03a-ri1.network.virginmedia.net [62.254.42.174]
  7     *        *        *     Request timed out.
  8    12 ms    20 ms    11 ms  uk-lon01b-ri1-ae-25-0.aorta.net [84.116.136.102]
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11    16 ms    15 ms    14 ms  213.161.83.239
 12    14 ms    14 ms    14 ms  vl2803.amscore2.vrt.sourcefire.com [172.110.205.57]
 13    15 ms    17 ms    17 ms  amsvpn.vrt.sourcefire.com [172.110.205.185]

Trace complete.

C:\>

     

    • spoulson's avatar
      spoulson
      On our wavelength
      3 months ago

      Thanks! Your route avoids the  84.116.135.30- > 64.125.28.150 hop which I think is the problem.

      • cje85's avatar
        cje85
        Wise owl
        3 months ago

        Your traceroute goes through the same hop as Roger's:

        Yours:

        7  uk-lon01b-ri1-ae-25-0.aorta.net (84.116.136.102)  70.679 ms  156.305 ms  15.548 m

        Roger:

        8 12 ms 20 ms 11 ms uk-lon01b-ri1-ae-25-0.aorta.net [84.116.136.102]

         

        My traceroute (posted earlier) goes through the one you mentioned but works fine:

        7    23 ms    31 ms    41 ms  uk-lon01b-ri1-ae-23-0.aorta.net [84.116.135.30]

        Can you confirm exactly which server you think has a problem? Is it 84.116.135.30 which works for me or 84.116.136.102 which works for Roger?

  • spoulson's avatar
    spoulson
    On our wavelength
    3 months ago

    This is my traceroute

    1  192.168.0.1 (192.168.0.1)  8.055 ms  71.147 ms  139.188 ms
2  * * *
3  80.255.200.164 (80.255.200.164)  10.555 ms  14.502 ms  9.166 ms
4  * * *
5  aor.uk-lon03a-ri1.network.virginmedia.net (62.254.42.174)  21.328 ms  11.761 ms  29.426 ms
6  * * *
7  uk-lon01b-ri1-ae-25-0.aorta.net (84.116.136.102)  70.679 ms  156.305 ms  15.548 ms
8  * * *
9  ae3.cr1.lhr15.uk.eth.zayo.com (64.125.28.150)  76.189 ms  20.585 ms  18.454 ms
(stops here)

     

  • legacy1's avatar
    legacy1
    Alessandro Volta
    3 months ago

    C:\Windows\System32>tracert amsvpn.vrt.sourcefire.com

    Tracing route to amsvpn.vrt.sourcefire.com [172.110.205.185]
    over a maximum of 30 hops:

      1     6 ms     6 ms     6 ms  10.112.32.133
      2    10 ms    13 ms     9 ms  80.255.196.176
      3     *        *        *     Request timed out.
      4    14 ms     9 ms     9 ms  aor.uk-lon03a-ri1.network.virginmedia.net [62.254.42.174]
      5     *        *        *     Request timed out.
      6    13 ms    10 ms    10 ms  uk-lon01b-ri1-ae-25-0.aorta.net [84.116.136.102]
      7     *        *        *     Request timed out.
      8    19 ms    18 ms    16 ms  ae3.cr1.lhr15.uk.eth.zayo.com [64.125.28.150]
      9    27 ms    18 ms    19 ms  213.161.83.239
     10    18 ms    15 ms    15 ms  vl2803.amscore2.vrt.sourcefire.com [172.110.205.57]
     11    15 ms    16 ms    13 ms  amsvpn.vrt.sourcefire.com [172.110.205.185]

    Trace complete.

    fine here

  • Client62's avatar
    Client62
    Alessandro Volta
    3 months ago

    Still no ping test from the OP.  A pity ... I guess that means it works.

    > tracert amsvpn.vrt.sourcefire.com

    Tracing route to amsvpn.vrt.sourcefire.com [172.110.205.185]
    over a maximum of 30 hops:

      1     2 ms     2 ms     2 ms  192.168.0.1
      2     *        *        *     Request timed out.
      3    13 ms    14 ms    12 ms  80.255.193.200
      4     *        *        *     Request timed out.
      5     *        *        *     Request timed out.
      6    19 ms    20 ms    19 ms  aor.uk-lon03a-ri1.network.virginmedia.net [62.254.42.174]
      7     *        *        *     Request timed out.
      8    21 ms    20 ms    22 ms  uk-lon01b-ri1-ae-23-0.aorta.net [84.116.135.30]
      9     *        *        *     Request timed out.
     10    25 ms    26 ms    25 ms  ae3.cr1.lhr15.uk.eth.zayo.com [64.125.28.150]
     11    23 ms    23 ms    24 ms  213.161.83.239
     12    27 ms    26 ms    24 ms  vl2803.amscore2.vrt.sourcefire.com [172.110.205.57]
     13    25 ms    33 ms    24 ms  amsvpn.vrt.sourcefire.com [172.110.205.185]

    Trace complete.

    • spoulson's avatar
      spoulson
      On our wavelength
      3 months ago

      Suffice to say ping doesn't work because the 84.116.135.30- > 64.125.28.150 hop fails

      PING amsvpn.vrt.sourcefire.com (172.110.205.185): 56 data bytes

      Request timeout for icmp_seq 0

      Request timeout for icmp_seq 1

      Request timeout for icmp_seq 2

      Request timeout for icmp_seq 3

      Request timeout for icmp_seq 4

      Request timeout for icmp_seq 5

      Successful routes I see make an alternative 84.116.135.30- > 213.161.83.239 hop 

       

      • cje85's avatar
        cje85
        Wise owl
        3 months ago

        At the start of the thread your problem was with 84.116.136.102, now it seems to have changed to  84.116.135.30, is that correct?

        Either way there's no problem with 84.116.135.30 for me:

        tracert amsvpn.vrt.sourcefire.com

        Tracing route to amsvpn.vrt.sourcefire.com [172.110.205.185]
        over a maximum of 30 hops:

          1     1 ms    <1 ms    <1 ms  RT-AX86U-9080 [192.168.1.1]
          2    12 ms    10 ms    10 ms  10.53.39.9
          3    18 ms    11 ms    10 ms  80.255.195.242
          4     *        *        *     Request timed out.
          5    31 ms    21 ms    26 ms  86.85-254-62.static.virginmediabusiness.co.uk [62.254.85.86]
          6     *        *        *     Request timed out.
          7    22 ms    27 ms    19 ms  uk-lon01b-ri1-ae-23-0.aorta.net [84.116.135.30]
          8     *        *        *     Request timed out.
          9    28 ms    25 ms    25 ms  ae3.cr1.lhr15.uk.eth.zayo.com [64.125.28.150]
         10  25 ms    27 ms    45 ms  213.161.83.239
         11    26 ms    26 ms    23 ms  vl2803.amscore2.vrt.sourcefire.com [172.110.205.57]
         12    43 ms    25 ms    23 ms  amsvpn.vrt.sourcefire.com [172.110.205.185]

  • spoulson's avatar
    spoulson
    On our wavelength
    3 months ago

    It turns out this isn't a routing problem. I think the zayo.com switch has been configured to drop packets sourced from 86.14.162.0/24 or more specific. I switched to modem mode which reallocated my IP out of this range and I can get to sourcefire.com now.  Thanks to the community for support. However, during this process I must say I found Virgin Media's support poor and I will consider this when the contract runs out.