Re: FW: [SLUG] hylafax

2006-03-14 Thread Keith Hopkins

Phill O'Flynn wrote:


Apparently the problem lies in the ip_tables.config

 


Hylafax seems to work if I do this:

  modprobe ip_conntrack

  modeprobe ip_conntrack ports=21,4559

  modeprobe ip_nat_ftp ports=21,4559

but this does not persist across reboots.

 


How do I do this?

 

For a 2.6 kernel, and I know this works in SuSE 9/10, modify 
/etc/modprobe.conf.local and add options lines like:

options   ip_conntrackports=21,4559
options   ip_nat_ftpports=21,4559

You might need to `depmod -a` to make this have effect.  The next time 
you insert these modules (modprobe or insmod), it will use these port 
values.


--Keith

--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html


Re: FW: [SLUG] hylafax

2006-03-13 Thread Bret Comstock Waldow
On Mon, 13 Mar 2006 23:35, Phill O'Flynn wrote:

 Hylafax seems to work if I do this:

 but this does not persist across reboots.

 How do I do this?

Tell your system to do it every time it starts up.

Tell us your distro (name  version) and we can tell you how to do that if you 
don't know.

Cheers,
Bret


pgpzu4rvcvh8h.pgp
Description: PGP signature
-- 
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html

Re: FW: [SLUG] hylafax

2006-03-13 Thread Matthew Hannigan
On Tue, Mar 14, 2006 at 02:04:46PM +1100, Phill O'Flynn wrote:
 
 I have had a look at /etc/sysconfig/iptables-config but not sure what to put
 in it.

The first comments in that file are a little short, but 
they summarise what's required pretty well:

# Load additional iptables modules (nat helpers)
#   Default: -none-
# Space separated list of nat helpers (e.g. 'ip_nat_ftp ip_nat_irc'), 
which
# are loaded after the firewall rules are applied. Options for the 
helpers are
# stored in /etc/modprobe.conf.
IPTABLES_MODULES=

So in your case that var would be

IPTABLES_MODULES=ip_conntrack ip_nat_ftp

 
 I tried 
 ...
 /etc/modprobe.conf.local and add options lines like:
 options   ip_conntrackports=21,4559
 options   ip_nat_ftpports=21,4559 ..

Yeah I dunno about /etc/modprobe.conf.local; I'd just put those
lines in /etc/modprobe.conf

 as suggested by Keith but I only had modprobe.conf. So after editing the
 file and rebooting the firewall was still blocking the transmission from the
 hylafax client. Does this file get processed on boot

You should be able to do

/sbin/service iptables restart

to get it working after the previous config changes,
but by all means do a reboot to satisfy yourself
that it still works after a reboot.


Matt
--
must get myself one of those sig things sometime

-- 
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html


Re: FW: [SLUG] hylafax

2006-03-13 Thread Matthew Hannigan
On Tue, Mar 14, 2006 at 02:50:41PM +1100, Phill O'Flynn wrote:
 DOH!!! I didn't see that but I am still getting
 
   [EMAIL PROTECTED] ~]# /sbin/service iptables restart
   Flushing firewall rules:   [  OK  ]
   Setting chains to policy ACCEPT: filter[  OK  ]
   Unloading iptables modules:[  OK  ]
   Applying iptables firewall rules: iptables-restore: line 36 failed
[FAILED]

I guess you have something funky on line 36 of /etc/sysconfig/iptables.

It also looks like you have iptables save and restore on stop/start.

Mine doesn't; I explicitly maintain /etc/sysconfig/iptables under
version control.

Whether it saves/restores or not seems to be another option in
/etc/sysconfig/iptables-config.  I suggest you set

IPTABLES_SAVE_ON_STOP=no
IPTABLES_SAVE_ON_RESTART=no

as well.

You can send your /etc/sysconfig/iptables file to me privately
if you want and I'll give it a butchers.


Matt




-- 
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html


Re: FW: [SLUG] hylafax

2006-03-12 Thread Billy Kwong
Hi Phil,

I used to setup HylaFAX with WHFC, eons ago.
http://www.uli-eckhardt.de/whfc/

As I recall, WHFC just worked straight out of the box, as long as you tell WHFC where HylaFAX lives.

Looks like WHFC is still being maintained.

BillOn 12/03/06, Phill O'Flynn [EMAIL PROTECTED] wrote:
I am having trouble sending a fax from a windows client (winprint hylafax)and I can't figure out whyI can send a fax from the linux box ok. I can also telnet the server andport and connect successfully
On the windows machine the client does everything it's supposed to until thedocument hits the print spooler which is where everything seems to stop.Is there a log file to check to see if the linux box is blocking the
transmission?I have tried by disabling the windows firewall but I still get the sameresponseRegards,Phill O'Flynn-Original Message-From: David Kempe [mailto:
[EMAIL PROTECTED]]Sent: Sunday, 12 March 2006 10:29 PMTo: Phill O'FlynnCc: slug@slug.org.auSubject: Re: [SLUG] hylafaxPhill O'Flynn wrote: Has anyone had experience with configuring hylafax with a windows client.
 Some help would be greatly appreciated right nowI've had a bit of experience, but you need to ask a more specificquestion... are you using whfc or one of the new ones?dave--SLUG - Sydney Linux User's Group Mailing List - 
http://slug.org.au/Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
-- 
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html

Re: FW: [SLUG] hylafax

2006-03-12 Thread Richard




I used this howto when I setup hylafax for a windows laptop.

http://brneurosci.org/linuxsetup24.html

On Sun, 2006-03-12 at 22:40 +1100, Phill O'Flynn wrote:


I am having trouble sending a fax from a windows client (winprint hylafax)
and I can't figure out why

I can send a fax from the linux box ok. I can also telnet the server and
port and connect successfully

On the windows machine the client does everything it's supposed to until the
document hits the print spooler which is where everything seems to stop.

Is there a log file to check to see if the linux box is blocking the
transmission?

I have tried by disabling the windows firewall but I still get the same
response


Regards, 
Phill O'Flynn







Don't worry it's not a bug, it's a feature.





-- 
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html