Greetings,
I've had the opportunity to look through the archive to try to find
something similar to my problem. Mostly I see problems relating to diald
bringing the connection up too frequenlty. I've got the opposite problem.
I've managed to get all set up with a stable ppp and masquerading setup
which I'm able to share with a win95 and mac client.
I can manually bring ppp up and down at will. I've installed what I
understand to be the current diald-version. Got it in rpm form from red-had
contrib area (diald-0.16.5a-1.i386.rpm)--also diald-config of the same version.
Running Redhad 5.0 setup with a recently upgraded kernel (2.0.35). I've had
ip networking up for about 3 months without problem. I am also running
Samba, but my problems don't seem affected by running without samba.
Problem: I can fire up diald after a fresh reboot, and it works like a
champ...connects and disconnects as it should. However, I have yet to get
it to connect twice. Frequently I'm getting a message approximately 2 mins
(1:57 to be exact) after diald brings down the ppp connection that the 'ppp
line dicipline successfully unregistered.'
The only way that I can get diald to initiate a connection again is to
reboot my Linux system, and then restart diald.
A couple of things I've noticed:
- My net configuration right now sets up a default route to my ethernet card
on my host. Before I run diald or manually run ppp, I drop this route by
entering 'route del default'.
- When diald brings down the ppp connection, ppp reports in
/var/log/messages that it has been killed with a signal 2. When I bring
down a manual ppp connection, ppp reports dying with a signal 15.
- I've noted in the archive that using /dev/modem can cause some permission
problems, so I'm now using /dev/ttyS1.
- I understand that one must echo the value 1 to ip_dynaddr in the proc
tree. I've seen it referred to as 'echo 1 > /proc/...' and 'echo '1' >
/proc/...'. I've tried both ways.
- Also note that I am using a stripped down ppp options file with diald: it
includes only a 'name' line and a 'debug' line.
- The way my pppd set-up is configured, when a ppp connection is initiated,
my resolv.conf file is replaced with one which references my ISP's
nameservers, and an instance of named is started as a cacheing name server.
When the ppp connection comes down, named is shut down and resolv.conf is
replaced with a local version referencing only my local host.
-I'm using an out of the box 'standard.filter' file, although I've also
tried a 'phone.filter' that came with the config files. Again-- didn't help
my problem.
- Finally, because the rather late notice of unregistration of ppp line
mentioned above, I've gotten the feeling that there's something not getting
released or unlocked, so for kicks I remove the 'lock' line from my
diald.conf file...unfortunately to no avail.
Again, I'm able to bring up and take down ppp manually as many times as I
like. But after one diald-sponsored ppp connection, I cannot connect again
though diald. Even if I restart diald, no joy. I have to reboot, restart
diald, and then I got one shot again. I'm gaining great knowledge about the
whole boot process--I've watched it happen over and over and over....
Thanks for help in advance. For anyone considering diald, I can say this
much... when inet, routed, named, masquerading, ppp, chat and diald are all
working properly, and diald brings up a connection, it is truly a beautiful
thing to behold...in my case rare, but still quite beautiful.
Sorry to be so longwinded. As I'm not a big-time Linux guru (a monkey could
load the RedHat package), there could well be some minor system
configuration trick that I've missed that's resulting in this problem.
Since you've gotten this far in my message, please indulge me for one more
moment: Linux rocks!!!!! Thanks to all who make it possible!
Barrett Morris
-----------------
Barrett Morris
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
