Did anyone get SSHCON working with ezTcp? Here it stops on "Connecting.." and nothing more happens..

>I suggest the new version to be 0.91 :P. 0.10 might be
> mistaken as an earlier version.

It is not a floating point number, it is version.revision.


[ Edited by Wishmaster on 2005/10/17 0:32 ]

And I forgot to say something: After 9, comes A. :P

[ Edited by amiades on 2005/10/16 23:18 ]

[ Edited by amiades on 2005/10/17 5:58 ]

Can't get https connection to work anymore with ezTCP v0.9. I have AmiSSL v2 installed.
Can anyone confirm this problem ?

@Motosampy

And I can't get ssh to work, sounds like it could be related.

Quote:

This problem is confirmed, AmiSSL really hangs up with ezTCP. It is being researched now, Andrija helps me.
Important point: what does "anymore" mean? Does this mean that it worked with some earlier version?

Version 0.10 is waiting for the approval. ANR users, please verify Shoutsearch, should work now. If not, post debuglog again (debugging version is also there).
2 Leo: Get ready, "resolve" tool is for you, i'll finish it for the next update and change debug options, we'll retest the resolver.

P.S. 2 webmasters: there are two bugs on MZ:
1. "No-cache" pragma is needed. I ocassionally forgot to log in, went to "submit" section and got "you are not logged in" error. Logged in, went there for the second time and got that again. I managed to get an upload form only when i managed to quickly press "reload" while displaying that error.
2. Originally the archive was named ezTCP0.10.lha. MZ gave me an error "only .zip, .lha, etc may be uploaded". This went away when i renamed it to ezTCP0_10.lha.

[ Edited by Sonic on 2005/10/17 16:05 ]

I'd like to ask anyone to provide me some information.
If you use (or just have) Genesis or AmiTCP v4, please, type "resolve morph.zone" in the CLI and send me an output (or just post here). I need the form of output to replicate.

"It's the same old song" - The Four Tops

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

> ANR users, please verify Shoutsearch, should work now.

Yes, it does. Thank you :-)

@Sonic

Yes, I'm pretty sure that SSL as working upto v0.8...

And I just notised that wget does not work either and I'm quite sure it did work with some earlier versions...

[ Edited by Motosampy on 2005/10/18 2:56 ]

Thanks!!! Tons of thanks for notice about v0.8. I carefully examined my socket event changes and found two stupid mistypes in connect() internals. Wrong socket pointer is used. I wonder how it works with most apps at all.
Wait for fixed v0.11 tomorrow.

great work!

Robert

0.11 is waiting.
2 Leo: These debug version and "resolve" tool are for you. Uncomment DOMAIN line in your resolv.conf, run debugging version, and execute "resolve morph.zone" (for example). It will produce two logs: in the syslog and in the current CLI. Give me a copy of them.
Then do the same with "resolve some.nonexistent.host.com".
I'll look at logs and try to figure out something.

Get it here:

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

Note: it seems MZ is switching between different databases from time to times. If you get v0.10, wait untill the database has switched back

Quote:
Please fix usergroup.library link. When i try to download it i get "document not found". Users are frustrated.

[ Edited by Sonic on 2005/10/19 20:13 ]

Sonic : nice work, so far it seems to work well with mldonkey, jabber & co. BTW, it asks for the AmiTCP: assign when I launch some apps. (maybe an outdated usergroup.library)

Anyway, what I'm really wondering is, how eztcp compares to miamiDX in terms of stability & performance. Isn't it based on a stack quite older than miamiDX ?

The only issue I had with MiamiDX, occured sometimes with mldonkey : sometimes, the connection was completely blocked and I had to CTRL-C mldonkey. I don't know if it was due to mldonkey or miami. Will figure it out soon.

Sorry for the offtopic, thanks again.

Edit : it seems mldonkey still happens to get blocked, however, contrary to miamidx, the rest of the connection still works afterwards, without having to CTRL-C mldonkey... If someone knows why it happens, I'll be very interested ! -- I can leave mldonkey a whole without any problem, but if I do something else at the same time, this always leads to this problem, sooner or later...

[ Edited by mahen on 2005/10/19 18:18 ]

Quote:

Thanks, i'm glad to hear this.
Quote:
Thanks again. Exactly, i missed this inside the library. Will fix in the next release. I didn't notice this since i have this assign in place (used Genesis before). For now just assign AmiTCP: to anywhere, no matter where. It attempts to load AmiTCP:Devs/netinfo.device.
Quote:
Yes, it is. You may compare it yourself. As to stability - as you can see, nothing crashes.
After bounty stage, source code will be put into the CVS and stack core may be upgraded then. It can be made newer then MiamiDX then.
Quote:
Happens with two stacks so obviously a bug in mldonkey.

SSL and wget still not working, what kind of information should I send to be able to help with this problem ?

Quote:

What does exactly happen?

@All

If files are missing in the download area, please report it by using the "broken download" link.

@Sonic

Please re-upload usergroup.library v4.3. Seems it was lost somewhere between the database switches.

Update:

Usergroup.library v4.3 back in place

ezTCP 0.11 binary has the same size than 0.10. Is this correct?

Sonic:

I test the last version and i must say this:

very good job.

With the little help form Mahen, i have create a connection in 10 mn. And i'm a lambda user.
I hope i see a little and basic interface for this nice program.

1. Yes, v0.11 has the same length as v0.10. The difference between them is actually 2 internal calls:
Was:
sowakeup(so, &head->so_rcv);
sowakeup(so, &head->so_snd);
(obviously result of sleeping 3 hours per day)
Now:
sowakeup(so, &so->rcv);
sowakeup(so, &so->snd);
For debug version another options are used so they are quite different.
2. 2 Motosampy: please specify your AmiSSL version, test if it works with IBrowse (it really should!), then re-test wget on any another site with -d option: "wget -d https://morph.zone", for example. And give me the output of wget. Debug output of ezTCP is set up to monitor quite different things now, it won't help here. BTW, specify your wget version. I tried yesterday, wget seems to be problematic itself since it crashed (EmulHandle xxx is not an EmulHandle) even when i called it without arguments at all. And, someone else, please re-check wget issue.
3. 2 Golem: did you actually test your netmask with recent version? The reason why i don't remember about your problem is because i fixed it long time ago. I tried yesterday, it perfectly accepted your netmask.