feature request: choose better default for "Target"

[Toralf Förster <toralf.foerster () gmx de>]

HI,

starting the zenmap at hone (DSL) the app provides the following 3 items 
for "Target": my hostname, the (first) local ip address of my ethernet card 
and the peer-to-peer ip address from my provider.
But it would make sense IMHO to provide the inet addr too (in the example 
below 85.177.150.53), isn't it ?

Here's what I mean (I configured my ethernet to always have a static ip 
address of 192.168.0.254, and in addition at work I have a DHCP address too):

n22 ~ # ifconfig
eth0      Link encap:Ethernet  HWaddr 00:0d:60:7b:2d:9b
          inet addr:192.168.0.254  Bcast:192.168.0.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:307472 errors:0 dropped:0 overruns:0 frame:0
          TX packets:226258 errors:21 dropped:0 overruns:0 carrier:21
          collisions:43 txqueuelen:100
          RX bytes:410634843 (391.6 MiB)  TX bytes:24445790 (23.3 MiB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:7509 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7509 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1352657 (1.2 MiB)  TX bytes:1352657 (1.2 MiB)

ppp0      Link encap:Point-to-Point Protocol
          inet addr:85.177.150.53  P-t-P:213.191.76.23  Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1492  Metric:1
          RX packets:12921 errors:0 dropped:0 overruns:0 frame:0
          TX packets:13849 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:3
          RX bytes:14660648 (13.9 MiB)  TX bytes:1171061 (1.1 MiB)


-- 
MfG/Sincerely

Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3

Attachment: signature.asc
Description: This is a digitally signed message part.

_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org