From: "Robert Jenkins" <raj@jrw.co.uk>
To: 'Matt Garman' <garman@raw-sewage.net>, linux-diald@vger.kernel.org
Subject: RE: diald slow to be useful...
Date: Thu, 30 May 2002 09:37:17 +0100 [thread overview]
Message-ID: <001d01c207b5$355dcd10$e239832c@jrws2> (raw)
In-Reply-To: <20020509220952.A587@raw-sewage.net>
Hi,
I'm using diald 0.99.4 on a Redhat 7.2 system.
It works perfectly without any patches or messing about, all I've done
is tweak some rules to control how it connects.
It's set to work 'on demand' most of the time, plus a couple of sessions
locked on each day.
If I bring the connection up by starting Internet Explorer on a windows
machine, it's online and working in a few seconds.
I'm using iptables for both NAT & firewall on the machine with diald,
and I've got both ip_dynaddr and routingf enabled.
I seem to remember some time ago (Redhat 5.x ???) that the browser
needed restarting after allowing time for the link to come up, but that
is not
needed with the current setup. I believe that problem was down to how
the kernel routing works & is not due to diald - the only way round it
is a newer kernel.
If you want better control of the connection, try dialmon - I've also
got this on the Windows box & it shows the state of the Diald
connection, amount of traffic, and allows the connection to be forced up
or down if required.
Regards,
Robert Jenkins.
next prev parent reply other threads:[~2002-05-30 8:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-10 3:09 diald slow to be useful Matt Garman
2002-05-10 16:53 ` Mike Jagdis
[not found] ` <"from jaggy"@purplet.demon.co.uk>
2002-05-17 23:50 ` Matt Garman
2002-05-29 9:09 ` Mike Jagdis
2002-05-29 11:18 ` Matt Garman
2002-05-30 11:41 ` Mike Jagdis
2002-05-30 18:24 ` Jonathan Goldblatt
2002-06-27 11:27 ` Bjorn Hammarberg
2002-05-30 8:37 ` Robert Jenkins [this message]
2002-05-30 11:46 ` Mike Jagdis
2002-05-30 13:51 ` Robert Jenkins
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='001d01c207b5$355dcd10$e239832c@jrws2' \
--to=raj@jrw.co.uk \
--cc=garman@raw-sewage.net \
--cc=linux-diald@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.