Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 20 Jan 1998 01:55:54 +0700 (KRS)
From:      Victor Sudakov <vas@vas.tsu.tomsk.su>
To:        brian@Awfulhak.org (Brian Somers)
Cc:        dwhite@resnet.uoregon.edu, questions@FreeBSD.ORG
Subject:   Re: iijppp + slirp
Message-ID:  <199801191855.BAA10209@vas.tsu.tomsk.su>
In-Reply-To: <199801182005.UAA09709@awfulhak.org> from "Brian Somers" at "Jan 18, 98 08:05:31 pm"

next in thread | previous in thread | raw e-mail | index | archive | help
Brian Somers wrote:
> > Doug White wrote:
> > > On Thu, 15 Jan 1998, Victor Sudakov wrote:
> > > 
> > > > Could you please help me make iijppp work with SLiRP on the server side?
> > > 
> > > How is SLiRP called?  You aren't running it in your dialup script..
> > 
> > It is started automatically after logging in into the server. I think, the
> > login shell is set to slirp.
> > 
> > > 
> > > > I start ppp as 'ppp -auto phantom'. It logs in but is never up, and the
> > > > default route is not changed. The /var/log/ppp.log grows though :-) It works
> > > > fine with the non-slirp provider BTW (the other entry called mpeks).
> > > 
> > > Did you look in the ppp.log to find out just why it won't connect?  You
> > > can post the relevant section(s) if you want us to decode it.  Post a
> > > sample attempted connect to phantom.
> > 
> > Sorry for the very long log.
> > 
> > ======= cut here =========
> [.....]
> > Jan 15 01:47:02 vas ppp[6649]: tun0: LCP: Magic is same (6a212a75) - 1 times 
> > Jan 15 01:47:03 vas ppp[6649]: tun0: LCP: SendConfigNak(Req-Sent) 
> > Jan 15 01:47:03 vas ppp[6649]: tun0: LCP:  MAGICNUM[6] 0x6a212a75 
> [.....]
> > ======= cut here =========
> > 
> > I would appreciate any input.
> 
> There's a bit in the FAQ (http://www.freebsd.org/FAQ/userppp.html).  
> Remove the "set openmode active".  If the peer never bothers to say 
> anything, drop me a line.  It's possible that there are some really 
> brain-dead ISPs out there that can't switch off ECHO on the line 
> quick enough to avoid confusing their ppp implementation with the 
> resulting flurry of REQ/NAKs for the magic number, and *also* can't 
> initiate LCP negotiations.... Once someone gives me an excuse, I'll 
> introduce a configurable delay :-)
> 

Well, when I remove "set openmode active", just nothing happens. I suppose
this is because SLiRP never bothers to say anything but this:

========= cut ===========

phantom: {1} slirp
Slirp v1.0c (RELEASE)

Copyright (c) 1995,1996 Danny Gasparovski and others.
All rights reserved.
This program is copyrighted, free software.
Please read the file COPYRIGHT that came with the Slirp
package for the terms and conditions of the copyright.

Reading config file: /usr/home/vas/.slirprc
Setting baudrate to 38400
IP address of Slirp host: 195.9.35.51
IP address of your DNS(s): 195.9.35.1
Your address is 10.0.2.15
(or anything else you want)

Type five zeroes (0) to exit.

[talking PPP, 38400 baud]

SLiRP Ready ...

========= cut ===========

... after which it just stops and waits for something. I never see those
{{{{ characters which indicate a ppp session. So iijppp never detects packet
mode :-(((

The log in this situation looks like this:
========= cut ===========

Jan 20 01:43:22 vas ppp[9636]: tun0: Connect: phantom.obluo.tomsk.su!login:
Jan 20 01:43:22 vas ppp[9636]: tun0: Chat: sending: XXXXXX^M
Jan 20 01:43:22 vas ppp[9636]: tun0: Chat: Expecting word:
Jan 20 01:43:22 vas ppp[9636]: tun0: Chat: Wait for (5): word: --> word:
Jan 20 01:43:22 vas ppp[9636]: tun0: Connect: XXXXXX^M
Jan 20 01:43:23 vas ppp[9636]: tun0: Connect: Password:
Jan 20 01:43:23 vas ppp[9636]: tun0: Chat: sending: XXXXXX^M
Jan 20 01:43:22 vas ppp[9636]: tun0: Connect: XXXXXXXX^M
Jan 20 01:43:23 vas ppp[9636]: tun0: Connect: Password:
Jan 20 01:43:23 vas ppp[9636]: tun0: Chat: sending: XXXXXXX^M
Jan 20 01:43:23 vas ppp[9636]: tun0: LCP: State change Initial --> Closed
Jan 20 01:43:23 vas ppp[9636]: tun0: LCP: State change Closed --> Stopped

[here I became impatient after looking at 'tail -f ppp.log for three minutes]

Jan 20 01:46:32 vas ppp[9636]: tun0: Phase: Connected to client from
127.0.0.1:4
100
Jan 20 01:46:34 vas ppp[9636]: tun0: Phase: Client connection closed.
Jan 20 01:46:36 vas ppp[9636]: tun0: Phase: Connected to client from
127.0.0.1:4
356
Jan 20 01:46:40 vas ppp[9636]: tun0: Phase: NewPhase: Terminate
Jan 20 01:46:40 vas ppp[9636]: tun0: LCP: State change Stopped --> Closed
Jan 20 01:46:40 vas ppp[9636]: tun0: Chat: Dial attempt 1 of 4
Jan 20 01:46:40 vas ppp[9636]: tun0: Chat: Expecting
Jan 20 01:46:40 vas ppp[9636]: tun0: Chat: sending: ATZ^M
Jan 20 01:46:40 vas ppp[9636]: tun0: Chat: Expecting OK-AT-OK
Jan 20 01:46:40 vas ppp[9636]: tun0: Chat: Wait for (5): OK --> OK
Jan 20 01:46:45 vas ppp[9636]: tun0: Chat: Can't get (5).
Jan 20 01:46:45 vas ppp[9636]: tun0: Chat: sending: AT^M
Jan 20 01:46:45 vas ppp[9636]: tun0: Chat: Wait for (5): OK --> OK
Jan 20 01:46:55 vas ppp[9636]: tun0: Chat: Can't get (5).
Jan 20 01:46:56 vas ppp[9636]: tun0: Phase: Modem: Connect time: 240 secs:
843 o
ctets in, 0 octets out
Jan 20 01:46:56 vas ppp[9636]: tun0: Phase:  total 3 bytes/sec
Jan 20 01:46:56 vas ppp[9636]: tun0: Phase: Enter pause (3) for redialing.
Jan 20 01:46:56 vas ppp[9636]: tun0: Phase: Client connection closed.
Jan 20 01:46:56 vas ppp[9636]: tun0: Phase: PPP Terminated (normal).
(END)
========= cut ===========

Needless to say, win95 works. Shit.

-- 
Victor Sudakov
mailto:vas@obluo.tomsk.su
http://www.obluo.tomsk.su/~vas
PGP public key: finger vas@obluo.tomsk.su



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199801191855.BAA10209>