Linux is a cruel joke

Linux is a cruel joke

Post by Chad Cunningha » Tue, 03 Mar 1998 04:00:00



Okay, I figure I'm about three days away from giving up on Linux.  I
have yet to make a functional ppp connection.  I have determined that
this could be due to one of three causes.

1) I am an idiot
2) My ISP uses a very strange PAP that I don't know how to configure
3) Linux really doesn't have ppp support and everyone else is in on the
joke
3)God, or Linus, hates me

For those of you who are wondering, yes, I have read all the How-To's,
mini How-To's, FAQ's, mini FAQ's, man pages, etc etc.  you name it, I've
read it.  So here is my status.  I have tried XIsp, ezppp, kppp, netcfg,
minicom, and a chat script.  I asked my ISP, and they say they use PAP,
so I've been configuring for that.  But, I used windows95's
hyperterminal to call them up, and it connected fine by just entering in
my password and username.  Does this mean they don't use PAP or what?
When I try to connect with linux not configured for PAP, it freezes up
when the debugging window says starting pppd...
I have used tail -f /var/log/messages to log what's going on.  With
netcfg, the output looks like this:
Mar  2 20:01:36 localhost ifup-ppp: pppd started for ppp0 on /dev/modem
at 115200
Mar  2 20:01:36 localhost kernel: CSLIP: code copyright 1989 Regents of
the University of California
Mar  2 20:01:36 localhost kernel: PPP: version 2.2.0 (dynamic channel
allocation)
Mar  2 20:01:36 localhost kernel: PPP Dynamic channel allocation code
copyright 1995 Caldera, Inc.
Mar  2 20:01:36 localhost kernel: PPP line discipline registered.
Mar  2 20:01:36 localhost kernel: registered device ppp0
Mar  2 20:01:36 localhost pppd[366]: pppd 2.2.0 started by root, uid 0
Mar  2 20:02:36 localhost pppd[366]: Serial connection established.
Mar  2 20:02:46 localhost pppd[366]: Using interface ppp0
Mar  2 20:02:46 localhost pppd[366]: Connect: ppp0 <--> /dev/modem
Mar  2 20:03:17 localhost pppd[366]: LCP: timeout sending
Config-Requests
Mar  2 20:03:17 localhost pppd[366]: Connection terminated.
Mar  2 20:03:17 localhost pppd[366]: Receive serial link is not 8-bit
clean:
Mar  2 20:03:17 localhost pppd[366]: Problem: all had bit 7 set to 0

I don't know what that problem means.  When I use my chat script, it
looks like this:

Mar  2 20:04:38 localhost pppd[394]: pppd 2.2.0 started by root, uid 0
Mar  2 20:04:38 localhost pppd[366]: ioctl(TIOCNXCL): Input/output error

Mar  2 20:04:38 localhost pppd[366]: Exit.
Mar  2 20:04:38 localhost pppd[394]: tcsetattr: Invalid argument
Mar  2 20:04:38 localhost pppd[394]: Exit.
Mar  2 20:05:22 localhost pppd[398]: pppd 2.2.0 started by root, uid 0
Mar  2 20:05:23 localhost chat[399]: send (ATDT9,6293030^M)
Mar  2 20:05:24 localhost chat[399]: expect (CONNECT)
Mar  2 20:06:02 localhost chat[399]: ATDT9,6293030^M
Mar  2 20:06:02 localhost pppd[398]: Serial connection established.
Mar  2 20:06:02 localhost chat[399]: CONNECT -- got it
Mar  2 20:06:03 localhost pppd[398]: Using interface ppp0
Mar  2 20:06:03 localhost pppd[398]: Connect: ppp0 <--> /dev/modem
Mar  2 20:06:33 localhost pppd[398]: LCP: timeout sending
Config-Requests

It will then repeat LCP: timeout sending Config-Requests for about five
minutes until it gives up.

If I try to use minicom and do a manual log in, or do the same thing
with kppp, everything goes very slow.  It takes about 30 seconds for the
username: prompt to display.  And yes, I have checked the connection
speed and it is 57600.  I have no clue what's going on here, but it is
wearing my patience thin.  If anyone can help me, I will be very
appreciative.

 
 
 

Linux is a cruel joke

Post by James Staffor » Wed, 04 Mar 1998 04:00:00



> Okay, I figure I'm about three days away from giving up on Linux.  I
> have yet to make a functional ppp connection.  I have determined that
> this could be due to one of three causes.

> 1) I am an idiot
> 2) My ISP uses a very strange PAP that I don't know how to configure
> 3) Linux really doesn't have ppp support and everyone else is in on the
> joke
> 3)God, or Linus, hates me

> For those of you who are wondering, yes, I have read all the How-To's,
> mini How-To's, FAQ's, mini FAQ's, man pages, etc etc.  you name it, I've
> read it.  So here is my status.  I have tried XIsp, ezppp, kppp, netcfg,
> minicom, and a chat script.  I asked my ISP, and they say they use PAP,
> so I've been configuring for that.  But, I used windows95's
> hyperterminal to call them up, and it connected fine by just entering in
> my password and username.  Does this mean they don't use PAP or what?
> When I try to connect with linux not configured for PAP, it freezes up
> when the debugging window says starting pppd...
> I have used tail -f /var/log/messages to log what's going on.  With
> netcfg, the output looks like this:
> Mar  2 20:01:36 localhost ifup-ppp: pppd started for ppp0 on /dev/modem
> at 115200
> Mar  2 20:01:36 localhost kernel: CSLIP: code copyright 1989 Regents of
> the University of California
> Mar  2 20:01:36 localhost kernel: PPP: version 2.2.0 (dynamic channel
> allocation)
> Mar  2 20:01:36 localhost kernel: PPP Dynamic channel allocation code
> copyright 1995 Caldera, Inc.
> Mar  2 20:01:36 localhost kernel: PPP line discipline registered.
> Mar  2 20:01:36 localhost kernel: registered device ppp0
> Mar  2 20:01:36 localhost pppd[366]: pppd 2.2.0 started by root, uid 0
> Mar  2 20:02:36 localhost pppd[366]: Serial connection established.
> Mar  2 20:02:46 localhost pppd[366]: Using interface ppp0
> Mar  2 20:02:46 localhost pppd[366]: Connect: ppp0 <--> /dev/modem
> Mar  2 20:03:17 localhost pppd[366]: LCP: timeout sending
> Config-Requests
> Mar  2 20:03:17 localhost pppd[366]: Connection terminated.
> Mar  2 20:03:17 localhost pppd[366]: Receive serial link is not 8-bit
> clean:
> Mar  2 20:03:17 localhost pppd[366]: Problem: all had bit 7 set to 0

> I don't know what that problem means.  When I use my chat script, it
> looks like this:

> Mar  2 20:04:38 localhost pppd[394]: pppd 2.2.0 started by root, uid 0
> Mar  2 20:04:38 localhost pppd[366]: ioctl(TIOCNXCL): Input/output error

> Mar  2 20:04:38 localhost pppd[366]: Exit.
> Mar  2 20:04:38 localhost pppd[394]: tcsetattr: Invalid argument
> Mar  2 20:04:38 localhost pppd[394]: Exit.
> Mar  2 20:05:22 localhost pppd[398]: pppd 2.2.0 started by root, uid 0
> Mar  2 20:05:23 localhost chat[399]: send (ATDT9,6293030^M)
> Mar  2 20:05:24 localhost chat[399]: expect (CONNECT)
> Mar  2 20:06:02 localhost chat[399]: ATDT9,6293030^M
> Mar  2 20:06:02 localhost pppd[398]: Serial connection established.
> Mar  2 20:06:02 localhost chat[399]: CONNECT -- got it
> Mar  2 20:06:03 localhost pppd[398]: Using interface ppp0
> Mar  2 20:06:03 localhost pppd[398]: Connect: ppp0 <--> /dev/modem
> Mar  2 20:06:33 localhost pppd[398]: LCP: timeout sending
> Config-Requests

> It will then repeat LCP: timeout sending Config-Requests for about five
> minutes until it gives up.

> If I try to use minicom and do a manual log in, or do the same thing
> with kppp, everything goes very slow.  It takes about 30 seconds for the
> username: prompt to display.  And yes, I have checked the connection
> speed and it is 57600.  I have no clue what's going on here, but it is
> wearing my patience thin.  If anyone can help me, I will be very
> appreciative.

Have you checked your hosts and resolve.cof files in the directory /etc?
I started to have problems this past weekend with PPP after it had been
working good for months. I called my ISP and they told me what my
netmask and my loacl IP number was. I then ran netconfig (at the shell
prompt type netconfig) and answered all the questions. Then I ran
pppsetup (you'll probably have to down load this) and all is working
better than ever.

Don't give up, Linux is the best!!

jamess

 
 
 

Linux is a cruel joke

Post by Josh Yelo » Wed, 04 Mar 1998 04:00:00


Quote:> If I try to use minicom and do a manual log in, or do the same thing
> with kppp, everything goes very slow.  It takes about 30 seconds for the
> username: prompt to display.

Username prompt? Hm...

OK, when your ISP is using PAP, there is no username prompt.  The ISP
sends weird character sequences, and your ppp daemon responds with more
weird character sequences.  I have seen an ISP which works like this:

1. You dial, and the ISP just sits there, saying nothing at all.
2. If you send weird character sequences, the ISP figures you're a ppp
daemon, and it starts doing PAP.
2. If you do anything else, the ISP figures you're a human being, and it
sends a Username prompt.

Sounds like you might have this kind of ISP.  If so, you have to make
sure your chat script doesn't send an extra return, or else the ISP will
think it's talking to a human.

But as for why ezppp didn't work?  Beats me, that's weird.

You might also want to add the "debug" option to pppd.  That'll put a
lot more useful information in your log file.

- Josh

 
 
 

Linux is a cruel joke

Post by Dana J. Laud » Wed, 04 Mar 1998 04:00:00



> > If I try to use minicom and do a manual log in, or do the same thing
> > with kppp, everything goes very slow.  It takes about 30 seconds for the
> > username: prompt to display.

> Username prompt? Hm...

> OK, when your ISP is using PAP, there is no username prompt.  The ISP
> sends weird character sequences, and your ppp daemon responds with more
> weird character sequences.  I have seen an ISP which works like this:

> 1. You dial, and the ISP just sits there, saying nothing at all.
> 2. If you send weird character sequences, the ISP figures you're a ppp
> daemon, and it starts doing PAP.
> 2. If you do anything else, the ISP figures you're a human being, and it
> sends a Username prompt.

> Sounds like you might have this kind of ISP.  If so, you have to make
> sure your chat script doesn't send an extra return, or else the ISP will
> think it's talking to a human.

> But as for why ezppp didn't work?  Beats me, that's weird.

> You might also want to add the "debug" option to pppd.  That'll put a
> lot more useful information in your log file.

> - Josh

My ISP uses a slightly different approach.  I did the test as stated in the
PPP-HOWTO with minicom and I received a "username:" and then "password:"
prompt.  Now, I have a shell account in addition to my PPP.  They distiguse
this by the login name.  Thus I have Pacsoshwi as a PPP login and acsoshwi as
my shell.  Everything worked fine, and no PAP was needed in my case.  I did
notice that the ISP's recommendation of setting the MPU to 576 was wrong,
1500 seems to work best for me. (the default in Red Hat 5.0)

Dana

 
 
 

Linux is a cruel joke

Post by David Wollma » Thu, 05 Mar 1998 04:00:00




Quote:>Okay, I figure I'm about three days away from giving up on Linux.  I
>have yet to make a functional ppp connection.  I have determined that
>this could be due to one of three causes.

>1) I am an idiot
>2) My ISP uses a very strange PAP that I don't know how to configure
>3) Linux really doesn't have ppp support and everyone else is in on the
>joke
>3)God, or Linus, hates me

I've been there. I just spent three weeks struggling with PPP and finally got it working. The
worst part? I'm not sure exactly which change was the magic bullet. I will say this, it's worth
the effort.

Why am I running Windows 95 now?

1) I have two drives, one partitioned FAT32, the other is all Linux. I haven't been able to get
the FAT32 patch to work yet, so I can't access my project files from Linux yet.

2) I have yet to move all my work over to Linux files. The biggest problem right now is my
Commence (PIM) databases. Do I install WINE or WABI and try Commence in Win emulation, or find
a PIM for Linux and port my data to it?

3) My ISDN TA isn't supported in Linux, and Diamond don't seem to want to talk to Linux people
about helping with driver development. Geez, it's a wonder these technology companies can stay
in business when they're run by luddite bean counters who don't have a clue...like they're
afraid some rogue Linux user is going to copy their microcode or something. Arghhh!

Quote:

>For those of you who are wondering, yes, I have read all the How-To's,
>mini How-To's, FAQ's, mini FAQ's, man pages, etc etc.  you name it, I've
>read it.  So here is my status.  I have tried XIsp, ezppp, kppp, netcfg,
>minicom, and a chat script.  I asked my ISP, and they say they use PAP,
>so I've been configuring for that.  But, I used windows95's
>hyperterminal to call them up, and it connected fine by just entering in
>my password and username.  Does this mean they don't use PAP or what?

Most access servers will give you what you need based on what they determine your
authentication requirements to be when you connect. When you dial in with a term program, the
server sees that and responds accordingly. If you dial in with PPP and PAP, it will most likely
see that and respond with an attempt at PAP auth negotitation.

Quote:>When I try to connect with linux not configured for PAP, it freezes up
>when the debugging window says starting pppd...

You're not getting enough debug information. Go to the file where you're setting the options
(usually /etc/ppp/options) and there should be a line that reads 'kdebug 7' or 'kdebug 25'. The
latter gets you A LOT of output, the former should suffice. This will output dumps of your
packets so you can "look inside" and see what's going on it LCP.

Quote:>I have used tail -f /var/log/messages to log what's going on.  With
>netcfg, the output looks like this:
>Mar  2 20:01:36 localhost ifup-ppp: pppd started for ppp0 on /dev/modem
>at 115200
>Mar  2 20:01:36 localhost kernel: CSLIP: code copyright 1989 Regents of
>the University of California
>Mar  2 20:01:36 localhost kernel: PPP: version 2.2.0 (dynamic channel
>allocation)
>Mar  2 20:01:36 localhost kernel: PPP Dynamic channel allocation code
>copyright 1995 Caldera, Inc.
>Mar  2 20:01:36 localhost kernel: PPP line discipline registered.
>Mar  2 20:01:36 localhost kernel: registered device ppp0
>Mar  2 20:01:36 localhost pppd[366]: pppd 2.2.0 started by root, uid 0
>Mar  2 20:02:36 localhost pppd[366]: Serial connection established.
>Mar  2 20:02:46 localhost pppd[366]: Using interface ppp0
>Mar  2 20:02:46 localhost pppd[366]: Connect: ppp0 <--> /dev/modem
>Mar  2 20:03:17 localhost pppd[366]: LCP: timeout sending
>Config-Requests
>Mar  2 20:03:17 localhost pppd[366]: Connection terminated.
>Mar  2 20:03:17 localhost pppd[366]: Receive serial link is not 8-bit
>clean:
>Mar  2 20:03:17 localhost pppd[366]: Problem: all had bit 7 set to 0

>I don't know what that problem means.  When I use my chat script, it
>looks like this:

>Mar  2 20:04:38 localhost pppd[394]: pppd 2.2.0 started by root, uid 0
>Mar  2 20:04:38 localhost pppd[366]: ioctl(TIOCNXCL): Input/output error

>Mar  2 20:04:38 localhost pppd[366]: Exit.
>Mar  2 20:04:38 localhost pppd[394]: tcsetattr: Invalid argument
>Mar  2 20:04:38 localhost pppd[394]: Exit.
>Mar  2 20:05:22 localhost pppd[398]: pppd 2.2.0 started by root, uid 0
>Mar  2 20:05:23 localhost chat[399]: send (ATDT9,6293030^M)
>Mar  2 20:05:24 localhost chat[399]: expect (CONNECT)
>Mar  2 20:06:02 localhost chat[399]: ATDT9,6293030^M
>Mar  2 20:06:02 localhost pppd[398]: Serial connection established.
>Mar  2 20:06:02 localhost chat[399]: CONNECT -- got it
>Mar  2 20:06:03 localhost pppd[398]: Using interface ppp0
>Mar  2 20:06:03 localhost pppd[398]: Connect: ppp0 <--> /dev/modem
>Mar  2 20:06:33 localhost pppd[398]: LCP: timeout sending
>Config-Requests

>It will then repeat LCP: timeout sending Config-Requests for about five
>minutes until it gives up.

>If I try to use minicom and do a manual log in, or do the same thing
>with kppp, everything goes very slow.  It takes about 30 seconds for the
>username: prompt to display.

This is most likely caused by the peer's desire to default to PAP authentication. It probably
times out waiting for PAP, then defaults to manual login.

Quote:> And yes, I have checked the connection
>speed and it is 57600.  I have no clue what's going on here, but it is
>wearing my patience thin.  If anyone can help me, I will be very
>appreciative.

Keep plugging away. I've learned more about networking in the last three weeks just by working
on Linux than I learn in the last three years with WinDOS.

--
Remove !SPAM from my email address to reply via email.

 
 
 

Linux is a cruel joke

Post by William McBri » Fri, 06 Mar 1998 04:00:00


: 2) I have yet to move all my work over to Linux files. The biggest
: problem right now is my Commence (PIM) databases. Do I install WINE or
: WABI and try Commence in Win emulation, or find a PIM for Linux and port
: my data to it?

Despite the tremendous efforts of the WINE developers, its level of
functionality and reliability is not yet terribly compelling.

--
William McBrine    | http://www.clark.net/~wmcbrine/

 
 
 

Linux is a cruel joke

Post by Dietmar Herrend?rfe » Fri, 06 Mar 1998 04:00:00



> Mar  2 20:03:17 localhost pppd[366]: Connection terminated.
> Mar  2 20:03:17 localhost pppd[366]: Receive serial link is not 8-bit
> clean:
> Mar  2 20:03:17 localhost pppd[366]: Problem: all had bit 7 set to 0

Ooops, how does this 7bit transfer come about???? It can hardly be
on your ISP's server side. To my knowledge ppp does NOT work
under any circumstances over 7bit serial links (open to corrections
here, but for the moment I am quite certain about this). Therefore
I am quite certain that this is the where your problem comes in.

However it is not that easy to guess, why you end up with a 7bit line!
If anyone can use your ISP at all (using the same way of logging as
you do) I suppose the problem must be on your side, though.

Make sure your modem is set to hardware handshake (AT&K3 for
most modems, but check with your manual). XON/XOFF protocol
will NOT work for ppp!. Make sure your modem doesn't have any
strange setting, which makes it mask out the 8th bit. Make sure
you can commuicate with your modem using something like
"minicom" while using hardware-handshake, 8bits, no parity.

If you manage to get  ppp connection under any other OS, I can't
see why eventually you shouldn't be succesful with Linux.

Good Luck

---
Dietmar Herrend?rfer
Electronic Engineering Laboratory
University of Kent at Canterbury
Canterbury, CT2 7NT, Great Britain

 
 
 

Linux is a cruel joke

Post by Bloody Viki » Sat, 07 Mar 1998 04:00:00


: Okay, I figure I'm about three days away from giving up on Linux.  I
: have yet to make a functional ppp connection.  I have determined that
: this could be due to one of three causes.

: 1) I am an idiot
: 2) My ISP uses a very strange PAP that I don't know how to configure
: 3) Linux really doesn't have ppp support and everyone else is in on the
: joke

[rm trials-and-tribulations.txt]

Reason number 4 is you don't know a friend in real life to come over to
help you out. That's a major problem I have with Linux! I admit I never
got PPP to work either, and I'm content with using Minicom and an ISP
shell account. PPP is nice for 2 reasons:

You can use an ISP that doesn't allow shell accounts.

You can use a GUI browser. (increasingly necessary, sadly.)

--
CAUTION: Email Spam Killer in use. Leave this line in your reply! 152680
                     "A man's car is his battleship"

2124025 bytes of spam mail deleted.           http://www.wwa.com/~nospam/

 
 
 

Linux is a cruel joke

Post by Subhas R » Mon, 09 Mar 1998 04:00:00




Quote:> Okay, I figure I'm about three days away from giving up on Linux.  I
> have yet to make a functional ppp connection.

Sorry that you are having so much trouble. Actually I too had to
struggle with PPP connection for two weeks when I was a Linux
newbie. Once it worked, I had very little problem with connecting many
different other ISPs.

Here are some suggestions:

Have you thought about trying some other ISPs? I am sure you have
choices. There are many top notch ISPs (like IBM.net, mindspring etc)
who have official web pages for Linux PPP setup. It will help if you
find somebody who had success with that ISP. Make sure you are not
running winmodem. Also, play with different values of MRU/MTU -- it
helped me once when I switched to MTU=1500.

 
 
 

Linux is a cruel joke

Post by charles » Mon, 09 Mar 1998 04:00:00




> : Okay, I figure I'm about three days away from giving up on Linux.  I
> : have yet to make a functional ppp connection.  I have determined that
> : this could be due to one of three causes.

> : 1) I am an idiot
> : 2) My ISP uses a very strange PAP that I don't know how to configure
> : 3) Linux really doesn't have ppp support and everyone else is in on the
> : joke

> [rm trials-and-tribulations.txt]

> Reason number 4 is you don't know a friend in real life to come over to
> help you out. That's a major problem I have with Linux! I admit I never
> got PPP to work either, and I'm content with using Minicom and an ISP
> shell account. PPP is nice for 2 reasons:

> You can use an ISP that doesn't allow shell accounts.

> You can use a GUI browser. (increasingly necessary, sadly.)

> --
> CAUTION: Email Spam Killer in use. Leave this line in your reply! 152680
>                      "A man's car is his battleship"

> 2124025 bytes of spam mail deleted.           http://www.wwa.com/~nospam/

Try pppbutton at

    ftp://ftp.mc.hik.se/pub/users/mia95anp/

if you don't have TCL/TK you can use the 'ppp-up' script that comes with it.
Put it in
/usr/sbin

This got me going when I was stuck with minicom and other dubious methods
and failures
of getting ppp connection going.

--
charles h
Huller Research

 
 
 

Linux is a cruel joke

Post by Ray » Mon, 09 Mar 1998 04:00:00



>Okay, I figure I'm about three days away from giving up on Linux.

Well, X is still fun to play around with. :-)

Quote:>I have yet to make a functional ppp connection.  I have determined that
>this could be due to one of three causes.

>1) I am an idiot
>2) My ISP uses a very strange PAP that I don't know how to configure
>3) Linux really doesn't have ppp support and everyone else is in on the
>joke
>4)God, or Linus, hates me

I have been trying to get a PPP connection with my Linux for about 3
weeks now, and I'm coming to the conclusion that your reason #3 is the
most likely.  It's all an intensely cruel, *ic joke.  Configuring
X is a cakewalk compared to getting Linux to connect to my ISP.

Quote:>For those of you who are wondering, yes, I have read all the How-To's,
>mini How-To's, FAQ's, mini FAQ's, man pages, etc etc.  you name it, I've
>read it.

Me too.  Worthless endeavors so far.

Quote:> So here is my status.  I have tried XIsp, ezppp, kppp, netcfg,
>minicom, and a chat script.  

Have you tried pppsetup?  I tried it, didn't work for me, but maybe it
will for you.  Linux seems very capricious (sp?) when it comes to how
it decides what users it might let on the Net...  (if it REALLY lets
any on at all).  pppsetup is a real nice idea, in theory.  Pity it
doesn't work for me, but at least my experiences are consistent in
terms of total failure for 3 weeks straight!

<snippty snip snip>

Quote:>Mar  2 20:02:46 localhost pppd[366]: Using interface ppp0
>Mar  2 20:02:46 localhost pppd[366]: Connect: ppp0 <--> /dev/modem
>Mar  2 20:03:17 localhost pppd[366]: LCP: timeout sending Config-Requests

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
DAMN!  *THIS* line looks familiar!!!!  Wonder what it means......      

Quote:>Mar  2 20:03:17 localhost pppd[366]: Receive serial link is not 8-bit clean:
>Mar  2 20:03:17 localhost pppd[366]: Problem: all had bit 7 set to 0

So do these two!  Exactly the error messages I am getting.  These and
something about the serial line (or connection ...?  I forget) being
"loopbacked".

Quote:> I have no clue what's going on here, but it is wearing my patience thin.

Sounds familiar!

Quote:> If anyone can help me, I will be very appreciative.

oh, *sure*, they'll *suggest* a ton of stuff...  just don't foget that
it *is* a cruel joke.   :-)  And we appear to be gluttons for
punishment.

Seriously, though, I wish you luck, and I'll be following this thread
since it seems our problems are quite similar.

Ray

 
 
 

Linux is a cruel joke

Post by Christopher Mahmoo » Tue, 10 Mar 1998 04:00:00


what version of pppd are you using?  Your line is more than likely
8-bit clean.
-ckm

 
 
 

Linux is a cruel joke

Post by Joholo » Thu, 12 Mar 1998 04:00:00


I was having the exact same errors.  I tried minicom and was able to get
through, I had thought it was a problem with my no name modem.  It turned out
that the ISP was using PAP for authentication.  I did a PAP-secrets script and
have had no problems since

 
 
 

Linux is a cruel joke

Post by Bob Taylo » Thu, 12 Mar 1998 04:00:00




[snip]

Quote:>>I have yet to make a functional ppp connection.  I have determined that
>>this could be due to one of three causes.

>>1) I am an idiot
>>2) My ISP uses a very strange PAP that I don't know how to configure
>>3) Linux really doesn't have ppp support and everyone else is in on the
>>joke
>>4)God, or Linus, hates me

0) You don't have PPP configured properly for your ISP

Quote:

> I have been trying to get a PPP connection with my Linux for about 3
> weeks now, and I'm coming to the conclusion that your reason #3 is the
> most likely.  It's all an intensely cruel, *ic joke.  Configuring
> X is a cakewalk compared to getting Linux to connect to my ISP.

Why don't you connect to your ISP with a terminal emulator, capture
the output and post it?

Quote:>>For those of you who are wondering, yes, I have read all the How-To's,
>>mini How-To's, FAQ's, mini FAQ's, man pages, etc etc.  you name it, I've
>>read it.

> Me too.  Worthless endeavors so far.

I don't think so. If you don't believe it will work, I guarentee it won't!

Quote:>> So here is my status.  I have tried XIsp, ezppp, kppp, netcfg,
>>minicom, and a chat script.  

[snip]

Quote:> <snippty snip snip>
>>Mar  2 20:02:46 localhost pppd[366]: Using interface ppp0
>>Mar  2 20:02:46 localhost pppd[366]: Connect: ppp0 <--> /dev/modem
>>Mar  2 20:03:17 localhost pppd[366]: LCP: timeout sending Config-Requests

> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> DAMN!  *THIS* line looks familiar!!!!  Wonder what it means......  

It means you don't have a valid chat script for this ISP.

Quote:

>>Mar  2 20:03:17 localhost pppd[366]: Receive serial link is not 8-bit clean:
>>Mar  2 20:03:17 localhost pppd[366]: Problem: all had bit 7 set to 0

In this particular case I would say your pppd is expecting packets and is
getting ASCII text instead. Another indication of misconfiguration.

[snip]

Quote:>> If anyone can help me, I will be very appreciative.

> oh, *sure*, they'll *suggest* a ton of stuff...  just don't foget that
> it *is* a cruel joke.   :-)  And we appear to be gluttons for
> punishment.

Nobody can help you with this attitude. Post some meaningful data and
just maybe someone can/will help you. Your problems CAN be solved you
know!

[snip]

--
+---------------------------------------------------------------+

|---------------------------------------------------------------|
| Like the ad says, at 300 dpi you can tell she's wearing a     |
| swimsuit. At 600 dpi you can tell it's wet. At 1200 dpi you   |
| can tell it's painted on. I suppose at 2400 dpi you can tell  |
| if the paint is giving her a rash. (So says Joshua R. Poulson)|
+---------------------------------------------------------------+

 
 
 

1. Is networking just a cruel hoax?

        OK.  Since about August of last year, I've been trying, without
any success, to install MkLinux DR3 on my PowerMac 6100.  Well, that's
not quite right: I can *install* it just fine.  What I can't do is make
it get a PPP connection, use the modem at all, or even admit that such
nigh-mythical things as netcfg exist.

        The installation process appears to run normally until it gets
to the configuration questions -- about the keyboard, the mouse,
'Do you want to set up LAN networking', and so on.  According to what
I've read, after this it is *supposed* to ask about dial-up or remote
networking.  It does no such thing (whether I answer yes or no to the
LAN question).

        If I attempt to run netcfg it reports this error:

  File "/usr/lib/rhs/netcfg/netcfg.py", line 23, in ?
    from Tkinter import *
  File "/usr/lib/python1.5/lib-tk/Tkinter.py", line 5, in ?
    import _tkinter # If this fails your Python is not configured for Tk
ImportError: libtiff.so.3: cannot open shared object file: No such file
or directory

        So far as I can determine, there is no such file as libtiff.so.3
anywhere in existence.

        I've searched Deja News and the MkLinux lists, and found a
handful of other people have had the same problem; but nobody has
any answers at all.  Neither do a panel of local Linux addicts I have
in the area; they've never seen nor heard of any problem like this.
I suspected it might be a defective CD-ROM, so got a fresh copy of the
whole disk image from the mklinux.apple.com site; it showed *precisely*
the same behavior for the whole matter.

        Running KDE, I'm able to give it the connection information, but
when I attempt to start a connection, it just sits there, happily,
waiting for the end of the world rather than actually, say, dialing the
number.  If I dial the number myself, the computer will never take the
ISP's answer as any kind of indication it should respond in some manner.

        Anyway.  I'm at the end of my rope here.  Nothing makes it want
to use a dial-up connection at all; even using sample PPP scripts can't
make it wake up.  I'm almost ready at this point to wipe out the
partitions and do a complete install of Civilization II.

        So.  Is there anything to be done?

        I'm running a 6100/60 with a 601 chip inside, 72 MB RAM; and have
MkLinux set up on a Jaz drive with a 100 MB MacOS partition, a 300 MB
/root, 150 MB /swap, and 450 MB /usr partition.  It's an external
Global Village 14.4 modem (the kind that came with the 6100 way, way,
waaaay back when).

                                                                Joseph Nebus
------------------------------------------------------------------------------

2. Date in seconds since 1/01/1901 at 1 AM

3. fsck on filesystems > 2 gig - a cruel hoax?

4. X-Windows/CDE for Linux

5. How to build ELF shared libraries -- A cruel hoax [;-)

6. Vancouver B.C Canada BSD Users Group

7. The cruel world of Alt-N

8. : Pipes and stderr

9. xman is treating me cruel

10. Thank you, Strider, for relating the cruel fate of your 19 family members

11. This clone thing...am I stupid, or am I right?

12. I am with the following error, when i am running lilo...