﻿id	summary	reporter	owner	description	type	status	component	version	resolution	keywords	cc	guest	host
16478	--natbindip1 not binding TCP traffic to interface => Fixed in 5.1.28	wrunning		"Hello! I am experiencing what seems to be the issue laid out previously here https://forums.virtualbox.org/viewtopic.php?f=7&t=34878.
To describe the situation myself:
Host OS has several external connections, a WAN and several OpenVPN connections and I want a certain VM to route its traffic through one of the vpn connections, vpn1. vpn1 has a route to 0.0.0.0/0, but with a higher metric than WAN.
I set up a NAT adapter for the guest VM, then used vboxmanage modifyvm vm1 --natbindip1 vpn1_IP.
What happens is that UDP traffic gets properly bind-ed to vpn1 and gets sent out through it, while TCP traffic goes out via WAN connection.I checked this both with wireshark, netstat and by setting up an outside listening endpoint for both UDP and TCP.
I have written myself a program that actually binds to the vpn1 connection and use it for both TCP and UDP traffic and everything works fine, so it isn't a routing issue.
Please let me know if there is any more information needed from my side in order to pinpoint the issue.
Thanks!"	defect	closed	network/NAT	VirtualBox 5.1.2	fixed	bind NAT		Windows	Windows
