[ILUG] dial-up, can't ping

[Conor Daly]

On Tue, Feb 27, 2001 at 04:16:13PM +0000 or thereabouts, Paul J Collins wrote:
> >>>>> "PA" == Paul Askins <paul.askins at analog.com> writes:
> 
>     PA> /etc/diald.conf has the lines
>     PA> local 0.0.0.0
>     PA> remote 0.0.0.0
> 
>     PA> in it.  Could this be problem?  I should probably change the
>     PA> remote one to the eircom ip.
> 
> That's usually shorthand for "use dynamic IPs".
diald.conf should contain the "dynamic" keyword.  You can use any pair of ip
addresses in the conf file though you should probably use *different*
numbers for "local" and "remote" though these may be simple placeholders and
it may not matter a damn.
> 
>     PA> I didn't know that ppp would use diald.conf though (if this is
>     PA> the problem).
> 
> pppd has its own set of config files.  When diald invokes pppd, it
> probably supplies the values given if they are not "0.0.0.0", and
> otherwise lets pppd sort out IP assignment.  (Pure guesswork!)
> 
diald likes to fire up pppd itself *after* doing all the handshaking and
authentication so pppd's configs should be minimal. My /etc/ppp/options
contains "noauth" and nothing else.

One thing I've found when using diald on an ipmasqing gateway is that, on
boot, when diald starts up, the first attempt to connect to the internet
must come from the gateway box.  Any connect attempts from other boxen on
the network are ignored until the gateway has managed to connect by itself
first.  I'm kinda thinking it's a routing thing there too.  I also found I
have to delete the default route (via eth0) on the gateway before starting
diald or its default route (via sl0) doesn't get set or something.

Details available on request.
-- 
Conor Daly 
Met Eireann, Glasnevin Hill, Dublin 9, Ireland
Ph +353 1 8064217 Fax +353 1 8064275
------------------------------------
 11:43pm  up 52 min,  3 users,  load average: 0.00, 0.01, 0.00