On Saturday 23 Nov 2002 1:47 pm, John Hasler wrote:
> Dave Selby writes:
> > Unfortunately pppds demand dialling doesnt work very well with dynamic IP
> > addresses alloctaion.
>
> It's working fine here.
>
> > It will dial up but then says it cand find the URL, you click OK,
> > re-request the URL
On Saturday 23 Nov 2002 1:47 pm, John Hasler wrote:
> Dave Selby writes:
> > Unfortunately pppds demand dialling doesnt work very well with dynamic IP
> > addresses alloctaion.
>
> It's working fine here.
>
> > It will dial up but then says it cand find the URL, you click OK,
> > re-request the URL
Dave Selby writes:
> Unfortunately pppds demand dialling doesnt work very well with dynamic IP
> addresses alloctaion.
It's working fine here.
> It will dial up but then says it cand find the URL, you click OK,
> re-request the URL while the link is up and it will work fine. This
> happens every
On Thursday 21 Nov 2002 11:49 pm, John Hasler wrote:
> Dave Selby writes:
> > BUT I cant get diald to work !
>
> Is there some reason why you can't use pppd's demand dialing option? You
> can configure it via pppconfig.
>
> > Any help much appreciated
>
> You haven't given us enough information.
ahh Found out what the problem is
I needed to have the correct /etc/hosts entries!
Ones that were consistent with my /etc/hostname!
Joe
On Fri, 11 Aug 2000, Joseph P Turner wrote:
>
> Hello I'm running diald on this DEbian box and got it to work quite well ,
> but then after a bit more m
Hello I'm running diald on this DEbian box and got it to work quite well ,
but then after a bit more mucking around I managed to stop it working :/
Basically the PAP authentication doens' twork.
I get the followin
ug 12 11:01:35 router chat[8281]: -- got it
Aug 12 11:01:35 router chat[828
On Mon, May 29, 2000 at 09:03:37PM -0700, Kenward Vaughan wrote:
> May 29 20:52:54 kaynjay diald[2221]: start sl0: SIOCSIFMETRIC: Operation not
> supported
> I don't know about the reroute issue, but the SIOCSIFMETRIC error is (to me)
> an obvious problem (seems fatal in its reporting). Is it so
On 29 May 00, at 21:03, Kenward Vaughan wrote:
> Lastly, is it possible to use "pon" to create the connection from diald?
> Seems that that would be the most reasonable way to insure success for us
> neophytes...
>
Hello Ken,
that could be (at least) difficult, because diald needs its special
On Tue, May 30, 2000 at 12:53:08AM +0100, Mark Brown wrote:
> On Mon, May 29, 2000 at 03:14:40PM -0700, Kenward Vaughan wrote:
>
> > May 29 15:03:16 kaynjay diald[915]: keepup parsing error. Got token
> > 'tcp.ssl'. Not a known tcp service port.
...
> The problem is that SSL is not defined in /etc
On Tue, May 30, 2000 at 12:53:08AM +0100, Mark Brown wrote:
> On Mon, May 29, 2000 at 03:14:40PM -0700, Kenward Vaughan wrote:
>
> > May 29 15:03:16 kaynjay diald[915]: keepup parsing error. Got token
> > 'tcp.ssl'. Not a known tcp service port.
...
> The problem is that SSL is not defined in /etc
On Mon, May 29, 2000 at 03:14:40PM -0700, Kenward Vaughan wrote:
> May 29 15:03:16 kaynjay diald[915]: keepup parsing error. Got token
> 'tcp.ssl'. Not a known tcp service port.
> Would someone please clue me in to this? I added a
> diald 120/tcp
> line to my services file due to the message ab
Hi,
I've been beating my head against the wall, it seems. I cannot get this
darned thing to work. I really think I have a script that should work, but
I get the following on trying to start diald:
May 29 15:03:16 kaynjay diald[915]: Unknown option 'reroute'
May 29 15:03:16 kaynjay diald[915]: k
Can someone help me with a diald problem?
I have a full slink install on my "server" and was trying to get diald setup on
it. I have setup the diald.options file to connect using the pon method. It
seems to connect fine, but hangs on makeing the link.
I"ve attached a syslog output of diald and
John Hasler wrote:
> Russell Rademacher writes:
> > What is the main purpose of slip running in the background? What is it
> > supposed to be listening so it can detect the network request packet and
> > then actually start dialing?
>
> Diald creates a SLIP interface, makes it the defaultroute, a
Russell Rademacher writes:
> What is the main purpose of slip running in the background? What is it
> supposed to be listening so it can detect the network request packet and
> then actually start dialing?
Diald creates a SLIP interface, makes it the defaultroute, and connects it
to a pty. Diald
Hello guys. I am still stuck with this diald problems which is getting
nuts. It seems it works fine for everyone else but not here. Basically... I
am on the box itself which have diald installed and I have set the local and
remote hosts at 192.168.0.1 and 192.168.0.2 and set the dial-up
I'm trying to get diald working and am having some problems. I have a
working ppp connection using the pon, poff scripts. I installed diald and
configured the /etd/diald/diald.options file and rebooted to test. It
wouldn't dial my modem. Turned on the debug options in diald to try to
get a hint
On Mon, 07 Jul 1997 13:19:36 PDT Stephen Witt ([EMAIL PROTECTED])
wrote:
> Hi, I'm trying to set diald up at home. I'm using Debian 1.3. My
> network connection is a modem using PPP to my ISP. My ISP
> dynamically assigns both local and remote IP addresses for this
> link. I've been usi
Hi, I'm trying to set diald up at home. I'm using Debian 1.3. My network
connection
is a modem using PPP to my ISP. My ISP dynamically assigns both local and
remote
IP addresses for this link. I've been using PPP manually for some time now, so
have a working connection script. The symptom
On Tue, 21 Jan 1997 18:24:33 +1100 Hamish Moffatt ([EMAIL PROTECTED]
rmit.edu.au) wrote:
> > On Mon, 20 Jan 1997 09:04:55 PST "Kevin Traas" ([EMAIL PROTECTED])
> > wrote:
> >
> > > Should we (or I) talk to someone and get the docs edited slightly and add
> > > a
> > > ", let me repeat, *** YOU
> On Mon, 20 Jan 1997 09:04:55 PST "Kevin Traas" ([EMAIL PROTECTED])
> wrote:
>
> > Should we (or I) talk to someone and get the docs edited slightly and add a
> > ", let me repeat, *** YOU DON'T NEED TO START pppd FROM YOUR DIALD CHAT
> > SCRIPT BECAUSE DIALD STARTS pppd AUTOMATICALLY ONCE THE C
On Mon, 20 Jan 1997 09:04:55 PST "Kevin Traas" ([EMAIL PROTECTED])
wrote:
> > You're starting pppd yourself in the connect script while diald expects
> to start pppd itself. The connect script should just execute the `chat'
> command.
> > Re-read the diald manpage and look in the mail archives,
> > My /etc/diald/diald.options file says
> > "connect "/etc/ppp/startppp-diald"", and that file says
> >
> > "pppd connect "chat -f /etc/ppp/chatscript""
> >
> > which contains my chatscript, and works fine. (I've been dialing
> > for the past few months by running pppd manually.)
>
> You're st
On Sun, 19 Jan 1997, Hamish Moffatt wrote:
>
> My /etc/diald/diald.options file says
> "connect "/etc/ppp/startppp-diald"", and that file says
>
> "pppd connect "chat -f /etc/ppp/chatscript""
>
This is becoming an FAQ. As stated in the doumentation, your chat
script should not start pppd. dia
> On Sun, 19 Jan 1997 18:44:32 +1100 Hamish Moffatt ([EMAIL PROTECTED]
> rmit.edu.au) wrote:
>
> > My /etc/diald/diald.options file says
> > "connect "/etc/ppp/startppp-diald"", and that file says
> >
> > "pppd connect "chat -f /etc/ppp/chatscript""
> >
> > which contains my chatscript, and work
On Sun, 19 Jan 1997 18:44:32 +1100 Hamish Moffatt ([EMAIL PROTECTED]
rmit.edu.au) wrote:
> My /etc/diald/diald.options file says
> "connect "/etc/ppp/startppp-diald"", and that file says
>
> "pppd connect "chat -f /etc/ppp/chatscript""
>
> which contains my chatscript, and works fine. (I've bee
I've been avoiding configuring diald for a while because it's
always looked (from a distance) like hell. Seems to be confirmed
by actually trying it.
I'm running named on diald system, and wish to keep doing so.
My named is configured to forward to other systems, and appears
to do this from non-do
In article <[EMAIL PROTECTED]>, Kevin Traas
<[EMAIL PROTECTED]> wrote:
|| Although things work, I do have some strange messages appearing in
|| /var/log/messages. Although things seem to be working okay, I think
|| they're probably something that should be looked into. Can you "shed any
|| l
quot;get with the
program".
Later,
Kevin Traas
> From: James Martino <[EMAIL PROTECTED]>
> To: Kevin Traas <[EMAIL PROTECTED]>
> Subject: Re: Diald Problems
> Date: Monday, January 13, 1997 6:35 PM
> >
> > So, I'm quite happy in that things are wo
> Jan 13 09:23:15 sally diald[9849]: PPP network layer died, but link did
> not. Probable configuration error.
I've been getting the same error for quite some time. Everything seems to
work, though.
--
John Goerzen | Running Debian GNU/Linux (www.debian.org)
Custom Programming|
[
Kevin Traas wrote:
>
> IT WORKS!!!IT WORKS!!!IT WORKS!!!IT WORKS!!!IT WORKS!!!
> IT WORKS!!!IT WORKS!!!
>
> Sorry Got carried away
>
> Thanks for all of your help, Philippe.
>
> At first, the login failed, but once I increased the timeout for the login
> sequence fr
On Mon, 13 Jan 1997 10:43:02 PST "Kevin Traas" ([EMAIL PROTECTED])
wrote:
> Can I ask you a question on how best to set up DNS in this situation, or
> should I repost (with different subj) to the list?
Will you be running bind locally or not ? If not, I suggest repeating three
times the namese
> From: Philippe Troin <[EMAIL PROTECTED]>
> To: Kevin Traas <[EMAIL PROTECTED]>
> Cc: debian-user@lists.debian.org
> Subject: Re: Diald Problems
> Date: Monday, January 13, 1997 10:38 AM
>
> On Mon, 13 Jan 1997 09:46:18 PST "Kevin Traas" ([EMAIL
On Mon, 13 Jan 1997 09:46:18 PST "Kevin Traas" ([EMAIL PROTECTED])
wrote:
> Although things work, I do have some strange messages appearing in
> /var/log/messages. Although things seem to be working okay, I think
> they're probably something that should be looked into. Can you "shed any
> ligh
From: Orn E. Hansen <[EMAIL PROTECTED]>
To: Kevin Traas <[EMAIL PROTECTED]>
Cc: Philippe Troin <[EMAIL PROTECTED]>; debian-user@lists.debian.org
Subject: Re: More diald problems.
Date: Monday, January 13, 1997 5:11 AM
> I saw your message on the debian mailing list, whe
IT WORKS!!!IT WORKS!!!IT WORKS!!!IT WORKS!!!IT WORKS!!!
IT WORKS!!!IT WORKS!!!
Sorry Got carried away
Thanks for all of your help, Philippe.
At first, the login failed, but once I increased the timeout for the login
sequence from 5 seconds to 15, everything
Hi,
I saw your message on the debian mailing list, where you described your
problem with getting up diald.
Now, what is happening is your 'ppp-up' script. Diald is informing you
in the log, that it doesn't get a return code from this script. It never
returns to diald, so diald thinks tha
This IMHO is not correct. From the diald-man-page:
PPPD OPTIONS
When diald is being used in PPP mode extra options can be
passed on to pppd by specifying them after a "--" on the
command line. This should not normally be necessary as
default options can be placed
On Sun, 12 Jan 1997 16:09:00 PST "Kevin Traas" ([EMAIL PROTECTED])
wrote:
> > So what happens is that pppd is started while diald thinks you're
> connecting... It cannot install the defaultroute too...
>
> Wow! That explains things!
>
> Thanks *so* much for your help! And an answer in only
> From: Philippe Troin <[EMAIL PROTECTED]>
> To: Kevin Traas <[EMAIL PROTECTED]>
> Cc: debian-user@lists.debian.org
> Subject: Re: More diald problems.
> Date: Sunday, January 12, 1997 3:49 PM
>
> Here it is !!!
> Diald starts pppd itself, you don't have
On Sun, 12 Jan 1997 15:29:48 PST "Kevin Traas" ([EMAIL PROTECTED])
wrote:
> As requested, I've included my configuration files throughout the message
> below. I hope this helps in figuring out what my problem is. (I've
> stripped out my username & passwords from the files)
I think I can u
Thanks very much for you help, Philippe.
As requested, I've included my configuration files throughout the message
below. I hope this helps in figuring out what my problem is. (I've
stripped out my username & passwords from the files)
TIA,
Kevin
> > However, NO MATTER WHAT I DO across t
On 12 Jan 1997, James LewisMoss wrote:
> Go to the diald web site and get the patch. It has a bug that once it
> takes ot down once it won't bring it back up. The patch fixes it.
> (Is running fine on my machine)
The new diald site is unreachable right now. Would you mind mailing
the patch.
Da
>
>On Sat, 11 Jan 1997, David Engel wrote:
>
>>
>> I didn't know there was a new version. Thanks. Diald now restores
>> the routes and interfaces to the state they were before the link was
>> brought up. However, diald still won't bring the link back up
>> automatically after it has taken it do
On Sat, 11 Jan 1997, David Engel wrote:
>
> I didn't know there was a new version. Thanks. Diald now restores
> the routes and interfaces to the state they were before the link was
> brought up. However, diald still won't bring the link back up
> automatically after it has taken it down. The
On Sat, 11 Jan 1997 [EMAIL PROTECTED] wrote:
> On Sat, 11 Jan 1997, David Engel wrote:
> > I have a nagging problem with 'defaultroute' that maybe you can help
> > me with. Everytime diald drops the link due to inactivity, it deletes
> > the default route. After that, diald won't bring the link b
On Sat, 11 Jan 1997, David Engel wrote:
>
> I have a nagging problem with 'defaultroute' that maybe you can help
> me with. Everytime diald drops the link due to inactivity, it deletes
> the default route. After that, diald won't bring the link back up for
> non-loopback addresses because there
On 10 Jan 1997, Guy Maor wrote:
> "Kevin Traas" <[EMAIL PROTECTED]> writes:
>
> > 2. From the docs, I thought diald would establish the default route to the
> > gateway automatically. Am I wrong in my assumption? If so, is what I did
> > to "fix" the problem the "right" way to go about it?
>
>
On Fri, 10 Jan 1997 17:49:26 PST "Kevin Traas" ([EMAIL PROTECTED])
wrote:
> Philippe Troin <[EMAIL PROTECTED]> wrote:
> > On Fri, 10 Jan 1997 09:31:43 PST "Kevin Traas" ([EMAIL PROTECTED])
> > wrote:
> Anyways, what I was trying to get across is that the connection process
> works perfectly aft
Thanks a lot for your reply. Here's some answers to your questions:
> From: Philippe Troin <[EMAIL PROTECTED]>
> To: Kevin Traas <[EMAIL PROTECTED]>
> Cc: debian-user@lists.debian.org
> Subject: Re: More diald problems.
> Date: Friday, January 10, 1997 3:04 PM
&
On Fri, 10 Jan 1997 09:31:43 PST "Kevin Traas" ([EMAIL PROTECTED])
wrote:
> 1. Why does diald drop my connection 30 seconds after establishing it,
> even though there are packets being sent across that would normally keep it
> alive. (Note - I can do anything across the connection once establi
"Kevin Traas" <[EMAIL PROTECTED]> writes:
> 2. From the docs, I thought diald would establish the default route to the
> gateway automatically. Am I wrong in my assumption? If so, is what I did
> to "fix" the problem the "right" way to go about it?
The right way is to add `defaultroute' to /et
Just to continue with the problems I'm having with Diald - I'd appreciate
any suggestions/comments about what I've provided below. TIA.
Note: I have "debug 31" enabled for diald.
When I try to ping a remote site, diald "cranks up" the connection to my
ISP; however, the ping never received a re
53 matches
Mail list logo
