Re: [hylafax-users] Can hylafax work with port 21 instead of 4559 ?

[Robert Bauer <rbauer@xxxxxxxxxxxxxxxxx>]

If I remember correctly, only processes running as root can open ports below 1024.  It looks like hfaxd is running as user uucp.

Robert Bauer
Snow Enterprises
(336) 623-7772 ext. 307

Guilherme Cardoso Lopes wrote:

I've tried that and hfaxd is running with the '-i 21' option but
netstat doesn't
show any use of door 21. I've also tried with two different scenarios: Using
another 'important' port and using an unused port. For the fist case I used
http port 80 and for the second case I used port 17000. In the fist case the
result was similar to using port 21. Using port 17000 worked alright.
There was no server software using any of the ports at the time of the
tests so
I'm guessing that may be a SuSE Linux internal restriction of the port use.


Here are the results of some tests:
------------------------------------
fax:/etc/init.d # ps  auxw | grep hfax[d]
uucp      7251  0.1  0.1   4516  1364 ?        Ss   17:28   0:00
/usr/local/sbin/hfaxd -i 21
------------------------------------
fax:/etc/init.d # netstat -atnp | grep :21
fax:/etc/init.d #
( This means nothing is listed. In fact, see below)
-------------------------------------
fax:/etc/init.d # netstat -atnp
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State      
PID/Program name
tcp        0      0 0.0.0.0:139             0.0.0.0:*               LISTEN     
6578/smbd
tcp        0      0 0.0.0.0:111             0.0.0.0:*               LISTEN     
5467/portmap
tcp        0      0 0.0.0.0:631             0.0.0.0:*               LISTEN     
6091/cupsd
tcp        0      0 127.0.0.1:25            0.0.0.0:*               LISTEN     
5765/master
tcp        0      0 0.0.0.0:445             0.0.0.0:*               LISTEN     
6578/smbd
tcp        0      0 :::22                   :::*                    LISTEN     
5583/sshd
tcp        0      0 ::1:25                  :::*                    LISTEN     
5765/master
tcp        0    240 192.168.65.157:22       192.168.65.141:3400     ESTABLISHED
7192/3
tcp        0      0 192.168.65.157:22       192.168.65.227:1519     ESTABLISHED
7119/2
----------------------------------------
(on a remote computer)
remote:~ # telnet 192.168.65.157 21
Trying 192.168.65.157...
telnet: connect to address 192.168.65.157: Connection refused
remote:~ #
(same thing happens with port 80 but enters normally with 4559 and 17000)
----------------------------------------



Quoting Giuseppe Sacco <eppesuig@xxxxxxxxxx>:

  

Il giorno lun, 06/02/2006 alle 11.07 +0000, Guilherme Cardoso Lopes ha
scritto:
    

Yes, I've tried that and too. I replaced the FAXPORT variable value in my
etc/init-d/hylafax with 21. That makes hylafax to run the hfadx
daemon with -i
21. I've also tried to do that after the hylafax statup and the result is
always the same: Hylafax start's up ok but remote access is denied
contrary to
what happened with using port 4559.
No ftp service is running on the machine though my linux skills are rather
mediocre and I may be missing something obvious...
      

[...]

Check if any other program is listening on that port: «netstat -atnp |
grep :21». Check if hfaxd is really running with correct parameters: «ps
auxw | grep hfax[d]»

Bye,
Giuseppe


____________________ HylaFAX(tm) Users Mailing List _______________________
 To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null
 *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*

    

____________________ HylaFAX(tm) Users Mailing List _______________________
  To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
 On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null
  *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*