[hylafax-users] One more... this one may be unsolveable...

[Karl Denninger <karl@xxxxxxxxxxxxx>]

Ok, one final niggle..... well, maybe more than a niggle.

I have my HylaFax server running on FreeBSD, and its ports are protected 
with ipfw.  Only a limited number of ports are open - 4559 is for HylaFax.

I also have my FTP server open (regular FTP) and it works in "passive" mode.

But - Hylafax does not, even if I try to turn it on in WHFC.

It refuses to connect and times out - what I'm getting in the firewall 
debug log looks like this:

Oct 21 00:07:48 FS kernel: ipfw: 14000 Deny TCP 208.54.94.101:51619 
70.169.168.7:52884 in via fxp0
Oct 21 00:07:57 FS last message repeated 2 times

Where "70.169.168.7" is my machine's (the server) address.

With passive turned OFF it does all sorts of "wrong" things (the other 
end is behind a NAT gateway when "roaming", so that definitely wouldn't 
work!)

But with PASV on isn't this problem supposed to be avoided?

It appears that Hylafax basically needs all ports open (!) inbound in 
order to work.....  the port number in the above appears to be randomly 
chosen.

--
Karl Denninger (karl@xxxxxxxxxxxxx)
http://www.denninger.net



%SPAMBLOCK-SYS: Matched [@hylafax.org], message ok


____________________ 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*