I'm currently using diald evrsion 0.99.1 and I'm having trouble with
the debug command. I suspect that if I solve this I'll be able to work
out what is going on with all the other problems I'm having
I'm using diald that came from an rpm off redhat's contrib site.
I was using diald on another client machine (which I no longer have
access to) that came from an rpm. I'm not sure of it's origin, but I
was able to use the debug 31 command to see what triggers were in
effect and what actual filter rule they were due to. I could also send
a customer kill sig (usr1 or usr2 I think) and I was able to dump the
current rule table. This also doesn't work. Can any one tell me what
the differences between version and debugging are and if I'm using the
right version?
My actual problem (which I'm unable to solve as I have no useful
debugging info) is that diald brings up the link when an internal
machine pops email off the server via ethernet (which is the diald
machine also) If I put a specific `ignore tcp.smtp` for source and
dest then pop stops working (I assume because of the sl0 interface not
proxying the packet correctly, or straight out ignoring them).
I'm masquerading with a fairly standard ipchains rulset
Chain forward (policy DENY):
target prot opt source destination ports
MASQ all ------ 192.100.10.0/24 anywhere n/a
Can anyone tell me how I can enable pop3 access internally without
having a pop3 request bring up the link?
Cheers
Alex!
--
Alex Garner <[EMAIL PROTECTED]>
NetCraft Australia
Phone (08) 8370 3650
http://www.netcraft.com.au
...I should have taken the blue pill.
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
