Bases on the backslash path style you mention I assume you're interested in Windows version of NetAdp, so.. 1. The NetAdp on windows is built from the src/VBox/HostDrivers/VBoxNetFlt source tree with VBOXNETADP defined, i.e. src\VBox\HostDrivers\VBoxNetAdp is not used. 2. The current code contains a VBOXNETADP_REPORT_DISCONNECTED conditionally compiled code (which is now disabled), to report link status as disconnected for the case the Host-Only adapter is not active (i.e. does not have intnet connected to it), so you can do whatever you need based on that code.

Hope this helps,
Mikhail


On 4/11/2011 7:02 PM, Ribhi Kamal wrote:
I'm just going through the code slowly to (hopefully) implement an interface to set the link status. Do you mind explaining a little bit what following method does:

from: src\VBox\HostDrivers\VBoxNetAdp.c
static DECLCALLBACK(bool) vboxNetAdpPortSetActive(PINTNETRUNKIFPORT pIfPort, bool fActive)

which calls vboxNetAdpSetState (line 91), but what does "state" mean here?

Thanks!

On Mon, Apr 11, 2011 at 4:23 AM, Klaus Espenlaub <[email protected] <mailto:[email protected]>> wrote:

    On 10.04.2011 00:03, Ribhi Kamal wrote:

        Does the virtualbox host-only adapter provide an interface to
        set its
        link status?


    You mean disconnecting it from the host? Don't think this exists
    right now, as it would be more or less the same as switching to
    Internal Networking... unlike for VMs, where one can control
    whether the cable is plugged in for each NIC.

    Klaus


        --
        -- Ribhi


    _______________________________________________
    vbox-dev mailing list
    [email protected] <mailto:[email protected]>
    http://vbox.innotek.de/mailman/listinfo/vbox-dev




--
-- Ribhi


_______________________________________________
vbox-dev mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-dev

_______________________________________________
vbox-dev mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-dev

Reply via email to