Custom Query (16363 matches)
Results (1204 - 1206 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #2899 | obsolete | nmap does not work on host attached tap devices | ||
| Description |
hi i have a virtualbox installed on a debian/testing i have a win32 xp guest system. The host has a tap0 device with 192.168.30.1 ip address the guest has a host interface under 192.168.30.2 attached to tap0 i can ping the guest from the host and the host from the guest ping 192.168.30.2 PING 192.168.30.2 (192.168.30.2) 56(84) bytes of data. 64 bytes from 192.168.30.2: 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 192.168.30.2
Starting Nmap 4.62 ( http://nmap.org ) at 2008-12-26 14:22 CET
Initiating ARP Ping Scan at 14:22
Scanning 192.168.30.2 [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 192.168.30.2 tell 192.168.30.1
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. |
|||
| #1049 | fixed | nmap 10.0.2.2 (host machine) results in vbox crash => Fixed in 2.1.0 | ||
| Description |
Scanning the host machine from inside the virtual machine with "nmap 10.0.2.2" results in a crash of the virtual machine. The problem is reproducible without problem here. What feels a bit weird is the delay between the command and the crash sometimes: nmap gives its result and the command line returns, then it takes some seconds until the crash (up to about a minute). All other networking seems to work fine, including mounting a share on the host via smb. The log file is attached, but does not contain any useful information as far as I can see (nothing about the crash in any case). Starting the microsoft visual studio debugger after the crash gives the following error: "Unhandled exception at 0x02f75b96 in VirtualBox.exe: 0xC0000005: Access violation writing location 0x06697674.". The exception address shows up again in the call stack in VBoxDD.dll. Didn't check so far, but if there is a version available with debugging symbols I might run that one again to get more information. Ah, right: VirtualBox 1.5.4, host Windows XP w/ service pack 2 and a stupid novell netware client, guest debian etch kernel 2.6.18 (-5-686). Network adapter 0 is NAT, the others are disabled. |
|||
| #6025 | fixed | nictypes documentation missing | ||
| Description |
User-Guide is lacking the mapping between 'nictype' and networking hardware description. Following nictypes are available: Am79C970A|Am79C973|82540EM|82543GC|82545EM|virtio Following networking hardware is described AMD PCNet PCI II; AMD PCNet FAST III (the default); Intel PRO/1000 MT Desktop; Intel PRO/1000 T Server; Intel PRO/1000 MT Server; Paravirtualized network adapter (virtio-net). However the mapping between both information is not obvious. |
|||

