Re: Strange PPP problem

1999-01-02 Thread Nathan E Norman
On Sat, 2 Jan 1999, Akop Pogosian wrote:

[ snip ]

 : > > Dec 31 04:39:49 debian icmplogd: destination unreachable from
 : > > [209.44.32.73]
 : 
 : I have no idea what that IP address is. It just starts pinging me once I
 : establish a ppp session.

Here's who to ask if you want to find out:

bohr:/var/named/pri $ nslookup 209.44.32.73
Server:  localhost
Address:  127.0.0.1

*** localhost can't find 209.44.32.73: Non-existent host/domain
bohr:/var/named/pri $ whois -h rs.arin.net 209.44.32
Savvis Communications Corp (NETBLK-SAVVIS2)
    Bonhomme Suite 1000
   St. Louis, MO 63105

   Netname: SAVVIS2
   Netblock: 209.44.0.0 - 209.44.63.255
   Maintainer: SAVV

   Coordinator:
  Zimmerman, Gary  (GZ84-ARIN)  [EMAIL PROTECTED]
  314.719.2423

   Domain System inverse mapping provided by:

   NS1.SAVVIS.NET   209.16.211.42
   NS2.SAVVIS.NET   204.194.10.206

   ADDRESSES WITHIN THIS BLOCK ARE NON-PORTABLE

   Record last updated on 11-Feb-98.
   Database last updated on 1-Jan-99 16:11:45 EDT.

The ARIN Registration Services Host contains ONLY Internet
Network Information: Networks, ASN's, and related POC's.
Please use the whois server at rs.internic.net for DOMAIN related
Information and nic.mil for NIPRNET Information.


--
Nathan Norman
MidcoNet  410 South Phillips Avenue  Sioux Falls, SD
mailto:[EMAIL PROTECTED]   http://www.midco.net
finger [EMAIL PROTECTED] for PGP Key: (0xA33B86E9)



Re: Strange PPP problem

1999-01-02 Thread Akop Pogosian


On 1 Jan 1999 [EMAIL PROTECTED] wrote:

Thank you for responce. I looked at old usenet archives and ppp-howto. It
looks like I have a routing problem, either on my side or on the server
side. I can talk to the dial-up server but no other hosts, even the DNS
servers are unreachable. This is what I have accomplished so far...

> > pppd options :
> 
> > -detach
>   ^^^
> 
> Why do you have this in your /etc/pppd/options?  It is not usually useful.
> 
> > routing table (after establishing ppp connection):
> 
> Looks normal.
> 
> > Dec 31 04:39:49 debian icmplogd: destination unreachable from
> > [209.44.32.73]

I have no idea what that IP address is. It just starts pinging me once I
establish a ppp session.
> 
> I don't understand where this is coming from.  What do your /etc/hosts and
> /etc/resolv.conf look like?

[EMAIL PROTECTED]:~$ cat /etc/hosts
127.0.0.1   debian  localhost
[EMAIL PROTECTED]:~$ cat /etc/resolv.conf
nameserver 109.144.16.5
nameserver 109.144.16.7


> -- 
> John HaslerThis posting is in the public domain.
> [EMAIL PROTECTED]Do with it what you will.
> Dancing Horse Hill Make money from it if you can; I don't mind.
> Elmwood, Wisconsin Do not send email advertisements to this address.
> 


Re: Strange PPP problem

1998-12-31 Thread Jim Foltz
Akop,

Did you try to dial you ISP with a terminal emulator, like minicom? This is
a good way to find out exactly what it expects as far as send and expect
strings.

The log looks similar to mine. My ISP uses CHAP. Have you tried making a
chap-secrets and using the name option in options?

On Thu, Dec 31, 1998 at 05:53:06AM -0800, Akop Pogosian wrote:
> 
> Ok, I have set up ppp connections several times but I am not an expert.
> I am trying to connect to my new ISP, INTX.NET (if anyone else is using
> INTX.NET as their ISP, please tell me what you do!) I had real hard time
> figuring out what kind of strings my ISP sends and expects. I have
> already managed to log in and start a ppp session. However, I can not ping
> anything besides the ppp server, not even the name servers. My ISP
> supplies all the information (e.g. IP address, default route,etc)
> dynamically. The only information that they gave me was the phone
> number and the name server ip addresses. Below, I list my pppd options,
> routing table as reported by route -n, and the system messages
> (I have used ezppp and pppconfig with various degrees of success)
> Thank you.
> 
> Akop.
> 
> pppd options :
> 
> -detach
> defaultroute
> noauth
> noproxyarp
> debug
> 
> routing table (after establishing ppp connection):
> 
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric RefUse
> Iface
> 209.144.16.19   0.0.0.0 255.255.255.255 UH0  00
> ppp0
> 127.0.0.0   0.0.0.0 255.0.0.0   U 0  00 lo
> 0.0.0.0 209.144.16.19   0.0.0.0 UG0  00
> ppp0
> 
> 
> system messages:
> 
> Dec 31 04:29:40 debian pppd[338]: pppd 2.3.5 started by root, uid 0
> Dec 31 04:29:40 debian pppd[338]: Using interface ppp0
> Dec 31 04:29:40 debian pppd[338]: Connect: ppp0 <--> /dev/cua2
> Dec 31 04:29:40 debian pppd[338]: sent [LCP ConfReq id=0x1 
>   ]
> Dec 31 04:29:40 debian pppd[338]: rcvd [LCP ConfAck id=0x1 
>   ]
> Dec 31 04:29:43 debian pppd[338]: rcvd [LCP ConfReq id=0x1 < 00 04 00 00>
> < 11 04 05 f4> < 13 09 03
> 00 c0 7b 5f fe fd>]
> Dec 31 04:29:43 debian pppd[338]: sent [LCP ConfRej id=0x1 < 00 04 00 00>
> < 11 04 05 f4> < 13 09 03 00 c0 7b 5f fe fd>]
> Dec 31 04:29:43 debian pppd[338]: rcvd [LCP ConfReq id=0x2 
>   ]
> Dec 31 04:29:43 debian pppd[338]: sent [LCP ConfAck id=0x2 
>   ]
> Dec 31 04:29:43 debian pppd[338]: sent [LCP EchoReq id=0x0
> magic=0x88c9]
> Dec 31 04:29:43 debian pppd[338]: sent [IPCP ConfReq id=0x1 
> ]
> Dec 31 04:29:43 debian pppd[338]: sent [CCP ConfReq id=0x1 ]
> Dec 31 04:29:43 debian pppd[338]: rcvd [IPCP ConfReq id=0x1  209.144.16.19>]
> Dec 31 04:29:43 debian pppd[338]: sent [IPCP ConfAck id=0x1  209.144.16.19>]
> Dec 31 04:29:43 debian pppd[338]: rcvd [CCP ConfReq id=0x1 < 11 06 00 01
> 01 03>]
> Dec 31 04:29:43 debian pppd[338]: sent [CCP ConfRej id=0x1 < 11 06 00 01
> 01 03>]
> Dec 31 04:29:43 debian pppd[338]: rcvd [LCP EchoRep id=0x0 magic=0x0]
> Dec 31 04:29:43 debian pppd[338]: rcvd [IPCP ConfRej id=0x1  0f 01>]
> Dec 31 04:29:43 debian pppd[338]: sent [IPCP ConfReq id=0x2  0.0.0.0>]
> Dec 31 04:29:43 debian pppd[338]: rcvd [CCP ConfRej id=0x1 ]
> Dec 31 04:29:43 debian pppd[338]: sent [CCP ConfReq id=0x2]
> Dec 31 04:29:43 debian pppd[338]: rcvd [IPCP ConfNak id=0x2  209.144.16.153>]
> Dec 31 04:29:43 debian pppd[338]: sent [IPCP ConfReq id=0x3  209.144.16.153>]
> Dec 31 04:29:43 debian pppd[338]: rcvd [CCP ConfRej id=0x2]
> Dec 31 04:29:43 debian pppd[338]: rcvd [IPCP ConfAck id=0x3  209.144.16.153>]
> Dec 31 04:29:43 debian pppd[338]: local  IP address 209.144.16.153
> Dec 31 04:29:43 debian pppd[338]: remote IP address 209.144.16.19
> Dec 31 04:30:13 debian pppd[338]: sent [LCP EchoReq id=0x1
> magic=0x88c9]
> Dec 31 04:30:13 debian pppd[338]: rcvd [LCP EchoRep id=0x1 magic=0x0]
> Dec 31 04:30:43 debian pppd[338]: sent [LCP EchoReq id=0x2
> magic=0x88c9]
> Dec 31 04:30:43 debian pppd[338]: rcvd [LCP EchoRep id=0x2 magic=0x0]
> Dec 31 04:31:13 debian pppd[338]: sent [LCP EchoReq id=0x3
> magic=0x88c9]
> Dec 31 04:31:13 debian pppd[338]: rcvd [LCP EchoRep id=0x3 magic=0x0]
> Dec 31 04:31:42 debian icmplogd: destination unreachable from
> [209.44.32.73]
> Dec 31 04:31:43 debian pppd[338]: sent [LCP EchoReq id=0x4
> magic=0x88c9]
> Dec 31 04:31:43 debian pppd[338]: rcvd [LCP EchoRep id=0x4 magic=0x0]
> Dec 31 04:32:13 debian pppd[338]: sent [LCP EchoReq id=0x5
> magic=0x88c9]
> Dec 31 04:32:13 debian pppd[338]: rcvd [LCP EchoRep id=0x5 magic=0x0]
> Dec 31 04:32:43 debian pppd[338]: sent [LCP EchoReq id=0x6
> magic=0x88c9]
> Dec 31 04:32:43 debian pppd[338]: rcvd [LCP EchoRep id=0x6 magic=0x0]
> Dec 31 04:33:03 debian icmplogd: destination unreachable from
> [209.44.32.73]
> Dec 31 04:33:13 debian pppd[338]: sent [LCP EchoReq id=0x7
> magic=0x88c9]
> Dec 31 04:33:13 debian pppd[338]: rcvd [LCP EchoRep id=0x7 magic=0x0]
> Dec 31 04:33:43 debian pppd[338]: sent [LCP EchoR

Strange PPP problem

1998-12-31 Thread Akop Pogosian

Ok, I have set up ppp connections several times but I am not an expert.
I am trying to connect to my new ISP, INTX.NET (if anyone else is using
INTX.NET as their ISP, please tell me what you do!) I had real hard time
figuring out what kind of strings my ISP sends and expects. I have
already managed to log in and start a ppp session. However, I can not ping
anything besides the ppp server, not even the name servers. My ISP
supplies all the information (e.g. IP address, default route,etc)
dynamically. The only information that they gave me was the phone
number and the name server ip addresses. Below, I list my pppd options,
routing table as reported by route -n, and the system messages
(I have used ezppp and pppconfig with various degrees of success)
Thank you.

Akop.

pppd options :

-detach
defaultroute
noauth
noproxyarp
debug

routing table (after establishing ppp connection):

Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse
Iface
209.144.16.19   0.0.0.0 255.255.255.255 UH0  00
ppp0
127.0.0.0   0.0.0.0 255.0.0.0   U 0  00 lo
0.0.0.0 209.144.16.19   0.0.0.0 UG0  00
ppp0


system messages:

Dec 31 04:29:40 debian pppd[338]: pppd 2.3.5 started by root, uid 0
Dec 31 04:29:40 debian pppd[338]: Using interface ppp0
Dec 31 04:29:40 debian pppd[338]: Connect: ppp0 <--> /dev/cua2
Dec 31 04:29:40 debian pppd[338]: sent [LCP ConfReq id=0x1 
  ]
Dec 31 04:29:40 debian pppd[338]: rcvd [LCP ConfAck id=0x1 
  ]
Dec 31 04:29:43 debian pppd[338]: rcvd [LCP ConfReq id=0x1 < 00 04 00 00>
< 11 04 05 f4> < 13 09 03
00 c0 7b 5f fe fd>]
Dec 31 04:29:43 debian pppd[338]: sent [LCP ConfRej id=0x1 < 00 04 00 00>
< 11 04 05 f4> < 13 09 03 00 c0 7b 5f fe fd>]
Dec 31 04:29:43 debian pppd[338]: rcvd [LCP ConfReq id=0x2 
  ]
Dec 31 04:29:43 debian pppd[338]: sent [LCP ConfAck id=0x2 
  ]
Dec 31 04:29:43 debian pppd[338]: sent [LCP EchoReq id=0x0
magic=0x88c9]
Dec 31 04:29:43 debian pppd[338]: sent [IPCP ConfReq id=0x1 
]
Dec 31 04:29:43 debian pppd[338]: sent [CCP ConfReq id=0x1 ]
Dec 31 04:29:43 debian pppd[338]: rcvd [IPCP ConfReq id=0x1 ]
Dec 31 04:29:43 debian pppd[338]: sent [IPCP ConfAck id=0x1 ]
Dec 31 04:29:43 debian pppd[338]: rcvd [CCP ConfReq id=0x1 < 11 06 00 01
01 03>]
Dec 31 04:29:43 debian pppd[338]: sent [CCP ConfRej id=0x1 < 11 06 00 01
01 03>]
Dec 31 04:29:43 debian pppd[338]: rcvd [LCP EchoRep id=0x0 magic=0x0]
Dec 31 04:29:43 debian pppd[338]: rcvd [IPCP ConfRej id=0x1 ]
Dec 31 04:29:43 debian pppd[338]: sent [IPCP ConfReq id=0x2 ]
Dec 31 04:29:43 debian pppd[338]: rcvd [CCP ConfRej id=0x1 ]
Dec 31 04:29:43 debian pppd[338]: sent [CCP ConfReq id=0x2]
Dec 31 04:29:43 debian pppd[338]: rcvd [IPCP ConfNak id=0x2 ]
Dec 31 04:29:43 debian pppd[338]: sent [IPCP ConfReq id=0x3 ]
Dec 31 04:29:43 debian pppd[338]: rcvd [CCP ConfRej id=0x2]
Dec 31 04:29:43 debian pppd[338]: rcvd [IPCP ConfAck id=0x3 ]
Dec 31 04:29:43 debian pppd[338]: local  IP address 209.144.16.153
Dec 31 04:29:43 debian pppd[338]: remote IP address 209.144.16.19
Dec 31 04:30:13 debian pppd[338]: sent [LCP EchoReq id=0x1
magic=0x88c9]
Dec 31 04:30:13 debian pppd[338]: rcvd [LCP EchoRep id=0x1 magic=0x0]
Dec 31 04:30:43 debian pppd[338]: sent [LCP EchoReq id=0x2
magic=0x88c9]
Dec 31 04:30:43 debian pppd[338]: rcvd [LCP EchoRep id=0x2 magic=0x0]
Dec 31 04:31:13 debian pppd[338]: sent [LCP EchoReq id=0x3
magic=0x88c9]
Dec 31 04:31:13 debian pppd[338]: rcvd [LCP EchoRep id=0x3 magic=0x0]
Dec 31 04:31:42 debian icmplogd: destination unreachable from
[209.44.32.73]
Dec 31 04:31:43 debian pppd[338]: sent [LCP EchoReq id=0x4
magic=0x88c9]
Dec 31 04:31:43 debian pppd[338]: rcvd [LCP EchoRep id=0x4 magic=0x0]
Dec 31 04:32:13 debian pppd[338]: sent [LCP EchoReq id=0x5
magic=0x88c9]
Dec 31 04:32:13 debian pppd[338]: rcvd [LCP EchoRep id=0x5 magic=0x0]
Dec 31 04:32:43 debian pppd[338]: sent [LCP EchoReq id=0x6
magic=0x88c9]
Dec 31 04:32:43 debian pppd[338]: rcvd [LCP EchoRep id=0x6 magic=0x0]
Dec 31 04:33:03 debian icmplogd: destination unreachable from
[209.44.32.73]
Dec 31 04:33:13 debian pppd[338]: sent [LCP EchoReq id=0x7
magic=0x88c9]
Dec 31 04:33:13 debian pppd[338]: rcvd [LCP EchoRep id=0x7 magic=0x0]
Dec 31 04:33:43 debian pppd[338]: sent [LCP EchoReq id=0x8
magic=0x88c9]
Dec 31 04:33:43 debian pppd[338]: rcvd [LCP EchoRep id=0x8 magic=0x0]
Dec 31 04:34:13 debian pppd[338]: sent [LCP EchoReq id=0x9
magic=0x88c9]
Dec 31 04:34:13 debian pppd[338]: rcvd [LCP EchoRep id=0x9 magic=0x0]
Dec 31 04:34:24 debian icmplogd: destination unreachable from
[209.44.32.73]
Dec 31 04:34:43 debian pppd[338]: sent [LCP EchoReq id=0xa
magic=0x88c9]
Dec 31 04:34:43 debian pppd[338]: rcvd [LCP EchoRep id=0xa magic=0x0]
Dec 31 04:35:13 debian pppd[338]: sent [LCP EchoReq id=0xb
magic=0x88c9]
Dec 31 04:35:13 debian pppd[338]: rcvd [LCP EchoRep id=0xb magic=0x0]
Dec 31 04:35:43 debian pppd[338]: se

Re: very strange PPP problem (more info)

1997-02-24 Thread spiegl
I few days ago, I wrote:

>There is something with my PPP setup that really startles me:
>(Teles S0.3 card, Debian Linux 1.2.6 distribution, 2.0.27 kernel)
>
>I have two ISPs, one (lets call it "I1") supports ISDN, the
>other one ("I2") supports ISDN and analog modem connections.
>
>I can connect to I1 without any problems and all works great.
>The preferred connection is to I2 via ISDN, though.  So:
>I can also connect to I2 using my 14.4bps analog modem, and all
>works as it should.  But when I connect to I2 using ISDN, pppd
>terminates the connection right after it received the "CONNECT 64000".
>Now what makes this situation even stranger, is that under Win95
>I can connect to I2 w/ ISDN perfectly.
>
>Okay, since I2's server is a WinNT machine, I first thought that
>the two different OS's don't like each other.  But then I found
>out that the analog connection is working.  Next I thought that
>the ISDN cards don't understand each other.  But since it's working
>under Win95, that can't be either.
>
>So, to summarize, it can't be a hardware problem (since it works
>under Win95) and it can't be a software problem (since the analog
>connection work with exactly the same pppd and PPP-Server at I2).
>
>I just don't understand this at all.  I anyone of you guys has
>an idea how I can get it to work, please give me a hint.


Hi again!

To give anyone who is willing to help me, some more information
I put together my ppp-scripts and pretty verbose debug log into
this file:
 http://www.appl-math.tu-muenchen.de/~spiegl/ppp.problem.txt

Thanks a lot in advance to all of you out there!
 Andy.
___
 Andy Spiegl, Institute for Applied Mathematics
 University of Technology, Muenchen, Germany
 E-Mail: [EMAIL PROTECTED]
 URL:http://www.appl-math.tu-muenchen.de/~spiegl
 PGP fingerprint: B8 48 24 7B DB 96 6F 1C  D9 6D 8E 6C DB C2 E7 E9
o  _ _ _
  - __o   __o  /\_   _ \\o  (_)\__/o  (_)
  --- _`\<,__`\<,__>(_) (_)/<_\_| \   _|/' \/
  -- (_)/ (_)  (_)/ (_)  (_)(_)   (_)(_)'  _\o_
 ~~~


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]


Re: very strange PPP problem (more info)

1997-02-24 Thread Andy Spiegl
>There is something with my PPP setup that really startles me:
>(Teles S0.3 card, Debian Linux 1.2.6 distribution, 2.0.27 kernel)
>
>I have two ISPs, one (lets call it "I1") supports ISDN, the
>other one ("I2") supports ISDN and analog modem connections.
>
>I can connect to I1 without any problems and all works great.
>The preferred connection is to I2 via ISDN, though.  So:
>I can also connect to I2 using my 14.4bps analog modem, and all
>works as it should.  But when I connect to I2 using ISDN, pppd
>terminates the connection right after it received the "CONNECT 64000".
>Now what makes this situation even stranger, is that under Win95
>I can connect to I2 w/ ISDN perfectly.
>
>Okay, since I2's server is a WinNT machine, I first thought that
>the two different OS's don't like each other.  But then I found
>out that the analog connection is working.  Next I thought that
>the ISDN cards don't understand each other.  But since it's working
>under Win95, that can't be either.
>
>So, to summarize, it can't be a hardware problem (since it works
>under Win95) and it can't be a software problem (since the analog
>connection work with exactly the same pppd and PPP-Server at I2).
>
>I just don't understand this at all.  I anyone of you guys has
>an idea how I can get it to work, please give me a hint.


Hi again!

To give anyone who is willing to help me, some more information
I put together my ppp-scripts and pretty verbose debug log into
this file:
 http://www.appl-math.tu-muenchen.de/~spiegl/ppp.problem.txt

Thanks a lot in advance to all of you out there!
 Andy.
___
 Andy Spiegl, Institute for Applied Mathematics
 University of Technology, Muenchen, Germany
 E-Mail: [EMAIL PROTECTED]
 URL:http://www.appl-math.tu-muenchen.de/~spiegl
 PGP fingerprint: B8 48 24 7B DB 96 6F 1C  D9 6D 8E 6C DB C2 E7 E9
o  _ _ _
  - __o   __o  /\_   _ \\o  (_)\__/o  (_)
  --- _`\<,__`\<,__>(_) (_)/<_\_| \   _|/' \/
  -- (_)/ (_)  (_)/ (_)  (_)(_)   (_)(_)'  _\o_
 ~~~


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]


Re: Strange ppp problem.

1996-12-17 Thread Joe Emenaker
> 
> I was experimenting
> with setting up ppp over a nul modem cable (with little luck, I might
> add).

To get mine working, I had to instruct getty not to die if it didn't see
the Carrier-Detect/DSR/CTS set. Otherwise, it wigged if the cable wasn't
hooked up. Getty would respawn faster than a rabbit on hormones and init
would have to chill it out for 5 minutes.

The inittab line that worked was:
S1:23:respawn:/sbin/getty -L -h 38400,19200,9600 ttyS1

> The question is: Why does the cable interfere in the first place? Is this
> a cua vs tty issue? 

>From what little experience I've had with serial ports in Unix, it's kind
of a Murphy's Law deal: if it *can* be a cua vs. tty issue, it WILL be one.
Every document I've read recently that seems to know what it's talking 
about says to use tty exclusively.

- Joe


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]


Re: Strange ppp problem.

1996-12-16 Thread Dale Scheetz
Well, I fixed the problem, but I still don't understand it.
First, it has nothing to do with the kernels (whew).
At the same time I was building the new 2.0.27 kernel, I was experimenting
with setting up ppp over a nul modem cable (with little luck, I might
add). After giving up on the ppp issue, I left the null modem cable
connecting the two machines serial ports. This seems to be the culprit. As
soon as I thought to remove the cable everything workes fine.
In addition, it turned out not to be a retry issue, as I did some other
work after a reboot and then could not establish the ppp connection.
When it works pppd takes about 3 seconds to get chat up and dialing. When
it doesn't work chat takes as much as 30-40 seconds to start dialing. I
can only assume that chat is somehow delayed in reading the modem and
misses the request for a login and then fails.
The question is: Why does the cable interfere in the first place? Is this
a cua vs tty issue? (My option file still uses cua3 as the device. It's an
old pppd installation that I have been loath to "fix" by upgrading since,
until now it has worked just fine)
If I can find the time, I will try changing the cua entry and see if it
will still work with the cable installed. I really need to fix this, since
at some point I want both the modem and the serial port running pppd. (One
to my provider and the other to my other machine)

Thanks in advance,

Dwarf

  --

aka   Dale Scheetz   Phone:   1 (904) 877-0257
  Flexible Software  Fax: NONE 
  Black Creek Critters   e-mail:  [EMAIL PROTECTED]

 If you don't see what you want, just ask --


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]


Strange ppp problem.

1996-12-13 Thread Dale Scheetz
I have recently been experiencing a problem with ppp. The problem began
when I built myself a new 2.0.27 kernel, but does not seem to be related
to the kernel.
Here's the problem: After a boot up, I can ppp to my ISP just fine the
first time, but after dropping the connection, I can not establish a
connection until after rebooting the machine. Ppp cranks up the chat
script, which dials the provider. The modems negotiate speed and seconds
after the connection is established chat declares an error an aborts
causing pppd to drop as well. The modems are still happily chirping to
each other, and I must disconnect the phone line to get the provider modem
to drop.
I am running both 2.1.5 and 2.0.27 kernels. I can swap from one kernel to
the other, or keep rebooting the same one and the behavior is always the
same: First time connect works flawlessly, any attempt after the first
connection always fails the same way.
Aside from building a new kernel, I can think of no other packages that I
might have installed during this period. Since that time, I have installed
all the rex base packages, but this has not changed the behavior.
Any idea what's going on? A method of debugging this problem would do as
well.

TIA,

Dwarf

  --

aka   Dale Scheetz   Phone:   1 (904) 877-0257
  Flexible Software  Fax: NONE 
  Black Creek Critters   e-mail:  [EMAIL PROTECTED]

 If you don't see what you want, just ask --


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]