I'm reasonably similar.
> o RedHat 5.0 with 2.0.32 kernel, no updates applied
5.2 with 2.0.36, but I've been through 5.0/2.0.32 on the way.
> o IPMasq is working correctly
Snap.
> o My internal network is 192.168.0.x
Snap.
> o I use a dynamic IP address from the ISP.
Not any more, but I used to.
> o BIND is configured and running correctly. It has one zone for my internal
> network (overkill. I know:) and caches for the rest of the world.
That's where we differ.
> o Latest diald RPMs from an official RedHat mirror site (0.16.5a)
Mine is compiled from 0.16 plus patch 5.
> When I have had diald configured and running, it seems to take over 45
> seconds to start dialling. Is this normal? The Linux machine is only a
> 486-100 with 32Mb of RAM but it is hardly doing anything.
486-100 recently moved from 16 to 64Mb.
Mine starts dialling pretty much immediately. Can you check nothing is trying
to do a name lookup *during* the dialout process, 'cos that I imagine would
have to time out before dialup completed. Which might take a couple of minutes.
---
Jim Hague - [EMAIL PROTECTED] (Work), [EMAIL PROTECTED] (Play)
Never trust a computer you can't lift.
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
