Quote:

You're right here. But:
1. MOSNet is not only "Native", it's also opensource. The only up-to-date opensource stack for the Amiga.
2. As i said - i'll try do do something in v0.17. In parallel i've currently continued to work on configuration editor.

@Sonic: first of all, 0.16 works for me absolutely stable, thank you.

I agree with Robin, that you should improve the speed.


If MOSNet is (or becomes) Miami-compatible, could the original PPPoE-Device be used? That would be an acceptable workaround, and you could focus on (in my eyes) more important issues.

Hi Sonic,

dhclient works properly now !

Gunne

Quote:

AFAIK (but may be i'm wrong, Miami users, clarify plz) Miami's pppoe.device is a physical-level device, not SANA-II one. It emulates serial.device and to use it you need to start regular PPP over this device.
AFAIK in *BSD is is done in the same way (it is regular PPP over TAP or TUN - again, *BSD wizards, correct me if i'm wrong). This means we need to get net/if_ppp.c and net/if_tun.c (or net/if_tap.c) and linked stuff from *BSD repository and fit this to MOSNet. This is not impossible task since MOSNet kernel is in fact BSD kernel. This just requires time.
Well, and again, i don't resist. If you want this feature there are several ways to go:
1. Just take this task to code yourself. I'll give you an access to the CVS, it's not forbidden.
2. Encourage some developers, probably by creating a bounty (or by other means, if you find ones).
3. Make an agreement with MorphBounties team (and other donors) about changing project's roadmap. Unfortunately i'm unable to clone myself to be able to work at PPP and GUI at the same time. Now i'm already working at graphical configuration editor, soon i'll produce experimental rebuld of the kernel (speedup attempt) and move to MiamiPanel support. I'll be unavailible from 29th December till 10th January because i won't be at work and won't have Internet access. Additionally, i change my job. This means i'll probably be unable to hang on IRC for the whole day. Anyway there's MorphOS mailing list, there's email, also MOSNet mailing list can be created in case of interest, there's this forum... I'll stay on line.

P. S. I'm glad that DHCP works flawlessly at last. 2 of 3 targets are complete now. Let's go for MiamiPanels!

[ Edited by Sonic on 2005/12/27 0:34 ]

Hi Sonic,

Here is some thoughts from me. Please remember just thoughts.

As dhclient now works properly, very great work, next logical step for me seems to be PPPoE.

A graphical GUI is of course also very nice. But going on/offline can also be made by launching a script through doubleclick on an icon, or by launching the script from the shell prompt (user-startup).

I do not myself have any possibilitie in doing any testing on PPPoE. Its not so very common used around here, but I know there is some isp's that uses it. I got the impression its more used by isp's in Germany ? The best would be if anyone who actually is using this, could do some testing.

Also how does it works using modem ? PPP, PAP, CHAP ?

Yes, miamipppoe is to set up in Miami as a 'serial type' device and mapped to the ethernet interface.

Anyway, the next step in the bounty says GUI.

Gunne

I dont see the point in PPPoE? All modern routers can do it for you. All the software "dialers" suck very bad from what I have seen in the past. Can you just used the stack to connect to your router or get a router if you dont have one and then have it do the PPPoE?

Quote:
The same. PPP, PPPoE and PPTP are the same from this point of view. There's no implementation currently. If it's done all 3 protocols will be usable. PPPoE and PPTP are implemented using a fake serial device which is tunnelled over ethernet.
Quote:
Correct. This is why i go for it.

[ Edited by Sonic on 2005/12/27 17:04 ]

Gelbsen

I've been really enjoying your posts... glad to see you active on MZ again..

magnetic


OH and Sonic keep it up and I vote for

MOScow tcp


or some varient of this. Also, that " I wish i could clone myself" bit was rather funny.

magnetic

ps: Acill you are really saying "buy a router" ??? LOL


pppoe support is important imho as many isp are using this protocol and buying a router is not an option for some people for a variety of reasons..

[ Edited by magnetic on 2005/12/27 10:27 ]

[ Edited by magnetic on 2005/12/27 10:29 ]

>1. Hm, seems that different people get different results. Not uncommon thing with Windows hosts... Probably things are not that bad.

seeing the feedback in this thread, it looks like all people
who have done speed tests get pretty bad results. there was one reporting telnetd.device got some higher cps,
but telnet was never intended as a binary transfer thing, and he didnt say how much he got and on what hardware.

Mosnet seems faster in responsetime and requesting all the urls for images on a www site seems faster,this is very good.

but in filetransfer on a local network it seems to perform 10-15 times slower that the hardware allows.

in my case on a pc and pegasos 50cm from eachother
both connected to a switch with around 1 meters of
cable, both have 100mbit nics, i get around 500k/s
copying from pc to morphos
(this is the same morphos_powerup.iso 27megs i've
been always speedtesting eztcp with)

i think it was v0.12 that copyed the file over in 35 secs,
thats around 8-900k/s but every version after needs
60-65 secs.

rebooting and launching miamidx on the same setup, i copy the file with 3000-3200k/s.

so something must be limiting the speed inside mosnet,
as the hardware,cables, windows host performs so'
much better with emulated 68k stack from the last
century.

Have you done any speed tests yourself ? i find it wierd
to start porting and enhancing this stack without
knowing its performance is reached first, isnt it
harder to track down its slowness after you have implemented feature after feature after feature ?

i doubt ferrari builders start polishing chrome and other eyecandy before they know the frame and engine and
everything technical having to do with its performance is 100% tuned first.

im not trying to be too negative here, but this is a very
important part of software for Morphos (a tcp stack)
and the bounty amount reflects this too, and
it would be a shame if its performance is this poor in the final build.

Catahogen:

Good points - performance should be main thing here. GUI Is not important as you just need On/Offline button.

The real mystery to me is that the Amitcp port for MOS performs better than Miami DX yet remains unreleased..

magnetic

Hi people,

I dont get it how you can manage to get so slow transfer rate ?

If I upload a file from my Pegasos running MorphOS -> Pegasos running Linux, I get around 4,7 Mb/s

Either using MOSNet or MiamiDX, only smaller not to note differences.

If i download a file to my Pegasos running MorphOS <- Pegasos running Linux, I get around 6.7 Mb/s

Either using MOSNet or MiamiDX, only smaller, not to note, differences.

Using Amitradecenter all the time.

I know of course that the average transfer speed should be around 10Mb/s, and thats also what it is if transfering between linux boxes.

Gunne

wooh....this sounds to good to be true.

and both a native ppc stack and emulated 68k stack
with same performance ?

Can it be that the hardware is in 'sync' ? pegasos/pegasos

Have you tried from and to a normal windows pc that everyone have ?
Have you tried with windows networking/samba since
thats more real day to day networking, instead of
ftp'ing stuff around the network.

With mosnet i cant even stream plain,normal torrent downloaded avi movies to my xbox, stutters all the time
because of slow transfer rate at the sending end,
streaming from pc in my garage, through wireless works
like a charm, its the same network as mosnet operates in, so its nothing wrong in the network.
i ftp to xbox in 9.8mb/s when using the pc.

maybe i should replace all my computers with pegasos'es..

Hi catohagen,

Well I am using an ordinary PC with Windows also. One, ordinary stationary one, is running Windows 2000, and is in the (cable)-lan.

With this machine I do communicate using Samba on the Pegasos with MorphOS. This as the MorphOS-machine then is available for accessing in Network Places in Windows. However I mainly only copy documents, pdfs and such things between them. So I have no idea how fast/slow that works, it works good the way I use it.

The other machine with Windows is a laptop running Windows XP and is dual booting Ubuntu. Its used in the wireless lan, so transfer with this is little bit slower, but the same with this, its not used for any heavely transfers, so it works as it works as to say .-)

For server purpose, communication and network, I feel that Linux is a much better and stable choice then Windows is. And Pegasos is a good and stable server platform with Linux.

And I do not think Samba/Windows is an ideal day to day solution. For transfering files between machines ftp is better, or even ssh as I believe. You can also mount partitions with NFS for instance for full access. Samba/windows have for me always been something aimed just for copying/accessing smaller files like documents etc things. And still there is software that needs Windows, however I do believe Linux will continue to become more and more popular also for office/desktop use.

Soo... Yeah, replacing all machines with Pegasos'es seems like a good choice to me...

Gunne

For proving Im not bluffing then

Download-window:

downloadsm.png

Upload-window:

uploadsm.png

MOSNet used for TCP.

Click on pictures for a larger view.

I'm getting ca. 2,3 MB/s from WinXP (Ceberus FTP) --> Peg1, and the other way 3,5 MB/s (both times ATC is used).

So, for me it's slightly faster than MiamiDx

http://prdownloads.sourceforge.net/unmorphos/MOSNet0.17.lha?download
Here is my last day online from the old job, so here is my Christmas present for you. This is mainly a bugfix, but also an attempt to speed up. Behcnmarkers, please don't be lazy to check this now. Probably things changed.
2 Alfie: Recheck all your tools, ascan works now. The problem was - beleive or not - D0 was used instead of A0 as event storage pointer in GetSocketEvents(). I really wonder how it worked at all with so many applications...
2 Leo: Please recheck your old resolving issue (wrong IP generation when DOMAIN is specified). Probably it's gone. If not, contact me and supply full log of the resolver operation.
2 AmiS (if you read this): i'll put init_inet_daemon() to RFE list, will be there in v0.18's netlib. set_socket_stdio() won't be there, i've already explained why and what to do instead.

Bleh Sourceforge, hurray MZ

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

UPDATE: Yes I get over 150k/sec with MiamiDX on the same file.

Hmm seems slow to me as well. I am on it now and I downloaded an MP3
podcast called the maccast. I got an averge speed of only 80k/sec on
my cable modem. I get much faster speeds on the Macs like between 300
to 600k/sec. I will post again after I transfer with MiamiDX to see
the speeds.

[ Edited by Acill on 2006/1/1 5:33 ]

[ Edited by Acill on 2006/1/1 5:47 ]

Could it be that, on some setups, MorphOS itself is spitting errors to the log "file" l¡ke a machine gun, thus slowing everything down?

boot with the option RAMDEBUG

Quote:

Question: Even sending the log to RAM should slow things down, right? Wasn't there an option to show log output directly in a window, to be sure if this is actually happening?

Quote:
That would be "LOGSERVER". I use it together with "RAMDEBUG"

Oh, and obviously printing to window is likely MUCH slower than just storing the information in ram.