And here are my words tured into working code:
https://sourceforge.net/project/screenshots.php?group_id=133480&ssid=22376
As you can see here, DHCP client at last obtained an IP from the server. All i need now is to replace that "Running script" with C function configuring the interface (there is no script and will never be, it's just a stub function which just prints parameters with which the script would be called).
I really hope i'll produce a new beta soon.

YES! When DHCP is in a beta that I can get I will use it at last! I cant wait. Thanks again Sonic, well done!

its coming along great sonic thanx for all your hard work so far =).

Heh... Decided to make next report just so as not to be quiet...
1. Updated kernel and environment components are built. Not everything works as expected, errors are non-fatal (netstat shows nothing, ifconfig doesn't show MAC addresses). I guess something is wrong in my kvm_read() function. "ifconfig" tool is now re-adopted from NetBSD because FreeBSD implementation is poor. NetBSD doesn't use that KVM crap and therefore doesn't introduce additional problems. Probably all future development will be based on NetBSD and not FreeBSD.
2. DHCP client itself is being finished, additional interface configuration routines are being written.
I really hope everything will settle up next week. This is a very large update, that's why so much work is required.

[ Edited by Sonic on 2005/12/1 17:49 ]

You do a wonderfull job Sonic. I will use your tcp/ip stack forever, just to show my support. Thanks for beeing so supportive! And all of you reports on how your progress is going on,..

Thanks again!


Regards,
Michal

Quote:

Wow. Forever? Will you marry it? ;)

Yes ;p

Well, well, here are the latest news:
1. ifconfig utility fixed - works.
2. netstat utility actually works but requires to implement some additional functions. So - left out for now. However it perfectly serves my debugging needs - dumping routing table.
3. DHCP client modifications are being finished.
So - soon v0.14 will be delivered. Thanks to all for your support.

Looking forward to it, will it have a GUI and be easy to install and setup?

http://prdownloads.sourceforge.net/unmorphos/ezTCP0.14.lha?download
Sorry, no new GUI parts yet. I will start MiamiPanel support as soon as DHCP support is 100% finished and tested.
I modified the configuration editor a bit, it looks much better now. Probably after some time you'll see first screenshots.

Or download it here :

https://morph.zone/modules/mydownloads/singlefile.php?lid=334

By the way: Don't know if someone did mention this before already, but as someone pointed out at amiga-news.de today, there is already a commercial product called ezTCP, too.

http://www.eztcp.com/

Sounds like it's time for a poll with a new name for what was once called ezTCP... Ideas?

Hi, I can't compile the Ambient Source with the MOS SDK.
The Error Messages are "permission denied" or "write protected." With Miami it works fine.

Greets
SkyRider

|||

[ Edited by Velcro_SP 24.09.2011 - 04:12 ]

Or Sonic TCP?

EasyTCP
MiniTCP
MorphTCP
SonicTCP
BlueTCP

MOSConnect
MorphConnect
MorphNet

etc. etc.

Huh... Could you explain the situation a bit more detailed?
What does actually happen? When? Under what conditions?

This must be a problem with ixemul apps and usergroup.lib from
ezTCP. There is also problem with my OpenSSH port - it hangs,
when launched with usergroup.library from ezTCP. Also cvs tool was
reported not to work correctly. When I replaced the lib with
usergroup.library from AmiTCP all ixemul apps works
fine.

Did you try to leave my usergroup.library and put netinfo.device to devs: ? Probably those tools ask the OS for current username and netinfo.device is needed for that crap. I didn't build it yet because i was pretty sure applications can work without it.
Okay, i'll research the problem.

MorphConnect sounds adequete

I'd rather go for a shorter name, like mosnet.

MZNet! Just kidding about that. Due to historical reasons, I would think that Magic#? would be appropriate naming conventions too. In the other thread, we see that there will be a bit more to what eztcp is than just a TCP/IP stack. So, a #?net would be better than #?TCP.

We could call it a city name, as Mr. Kruse was so fond of in his time (Miami, Daytona, etc). How about pulling out our astronomical encyclopedia, and use a name of a moon in the solor system? Ganymede, Titan, etc.

GaiaNet :)

How about just NetStack or something obvious like this.

Every new user (hoho) will know immediately what it is for without reverting to grab the mos dictionary of cryptic and obscure program names.