Discussion Locked

Retrieve Remote Machine IP

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a network of considerable big size. The machines are all windows based. The server is linux. My requirement is to get the IPs of all the machines that come in contact with my network via any means i.e. chat, mail etc. To simplify the requirement I explain the scenario as below:

I want to get the remote machine's ip that comes in contact with any user on any machine in my network. The contact may be thru chat. Actually thats primary.

So what I wanna know is how is it possible if at all it is?

Plz. provide your valuable inputs in this regard.

4 replies

by bfilmfan

Intrusion detection systems are used to detect anomalies with the aim of catching hackers before they do real damage to your network. They can be either network- or host-based. A host-based intrusion detection system is installed on the client computer, while a network-based intrusion detection system resides on the network.
intrusion detection systems work by either looking for signatures of known attacks or deviations of normal activity. These deviations or anomalies are pushed up the stack and examined at the protocol and application layer. They can effectively detect things such as Xmas tree scans, DNS poisonings, and other malformed packets.

A good network based intrusion detection systems is SNORT. It is free and will run on Linux and Windows computers. One simple way to set it up is to span a port, and allow that port to capture all traffic that traverses that node of the network. Install SNORT on your OS of choice and connect it to that portion of the network with a "receive only" network cable. Once you configure your rules set, you will be ready to go!

by choppit

I use Tethereal for logging connections for relatively short periods of time (up to 24 hours). I use a dedicated NIC on a Linux box to capture traffic mirrored from the router port. This also gives me valuable insight into how the network is being used throughout the day.

by brunob75

Your scenario 'explanation' actually appears to make the requirements more complex, not simpler.
Because you don't say, we have to assume you have a classic firewall/proxy + NAT setup

As previous posts have stated, the way to log traffic to/from outside is right at the gateway. You firewall/proxy boxes should have everything that's needed to do that.

Now when you say ALL IPs 'that come in contact with any user on any machine in my network', do you mean purely internal traffic as well ?

Then either you'll have to have sniffers on each network segment or switch, or find a way to log local traffic information on each host.
On a 'considerable size network', that's a lot of work and a lot of data too, most of it useless and totally predictable (traffic to servers and proxies).

Unless you have this specific requirement to keep track of everything going on, maybe you should look into refining your requirements and try to track only what's relevant, maybe unusual and in any case useful to you. Properly configured sniffers and IDSes can help you do that.

Also, as always, logging is useless unless the data is actually monitored and analyzed.

This discussion is closed to new replies.