Custom Query (16363 matches)
Results (172 - 174 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #5952 | fixed | --disable-xpcom build fails | ||
| Description |
Building with "--disable-xpcom" fails:
==
kmk[2]: * No rule to make target Appearently there is a dependency on libxml2. But the configure script does not checks/configures libxml2 when XPCOM is disabled. |
|||
| #8445 | fixed | --logfile and --verbose options appear to have no effect unless run as root | ||
| Description |
Subject says it all. Maybe vboxwebsrv just isn't meant to run as a non-root user? |
|||
| #16478 | fixed | --natbindip1 not binding TCP traffic to interface => Fixed in 5.1.28 | ||
| Description |
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! |
|||

