VirtualBox

Changes between Initial Version and Version 1 of Ticket #15303


Ignore:
Timestamp:
Apr 12, 2016 12:59:54 AM (8 years ago)
Author:
Valery Ushakov
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #15303 – Description

    initial v1  
    11When using a NAT network, the host adapter will generate TCP RST packets in response to packets that are not destined for that interface. For example, here we have the following network setup:
    2 
     2{{{
    3352:54:00:12:35:02 10.0.2.2   VirtualBox router
    4408:00:27:7c:00:6c 10.0.2.15  VM
    5 
     5}}}
    66And the VM sends this packet:
    7 
     7{{{
    88TCP SYN
    99Src: Eth 08:00:27:7c:00:6c / IP 10.0.2.15  / TCP 15717
    1010Dst: Eth 08:00:27:7c:00:6d / IP 10.0.2.100 / TCP 80
    11 
     11}}}
    1212Then, the VM will receive this spurious packet:
    13 
     13{{{
    1414TCP RST,ACK
    1515Src: Eth 52:54:00:12:35:02 / IP 10.0.2.100 / TCP 80
    1616Dst: Eth 08:00:27:7c:00:6c / IP 10.0.2.15  / TCP 15717
    17 
     17}}}
    1818Note the soruce MAC. This is the host adapter's MAC. The expected result is that no packet will be sent in response to the original packet above, since the target host does not exist on the network and any other host receiving the packet should disregard it since the destination MAC does not match their MAC.
    1919
    2020I have attached a pcap of the problem that was generated like this (nping is part of nmap):
    21 
     21{{{
    2222arping -I enp0s3 -c 1 10.0.2.2
    2323nping --tcp --dest-mac 08:00:27:7c:00:6d 10.0.2.100
    24 
     24}}}
    2525Tested with VirtualBox 4.3.36, 5.0.12 and 5.0.16 using Debian, Ubuntu and FreeBSD.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy