Bug 818494

Summary: hylafax: No faxing over the network since upgrade from 12.2
Product: [openSUSE] openSUSE Tumbleweed Reporter: Axel Braun <axel.braun>
Component: BasesystemAssignee: E-mail List <bnc-team-screening>
Status: RESOLVED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P3 - Medium    
Version: 13.1 Milestone 0   
Target Milestone: 13.1 Milestone 0   
Hardware: i686   
OS: openSUSE 12.3   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Axel Braun 2013-05-04 06:45:40 UTC
User-Agent:       Mozilla/5.0 (X11; Linux i686; rv:20.0) Gecko/20100101 Firefox/20.0

I use hylafax in a local network since several years. 
/var/spool/fax/etc/hosts.hfaxd contains the lines

localhost
127.0.0.1
192.168.2.*
*.mydomain.internal

which should allow all hosts in the local network faxing.
Since upgrade to 12.3 this does not work any longer:
When I send a fax out of the 192.168.2.* network, it is not accepted any longer:

southpole HylaFAX[11342]: checkHostIdentity("localhost")
southpole HylaFAX[11342]: <--- 130 Warning, client address "192.168.2.101" is 
not listed for host name "localhost".
southpole HylaFAX[11342]: Parsing hostPort(): "EPRT"
southpole HylaFAX[11342]: Parsing "|1|192.168.2.101|38849|"
southpole HylaFAX[11342]:  `-> s.length() = 23
southpole HylaFAX[11342]:  `-> s[0] = '|'
southpole HylaFAX[11342]:  `-> s[2] = '|'
southpole HylaFAX[11342]:  `-> s[22] = '|'
southpole HylaFAX[11342]: Looks like extended syntax: "|1|192.168.2.101|
38849|" [7C: |]
southpole HylaFAX[11342]: `-> Got a: 192.168.2.101[17]
southpole HylaFAX[11342]: `-> Got a: 38849[23]
southpole HylaFAX[11342]: Parsed: Family 1 Address 192.168.2.101 Port 38849
southpole HylaFAX[11342]: Filesystem has SysV-style file creation semantics.

The server checks the network address in its own localhost. hosts.hfaxd is ignored.

Reproducible: Always

Steps to Reproduce:
1. see above
2.
3.
Comment 1 Philipp Thomas 2013-06-05 10:00:08 UTC
Please report this on the upstream hylafax list. See http://www.hylafax.org/content/Mailing_Lists for info. When you've done so please post the URL for the upstream report in the bug entry.
Comment 2 Axel Braun 2013-10-09 08:48:08 UTC
Actually, I tried to get a response from the mailing list, but was not succesful.
Did you actually thought about switching to hylafax+ ?
https://build.opensuse.org/package/show/home:DocB/hylafax+
Comment 3 Philipp Thomas 2013-11-26 15:08:36 UTC
Would you be willing to take over maintainership for openSUSE? I only took over the package because its former maintainer had left SUSE. As I don't use hylafax myself I would be more than willing to hand over the package. In that case you'd also be free to switch over to hylafax+ ;-)
Comment 4 Philipp Thomas 2013-11-29 15:56:30 UTC
Now that we're going to switch to hylafax+ anyways I'm closing this bug.
Comment 5 Axel Braun 2014-02-09 11:53:36 UTC
After some investigation I have found the solution: The Firewall on the client is causing the problem. Obviously the server is initiating a data transfer from the client, which is blocked by the clients FW.

Adding a 'user-defined rule' like allowing all traffic from 192.168.2.0/24 to the clients FW solves the problem.