Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Firewalls
[Top] [All Lists]

Re: Wierd ICMP in logs

Subject: Re: Wierd ICMP in logs
Date: 14 Sep 2004 22:17:54 +0200
El dom, 12 de 09 de 2004 a las 20:51, Mark escribiÃ:
I am running openBSD with PF for my firewall.

I found these wierd entries in my log file:
Sep 12 10:37:59.896280 rule 1/0(match): block in on xl0: 24.21.214.129 > 
68.*.*.*: icmp: host 192.168.1.100 unreachable [tos 0xc0]
Sep 12 10:37:59.905766 rule 1/0(match): block in on xl0: 24.21.214.129 > 
68.*.*.*: icmp: host 192.168.1.100 unreachable [tos 0xc0]
Sep 12 10:38:06.194229 rule 1/0(match): block in on xl0: 24.21.214.129 > 
68.*.*.*: icmp: host 192.168.1.100 unreachable [tos 0xc0]

My question is why is it saying host 192.168.1.100 unreachable? Thats an 
internal IP on my network, how can this 24.21.214.129 IP be pinging IP's on 
my internal network? Is there something i can do to block this? I am 
currently blocking all external icmp traffic.

PS: I have * out my ip address.

Thanks


It seems to me like a problem with the routes, because the machine
24.21.214.129 it's responding you that that address is unreacheable,
this is probably caused because you are trying to access from the
machine 68.*.*.* to an address 192.168.1.100 in the network which
router is 24.21.214.129, that it's responding you that address is
unreachable. I suppose you are trying to access 192.168.1.100 in your
local network and not in the remote network, but maybe a problem with
the routes is doing that this packets go to the remote network.

-- 
Jose Maria Lopez Hernandez
Director Tecnico de bgSEC
jkerouac@bgsec.com
bgSEC Seguridad y Consultoria de Sistemas Informaticos
http://www.bgsec.com
ESPAÃA

The only people for me are the mad ones -- the ones who are mad to live,
mad to talk, mad to be saved, desirous of everything at the same time,
the ones who never yawn or say a commonplace thing, but burn, burn, burn
like fabulous yellow Roman candles.
                -- Jack Kerouac, "On the Road"

<Prev in Thread] Current Thread [Next in Thread>