Bob Billson wrote:
>
> "Keith G. Murphy" <[EMAIL PROTECTED]> wrote:
> > > stats molec3 "*" -
> > > ^^
> > > Is this column supposed to be the local machine name? I can't find it
> > > documented anywhere.
> >
> > Yes, it is. It does seem to be very poorly documented. I think
"Keith G. Murphy" <[EMAIL PROTECTED]> wrote:
> > stats molec3 "*" -
> > ^^
> > Is this column supposed to be the local machine name? I can't find it
> > documented anywhere.
>
> Yes, it is. It does seem to be very poorly documented. I think once
> you fix that, you'll be in b
"Marc Mongeon" <[EMAIL PROTECTED]> wrote:
> My /etc/ppp/options also contains the following options:
>
> +pap
> -chap
Don't have that in mine, but it's worth a try. :-)
bob
--
bob billson email: [EMAIL PROTECTED] ham: kc2wz
(\
John Pearson <[EMAIL PROTECTED]> wrote:
> I have absolutely no idea why, but my slink boxes with ppp-pam
> installed require an extra field in pap-secrets for dial-in PPP
> to work, like so:
> richmolec3 "" * *
>
> If you still have problems after changing "molec3" to your hostname,
> t
On Mon, Sep 13, 1999 at 10:02:56AM -0500, Keith G. Murphy wrote
> Bob Billson wrote:
> >
> [cut]
> >
> > # Every regular user can use PPP and has to use passwords from /etc/passwd
> > #* molec3 "" *
> > richmolec3 "" *<--the only user allowed to run ppp
> Substitu
Bob:
My /etc/ppp/options also contains the following options:
+pap
-chap
Which requires the peer to use PAP and prevents it from using CHAP
to authenticate. I don't know how pppd handles defaults when these
options aren't present. Adding the "debug" option in the options file
will cause authen
Bob Billson wrote:
>
[cut]
>
> # Every regular user can use PPP and has to use passwords from /etc/passwd
> #* molec3 "" *
> richmolec3 "" *<--the only user allowed to run ppp
Substitute a real username and your machine name here.
>
> # UserIDs that cannot use PP
Good evening all... I'm trying to set up a friend's slink box do allow a
dial-up ppp login. pppd doesnt' want to cooperate. I'm going nuts
to figure what I overlooked.
I'm trying to use mgetty's AutoPPP feature. I have the AutoPPP line
uncommented in /etc/mgetty/login.config. I can log in, but
> By the way, the following is copied from /usr/doc/mgetty/README.debian
> High Baud Rates
> ---
> Linux supports 115200 and 57600 Baud, so does mgetty. But some to ols
> (notably rlogin and telnet) crash with a segfault at those high
> baudrates.
I used ppp as a poor-man's LAN f
As a test, can you replce the ATZ with a full init command (I use
AT&FE0V1&C1&D2S95=47S0=0M0 with my modem) ?
By the way, the following is copied from /usr/doc/mgetty/README.debian
"
High Baud Rates
---
Linux supports 115200 and 57600 Baud, so does mgetty. But some to ols
(no
On Sat, Feb 21, 1998 at 03:25:42PM -0500, Tim Sailer wrote:
> I wrote:
> > I just tried to shuffle modems. Only /dev/ttyC1 shows connect speeds.
> > That rules out modem settings.
>
> That makes me thing you need to look at /etc/mgetty.config. Check the
> per-port init strings.
This is it:
#
#
Jeff Noxon wrote:
> > > > > On Mon, Feb 16, 1998 at 01:06:59PM -0600, Jeff Noxon wrote:
> > > > >> I have three dial-in modems on my hamm box. They are all identical
> > > > >> USR Couriers AFIAK, and their configuration *appears* to be the same.
> > > > >> But one port always shows connect speed
On Thu, Feb 19, 1998 at 04:48:04PM +, David Wright wrote:
> On Thu, 19 Feb 1998, Jeff Noxon wrote:
>
> > On Wed, Feb 18, 1998 at 04:33:58AM +, [EMAIL PROTECTED] wrote:
> > > > On Mon, Feb 16, 1998 at 01:06:59PM -0600, Jeff Noxon wrote:
> > > >> I have three dial-in modems on my hamm box.
I guess I am only repeating what I have said before, but it realy odd.
Have you tried to dump the configurations and user profiles of the modems
(AT&V with my modem) ?
> The modem settings are identical. The modem firmware revisions are
> identical. The mgetty configuration lines are the same.
David Wright wrote:
>
> On Thu, 19 Feb 1998, Jeff Noxon wrote:
>
> > On Wed, Feb 18, 1998 at 04:33:58AM +, [EMAIL PROTECTED] wrote:
> > > > On Mon, Feb 16, 1998 at 01:06:59PM -0600, Jeff Noxon wrote:
> > > >> I have three dial-in modems on my hamm box. They are all identical
> > > >> USR Co
On Thu, 19 Feb 1998, Jeff Noxon wrote:
> On Wed, Feb 18, 1998 at 04:33:58AM +, [EMAIL PROTECTED] wrote:
> > > On Mon, Feb 16, 1998 at 01:06:59PM -0600, Jeff Noxon wrote:
> > >> I have three dial-in modems on my hamm box. They are all identical
> > >> USR Couriers AFIAK, and their configurati
On Wed, Feb 18, 1998 at 04:33:58AM +, [EMAIL PROTECTED] wrote:
> > On Mon, Feb 16, 1998 at 01:06:59PM -0600, Jeff Noxon wrote:
> >> I have three dial-in modems on my hamm box. They are all identical
> >> USR Couriers AFIAK, and their configuration *appears* to be the same.
> >> But one port a
> On Mon, Feb 16, 1998 at 01:06:59PM -0600, Jeff Noxon wrote:
>> I have three dial-in modems on my hamm box. They are all identical
>> USR Couriers AFIAK, and their configuration *appears* to be the same.
>> But one port always shows connect speed in wtmp, and the others do not:
>
> Are you sure
On Mon, Feb 16, 1998 at 01:06:59PM -0600, Jeff Noxon wrote:
> I have three dial-in modems on my hamm box. They are all identical
> USR Couriers AFIAK, and their configuration *appears* to be the same.
> But one port always shows connect speed in wtmp, and the others do not:
Are you sure that they
I have three dial-in modems on my hamm box. They are all identical
USR Couriers AFIAK, and their configuration *appears* to be the same.
But one port always shows connect speed in wtmp, and the others do not:
mystic:~$ finger
Login NameTty Idle Login Time Office Office Phone
j
> On Wed, 28 May 1997, Kevin Traas wrote:
>
> > This sounds like a device lock contention problem. Try using
> > /dev/ttyS1 for incoming (i.e. mgetty) and use /dev/cua1 for outgoing
> > (i.e. PPP).
>
> NO!
>
> Don't use cua devices for anything. They're obsolete and doing this will
> CAUSE locki
> On Wed, 28 May 1997, Kevin Traas wrote:
>
> > This sounds like a device lock contention problem. Try using
> > /dev/ttyS1 for incoming (i.e. mgetty) and use /dev/cua1 for outgoing
> > (i.e. PPP).
>
> NO!
>
> Don't use cua devices for anything. They're obsolete and doing this will
> CAUSE locki
> > What I am saying is that after I start mgetty for /dev/ttyS1, I
> > cannot access /dev/ttyS1 (like dailing to my isp using chat) anymore
> > which is not what the manual of mgetty suggests.
try putting the word "lock" in /etc/ppp/options.
also check your /etc/ppp/options and /etc/mgetty/mget
> > > I have a problem with mgetty. I have put an entry in /etc/inittab to
> > start
> > > mgetty. However, when I start the ppp process, it complains that
kernel
> > > lacks PPP support which is wrong. I look at the log messages and it
saids
> > > the device is busy.
> > > However, if I start mget
On Wed, 28 May 1997, Kevin Traas wrote:
> > I have a problem with mgetty. I have put an entry in /etc/inittab to
> start
> > mgetty. However, when I start the ppp process, it complains that kernel
> > lacks PPP support which is wrong. I look at the log messages and it saids
> > the device is bus
> I have a problem with mgetty. I have put an entry in /etc/inittab to
start
> mgetty. However, when I start the ppp process, it complains that kernel
> lacks PPP support which is wrong. I look at the log messages and it saids
> the device is busy.
> However, if I start mgetty by hand, I can start
Hello all,
I have a problem with mgetty. I have put an entry in /etc/inittab to start
mgetty. However, when I start the ppp process, it complains that kernel
lacks PPP support which is wrong. I look at the log messages and it saids
the device is busy.
However, if I start mgetty by hand, I can star
27 matches
Mail list logo
