Igor:
Heya. Some replies:
> The issue is:
> Kaboodle uses its IP (A.B.C.D) and pings address range
> A.B.C.1 - A.B.C.224 which is not right
>
> I implemented:
> (a) define all my IPs and their masks
> (b) do ping in cycle by all net interfaces and address ranges
> corresponding to their masks
That's good. Are these changes committed into the CVS server?
Also, what is the status of the "interface checking" we spoke about
the other week? I recall we were going to iterate thru all of the
interfaces, and determine which were active and ignore the ones which
we not. Has that been implemented?
> To do next:
> CSearchNetworkManager deals with a single net interface data set. Now the
> data is initiated in
> BOOL CNIDPC::GetMacAddressforLocalMachine()
> {
> CSearchNetworkManager::SetNetworkId(networkID);
> CSearchNetworkManager::SetSubnetMask(subnetMask);
> CSearchNetworkManager::SetInterfaceIndexaAndType(...);
> }
>
> 1. We should create an array of net interface data sets.
> 2. CSearchNetworkManager::StartPing(PING_CODE code) should
> verify responses to our ping not at one interface only but using the
> interface array.
That's probably a good idea. Please see my thread to VK
about this: I only want one machine to be the "active pinger" for
the LAN. Everything else is a passive listener, and only does a
whole-LAN-ping when the user clicks the Refresh button.
Lastly, please confirm that you can get the VPN connection
using the Zebedee tunnel to work. Thanks!
-Scott
-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
Kaboodle-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
