Hello there,

I am a very satisfied Linux user. I am having bit problem with  diald.

This is the scenario.

I installed the diald-1.16.5a-1.i386.rpm  and
diald-config-0.16.5a-1.i386.rpm. on RH 5.1 (2.0.34)

My /etc/diald.conf file looks like this with default standard.filter file

mode ppp
connect /etc/diald/connect
device /dev/ttyS1
speed 38400
modem
lock
debug 31
crtscts
dynamic
local 192.168.0.1
remote 207.82.134.36 
netmask 255.255.255.0
include /usr/lib/diald/standard.filter


where 207.82.134.36 is my isp router (which does changes frequently)


I have two linux machine one with 192.168.0.1 (server) on eth0 and the
192.168.0.2 on eth0:0 (on alias) as client.

I have the following routing table when the server is booted

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
207.82.134.36   *               255.255.255.255 UH    1      0        2 sl0
192.168.0.0     *               255.255.255.0   U     0      0        5 eth0
127.0.0.0       *               255.0.0.0       U     0      0        6 lo
default         *               0.0.0.0         UG     0      0        1 eth0



My dilad log shows this after every bootup

Oct 29 23:22:11 trisuli diald[328]: Starting diald version 0.16.5
Oct 29 23:22:11 trisuli diald[328]: Proxy device established on interface sl0
Oct 29 23:22:11 trisuli diald[328]: Setting pointopoint route for sl0
Oct 29 23:22:11 trisuli diald[328]: Establishing routes for sl0
Oct 29 23:22:11 trisuli diald[328]: Changed snoop device to sl0
Oct 29 23:22:11 trisuli diald[328]: Diald initial setup completed.

Now, when I type to ping,telnet or www from the client linux box, the
diald
does not even try to dial. I have no cron job for the diald.
But when I execute "diald up" it dials and this is the log message I get.

Oct 29 23:50:09 trisuli diald[488]: filter accepted rule 30 proto 1 len 84 packet 
192.168.0.2,0 => 206.82.134.36,0
Oct 29 23:50:09 trisuli diald[488]: filter accepted rule 12 proto 6 len 265 seq 
5229336a ack 1218af flags  PUSH ACK packet 206.82.134.34,3128 => 206.82.134.43,1060
Oct 29 23:50:10 trisuli diald[488]: filter accepted rule 30 proto 1 len 84 packet 
192.168.0.2,0 => 206.82.134.36,0
Oct 29 23:50:41 trisuli last message repeated 31 times
Oct 29 23:50:52 trisuli last message repeated 11 times
Oct 29 23:50:53 trisuli diald[488]: filter accepted rule 30 proto 1 len 84 packet 
192.168.0.2,0 => 206.82.134.36,0
Oct 29 23:51:24 trisuli last message repeated 31 times
Oct 29 23:52:09 trisuli last message repeated 45 times
Oct 29 23:52:10 trisuli diald[488]: filter accepted rule 12 proto 6 len 265 seq 
5229336a ack 1218af flags  PUSH ACK packet 206.82.134.34,3128 => 206.82.134.43,1060
Oct 29 23:52:10 trisuli diald[488]: filter accepted rule 30 proto 1 len 84 packet 
192.168.0.2,0 => 206.82.134.36,0
Oct 30 00:00:27 trisuli diald[488]: Delaying 30 seconds before clear to dial.

Now, I don't understand why it never disonnects after a certain time
when there is no activities on the interface and
if I manually disconnect then its retries to connect to my isp every 30
seconds with no apparent reason. I don't have netbios running in my
server.


Any suppestion is highly appreciated.



TIA.

Jas

-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]

Reply via email to