Bug#505130: [xsane] freezes if only port 6566 is reachable
Simon Wenner [EMAIL PROTECTED] wrote: Hi, Ok, I see the issue. After taking a second look, I realised that both (xsane and scanimage) freeze infinitely ( 15 minutes). They did not Yeah, what I expected. By the way, there is a netfilter module for the SANE protocol, so if your firewall is a Linux box you'd probably want to use it. JB. -- Julien BLACHE - Debian GNU/Linux Developer - [EMAIL PROTECTED] Public key available on http://www.jblache.org - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#505130: [xsane] freezes if only port 6566 is reachable
Hi, Ok, I see the issue. After taking a second look, I realised that both (xsane and scanimage) freeze infinitely ( 15 minutes). They did not reach any timeout. Scanimage is just more verbose. And they behave identical in whatever order they are called. Sorry for the noise. But still... a more realistic timeout would be nice, followed be an error message. If technically possible/reasonable. Cheers, Simon Julien BLACHE schrieb: Simon Wenner [EMAIL PROTECTED] wrote: Hi, My scanner is attached to my Debian Etch box and shared on the network. I access it with a Lenny box. If the firewall (firehol) on the server is configured too restrictive, i.e. only the saned control port (6566) is reachable, xsane just freezes and has to be killed. This is very confusing for the user. Standard TCP/IP issue. If you're dropping packet, the connecting side has no way whatsoever to know that and a very long timeout will eventually be reached. No problem here. Scanimage at least reports an Error during device I/O. There's no reason why XSane and scanimage would behave differently, except maybe if you tried scanimage after XSane. It'd be nice if you could try it again both way around and track the problem down, if there is any. JB. signature.asc Description: OpenPGP digital signature
Bug#505130: [xsane] freezes if only port 6566 is reachable
Package: xsane Version: 0.995-6 Severity: normal My scanner is attached to my Debian Etch box and shared on the network. I access it with a Lenny box. If the firewall (firehol) on the server is configured too restrictive, i.e. only the saned control port (6566) is reachable, xsane just freezes and has to be killed. This is very confusing for the user. Scanimage at least reports an Error during device I/O. --- System information. --- Architecture: i386 Kernel: Linux 2.6.26-1-686 Debian Release: lenny/sid 900 testing security.debian.org 900 testing mirror.switch.ch 900 testing debian.netcologne.de 500 stable mirror.switch.ch --- Package information. --- Depends (Version) | Installed ===-+-== xsane-common (= 0.995-6) | 0.995-6 libatk1.0-0 (= 1.20.0) | 1.22.0-1 libc6 (= 2.7-1) | 2.7-15 libcairo2 (= 1.2.4) | 1.6.4-6.1 libgimp2.0 (= 2.4.0) | 2.4.7-1 libglib2.0-0 (= 2.12.0) | 2.16.6-1 libgtk2.0-0 (= 2.12.0) | 2.12.11-4 libjpeg62 | 6b-14 liblcms1 (= 1.15-1) | 1.17.dfsg-1 libpango1.0-0 (= 1.20.3) | 1.20.5-3 libpng12-0 (= 1.2.13-4) | 1.2.27-2 libsane (= 1.0.11-3) | 1.0.19-21 libtiff4 | 3.8.2-11 zlib1g (= 1:1.1.4) | 1:1.2.3.3.dfsg-12 signature.asc Description: OpenPGP digital signature
Bug#505130: [xsane] freezes if only port 6566 is reachable
Simon Wenner [EMAIL PROTECTED] wrote: Hi, My scanner is attached to my Debian Etch box and shared on the network. I access it with a Lenny box. If the firewall (firehol) on the server is configured too restrictive, i.e. only the saned control port (6566) is reachable, xsane just freezes and has to be killed. This is very confusing for the user. Standard TCP/IP issue. If you're dropping packet, the connecting side has no way whatsoever to know that and a very long timeout will eventually be reached. No problem here. Scanimage at least reports an Error during device I/O. There's no reason why XSane and scanimage would behave differently, except maybe if you tried scanimage after XSane. It'd be nice if you could try it again both way around and track the problem down, if there is any. JB. -- Julien BLACHE - Debian GNU/Linux Developer - [EMAIL PROTECTED] Public key available on http://www.jblache.org - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
