I have been a long time and avid user of diald and have run 0.16.5 for
sometime on a system with a 2.0.36 kernel. Recently with the new diald
0.9 series, I looked forward to the new updates. I have had minor
compilation problems with all versions put have resolved those. When I
run diald version 0.982 on an existing working system by simply
replacing the 0.16.5 daemon everything works fine. Recently, I stepped
up to diald 0.99 and found that in the same case substituting the new
diald daemon broke internal routing while the link was up. Then I went
back and compiled 0.983 which I originally skipped and found it had the
exact same behavior. It appears that something between 0.982 and 0.983
broke internal routing at least on 2.0.36 kernels.
Here is the detailed behavior: I use the typical 192.168.1.x internal
net over eth0 with masquerading to the Internet on a ppp dialup link
through diald. The system running diald is 192.168.1.1 and it can ping
any 192.168.1.x machine on my local network while the 0.983 or 0.99
diald is running, but not connected to the Internet. When I bring the
link up, I can now ping out to sites on the Internet from the system
running diald, but I can no longer ping any of the machines on my local
network nor can they ping me or the Internet. Take the link down, and
everything returns to normal. This can be repeated with the same
behavior. up broke, down ok
The routing table looks fine in all instances, nothing unusual. Again
this is a working environment where the only difference is which version
of diald I run.
If anyone has any ideas, I would appreciate it.
Dave Straitiff
Syrinex Communications
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
