Destination net unreachable?

Discussion in 'Networking & Security' started by spaceman, May 22, 2013.

  1. spaceman

    spaceman [H]ardForum Junkie

    Messages:
    14,193
    Joined:
    Jan 7, 2005
    Did a trace to help solve some possible instability in my connection. After 6 hops I got the title of the thread. Not sure how to translate it. It may be an MTU size issue? Would appreciate any insights. Thanks

    F:\Users\dave>tracert cox.com

    Tracing route to cox.com [24.248.75.200]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms esr9850.esr9850 [192.168.0.1]
    2 7 ms 8 ms 11 ms 10.65.20.1
    3 9 ms 9 ms 10 ms 98.172.172.192
    4 9 ms 7 ms 7 ms 98.172.172.129
    5 62 ms 73 ms 28 ms dukedsrj01-ge-210.0.rd.at.cox.net [68.1.1.121]
    6 lkhndsrc01-pos0901.rd.at.cox.net [68.1.0.5] reports: Destination net unrea
    chable.

    Trace complete.
     
    Last edited: May 22, 2013
  2. Pinski

    Pinski Limp Gawd

    Messages:
    140
    Joined:
    Feb 20, 2005
    The router at that point has no idea how to get there.
     
  3. spaceman

    spaceman [H]ardForum Junkie

    Messages:
    14,193
    Joined:
    Jan 7, 2005
    Reboot router or is it the routing table?
     
  4. spaceman

    spaceman [H]ardForum Junkie

    Messages:
    14,193
    Joined:
    Jan 7, 2005
    It appears that the ddos issue is extending beyond just bf3. Cox, comcast, Att, charter are all having issues. I thought they caught the main culprit recently. Shit.
     
  5. spaceman

    spaceman [H]ardForum Junkie

    Messages:
    14,193
    Joined:
    Jan 7, 2005
    Tried cox.net and got a bit more out of it

    F:\Users\dave>tracert cox.net

    Tracing route to cox.net [68.99.123.161]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms esr9850.esr9850 [192.168.0.1]
    2 9 ms 7 ms 9 ms 10.65.20.1
    3 9 ms 8 ms 8 ms 98.172.172.194
    4 7 ms 8 ms 8 ms 98.172.172.133
    5 30 ms 28 ms 30 ms dukedsrj02-ge210.0.rd.at.cox.net [68.1.1.123]
    6 31 ms 30 ms 29 ms 68.1.15.238
    7 32 ms 30 ms 31 ms 68.99.123.4
    8 30 ms 30 ms 30 ms ww2.cox.com [68.99.123.161]

    Trace complete.
     
  6. timberdoodle

    timberdoodle Gawd

    Messages:
    878
    Joined:
    Sep 22, 2008
    I'm not sure what you are trying to prove here.....Cox most likely has a border firewall or gateway that is not permitting packets for cox.com. Actually, it looks to me like their cox.net and cox.com dns entires may be reversed for whatever reason. It's not abnormal to NOT be able to reach an endpoint especially if they are hosting it internally.
     
  7. spaceman

    spaceman [H]ardForum Junkie

    Messages:
    14,193
    Joined:
    Jan 7, 2005
    Not trying to prove anything. Just having issues with online connectivity in games. Especially bf3. I know ddos is an issue with them.

    I was concerned that cox and my thus connection was having similar issues with everything.
     
  8. timberdoodle

    timberdoodle Gawd

    Messages:
    878
    Joined:
    Sep 22, 2008
    In that case, are you unable to establish a gaming connection at all or is it just lag.
     
  9. spaceman

    spaceman [H]ardForum Junkie

    Messages:
    14,193
    Joined:
    Jan 7, 2005
    Both in the case of bf3. Should I ping a game server instead?
     
  10. spaceman

    spaceman [H]ardForum Junkie

    Messages:
    14,193
    Joined:
    Jan 7, 2005
    Issue is true for many people. You can be playing and having no issues then either get disconnected or start lagging so badly you may as well be disconnected. I am thinking that they are still having ddos issues even though the official word is that it has been stopped.

    This is a server I played 30 minutes in this morning and got disconnected near the end of the round. I have played 4-5 rounds in the last week or two and each has had a similar issue. I think the ea master servers are the actual issue. Not sure how to trace that.


    Tracing route to c-74-91-125-149.managed-vds.internap-chicago.nfoservers.com [74
    .91.125.149]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms esr9850.esr9850 [192.168.0.1]
    2 8 ms 7 ms 8 ms 10.65.20.1
    3 8 ms 7 ms 7 ms 98.172.172.192
    4 19 ms 8 ms 9 ms 98.172.172.129
    5 20 ms 21 ms 20 ms 68.1.4.139
    6 21 ms 19 ms 19 ms te6-3.ar3.DCA3.gblx.net [67.17.134.45]
    7 37 ms 35 ms 34 ms Internap-Chicago.TenGigabitEthernet2-4.ar5.CHI1.
    gblx.net [208.48.24.186]
    8 36 ms 35 ms 39 ms border5.po2-bbnet2.chg.pnap.net [64.94.32.74]
    9 34 ms 36 ms 37 ms c-74-91-125-149.managed-vds.internap-chicago.nfo
    servers.com [74.91.125.149]

    Trace complete.