Bug #2209

Hylafax: clients can't connect to hfaxd

Added by Giacomo Sanchietti almost 8 years ago. Updated almost 8 years ago.

Status:CLOSEDStart date:
Priority:NormalDue date:
Assignee:-% Done:

100%

Category:nethserver-hylafax
Target version:v6.4-beta2
Security class: Resolution:
Affected version:v6.4-beta1 NEEDINFO:No

Description

The hfaxd daemon listen on port 4559. Fax clients can connect to server using a protocol like FTP.

Actually tcp port is closed because it's associated to hylafax key on configuration db.

Solution:
Create a new hfaxd and move access and status properties from hylafax to hfaxd

Workaround:

 config set hfaxd service TCPPort 4559 access private status enabled
 signal-event firewall-adjust
 config delprop hylafax status
 config delprop hylafax access
 config delprop hylafax TCPPort

Associated revisions

Revision 21e43203
Added by Giacomo Sanchietti almost 8 years ago

nethserver-hylafax-migrate: change hylafax key type to 'service'. Refs #2209

Revision 1180304e
Added by Giacomo Sanchietti almost 8 years ago

pam configuration: include password-auth file. Refs #2209

Revision 80a5c45e
Added by Giacomo Sanchietti almost 8 years ago

hosts template: add domain name to local machine records. Refs #2209

History

#1 Updated by Giacomo Sanchietti almost 8 years ago

  • Assignee set to Giacomo Sanchietti

#2 Updated by Giacomo Sanchietti almost 8 years ago

  • Status changed from NEW to TRIAGED
  • % Done changed from 0 to 20

Workaround tested.

#3 Updated by Giacomo Sanchietti almost 8 years ago

  • Status changed from TRIAGED to ON_DEV
  • % Done changed from 20 to 30

#4 Updated by Giacomo Sanchietti almost 8 years ago

  • Status changed from ON_DEV to TRIAGED
  • % Done changed from 30 to 20

#5 Updated by Giacomo Sanchietti almost 8 years ago

  • Status changed from TRIAGED to ON_DEV
  • % Done changed from 20 to 30
  • Resolution set to REJECTED

Actually the defaults on nethserver-hylafax package are correct.
The problem it's generated by migration process.

In the old smeserver-hylafax package, the hylafax key has configuration type. The type must be changed to service during migration process.

#6 Updated by Giacomo Sanchietti almost 8 years ago

  • Status changed from ON_DEV to MODIFIED
  • % Done changed from 30 to 60

#7 Updated by Giacomo Sanchietti almost 8 years ago

  • Status changed from MODIFIED to ON_QA
  • Assignee deleted (Giacomo Sanchietti)
  • % Done changed from 60 to 70
New package in nethserver-testing:
  • nethserver-testing-1.0.2-2.0git21e43203.ns6
Test case
  1. Update nethserver-hylafax package
  2. Modify hylafax key type and simulate a migration (ignore errors about fax directories):
    config settype hylafax configuration
mkdir -p /tmp/t/home/e-smith/db
cp /var/lib/nethserver/db/configuration /tmp/t/home/e-smith/db
/etc/e-smith/events/actions/nethserver-hylafax-migrate migrate /tmp/t
signal-event firewall-adjust
  3. Check hylafax key type is service and port 4559 is open

#8 Updated by Giacomo Sanchietti almost 8 years ago

  • Description updated (diff)

#9 Updated by Giacomo Sanchietti almost 8 years ago

  • Description updated (diff)

#10 Updated by Giacomo Sanchietti almost 8 years ago

  • Status changed from ON_QA to TRIAGED
  • % Done changed from 70 to 20
  • Resolution deleted (REJECTED)

#11 Updated by Giacomo Sanchietti almost 8 years ago

Hylafax doesn't correctly resolve client hostname if client ip address is not contained inside /etc/hosts file with associated FQDN.

Also pam configuration file need to be rewritten to meet NethServer configuration.

#12 Updated by Giacomo Sanchietti almost 8 years ago

  • Status changed from TRIAGED to ON_DEV
  • Assignee set to Giacomo Sanchietti
  • % Done changed from 20 to 30

Fix for nethserver-hosts package:

--- /etc/e-smith/templates/etc/hosts/40hosts_local    2013-06-12 12:24:49.000000000 +0200
+++ /etc/e-smith/templates-custom/etc/hosts/40hosts_local    2013-10-15 15:06:55.810736373 +0200
@@ -18,7 +18,7 @@

     my $Description = $host->prop('Description') || "";
         $OUT .= "# ${Description}\n" if($Description);
-        $OUT .= sprintf "%-18s %s\n", $IpAddress, $host->key;
+        $OUT .= sprintf "%-18s %s\n", $IpAddress, join('.', $host->key, $DomainName);
     }

     $OUT;

#13 Updated by Giacomo Sanchietti almost 8 years ago

  • Status changed from ON_DEV to MODIFIED
  • % Done changed from 30 to 60

#14 Updated by Giacomo Sanchietti almost 8 years ago

  • Status changed from MODIFIED to ON_QA
  • % Done changed from 60 to 70
New packages in nethserver-testing:
  • nethserver-hosts-1.0.4-1.0git80a5c45e.ns6.noarch.rpm
  • nethserver-hylafax-1.0.2-3.0git1180304e.ns6.noarch.rpm

See previously documented test case, try also to connect and view faxes from a client (http://www.yajhfc.de/).
Make sure reverse-dns of client is correct, also disable firewall on client side.

#15 Updated by Giacomo Sanchietti almost 8 years ago

  • Assignee deleted (Giacomo Sanchietti)

#16 Updated by Davide Principi almost 8 years ago

  • Assignee set to Davide Principi

#17 Updated by Davide Principi almost 8 years ago

  • Assignee changed from Davide Principi to Massimo Palazzetti

Test case is verified

Massimo is testing if his client is working properly.

Ignored errors, when migrate action was run:

# /etc/e-smith/events/actions/nethserver-hylafax-migrate migrate /tmp/t
[ERROR] Source /tmp/t//home/e-smith/fax/docs/sent is not a directory!
 at /etc/e-smith/events/actions/nethserver-hylafax-migrate line 64
[ERROR] Source /tmp/t//home/e-smith/fax/docs/received is not a directory!
 at /etc/e-smith/events/actions/nethserver-hylafax-migrate line 65
[ERROR] Source /tmp/t//home/e-smith/fax/docs/sentm is not a directory!
 at /etc/e-smith/events/actions/nethserver-hylafax-migrate line 67
[ERROR] Source /tmp/t/home/e-smith/hylafax/info is not a directory!
 at /etc/e-smith/events/actions/nethserver-hylafax-migrate line 73
[ERROR] Source /tmp/t/home/e-smith/hylafax/recvq is not a directory!
 at /etc/e-smith/events/actions/nethserver-hylafax-migrate line 74

Warning in /var/log/messages:

Oct 17 07:51:10 davidep2 esmith::event[2521]: expanding /var/spool/hylafax/etc/config.nethesis
Oct 17 07:51:10 davidep2 esmith::event[2521]: WARNING in /etc/e-smith/templates//var/spool/hylafax/etc/config.nethesis/15AreaCode: Use of uninitialized value in concatenation (.) or string at /etc/e-smith/templates//var/spool/hylafax/etc/config.nethesis/15AreaCode line 10.
Oct 17 07:51:10 davidep2 esmith::event[2521]: WARNING: Template processing succeeded for //var/spool/hylafax/etc/config.nethesis: 1 fragment generated warnings
Oct 17 07:51:10 davidep2 esmith::event[2521]:  at /etc/e-smith/events/actions/generic_template_expand line 56

#18 Updated by Massimo Palazzetti almost 8 years ago

  • Status changed from ON_QA to VERIFIED
  • % Done changed from 70 to 90

The client works properly now

#19 Updated by Giacomo Sanchietti almost 8 years ago

  • Status changed from VERIFIED to CLOSED
  • Assignee deleted (Massimo Palazzetti)
  • % Done changed from 90 to 100
In nethserver-updates:
  • nethserver-hosts-1.0.5-1.ns6.noarch.rpm
  • nethserver-hylafax-1.0.3-1.ns6.noarch.rpm

Also available in: Atom PDF