1. Found out all problems with ascan. It's ba-a-a-dly written.
2. Checked out hserv issue and found the bug. FD_ACCEPT is never generated. Will be fixed.

Nhaaaa ascan was written centuries ago for sasc and the rael amiga !!!11 :p

BTW, may be it's time to upgrade it a bit and add a NetInfo1.4-alike graphical interface to it? Would be great!

I incorporated all the changes and everything is fine right now. DHCP already sets up DNS servers. However i delay v0.15 a little since i would like to implement some other DHCP options and close this stage completely.

Have just finished coding the rest of things. Now i need just to test everything anv v0.15 will be ready.
Then some testing period will follow, during it i'll move my activity to configuration editor. If no critical bugs are found, i'll start implementing MiamiPanels support. v0.16 will come with them then.

this is a very very good news. I'll test this version 0.15.

Thank you very much and merry christmas

[ Edited by serge on 2005/12/23 3:48 ]

Whoo! With DHCP done I will at last give it a try. Thanks for all your work. I cant wait to see it in action.

BTW/ Can anyone that has been using this to get on the internet tell me if its faster then using MiamiDX? I've tried Genesis and didnt like it, so if this is faster it would give a good reason to change.

Quote:

Hey Acill m8!
Its much faster. Ive been using MiamiDX before.
After switching to ezTCP, the CPS on the telnetd.device in the bbs was much better.
The Throughput is faster so i guess it will be with everything.

http://sourceforge.net/project/showfiles.php?group_id=133480&package_id=171550&release_id=380317

DHCP support complete! Also some fixes incorporated.
2 Alfie: Please test hserv, should work now. About that daytime script - i didn't care for now, it's just a demo script. If someone finds the same issue in a real working application, i'll deal with this immediately.
2 Leo: debug version is for you and your strange DNS. Please contact me and get a detailed instruction, preferrably on IRC to be able to do something interactively.

Sorry a bit, some minor issues were discovered, in addition some DHCP support functions should be done in a better way than they are now. So i'll start MiamiPanels in v0.17. v0.16 will be there next week and there i'll rewrite the code in order to kill all flaws.

really great work Sonic!

Quote:

Genesis is still *much* faster than the current ezTCP (approx 5x on my system), and that's why I haven't changed.

If one cannot achieve decent transfer speeds, the stack is pretty useless for me. I've seen MOS1.5's Amitcp-implementation in action, and it performs over 10mb/sec. With ezTCP I get between 1-2mb/sec.

And the latest update can ofcourse be found here:

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

Quote:

Then speed must be ramped up! The whole point of having a PPC native stack just goes away if it is slower than emulated 68k stacks!

Finished rewriting NetDB handling. v0.16 needs only to be compiled, debugged and released.
WARNING!!! A VERY BIG BUG in v 0.15: dhclient doesn't work correctly. For those who know: i've forgotten RTF_GATEWAY flag at default gateway setup. The result is: you can't ping anything outside of your subnet.
A workaround is to execute a sequence of three commands after starting up dhclient:
Wait 15
route delete default
route add default <your_gateway>
15 seconds delay is needed for the dhclient to set up the interface. I am really rerribly sorry for spoiled party...
This is already fixed in the CVS. v0.16 will be rocking! :)

Why the heck is is slower then the emulated stack in Genesis then? I dont understand that at all. The only reason I dont use Genesis now is its lack of DHCP (I have a router and dont NEED it, but I like it) and I never could get it to come online by itself and be hidden away at bootup like I do with MiamiDX. Solve those issues and I am a convert.

Acill,

Give Sonic little time. Its not an very easy task to write a TCP-software.

Probably it will be perfectly working dhclient in next build now. Then perhaps work to look for how to optimize things as for speed for transfers, could start ?

Gunne



[ Edited by gunne on 2005/12/23 22:25 ]

Quote:

I read in an earlier thread that arosTCP is based on some pretty old algorithms.

Well it seems to be faster then Miami and thats fine for me. I guess the code that amiTCP found in genesis was much better then was Sonic started with from the Aros port. All I hope for now is some good GUI tools and setup features. Its a nice app as it is now. Well worth the time put in.

Whats nice is soon will have no more questions from new users about Miami Keys. We can at last direct them to the MorphOS native stack to use.

lo,
i have fixed the startnet and stopnet script to work correctly with MOSnet v0.15
startnet also include the gateway-workaround to get dhcp working.
to get MOSnet working just follow this steps:
1. download MOSnet, unpack it and copy it to hdd
2. download http://www.morphos-news.de/temp/MOSnet_Starter.lha , unpack it and copy startnet to sys:c and stopnet to MOSnet/c
3. edit sys:c/startnet to your needs ... if you have a dhcp server you only have to set the right path to MOSnet on your hdd and the gateway ip.
4. to go online using dhcp, type the following command in shell "startnet ip=dhcp" ... if you made allright you are online. you can also use "startnet ip=dhcp debug" to get some debug output.
5. to go offline just type "stopnet" to shell

cu the antibike

Hi,

Nice script antibike !

No time try it right now, but later.

Gunne

Hello all!
http://prdownloads.sourceforge.net/unmorphos/MOSNet0.16.lha?download
I really hope that this time everything is okay.
As to the speed questions...
1. Hm, seems that different people get different results. Not uncommon thing with Windows hosts... Probably things are not that bad.
2. This is v0.16 and it should be stable. Okay, i give a little time to test it. If it's really stable, i'll produce an experimental kernel build with some things changed. PROBABLY it will speed it up. PROBABLY it will make it unstable, i don't know yet. This is why i haven't introduced these changes yet. I beleive you wouldn't like if i for example fix DHCP but break the kernel and next release you've waited for so much is completely unusable.
A big schedule for v0.17 is MiamiPanel support. I will start with it as soon as v0.16 is proven to be stable and bug-free. Panels support requires another set of major rewrites in the kernel.

Just to boost my number of posts: you can of course download MOSNet v0.16 from MZ as well.

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

That's very good news!

Do you have any idea how much effort it would need to add PPPoE support?

Regards,
Jürgen

@Sonic

Speed should be a more important goal for you.
Where is the sense in having a native stack
when it is slower than the emulated alternatives ?

Heh, nice... First real feature request...
1. Of course it can be implemented.
2. Not a week or two. Probably 1-2 months... There are two ways to implement it:
a) Write a PPPoE SANA-II device from scratch.
b) Take a PPPoE implementation from *BSD and integrate it into the kernel.
I guess (b) is prefferred since there's no need to write anything from scratch and in-kernel PPPoE is more efficient and would be easier to set up. IMHO SANA-II drivers are designed for hardware abstraction. Protocol abstraction is simply not their job.
Currently i am unable to write the support because:
1. I don't have time.
2. I don't have good testbase.
It is possible to raise this topic again. The project becomes huge and it can be divided. I would suggest to break it into subtasks. Implementing PPP and PPPoE (they are linked together) could become one of these subtasks.