id,summary,reporter,owner,description,type,status,component,version,resolution,keywords,cc,guest,host 4540,NAT does not seem to properly set the source ip of some incoming packets,Jason Desai,,"Since upgrading to VirtualBox 3, I've been having problems with NAT. Things worked fine in 2.2.4. Specifically, it appears that the source address of packets are not being NATed properly. Some of them appear to come from 10.0.2.2 instead of from their real source address. This can cause applications drop packets, making it look like there is latency, or packet loss. I will attach a wireshark capture from the guest when it was pinging www.virtualbox.org. Notice that some of the responses come from 10.0.2.2, and not from 208.73.210.26. This causes the guest to wait until it times out for the ping response, and then next echo request is sent out after the timeout (5 seconds in this case). I've seen this happen with udp packets as well, causing issues for VPN types of applications. Reverting to 2.2.4 or changing to bridged networking fixes the issue.",defect,closed,network/NAT,VirtualBox 3.0.4,fixed,,,other,other