[En-Nut-Discussion] Errors with ARP, DHCP, FTP, syslog and Ethernut 1.3-G

Harald Kipp harald.kipp at egnite.de
Thu Jan 27 10:30:28 CET 2005


Hi,

Sorry for not having sent a response to Dusan yet. During the
last days I've been busy with DHCP problems. The latest CVS
changes broke auto ARP: Starting a ping on Ethernut and
resetting the board will hang.

Beside that, DHCP error handling had been changed in a way, which
is not fully correct. If, for example, a broadcast transmit
fails, DHCP should not be restarted but give up and inform the
application. There are several other minor flaws and it is not
following RFC2131 in some parts.

Btw. I assume, that the syslog problem reported by Ralf is not
completely solved by fixing the ARP problem in the way Dusan
suggested.

Another one: Using an FTP server with Win32 Explorer makes
Ethernut fail. The Windows Explorer FTP is quite buggy (at
least on my W2K machine), but definitely Ethernut fails.

Finally there had been a problem with Ethernut 1.3 Rev-G.
Applications with external RAM access but without or late
RTL8019AS initialization fail with memory errors. This
had been fixed in CVS HEAD, btw.

This is a large list for the next release. Most of the
problems had been detected recently during extensive tests
of CVS HEAD and it took some time to analyze them. I still
hope to get it done within the very next few days.

Harald




More information about the En-Nut-Discussion mailing list