> I compiled diald using 'make' and 'make install'. I create a
> diald.conf file
> using the example for 'leaf node using dynamic local address
> using ppp'.
> This is my diald.conf file:
>
> mode ppp
> connect "/usr/sbin/chat -f /etc/sysconfig/network-scripts/chat-ppp0"
> device /dev/modem
> speed 115200
> modem
> lock
> crtscts
> local 192.168.0.100
> remote 192.168.0.101
> dynamic
> defaultroute
> include /usr/lib/diald/standard/filter
I suspect a typo unless you created a new file :)
I think you want:
include /usr/lib/diald/standard.filter
> debug 0x007F
>
> I started diald from the command-line and my /var/log/messages has the
> following:
>
>
> Aug 28 19:05:33 jakemain diald[858]: Unable to open options
> file /usr/lib/diald/
> standard/filter: No such file or directory
That's right - fixing the typo should take care of this.
> Aug 28 19:05:34 jakemain modprobe: can't locate module tap0
[snip]
RH uses Linux kernel 2.2.x. Follow the instructions in the README.ethertap
file from the diald package:
--
If you build ethertap as a module you need to add lines like:
alias tap0 ethertap
options tap0 -o tap0 unit=0
alias tap1 ethertap
options tap1 -o tap1 unit=1
...
etc.
to your /etc/modules.conf.
--
If you'd rather use slip then turn off tap lookups in conf.modules (or
modules.conf as your distribution prefers).
--
alias tap0 off
alias tap1 off
...
etc.
--
kernels 2.2.x add the following note in Documentation/ethertap.txt, it may
help if you've already done the above and you still see the error messages.
Though to be honest I haven't seen it as necessary unless ethertap support
was built directly into the kernel and not a module. The default kernel
shipped with RH6 includes ethertap support as a module - following this
advice definately won't hurt, but it shouldn't make much difference.
--
First you will have to enable Ethertap in the kernel configuration.
Then you will need to create any number of ethertap device files,
/dev/tap0->/dev/tap15. This is done by the following command.
mknod /dev/tap* c 36 16 ( 17 18 19 20 for tap1,2,3,4...)
** Replace * with the proper tap device number you need. **
--
[snip]
> Aug 28 19:05:38 jakemain diald[859]: start sl0: SIOCSIFMETRIC: Operation
not supported
warning message - can be safely ignored - diald uses a routing command that
includes the metric for the link (highly desired in linux 2.0.x but not
available in linux 2.2.x)
> Aug 28 19:05:38 jakemain diald[859]: Diald initial setup completed.
> At this point, I would expect diald to make a connection if I
> 'ping' or
> display a web page. Instead, nothing.
Actually at this point you can't bring up the link because the file that
tells diald what traffic to handle has not been included. Fixing the typo
above should take care of this.
If changing that line does not work then for testing purposes only replace
that include line in diald.conf with:
accept any 600 any
this should bring up the link for any traffic for 5 minutes. Of course you
really want to use a filter file because of the added power and flexibility.
> Also, using the 'route' command, the command hangs.
Always use 'route -n' for debugging network connections (-n turns off DNS
lookups which can appear to hang the command if any of the addresses cannot
be resolved locally)
HTH,
Lourdes
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
