• Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
  • Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
Collapse

You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:

  • You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
  • You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
  • If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.

Previously on "Fun with traceroute"

Collapse

  • Sysman
    replied
    Bummer. There's always someone who'll spoil the fun.

    Leave a comment:


  • mudskipper
    replied
    Originally posted by doodab View Post
    That is clever.
    And now it's down.

    Relentless DDoS

    This is why we cant have nice things. Beaglenetworks.net has been ddos’ed all day. 216.81.59.173 has recently come under massive attack at > 1gbps. I cannot allow my upstreams to deal with this so I have no choice but to take it off line.

    Appologies to all

    Leave a comment:


  • doodab
    replied
    That is clever.

    Leave a comment:


  • KentPhilip
    replied
    Originally posted by Contreras View Post
    traceroute -m 100 for the whole story.

    C:\>tracert -h 100 216.81.59.173

    Tracing route to FIN [216.81.59.173]
    over a maximum of 100 hops:

    1 42 ms 95 ms 93 ms bebox.config [192.168.1.254]
    2 * * * Request timed out.
    3 18 ms 19 ms 17 ms 195.66.225.189
    4 17 ms 20 ms 18 ms 10gigabitethernet1-1.core1.lon1.he.net [195.66.2
    24.21]
    5 85 ms 92 ms 92 ms 10gigabitethernet7-4.core1.nyc4.he.net [72.52.92
    .241]
    6 111 ms 93 ms 91 ms 10gigabitethernet2-3.core1.ash1.he.net [72.52.92
    .86]
    7 104 ms 118 ms 108 ms 10gigabitethernet1-2.core1.atl1.he.net [184.105.
    213.110]
    8 107 ms 104 ms 104 ms 216.66.0.26
    9 * * * Request timed out.
    10 144 ms 141 ms 141 ms Episode.IV [206.214.251.1]
    11 141 ms 142 ms 143 ms 206.214.251.6
    12 145 ms 141 ms 140 ms It.is.a.period.of.civil.war [206.214.251.9]
    13 141 ms 141 ms 142 ms Rebel.spaceships [206.214.251.14]
    14 144 ms 141 ms 140 ms striking.from.a.hidden.base [206.214.251.17]
    15 142 ms 143 ms 141 ms have.won.their.first.victory [206.214.251.22]
    16 141 ms 140 ms 145 ms 206.214.251.25
    17 143 ms 142 ms 142 ms During.the.battle [206.214.251.30]
    18 144 ms 141 ms 143 ms Rebel.spies.managed [206.214.251.33]
    19 142 ms 145 ms 142 ms to.steal.secret.plans [206.214.251.38]
    20 138 ms 140 ms 142 ms to.the.Empires.ultimate.weapon [206.214.251.41]

    21 139 ms 141 ms 143 ms the.DEATH.STAR [206.214.251.46]
    22 138 ms 140 ms 139 ms an.armored.space.station [206.214.251.49]
    23 139 ms 142 ms 142 ms with.enough.power.to [206.214.251.54]
    24 143 ms 143 ms 141 ms destroy.an.entire.planet [206.214.251.57]
    25 140 ms 146 ms 146 ms Pursued.by.the.Empires [206.214.251.62]
    26 142 ms 141 ms 139 ms 206.214.251.65
    27 142 ms 143 ms 142 ms Princess.Leia.races.home [206.214.251.70]
    28 143 ms 141 ms 146 ms aboard.her.starship [206.214.251.73]
    29 138 ms 141 ms 144 ms custodian.of.the.stolen.plans [206.214.251.78]
    30 141 ms 143 ms 144 ms that.can.save.her [206.214.251.81]
    31 141 ms 149 ms 142 ms people.and.restore [206.214.251.86]
    32 146 ms 146 ms 142 ms freedom.to.the.galaxy [206.214.251.89]
    33 142 ms 143 ms 142 ms 206.214.251.94
    34 145 ms 139 ms 149 ms 0------------------0 [206.214.251.97]
    35 143 ms 144 ms 143 ms 206.214.251.102
    36 145 ms 143 ms 141 ms 0----------------0 [206.214.251.105]
    37 145 ms 140 ms 140 ms 0---------------0 [206.214.251.110]
    38 139 ms 145 ms 142 ms 0--------------0 [206.214.251.113]
    39 141 ms 173 ms 143 ms 0-------------0 [206.214.251.118]
    40 145 ms 143 ms 143 ms 0------------0 [206.214.251.121]
    41 149 ms 144 ms 141 ms 0-----------0 [206.214.251.126]
    42 141 ms 142 ms 143 ms 0----------0 [206.214.251.129]
    43 142 ms 145 ms 144 ms 0---------0 [206.214.251.134]
    44 148 ms 144 ms 143 ms 0--------0 [206.214.251.137]
    45 145 ms 144 ms 147 ms 0-------0 [206.214.251.142]
    46 142 ms 143 ms 143 ms 0------0 [206.214.251.145]
    47 142 ms 144 ms 141 ms 0-----0 [206.214.251.150]
    48 148 ms 143 ms 143 ms 0----0 [206.214.251.153]
    49 142 ms 148 ms 144 ms 0---0 [206.214.251.158]
    50 144 ms 152 ms 147 ms 0--0 [206.214.251.161]
    51 140 ms 143 ms 141 ms 0-0 [206.214.251.166]
    52 145 ms 142 ms 144 ms 00 [206.214.251.169]
    53 145 ms 146 ms 140 ms 206.214.251.174
    54 146 ms 148 ms 142 ms By.Ryan.Werber [206.214.251.177]
    55 152 ms 143 ms 141 ms When.CCIEs.Get.Bored [206.214.251.182]
    56 141 ms 144 ms 141 ms read.more.at.beaglenetworks.net [206.214.251.185
    ]
    57 142 ms 145 ms 145 ms FIN [216.81.59.173]

    Trace complete.
    And beaglenetworks.net
    links to:
    Untitled
    which describes how he did it.
    Well done Ryan.Werber!

    Leave a comment:


  • Contreras
    replied
    Originally posted by Sysman View Post
    On Unix or Linux open up a terminal session and type this:

    Code:
    traceroute 216.81.59.173
    On Windows open up the command prompt and type this:

    Code:
    tracert 216.81.59.173
    and watch the story unfold.
    traceroute -m 100 for the whole story.

    Leave a comment:


  • MarillionFan
    replied
    Really?

    Leave a comment:


  • Platypus
    replied
    Amazing !!

    Leave a comment:


  • vetran
    replied
    Thankyou

    Leave a comment:


  • ctdctd
    replied

    Leave a comment:


  • Cliphead
    replied

    Leave a comment:


  • KentPhilip
    replied
    Fantastic

    Leave a comment:


  • mudskipper
    replied

    Leave a comment:


  • Troll
    replied

    Leave a comment:


  • Sysman
    started a topic Fun with traceroute

    Fun with traceroute

    On Unix or Linux open up a terminal session and type this:

    Code:
    traceroute 216.81.59.173
    On Windows open up the command prompt and type this:

    Code:
    tracert 216.81.59.173
    and watch the story unfold.

Working...
X