Page 1 of 1

Exposing server access from outside Sheepshaver

Posted: Sat Apr 02, 2016 4:21 am
by Schala
There's an old, old client-server file sharing program called Carracho that's been abandoned for 11 years despite its site and download links still up and working. The programs are Carbon-built so they run like a charm on Sheepshaver with OS 9.04. However, because I want to code a rewrite compatible with today's machines, I'm trying to use Wireshark on my host system (Windows 10) to packet sniff the activity on it. Carracho uses TCP ports 6700/6701, but I'm not getting any entries from those ports when sniffing.

I then tested Classilla by loading google.com while packet capturing. Sure enough, Wireshark picks that up under my LAN address. I'm sure now that my problem is that the Carracho server I'm running isn't actually online. I've even tried designating the ports to forward on my router with no success.

I tried going to TCP/IP and switching it from DHCP to manual without luck, and finding an OS 9 copy of EtherPeek seems impossible.

I would very much appreciate any help I can get. Thanks!

Re: Exposing server access from outside Sheepshaver

Posted: Sat Apr 02, 2016 6:50 am
by Cat_7
Hi,

I assume you running SheepShaver with slirp networking? If so, the networking possibilities are limited. Slirp provides a SheepShaver-local DHCP server, only allowing a limited set of ports (80/21). I guess you would need to run SheepShaver with the ethernetdriver to get a server running. See the SheepShaver Appletalk guide. The network solution provided there does much more than just provide Appletalk support.

There is, however, one major drawback: there is no 64 bit solution. You might consider running SheepShaver in a Linux VM, or Windows 7 32 bit VM with networking set to promiscuous.

Best,
Cat_7

Re: Exposing server access from outside Sheepshaver

Posted: Sun Apr 03, 2016 6:19 am
by Schala
Well I dual boot with Arch Linux. However, SheepShaver always fails to compile when it runs a tool called dyngen, citing __stkchk_fail is an unresolved reference. I've sought to resolve this, but apparently stock GCC has no libssp, and -fno-stack-protector doesn't seem to apply to dyngen.

Re: Exposing server access from outside Sheepshaver

Posted: Sun Apr 03, 2016 7:19 am
by Cat_7
Did you try our pre-compiled SheepShaver for Linux releases?
http://www.emaculation.com/forum/viewto ... 5420#35420

Best,
Cat_7

Re: Exposing server access from outside Sheepshaver

Posted: Sun Apr 03, 2016 9:00 am
by Cat_7
I just compiled SheepShaver in latest Arch Linux (through arch-anywhere 64 bit) in Virtual box.
A lot of warnings, but no errors, SheepShaver runs.

Edit: If you want, I can send you the executable.

Best,
Cat_7

Re: Exposing server access from outside Sheepshaver

Posted: Sun Apr 03, 2016 11:14 am
by Schala
Hmm... what Arch Linux packages are needed to compile this, perhaps? I have libxxf86dga and libxxf86vm listed as the only deps.

Re: Exposing server access from outside Sheepshaver

Posted: Mon Apr 04, 2016 7:32 pm
by adespoton
Carracho was written by a Hotline community member as a response to Hotline 1.5 and the corporate takeover, and all the brouhaha that came out of that. The guys that made it are still around, and I believe the protocol docs are also around somewhere. It didn't last too long as it was replaced by Haxial KDX pretty quickly, which was then replaced itself by Zanka's Wired.

Nowadays, of course, a similar system can all be run via TorBrowser and Tor Chat. You can even run Hotline, Carracho, KDX or Wired as Tor private services.

Hmm; I can't seem to find the community Carracho protocol docs, but they should be around somewhere.

https://en.wikibooks.org/wiki/The_World ... mentations might be useful if you want to run a historical collection of Internet BBSes :)

Re: Exposing server access from outside Sheepshaver

Posted: Tue Apr 05, 2016 12:54 am
by Schala
Wired would be good, except it has a bloated protocol from what I've seen.