TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message to
[EMAIL PROTECTED]  Contact [EMAIL PROTECTED] for help with any problems!
----------------------------------------------------------------------------

I have been investigating similar occurances here that appear to have only
started mid-way through last month.
The difference here is the IP addresses being flagged as the Trace Route
source, are 2 arbitrary addresses in our network. I have confirmed that
there are NO computers in our network using either of these numbers... The
traces are consistantly directed to various networks in Romania.
I have sniffed and set traps and numerous filters for any and all traffic
using either of the arbitrary addresses... Nothing ever was logged while the
Trace Routes continued.
I finally found a little clue this weekend...  one of the Romanian target
addresses didn't exist, so the TCP error was sent back to the true source
(in Germany). Here's what that packet described:
German source (10.10.10.1) sends a packet destined for for a non-existant
computer in my network (192.168.1.1). The header of that packet lists source
address as 192.168.1.1 (my network) and the source as one of the Romanian
targets.
It appears as if, as long as the Romanian target exists, the German source
is probing and prodding, all the while disguising themselves as me...
My confusion is:
Without an agent like leapfrog or netcat in my walls for the German source
to point to, how are they successfully able to use my network as a sort of
'Clark Kent phone booth'?
The address they are communicating with in my network does not exist, but
they are dynamically using it as a spoofed source and completly hiding
themselves from all sensors?

David Gager, MCP
Network Operations Center
Educational Service District 112
Vancouver, Washington
360.750.7502 ext. 387


-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
[EMAIL PROTECTED]
Sent: Thursday, April 05, 2001 1:14 PM
To: [EMAIL PROTECTED]
Subject: Traceroute



TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message to
[EMAIL PROTECTED]  Contact [EMAIL PROTECTED] for help with any
problems!
----------------------------------------------------------------------------

Here is my situation:
     I have an external IDS Real Secure 3.2.1.  It receives an ICMP packet
from a router that states the TTL has expired.  The router that sends the
packet is x.x.x.x  The contents of the packet say that my IP (y.y.*.0)
Where the 1st & 2nd octets are set the 3rd is random and the fourth is 0,
sent a packet to an address z.z.z.z.   After verifying traffic with a
sniffer, we determined our IP was being spoofed and we were never sending
those packets.  However the IDS reads the packet from the router x.x.x.x
and assumes that we initiated a traceroute to z.z.z.z and flags.

     1.  Why does this happen. (Flag as a traceroute originating from my
network)
     2.  How do I make it stop.
Michael Booth
IS Security
"There is a war out there, and it's about who controls the information,
it's all about the information."






Reply via email to