Hi Brad,
> Mar 9 22:07:34 localhost diald[648]: Unable to open options file
> /etc/diald/standard.filter: No such file or directory
No filter file is loaded. Without a filter no packets can bring up a link.
You probably need to change that line to
include /usr/lib/diald/standard.filter
or copy the standard.filter file into /etc/diald/
If the file really is in /etc/diald then double check permissions and
ownership.
> Mar 9 22:07:34 localhost diald[648]: Unknown option 'reroute'
What version of diald, reroute went away...
> Mar 9 22:07:34 localhost diald[649]: Creating FIFO
> Mar 9 22:07:34 localhost diald[649]: Using fifo /etc/diald/diald.ctl
> Mar 9 22:07:34 localhost modprobe: can't locate module tap0
> Mar 9 22:07:35 localhost modprobe: can't locate module tap1
> Mar 9 22:07:35 localhost modprobe: can't locate module tap2
> Mar 9 22:07:35 localhost modprobe: can't locate module tap3
> Mar 9 22:07:36 localhost modprobe: can't locate module tap4
> Mar 9 22:07:36 localhost modprobe: can't locate module tap5
> Mar 9 22:07:36 localhost modprobe: can't locate module tap6
> Mar 9 22:07:36 localhost modprobe: can't locate module tap7
> Mar 9 22:07:37 localhost modprobe: can't locate module tap8
> Mar 9 22:07:37 localhost modprobe: can't locate module tap9
> Mar 9 22:07:37 localhost modprobe: can't locate module tap10
> Mar 9 22:07:37 localhost modprobe: can't locate module tap11
> Mar 9 22:07:38 localhost modprobe: can't locate module tap12
> Mar 9 22:07:38 localhost modprobe: can't locate module tap13
> Mar 9 22:07:38 localhost modprobe: can't locate module tap14
> Mar 9 22:07:39 localhost modprobe: can't locate module tap15
See the README.ethertap file that came with diald.
> Mar 9 22:07:39 localhost diald[649]: Proxy device established on
> interface sl0
> Mar 9 22:07:39 localhost diald[649]: start sl0: SIOCSIFMETRIC:
> Operation not supported
> Mar 9 22:07:39 localhost diald[649]: start sl0: SIOCDELRT: No such
> process
These 2 annoying messages can be ignored. Setting the metric with the start
interface command used by diald is not supported by kernel 2.2+. Diald
tries to remove any existing default route before creating a new one. You
didn't have one thus the error message.
> Mar 9 22:07:39 localhost diald[649]: Diald initial setup completed.
> Mar 9 22:09:29 localhost gpm[424]: Skipping a data packet (?)
> Mar 9 22:09:29 localhost gpm[424]: Error in protocol
> Mar 9 22:09:30 localhost last message repeated 64 times
> Mar 9 22:11:35 localhost gpm[424]: Skipping a data packet (?)
> Mar 9 22:11:35 localhost gpm[424]: Error in protocol
> Mar 9 22:11:35 localhost last message repeated 64 times
> Mar 9 22:12:25 localhost gpm[424]: Skipping a data packet (?)
> Mar 9 22:12:25 localhost gpm[424]: Error in protocol
> Mar 9 22:12:25 localhost last message repeated 64 times
> Mar 9 22:13:21 localhost gpm[424]: Skipping a data packet (?)
> Mar 9 22:13:21 localhost gpm[424]: Error in protocol
> Mar 9 22:18:16 localhost last message repeated 65 times
> Mar 9 22:18:17 localhost last message repeated 65 times
Make sure modem and mouse are not on the same tty, next make sure they do
not share an interrupt.
Good luck to you,
Lourdes
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
