[En-Nut-Discussion] Re: Trying to work with PPP

Mike Cornelius mikec at call-direct.com.au
Sat Dec 18 00:29:15 CET 2004


Eduardo and Harald,

I have a version of PPP which supports CHAP (and has done so for at least a
year) I'm supprised it's not made it back to the main distribution (I
probably forgot to let anyone know).

I've not got the time to do a diff and tes between my PPP code and the main
distribution though so could anybody with the time to do so let me know and
I'll forward my code to you.

The atmega can easily do MD5 fast enough for CHAP, I've never actually timed
it but it's in the order of milliseconds.

For reference it can also do 1024 bit RSA in about 1.5 seconds with a 7.32
MHz crystal. 

Regards,

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Mike Cornelius                      Internet: mikec at call-direct.com.au
Call Direct Cellular Solutions      Phone:    +61 2 9209-4259
Suite 145                           FAX:      +61 2 9209-4196
National Innovation Centre          URL:      http://www.call-direct.com.au
Australian Technology Park
Eveleigh NSW 1430
Australia                  
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


-----Original Message-----
From: en-nut-discussion-bounces at egnite.de
[mailto:en-nut-discussion-bounces at egnite.de] On Behalf Of Harald Kipp
Sent: Tuesday, 14 December 2004 6:45 PM
To: Ethernut User Chat (English)
Subject: Re: [En-Nut-Discussion] Re: Trying to work with PPP

Eduardo,

It's the other way round. Ethernut PPP can do PAP only, not CHAP. If your
provider doesn't support PAP, you're lost unless you enhance the Nut/Net
stack. But no idea wether the ATmega is able to calculate CHAP encryption in
time.

Harald

At 18:10 13.12.2004 +0100, you wrote:
>Hi again,
>
>I don't resign in my particular game with the PPP (sorry), but I am not 
>an expert in it (in fact I'm new in that field). After testing the 
>fantastic Serial Analyzer of Mike Cornelius (THANKS!!!), I can put some 
>questions on the board about the behaviour of Ethernut (2.1B):
>
>1- I have noted that the Packet identifier starts at 0x01 (usually it 
>starts at 0x00) with a CHAP MD5 request, it sends the 0x02 identifier 
>with the same request, and then it sends a simple packet with the Async 
>Control char map and the magic number WITH IDENTIFIER 0x01 (should it 
>be 0x03????)
>
>2- The ISP sends Nak to all the requests and proposes PAP as 
>authentication protocol. Ethernut insists in CHAP, and sends a 
>Termination request again with identifier 0x01!!
>
>3- I have configured my PC in order to emulate the connection under 
>CHAP and the ISP works ok. In fact the PC sends the same packets that 
>Ethernut sent, but without repeating the identifier numbers.
>
>4- Is it possible to change the parameters of PPP in Ethernut? (change 
>CHAP to PAP, ...)
>
>Any suggestions? Any known bug?
>
>Thx,
>
>Eduardo

_______________________________________________
En-Nut-Discussion mailing list
En-Nut-Discussion at egnite.de
http://www.egnite.de/mailman/listinfo.cgi/en-nut-discussion




More information about the En-Nut-Discussion mailing list