How could it be removed? If I simply leave it blank, MosNet refuses to
start. I don't know of anything sensible to put there (anything that
does not cause a delay).

resolv.conf, "seems" to accept multiple DNS (as AmiTCP after all)

i have f.e.:

domain alice.it
nameserver 80.20.6.xx
nameserver 212.216.112.xx

Try to use an alternative DNS (if any)

It works here, without any delay.

Is there non removed debug code?
found out that i get this strange traffice on the network
192.168.123.3 192.168.15.88 syslog
Pegasos IP DestinationIP Servicename

Only noticed as the dest ip routes into another network on 255.255.255.0 subnet mask.

Also i found strange traffic to
80.82.220.60 Port 8888
If opend in a webrowser:
http://80.82.220.60/

The Page says
"Secret...messages"

Im not sure anymore if the source IP was from the pegasos too, the logfile got truncated to fast.

any ideas?

Well, this IP is conected to vapor.com, so my guess this is propably to verify AmIRC or other Vapor Products.

This ip reverse resolves to http://boron.vapor.com/

Well ok thanks, anyway its strange.
Guess nobody likes "Calling Home Software"

I will block it then (Is this windows?)

Still the strange private ip left. Looks like debug stuff.

probably that vapor.com traffic, is due the vapor_xxx.library, i guess . . or hope!

"Still the strange private ip left. Looks like debug stuff."

but, that IPs are in your local IP range? (i'm only trying to understand me too, so sorry for the stupid questions)

i.e if you do an ifconfig -a from shell

> ifconfig -a
lo0: flags=9<UP,LOOPBACK> mtu 1536
inet 127.0.0.1 netmask 0xff000000
eth0: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX> mtu 1500
address: 00:c0:26: :97:
inet 192.168.. netmask 0xffffff00 broadcast 192.168.xxx.xxx

then PING to the broadcast address (mine 192.168.xxx.xxx)

PING 192.168.xxx.xxx (192.168..): 56 data bytes
64 bytes from 192.168..: icmp_seq=0 ttl=255 time=2 ms
64 bytes from 192.168..: icmp_seq=0 ttl=30 time=2 ms (DUP!)
64 bytes from 192.168..: icmp_seq=1 ttl=255 time=1 ms
64 bytes from 192.168..: icmp_seq=1 ttl=30 time=2 ms (DUP!)

do you get DUPs?

Quote:

Remove just a DOMAIN line.

Ok, the syslog thing was nonsense.

I got it mixed up due to a new dhcp configuration.
It was my dbox (digital receiver) and not the peg.
But the vapor.com shit is still running (but blocked)..
well...

MosNet still fails here when I use bittorrent with a popular torrent
(related to too many connections, probably). I increased TCP_SendSpace
and TCP_RecvSpace (in db/general.config) but I still get lots of error
messages saying:
m_clalloc: max amount of memory already used (1045424 bytes).
sana_read (eth): not enough mbufs

There's a dozen or so repetitions, and the network ceases working. Is
this 1 meg limit hardcoded somewhere or is there another option?

here i have 32768 for both as buffer size but AFAIK, with this values you will have very slow transfers on your local LAN (don't ask me why).

I've actually given up on it. Its nice having a native stack for MorphOS at last, but the bugs and problems I have with it are not worth it. Since i get much faster transfers ising MiamiDX and since I paid for my keys a long time ago I continue to just use that.

If MOSnet is capable of working better with just some config file edits I would recomend we get some good solid docs done for it. We all paid a lot for it, why not make it work as it should eh?

Mosnet stops working here after a while when using ATC and downloading a large file (large = >~ 100Mb , have not yet notised any problems with normal size files). The traffic just stops and going offline and then back online is enough to continue....

The following changes seem to have solved all urgent problems for
me:

In mosnet:db/resolv.conf

- comment out everything with a # at the beginning of each line

In mosnet:db/general.conf

Use the following lines:
TCP_SendSpace=8192
TCP_RecvSpace=16384
MBUF_CONF MaxMem=4096

Possibly you may want to increase TCP_SendSpace even further, though
this seems enough for me.

I'm back to mdx,too ...
The dns-resolve is way too slow and
the connectionspeed is too ... on a
600mb file copied with scp to my
webserver it's been 30% slower compared
to mdx and thats the "slowest" amiga tcp-ip stack.

>t's been 30% slower compared
>to mdx and thats the "slowest" amiga tcp-ip stack

Set recv and sendspace in MaimiDX to 50000 and it will be much faster, too.


[ Edited by Wishmaster on 2006/5/7 15:25 ]

The dns slowness can be fixed (see my previous post), but sure.. it's
not the fastest or best stack in existance. It's available though and
much better than nothing at all.

Merko:

>The dns slowness can be fixed (see my previous post)

Well, can you please explain me how then I accomplish
to resolve internet names if I remove all resolf.config
entries ? If I do so, I cannot go to the outer world
anymore. Also I defined my local domain name
in resolv.config. Perhaps I can put it somewhere also ?

@Wishmaster

My mdx installation is so old (I just copied from my a1200)
that I've made similar setting half a decade ago

@merko

You can speed up the dns, still it's too slow ... takes
sometimes nearly half a second to resolve a name.
That sounds not much but I'm going through websites
really quick and it's a pita to see Voyager hanging
there for a second before transmitting the site starts.

MDX is the better choice for those of us who are lucky
enough to be the owner of a mdx-key ...

[ Edited by Robin on 2006/5/7 9:16 ]

Sorry Elena, there was some crucial info missing: Those settings are
valid if you use DHCP. If you're not, you need to put your own info
there of course as the docs explain. The docs never explain that you
need to remove this stuff if you use DHCP, however.

Robin: Hmm, I don't have such delays. I agree it would be highly
annoying.

Merko: Thanks for the tips. they do seem to help speed hings up here, but still not wuite as fast as MDX. Its a good start though.

Merko:

>Sorry Elena, there was some crucial info missing: Those >settings are
>valid if you use DHCP.

Opps... now it's clear :)

> If you're not, you need to put your own info
>there of course as the docs explain. The docs never >explain that you
>need to remove this stuff if you use DHCP, however.

Thanks for the info. One never knows...

I made some tests with smbfs and Pegasos1 (G3/600) with AmiTCP, MiamiDX and MOSNet... I can't get good rates with Miami.. never got. I wonder if there's any trick or is Miami just using that much cpu, that you should have G4 :) It seemed to have bigger cpu load than amitcp/mosnet. Also seems that internal VIA Rhine is faster than cheapo PCI Realtek. For comparison there's also speed with A1200/060@60 :)

Results are here: http://jpv.wmhost.com/smbfs_test.txt


[ Edited by jPV on 2006/5/8 11:41 ]

Hello all!
Just decided to give a short notice. The project is not abandoned. I'm busy and don't know how long it will take me to finish this work but TCP protocol code upgrade is almost done (approx. 85% completed). This will include T/TCP and dynamic window size support and is expected to speed up the program.

@ Sonic

Hi, nice to hear from you that you are working on the TCP upgrade :))

I'm looking forward to test...

Regards

Christoph