-
Notifications
You must be signed in to change notification settings - Fork 319
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
scan failure on one backend causes failures on all #559
Comments
right now, we have
So, in the case we have a partial failure (usb works, but Ethernet does not), how do we want to return things?
|
What is an Ethernet failure? Is that just it didn't find anything? |
So, if it's a bad-actor on the network, we can consider it doesn't exist and continue with the rest that do exist? Another option is to extend the API a bit, and add a This could probably be useful for local contexts as well [later] when stuff gets added/extended to the local context to do more validation in there.
So, |
It's when something response that they do have a IIO device via dns-sd, but don't actually have iiod running. This happens if you have an old install with a iio_services file in /etc/avahai/ ... but no iiod running. The Linux side handles this case, but the windows implementation doesn't like it, and returns a failure. |
I think the issue is - the Linux code actually port knocks, and the Windows code does not... That is the easiest fix. |
Both the Linux and Mac implemations of DNS SD ensures something is there before passing the host information up the stack. The Windows implemnation was missing this, so add it. Fix #559 Signed-off-by: Robin Getz <[email protected]>
Both the Linux and Mac implemations of DNS SD ensures something is there before passing the host information up the stack. The Windows implemnation was missing this, so add it. Fix #559 Signed-off-by: Robin Getz <[email protected]>
Both the Linux and Mac implemations of DNS SD ensures something is there before passing the host information up the stack. The Windows implemnation was missing this, so add it. Add locking since it's needed by those functions. Fix #559 Signed-off-by: Robin Getz <[email protected]>
Both the Linux and Mac implemations of DNS SD ensures something is there before passing the host information up the stack. The Windows implemnation was missing this, so add it. Add locking since it's needed by those functions. Fix #559 Signed-off-by: Robin Getz <[email protected]>
Both the Linux and Mac implemations of DNS SD ensures something is there before passing the host information up the stack. The Windows implemnation was missing this, so add it. Add locking since it's needed by those functions. Fix #559 Signed-off-by: Robin Getz <[email protected]>
Both the Linux and Mac implemations of DNS SD ensures something is there before passing the host information up the stack. The Windows implemnation was missing this, so add it. Add locking since it's needed by those functions. Fix #559 Signed-off-by: Robin Getz <[email protected]>
Both the Linux and Mac implemations of DNS SD ensures something is there before passing the host information up the stack. The Windows implemnation was missing this, so add it. Add locking since it's needed by those functions. Fix #559 Signed-off-by: Robin Getz <[email protected]>
Both the Linux and Mac implemations of DNS SD ensures something is there before passing the host information up the stack. The Windows implemnation was missing this, so add it. Add locking since it's needed by those functions. Fix #559 Signed-off-by: Robin Getz <[email protected]>
Both the Linux and Mac implemations of DNS SD ensures something is there before passing the host information up the stack. The Windows implemnation was missing this, so add it. Add locking since it's needed by those functions. Fix #559 Signed-off-by: Robin Getz <[email protected]>
Both the Linux and Mac implemations of DNS SD ensures something is there before passing the host information up the stack. The Windows implemnation was missing this, so add it. Add locking since it's needed by those functions. Fix #559 Signed-off-by: Robin Getz <[email protected]>
@mhennerich noticed that an ethernet scan failure causes a total scan failure...
I think this is a problem with bad actors on ethernet with a Windows clients.
But will need to check a little bit more...
The text was updated successfully, but these errors were encountered: