Page 1 of 1

Identify Virus Ip Location help !!

Posted: Tue Nov 24, 2009 12:30 am
by doctor
hi .. i'm a provider and there is a virus on my network .. i dun know which ip is the real infected one .. i added a firewall filter to block the virus but i really need to identify which ip how can i do that PLZ HELP

Re: Identify Virus Ip Location help !!

Posted: Tue Nov 24, 2009 12:56 am
by fewi
Use torch to watch for traffic that matches the ports you're experiencing problems on:
/tool torch interface={client_facing_interface} src-address=0.0.0.0/0 dst-address=0.0.0.0/0 port={port used by virus}
It'll display, among other things, the IP addresses of the clients participating in traffic that matches those parameters.

Re: Identify Virus Ip Location help !!

Posted: Wed Nov 25, 2009 1:40 pm
by doctor
ok thnx i'll try that but is there a more simple way like a firewall filter or a mangle rule to identify which ip/ips that has/have the virus cuz i have too many clients and it's hard to detect the infected one :S

Re: Identify Virus Ip Location help !!

Posted: Thu Nov 26, 2009 12:53 pm
by Pilgrim
I guess that if you know the ports used by the virus, then you could just set up a line in your firewall to log all traffic through these ports.

Re: Identify Virus Ip Location help !!

Posted: Fri Dec 11, 2009 12:58 pm
by doctor
line like what .. give me an example plz .. suppose the virus port is 445

Re: Identify Virus Ip Location help !!

Posted: Fri Dec 11, 2009 6:04 pm
by Cr33p3r
if you have a firewall rule already dropping the traffc, copy the rule and change the action from drop to log. voila ;)

Re: Identify Virus Ip Location help !!

Posted: Sun Dec 13, 2009 4:15 am
by butche
First, if you are not already dropping traffic to/from the netbios ports, you should do that.
/ip firewall filter
add chain=forward protocol=udp port=445,135-139 action=drop
add chain=forward protocol=tcp port=445,135-139 action=drop
If it is some virus that does not spread using netbios, then you should identify the traffic with either torch or a firewall rule that logs traffic. Something like the following will give you a log rule:
/ip firewall filter
add chain=forward action=log
That is likely to generate a LOT of traffic. You can tune the above rule to narrow down what traffic you are looking for with the log action.