I'm not quite sure what the filters and such do, I think they monitor various
tcp/udp ports to see if there is traffict, and if so where it is going.  It
will then set an idle time for disconnection (I think..)  I only had to change
standard.filter in the first filter line, because it would disconnect me after
about 2.2 milliseconds of idle time.  I just commented the line out. (#accept
tcp 15 tcp.syn)  If you want, you can just increase the time, but I didn't as
my ISP has a 10 minute idle limit anyway.
Here is what my /etc/diald.conf file looks like:

mode ppp
fifo /etc/diald/diald.ctl
connect /usr/sbin/ppp-on
disconnect /usr/sbin/ppp-off
device /dev/modem
speed 115200
modem
lock
crtscts
local 192.168.0.253
remote 192.168.0.254
dynamic
defaultroute
include /usr/lib/diald/standard.filter

That is almost straight out of the man file.  Check it out to see what all the
options are.  Like I said, I didn't have to do anything special for my masq'd
boxen (as is mentioned in README.masq in the diald source dir), except add some
entries in /etc/hosts.  But I don't use the "ipfwadm -M" option either.  I'm
not sure if that has anything to do with it though.
On my Slackware box, I just edit my startup scripts in /etc/rc.d.  I made my
own rc.net file to startup my masq network as well as load diald.  You might
have something like "rc.local" that you can use instead of making a new file.
The entry I put in that file is "/usr/sbin/diald".  Nothin' to it.
Hope that helps, and good luck.

- Matt.

"Adams, James" wrote:

> Thanks for responding. Perhaps it's a case of running out of patience, but I
> have not had much luck with diald at all. What do the filters do? Is there
> anything that needs to be configured there. Also what does a sample diald
> conf file look like? and one more, if it is a daemon how do you get it to
> run on boot? Thanks.
>
>                                                                         Jim
> Adams
>                                                                 Please
> respond to [EMAIL PROTECTED]
>
> On Monday, June 14, 1999 3:46 PM, kidlinux [SMTP:[EMAIL PROTECTED]] wrote:
> > "Adams, James" wrote:
> >
> > > Maybe a stupid one. If all that you want to do is to automatically
> > > initiate
> > > a dial-up connection when a
> > > connection to the internet is required, would demand dialing be just
> > > as
> > > effective? I have a small network at home with 3 boxes connected to
> > > the main
> > > Linux box. Will demand dialing work in this case or will I still have
> > > to
> > > work through my frustration with diald? Any help anyone would care to
> > > offer
> > > to this neophyte would be appreciated.
> > >
> > >
> > > -
> > > To unsubscribe from this list: send the line "unsubscribe linux-
> > > diald" in
> > > the body of a message to [EMAIL PROTECTED]
> >
> > Demand dialing (with pppd, I assume) would work.  However, unless you've
> > got a
> > static IP, it may not be any easier to set up than diald.  The pppd man
> > file
> > says
> >
> > "... the use of demand dialling with peers that do dynamic IP address
> > assignment is not recommended."
> >
> > I've spoken to someone who claims to have done it, and I tried it
> > because diald
> > sounded difficult to setup with IP Masquerading.  Once I read that line
> > in the
> > pppd man file, I went back to diald and found it easy to setup with my
> > masq'd
> > machines (all I had to do was add hostnames in /etc/hosts on each box
> > and make
> > a small /etc/diald.conf file).
> >
> > - Matt.
> >
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-diald"
> > in
> > the body of a message to [EMAIL PROTECTED]


-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]

Reply via email to