Re: [masq] [masq] pap login fails when nameserver traffic causes diald

1998-12-23 Thread Stefen Boyd
At 11:05 AM 12/23/98 -0600, Fuzzy Fox wrote: This just tells you that the connection opened, then closed. To get more information, start pppd with the "debug" option. Then it will show you the negotiation with the remote side. Beware, if you use PAP, your password will appear in the log.

Re: [masq] [masq] pap login fails when nameserver traffic causes diald

1998-12-23 Thread David A. Ranch
No, in diald, these addresses must be specified as placeholders, but don't do anything, as far as I can tell. The keyword "dynamic" in the diald.conf file helps guarantee this. Right.. I think you can use 0.0.0.0 though. --David

Re: [masq] [masq] pap login fails when nameserver traffic causes diald

1998-12-23 Thread David A. Ranch
I suppose pap comes from the MLPPP the modem tries to setup. I haven't been able to do the chat login with the isdn modem. You cannot run CHAT scripts with ISDN connections because ISDN is a syncronous connection vs. a modem is asyncronous. If you want to put an ISDN T/A into asyncronous

Re: [masq] [masq] [masq] pap login fails when nameserver traffic causes diald to bringup link

1998-12-23 Thread Stefen Boyd
At 11:11 AM 12/23/98 -0800, David A. Ranch wrote: I'm using a serial card that (due to a jumper) gives 4x what I ask. I'm pretty sure this is working ok since I'm seeing "CONNECT 230400" from the modem Ok.. that sounds good. What card is this anyway? Hayes ESP? LavaLink? Etc? Boca Turbo 2x2

Re: [masq] [masq] [masq] pap login fails when nameserver traffic causes diald to bringup link

1998-12-23 Thread David A. Ranch
1) The 16650 serial - modem isn't reliable at 230400 (using cable supplied with modem. I've heard that Linux's setserial has problems with 16650s. 2) My old 486SX can't keep up with 230400 even when using a 16650 I bet thats an issue too. --David