wlug-request(a)list.waikato.ac.nz wrote:

Send wlug mailing list submissions to wlug(a)list.waikato.ac.nz

To subscribe or unsubscribe via the World Wide Web, visit http://list.waikato.ac.nz/mailman/listinfo/wlug or, via email, send a message with subject or body 'help' to wlug-request(a)list.waikato.ac.nz

You can reach the person managing the list at wlug-owner(a)list.waikato.ac.nz

When replying, please edit your Subject line so it is more specific than "Re: Contents of wlug digest..."

Today's Topics:

1. Connecting to KOL with dialup (Michael McDonald) 2. Re: Connecting to KOL with dialup (John Rye)

----------------------------------------------------------------------

Message: 1 Date: Sat, 21 Mar 2009 09:52:25 +1300 From: Michael McDonald <mikencolleen(a)gmail.com> Subject: [wlug] Connecting to KOL with dialup To: Waikato Linux Users Group <wlug(a)list.waikato.ac.nz> Message-ID: <e58eb89b0903201352x36c95734hd9eb5f1c77082e69(a)mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1

I set up a user with a trial of Ubuntu, an external modem, and a KOL connection. (Would be lovely to have broadband, but in this situation broadband is "not on").

Dialup seems to be changing! I had a few problems during testing connecting to Xtra (see http://wlug.org.nz/Xtra ) ... Xtra's prompts upset wvdial. I thought "Oh well, if I can get Xtra to connect, I ought to be able to get KOL to talk using the same technique".

Trying the usual methods of connecting didn't give any joy, so I used putty to find out what was happening. Name and Password was fine, but then KOL responded with a binary string, repeated every second or so, 6th byte incrementing, for a while and then disconnected. The string is ...

ff 03 c0 21 01 dc 00 12 01 04 7f d5 03 04 c0 23 05 06 77 2d 1d b1 (dc was the byte that incremented with each message)

Is this familiar to anyone? I haven't rung KOL as the website claims no support for Linux, and I wouldn't expect normal help-desk staff to be able to answer that query anyway. At worst, I've donated, $10 to KOL!

Now that the user has the computer, I've got to set up another one for testing. :-) (Not a problem!)

Any suggestions?

Michael

------------------------------

Message: 2 Date: Sat, 21 Mar 2009 10:51:10 +1300 From: John Rye <jrt746(a)clear.net.nz> Subject: Re: [wlug] Connecting to KOL with dialup To: wlug(a)list.waikato.ac.nz Message-ID: <20090321105110.8b7ad732.jrt746(a)clear.net.nz> Content-Type: text/plain; charset=US-ASCII

On Sat, 21 Mar 2009 09:52:25 +1300 Michael McDonald wrote:

...

I set up a user with a trial of Ubuntu, an external modem, and a KOL connection. (Would be lovely to have broadband, but in this situation broadband is "not on").

Dialup seems to be changing! I had a few problems during testing connecting to Xtra (see http://wlug.org.nz/Xtra ) ... Xtra's prompts upset wvdial. I thought "Oh well, if I can get Xtra to connect, I ought to be able to get KOL to talk using the same technique".

Trying the usual methods of connecting didn't give any joy, so I used putty to find out what was happening. Name and Password was fine, but then KOL responded with a binary string, repeated every second or so, 6th byte incrementing, for a while and then disconnected. The string is ...

ff 03 c0 21 01 dc 00 12 01 04 7f d5 03 04 c0 23 05 06 77 2d 1d b1 (dc was the byte that incremented with each message)

Is this familiar to anyone? I haven't rung KOL as the website claims no support for Linux, and I wouldn't expect normal help-desk staff to be able to answer that query anyway. At worst, I've donated, $10 to KOL!

Now that the user has the computer, I've got to set up another one for testing. :-) (Not a problem!)

Any suggestions?

Try setting your /etc/ppp/options like this: ===== lock noauth defaultroute ipcp-max-configure 65 ipcp-accept-local ipcp-accept-remote idle 600 =====

This works for me

John

------------------------------

_______________________________________________ wlug mailing list wlug(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/wlug

End of wlug Digest, Vol 213, Issue 10 *************************************

Try installing Gnome-ppp and set it to run "Stupid mode" in other words ignore init strings. Quite a while since I did it, but I got it to work. I think gnome-ppp is the only one that works because it can be set to ignore init strings. Hope that helps Dave