search

alexpevzner / sane-airscan

Scanner Access Now Easy - universal driver for eSCL (Apple AirScan) and WSD
Other
289 stars 44 forks source link

Unable to connect to Brother ADS-2700W #326

Closed pschichtel closed 9 months ago

pschichtel commented 9 months ago

It worked with the previous version 0.99.27 and stopped working with 0.99.28. I've bisected the issue to cb8a28e601551d94c30a23e07d8277b0786f7fda.

airscan-discover output with the last commit that works:

[devices]
  Brother ADS-2700W [000ec6efc1f6] = http://192.168.1.154:53048, WSD

airscan-discover output with cb8a28e601551d94c30a23e07d8277b0786f7fda:

[devices]
  Brother ADS-2700W = http://192.168.1.154:53048, WSD
pschichtel commented 9 months ago

My system is dual stack, but the scanner is connected only via IPv4.

pschichtel commented 9 months ago

Just reverting that single commit fixes it.

pschichtel commented 9 months ago

Just merely creating the resolver (avahi_service_resolver_new call) seems to cause the issue.

alexpevzner commented 9 months ago

Hi @pschichtel,

could you please run airscan-discover -t with and without that commit? It will create the airscan-discover-zeroconf.log file, I would ask you to publish both.

pschichtel commented 9 months ago

@alexpevzner https://gist.github.com/pschichtel/a509f9bdafc765441816b77479124d96

alexpevzner commented 9 months ago

Hi @pschichtel,

it's a quite clear what is broken in discovery and I will fix it soon.

What is not clear, is why device cannot be connected. Even with this problem discovery ends with the valid endpoint URL, so scanner must work.

Can I see a protocol trace?

pschichtel commented 9 months ago

By protocol trace, do you mean something like tcpdump?

alexpevzner commented 9 months ago

No. In the /etc/sane.d/airscan.conf uncomment the following lines:

[debug]
trace = ~/airscan/trace

Then try to scan. The ~/airscan/trace directory will be created and the very long log files ("protocol traces") will be written there. I want to see such a file.

Only .log files are interesting for now, .tar files not required

pschichtel commented 9 months ago

Sure, I can do that later today.

alexpevzner commented 9 months ago

The problem in discovery was fixed - waiting for your confirmation that the fix works for you.

And I still want protocol trace to look to that part of the problem that I cannot understand/reproduce.

pschichtel commented 9 months ago

yes, latest master works for me.

here is the trace logs: https://gist.github.com/pschichtel/7c892ab88ca43e7d9d509986001f7a3f