Hi Everyone,
I know I've been away for a while.
I recently encountered something strange with macro.SANE. I relocated
the scanner in my office (actually a MFP) away from my desk. It sits
next to the machine which is my router/gateway (and which runs
Shorewall). Setting up network printing (via CUPS) was straighforward.
However, setting up scanning to work over the network proved
troublesome.
In the end I figured out that even with a SANE/ACCEPT rule that somehow
connection tracking wasn't working (based on the presence of "reject"
messages in syslog where I correlated the DPT with the port on which a
saned was spawned and listening). Today I made another attempt on it and
it seems that the way the macro is written, the connection tracking
helper does not get loaded:
?if ( __CT_TARGET && ! $AUTOHELPERS && __SANE_HELPER )
PARAM - - tcp 6566 { helper=sane }
?else
PARAM - - tcp 6566
?endif
When I restart Shorewall, the output of 'lsmod | sane' showed
nf_conntrack_sane with a reference count of 0. Xsane on my workstation
recognized the scanner and I could hit "Acquire preview" and it would
begin the preview scan process, but then hang. Every single time.
However, after copying macro.SANE from /usr/share/shorewall to
/etc/shorewall and replacing the above with this:
PARAM - - tcp 6566 { helper=sane }
Then a restart of shorewall and voilà, 'lsmod | sane' showed
nf_conntrack_sane with a reference count of 2.
After making this change, scanning started to work perfectly.
The odd thing is that I know I have other helpers working correctly. I
have AUTOHELPERS=Yes in /etc/shorewall/shorewall.conf and things like
FTP work as expected.
I'm wondering if anyone might have an idea of what is going with this.
Regards,
-Roberto
--
Roberto C. Sánchez
http://people.connexer.com/~roberto
http://www.connexer.com
_______________________________________________
Shorewall-users mailing list
Shorewall-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shorewall-users
