WormHole: great tool to easily transfer files via LAN

Did anybody yet manage to get it working between Windows Host and QEmu AOS4 Peg2 emulation? Started it on both ends, accepted the firewall changes on Win11 side and also checked the debug output.

Could not find any problems but Wormhole does not connect to each other. (On Win side IIRC it always shows connected to 127.0.0.1
disconnected from 127.0.0.1 and repeats this endlessly.

@Reth

Tested under Qemu AmigaOneXE and for me Wormhole works perfectly. however I run Qemu as Sudo under MacOs maybe that makes the difference.

I also use “vmnet-bridged” for the internet connection.

https://vimeo.com/1078742454?share=copy

@lazi

Quote:

It's great that Wormhole also receives this support.

@Reth

Yes I managed to get this working. I use a tap network connection
for qemu, and give AOS a static ip address in the same range as Windows.
Works like a charm. EDIT:It should also work with DHCP.Although it takes a long time for OS4 to find the DHCP settings.
EDIT2: with tap network connection, the speed under OS4 is very slow. I get about 700K/s to 1MB/s with my 1 Gbps connection. Previously mentioned 16K/s is on my Mister.
So for large files it's better to use an usb-stick.

@Reth
I don't know what ports WormHole needs but for QEMU network configuration docs see the FAQ on my qmiga.codeberg.page The QEMU doc linked from these shows how the user/slirp network works. It's behind it's own NAT so if you want to allow connection to the guest you need hostfwd option to open the port similar how you have to allow incoming connections on your router. Think of the user/slirp network as a LAN behind a router doing NAT.

@Maijestro

Did some google search but it seems this is a MacOS related parameter? As for bridging on Win11 I did not yet find an "easy" to understand way to get it done.


@balaton

Thank you. Seems there is something for Win2000/XP for which OpenVPN is needed (for Using TAP network interfaces). Guess I will then stick to the USB solution + FTP. Or did I got something wrong here?

@balaton

WormHole uses the port 64738.

Hi Lazi,

Thanks for posting another version of Wormhole!

I installed it on my Amigas and it worked great. Auto accept is
working great. Clipboard syncing is a nice add! The progress
indicator is working.

I'll be curious to see how things work with foreign systems, if I can
ever get them to work. Still stuck on loonix x86 and osx PPC.

In both cases I decompressed the archives, I see the program file, it's
recognized as an application, but nothing will get it to actually,
recognizably run.

On linux in properties it says "executable (application/x-executable",
permissions are set to read+write and it shows it's an allowed executable.
I tried double-clicking & using the pop-up menu "run" in the GUI and
I tried running it in the shell (with "." & "./" prepended). I also
ran "chmod +x ", that didnt complain, but that made no
difference.

On the 10.4 mac, it's also recognized as a "application (PowerPC)",
I set all the persmissions to read+write, tried to double-click, "open"
and run it from the dock. In their shell I also tried all the path
possibilities, chmod'd, etc. Either it can't find it or (with "./")
it just says it's a directory (not an app).

There's probably some foreign magic I haven't been let in on.
Any clues?

Thanks again,

PJS

Tried Wormhole today between two OS3.2 miggies. The system with RTG runs fine but the other one (non RTG with IndiAGA) gets error "Hollywood does not run on palette screens. Please switch to a high or true colour mode"

is there any way to get Wormhole working without RTG ?

@328gts

Sorry, but currently palette screenmodes are not supported.
It could be done and I will try it later. Should note that it will still needs megabytes of memory.

The best way would be to port it to another progamming language that suits more to the mildly expanded classic amigas.
I would love to do that, but no promises. Maybe after it is finished in the current form. Far away in a distant future!

@lazi

ok thanks for the explanation, I'm running a TF1260 with 128MB ram so hoping that's enough? but I do understand that Hollywood in general is pretty heavy on resources so that's a no go on stock miggies

@lazi
Quote:
I've heard there are theories that you can travel far away very fast and maybe even in time through a worm hole... (Sorry.)

@balaton
Hmm, looks like another feature request.
I was thinking about it before I will came back from the distant future!

Is wormhole between two MOS machines a supported config? I haven't yet been able to get it to work. One or other of the wormhole instances just crashes. One thing I did note is that my MOS laptop says "eth0" for both host names, but really on the laptop it is using wl0. Of course it's zero config so I don't see anywhere to tell it which interface to use.

It does seem to connect once in a while but it's very unreliable and I haven't managed to transfer anything reliably.

Just to report back on this one - I connected my Powerbook G4 laptop to wired ethernet so that eth1 was the device in use and everything started working and became fast and reliable.

So it would appear there is a fault in the code that assumes the device name. Or something like that. Whatever the issue, it should have detected that eth1 (or eth0, I forget) was not actually in use and in fact wl0 was the device it should have used.