Ticket #2899 (closed defect: obsolete)

Opened 7 years ago

Last modified 8 weeks ago

nmap does not work on host attached tap devices

Reported by: zashone Owned by:
Priority: major Component: network/hostif
Version: VirtualBox 2.1.0 Keywords: tap nmap
Cc: Guest type: Windows
Host type: Linux

Description (last modified by vushakov) (diff)

hi i have a virtualbox installed on a debian/testing

i have a win32 xp guest system.

The host has a tap0 device with ip address the guest has a host interface under attached to tap0

i can ping the guest from the host and the host from the guest

PING ( 56(84) bytes of data.
64 bytes from icmp_seq=1 ttl=128 time=3.02 ms

but if i try to nmap the guest from the host it does not work (even with -PN)

nmap -v -A

Starting Nmap 4.62 ( ) at 2008-12-26 14:22 CET
Initiating ARP Ping Scan at 14:22
Scanning [1 port]
Completed ARP Ping Scan at 14:22, 0.21s elapsed (1 total hosts)
Read data files from: /usr/share/nmap
Note: Host seems down. If it is really up, but blocking our ping probes, try -PN
Nmap done: 1 IP address (0 hosts up) scanned in 0.287 seconds
           Raw packets sent: 2 (84B) | Rcvd: 0 (0B)

i can not identify exactly the problem. but if i tcpdump on tap0 i noticed a strange behavior on arp requests

14:10:24.471499 arp who-has tell
14:10:24.471749 00:02:08:00:27:1c (oui Unknown) > 00:01:08:00:06:04 (oui Unknown), ethertype Unknown (0xa9db), length 46: 
	0x0000:  c0a8 1e02 c205 a87b 714f c0a8 1e01 804b  .......{qO.....K
	0x0010:  2910 0001 0000 0000 0001 2046 4845 5046  )..........FHEPF

i did not used virtualbox for a while as i was waiting for some feature from that version but i m pretty sure that nmap worked like a charm in the 2.0 series.

Change History

comment:1 Changed 7 years ago by zashone

i switched back to 2.0 and nmap works fine , i think there is really a problem with the new network stack when using tap devices

comment:2 Changed 7 years ago by frank

  • Component changed from network to network/hostif

comment:3 Changed 4 years ago by aleksey

I guess this issue is obsolete. Disagree, anyone?

comment:4 Changed 8 weeks ago by vushakov

  • Status changed from new to closed
  • Resolution set to obsolete
  • Description modified (diff)
Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use