If this is your first visit, be sure to
check out the Forum Rules by clicking the
link above. You may 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.

I haven't tried. I usually use trace route in windows but Ill give it a go tomorrow. Always love a challenge. What kind of compile errors if any did you get?

It comes compiled in BT2.... but I'm not sure if I hosed the libraries it needs by upgrading some of the packages in BT; I'll have to try a fresh ISO to see if it works out of the box.

I'm getting a ton of nasty errors. The package from Paketto includes a readme that mentions a backwards compatibility issue with libnet 1.1.1 > and that 1.0.2 has to be used, so tomorrow I may install / symlink the older libnet and see where that gets me.

I've been itching to try paratrace out ever since I read about it in a new book I have. The source gzip comes with another cool tool (that I haven't been able to get to work outside of my subnet) called scanrand, which supposively has been noted in scanning an entire class B network (65K+ hosts) for web servers with 8000 hits in 4 seconds (achieves this by firing off syn packets making no effort to retain session state).

I'm too beat to attempt to get it compiled tonight; tomorrow is another day to play

I cant seem to get scanrad to work on the out side either. the command completes but with no type of output. I got paratrace to work though. It was weird though I issued the command and it hung forever but then I opened a new shell and pinged google and then I got the out put.......

I cant seem to get scanrad to work on the out side either. the command completes but with no type of output. I got paratrace to work though. It was weird though I issued the command and it hung forever but then I opened a new shell and pinged google and then I got the out put.......

VERY COOL! ... I'm going to try that method when I get home this evening; hopefully the fix will be just as simple for me (I've probably spent a total of 4 hours trying to get it to work over the last few days)...

I got paratrace to work though. It was weird though I issued the command and it hung forever but then I opened a new shell and pinged google and then I got the out put.......

This makes sense based on the description of the tool:

Paratrace traces the path between a client and a server, much like "traceroute", but with a major twist: Rather than iterate the TTLs of UDP, ICMP, or even TCP SYN packets, paratrace attaches itself to an existing, stateful-firewall-approved TCP flow, statelessly releasing as many TCP Keepalive messages as the software estimates the remote host is hop-distant. The resultant ICMP Time Exceeded replies are analyzed, with their original hopcount "tattooed" in the IPID field copied into the returned packets by so many helpful routers. Through this process, paratrace can trace a route without modulating a single byte of TCP/Layer 4, and thus delivers fully valid (if occasionally redundant) segments at Layer 4 -- segments generated by another process entirely.

Unless the traffic is originating from you or you were dual homed and it was flowing 'through' you I don't see how you could "attach" to it.

I'm a compulsive post editor, you might wanna wait until my post has been online for 5-10 mins before quoting it as it will likely change.

I know I seem harsh in some of my replies. SORRY! But if you're doing something illegal or posting something that seems to be obvious BS I'm going to call you on it.