Another day, another experiment.
Here's my setup:
Handheld PC
(any really
) connected via rs232-to-usb converter to my windows PC. The serial port is forwarded to a VM running the latest Debian version.
On Debian, I installed SLIRP.
Starting SLIRP with
slirp -P "tty /dev/ttyS0" -b 115200
And setting up a new connection using remote networking on my Jornada 720, 115200 baud, tried every configuration of compression/etc. Nothing happens, HPC is stuck trying to connect.
One thing that could be an issue is that Windows computers - before initializing a SLIP connection - send "CLIENT" and wait to receive "CLIENTSERVER" before proceeding with the connection.
According to the SLIRP manpage:
Quote
MS_DCC
This isn't an option, its a compile time choice, and its a hack. If
enabled, when slirp is run and PPP is selected, while the PPP link
is down, SLIRP will respond to an incoming word of "CLIENT" with the
reply "CLIENTSERVER"
This will allow a MS windows PC to connect to slirp using direct
cable connect (Over the serial port at least).
It has 1 major advantage over using a normal DCC, and that is that
the IP address of the connecting host is masqueraded. (Which windows
won't do normally)
Not sure if the SLIRP I have is compiled with that option.
I made a little test program that listens for CLIENT and replies CLIENTSERVER, and indeed, after that the Jornada sends some garbled mess which are hopefully SLIP packets.
PS C:\Users\Thomas\Code\serialport-test> ts-node index.ts
IN: CLIENT
OUT :CLIENTSERVER
IN: ~?}#?!}!}!} }.}"}&} } } } }'}"}(}"p4~