The documentation for diald 0.99.1 states that any buffered packets are sent back through the kernel for firewall processing when the link comes up with a dynamic address. I tried to test this with: ipchains -A input -j ACCEPT -l ipchains -A output -j ACCEPT -l ipchains -A forward -j ACCEPT -l so that all packets going through the kernel get logged. So I try to make a connection, and while I see the SYN packets going to the proxy, I don't see the them when they are retransmitted through the kernel by diald ( or should I be seeing them at all? ). Where am I going wrong? 1) I'm a newbie to ipchains so am I doing something wrong there? 2) Is there something in the Linux kernel preventing me from doing this? 3) Is it related to these error messages showing up in the log? modprobe: can't locate module tap0 modprobe: can't locate module tap1 . . . modprobe: can't locate module tap15 diald[24467]: start sl0: SIOCSIFMETRIC: Operation not supported . . . diald[24467]: start ppp0: SIOCSIFMETRIC: Operation not supported Here is what diald.conf looks like: # Beginning of diald.conf mode ppp connect "/usr/sbin/chat -f /etc/diald/connect" device /dev/ttyS0 speed 115200 modem lock crtscts local 192.168.0.1 remote 134.67.40.149 dynamic stop-dial-timeout 20 buffer-packets defaultroute redial-timeout 30 include /usr/lib/diald/standard.filter pppd-options name mvs # End of diald.conf BTW, diald works wonderfully in all other aspects. Those errors seem to indicate that I'm missing a few drivers. Well that was a mouthful! Write me back for any clarification you might need. I am running Mandrake 6.0 with Linux 2.2.9 Thanks for everything, especially if you made it to the bottom of this message :-) Mark - To unsubscribe from this list: send the line "unsubscribe linux-diald" in the body of a message to [EMAIL PROTECTED]
