Bug#505130: [xsane] freezes if only port 6566 is reachable

2008-11-17 Thread Julien BLACHE
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

Bug#505130: [xsane] freezes if only port 6566 is reachable

2008-11-16 Thread Simon Wenner
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

Bug#505130: [xsane] freezes if only port 6566 is reachable

2008-11-09 Thread Simon Wenner
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

Bug#505130: [xsane] freezes if only port 6566 is reachable

2008-11-09 Thread Julien BLACHE
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