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
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
18 matches
Mail list logo
