Since I switched to the kernel pppoe I receive a lot errors with nmap.

"Cannot determine route to %FOO".

For example with a bank-website:

lynx www.cc-bank.de works perfectly
nmap -P0 -sSV -p80 www.cc-bank.de does not work.

nslookup www.cc-bank.de does work so it`s realy a neat routing issue.
Another example with www.heise.de:


sudo nmap -P0 -sS -sV -vvv www.heise.de

Starting Nmap 4.11 ( http://www.insecure.org/nmap/ ) at 2006-07-13
17:52 CEST WARNING: Unable to find appropriate interface for system
route to 0.0.0.1

WARNING: Unable to find appropriate interface for system route to
0.0.0.0

nexthost: failed to determine route to 193.99.144.85
QUITTING!


Please don`t get me wrong I just needed some Servers where I`m sure
they where working. I tried it also with -e pppoe0 and later with fxp0
(wich failed, no Adress).

godfather $ sudo nmap -e pppoe0 -P0 -sSV -p22,80 -vvv www.heise.de

Starting Nmap 4.11 ( http://www.insecure.org/nmap/ ) at 2006-07-13
17:58 CEST WARNING: Unable to find appropriate interface for system
route to 0.0.0.1

WARNING: Unable to find appropriate interface for system route to
0.0.0.0

DNS resolution of 1 IPs took 0.04s.
Initiating SYN Stealth Scan against www.heise.de (193.99.144.85) [2
ports] at 17:58 The SYN Stealth Scan took 3.02s to scan 2 total ports.
Host www.heise.de (193.99.144.85) appears to be up ... good.
Interesting ports on www.heise.de (193.99.144.85):
PORT   STATE    SERVICE VERSION
22/tcp filtered ssh
80/tcp filtered http

Nmap finished: 1 IP address (1 host up) scanned in 3.127 seconds
               Raw packets sent: 4 (176B) | Rcvd: 0 (0B)
godfather $ 

As you can see nmap displays everythign as filtered.
It doesn`t matter wich IP I scan even if I would scan www.hotmail.com
with Port 80 it would tell me it`s filtered.

I`ve NO active pf and the only stuff I made was switching from userland
pppd to Kernel pppd.


Any hints to make nmap working?


Kind regards,
Sebastian

p.s. OpenBSD AMD64/3.9-Stable with a current nmap-Port. (same result
with 3.95 so doesn`t matter)

Reply via email to