Mailinglist Archive: opensuse (1377 mails)

[Anthony.Schlemmer@xxxxxxx (Anthony Schlemmer)]

Brian Armstrong wrote:
> 
> Hello Tony,
> 
> What I'm trying to grasp is how diald is actually making the call? I went
> back through the files diald.conf and connect and am beginning to understand
> somewhat how these are configured. It seems that once diald initializes the
> diald file it will call connect and then progress from there. However, how
> do I get diald to actually try to make the call? Can I force it?
> 
> How do I get it do dial-on-demand?
> 
> Thanks.
> 
> Brian Armstrong.
> 
>

[snip]

You need to have "diald" running and if you have configured it
correctly, any packets going outside your localhost should cause it to
dial using the specified "connect" script. Did you look at the
configuration files I emailed you? Those are what I'm using and they
were taken from from "/usr/doc/packages/diald/config" directory and
modified just slightly. A diff against the files I supplied and what I
mailed you should show you exactly what I changed. 

I'm certain I only changed the "diald.conf" file to include all of my
pppd setup information. I did make one tweak to the rule which
determines how long the link stays up after an HTTP request goes
through. The stock file has like 120 seconds and that's way too short as
I pause and read pages and such. My modem would be dialing out all of
the time as the link would go down way too often. I modified it so HTTP
requests keep the link up for 600 seconds (10 minutes) which is much
more reasonable.

I'm not sure how much more help I can be to you. I don't think I
supplied my firewall rule files in that tar file bundle I sent you but
they're aren't really needed unless you're using your Linux box as a
gateway to the internet and plan to use IP masquerading.

Tony


-- 
Anthony.Schlemmer@xxxxxxx
-
To get out of this list, please send email to majordomo@xxxxxxxx with
this text in its body: unsubscribe suse-linux-e