Replies interspersed below.
At 10:07 AM 4/19/00 +0200, TAG wrote:
>Hi,
>
>OK - is pppd running ??
How would I know? Try "ps ax |grep ppp" to see if it is. Or see what the
logs tell you.
>Also - I hate having to test it like that - but that is the only way it
>can be done now!!
Huh? Do you mean the "su" piece of your script?
>I have no clue on how to get it to run from mgetty
Well, I already suggested you consult the documentation for mgetty. Did you?
Did it offer no "clues"?
>and what the error
>message is associated with the "remote system is required to
>authenticate" ??
It seems clear enough to me on its face, and I tried to explain it in my
prior response. Did you check the pppd documentation as I suggested? To what
effect? If something in the docs, or in my prior answer, is unclear, try
asking a question about it. Just saying "no clue" is hard to respond to.
>> >pppd: By default the remote system is required to authenticate itself
>> >pppd: (because this system has a default route to the internet)
>> >pppd: but I couldn't find any suitable secret (password) for it to use to
>> >do so.
>>
>> What is address 192.168.1.74? Which end of the connection? How is it being
>> assigned? What networks does the host support (what is its routing table,
>> for example)? This may just be the same options problem as before, but
>> without seeing your ppp setup (the relevant options file(s) or command-line
>> arguments) I can only guess.
>
>
>OK - the 192.168.1.74 - is the internal ip address that is available to be
>given to the client!! It is not being assigned it is set manually in
>dial-up networking on the client side!!
This is just a terminology mismatch. pppd is assigning the address to the
"client" host. That's all I was asking about. A host can also (try to) set
its own ppp address; this rarely works, given the usual way ppp "server"
ends are set up.
>The server is on the 192.168.1. network - here is the options.server file:
>
>-detach
>asyncmap 0
>modem
>crtscts
>lock
>proxyarp
>ms-dns xxx.xxx.xxx.xxx
>ms-dns yyy.yyy.yyy.yyy
>
>the options file is the same!!
As I suggested in my prior message, try adding "noauth" and see if that
eliminates the error.
>
>The options.ttyS0 is:
>192.168.1.71:192.168.1.74
>
>the first is the internal IP of the server - the second is the IP assigned
>to the client???
I'm confused again about server and client. All these files are on your
server, right? And it gets a call from your Win98 host, then hangs up and
dials back to it? If so, except for the "noauth" part, it all looks fine on
the Linux end.
------------------------------------"Never tell me the odds!"---
Ray Olszewski -- Han Solo
Palo Alto, CA [EMAIL PROTECTED]
----------------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.linux-learn.org/faqs
