[diald 2.0] Some bugs

Michael Schlenstedt <[email protected]> Sun, 29 Feb 2004 14:59:57 +0100
Newsgroups org.kernel.vger.linux-diald
Message-ID <[email protected]>
Hi!

I just swapped from pppd-DialOnDemand to diald V2.0 (fetched from cvs).
There are some bugs/problems I have had. So maybe it's interested for
somebody?

BTW: Is there still any development-activity? I think it would by very sad if
such a project will die :-( If some testers are needed, please contact me!
Unfortunately my knowledge in C is very bad, so I can't help to develope
directly :-(

My enviroment:

Kernel 2.4.24
Diald 2.0 (fetched from cvs)
net-tools 1.60
route 1.98 (2001-04-15)


1. Compile error

When compiling I got the following error (I got the same error with
version 1.0):

,----
| gcc -g -O2 -DHAVE_CONFIG_H -I. -DDIALD_CONFIG_FILE=\"/etc/diald.conf\"
| -DDIALD_DEFS_FILE=\"/usr/share/diald/diald.defs\"
| -DRUN_PREFIX=\"/var/run\"  -o diald diald.o options.o modem.o filter.o
| slip.o lock.o ppp.o dev.o proxyarp.o fsm.o timer.o parse.o buffer.o
| route.o bufio.o utils.o firewall.o log.o access.o proxy.o proxy_tap.o
| proxy_tun.o proxy_slip.o proxy_dev.o shell.o -lutil -lpam -lnsl -ldl 
| log.o: In function `xstrerror':
| /usr/src/packages/diald/log.c:24: `sys_errlist' is deprecated; use
| `strerror' or `strerror_r' instead
| /usr/src/packages/diald/log.c:23: `sys_nerr' is deprecated; use
| `strerror' or `strerror_r' instead
`----

2. TUN

I use tun as my proxy-device. When starting diald, I got the following
error:

diald[1734]: Using fifo /var/run/diald.fifo
diald[1734]: Proxy device established on interface tun0
diald[1734]: running '/sbin/ifconfig tun0 192.168.99.1 pointopoint
             192.168.99.2 broadcast 0.0.0.0 netmask 255.255.255.255 metric
             1 mtu 1500 up'
diald[1734]: start tun0: SIOCSIFMETRIC: Operation not supported 
diald[1734]: SIGCHLD[1]: pid 1735 system, status 256
diald[1734]: start tun0: Establishing routes for tun0
diald[1734]: running '/sbin/route add 192.168.99.2 netmask 255.255.255.255 
                     metric 1  dev tun0'
diald[1734]: start tun0: route: netmask 00000000 doesn't make sense with host
                         route 
diald[1734]: start tun0: Usage: route [-nNvee] [-FC] [<AF>]           List 
                         kernel routing tables 
diald[1734]: start tun0:        route [-v] [-FC] {add|del|flush} ...  Modify
                                routing table for AF. 
diald[1734]: start tun0:  
diald[1734]: start tun0:        route {-h|--help} [<AF>]              Detailed
                                usage syntax for specified AF. 
diald[1734]: start tun0:        route {-V|--version}                  Display
                                version/author and exit. 

[...]

diald[1734]: SIGCHLD[3]: pid 1737 system, status 1024
diald[1734]: running '/sbin/route add default metric 1  netmask 0.0.0.0 dev tun0'
diald[1734]: SIGCHLD[4]: pid 1738 system, status 0
diald[1734]: Changed snoop device to tun0
diald[1734]: Diald initial setup completed.


3. Reroute from proxy to real interface

Seems that diald 2.0 (and even 0.99 and 1.0) do not know 'reroute'
anymore?

,----
| Feb 29 14:50:52 gandalf diald[1717]: Unknown option 'reroute'
| Feb 29 14:50:52 gandalf diald[1717]: Parsing error. Got token ' ' when
|                                      end of parse was expected.
| Feb 29 14:50:52 gandalf last message repeated 14 times
`----

Bye,
Michael