You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All my old computers all the way back to my first 8080 in the 1970s had a modem (my first 110 baud modem predated Hayes standard!) It would be nice to be able to emulate that function.
I imagine it could be done by specifying a TCP port number and forwarding the Com1 traffic to the user's IP on that port.
But I'm sure there are many solutions that are possible.
Imagine being able to open a PPP connection on Com1 to enable Windows 3.10 to use Winsock over PPP and have the request actually go to a PPP server and work! (us users would have to provide our own Hayes emulation and PPP server.)
Or imagine a terminal client under DOS being able to access an emulated BBS, there are several that are still up on the Internet.
For security, the traffic should only be possible to send to the user's IP and not elsewhere, otherwise you become a possible ddos source.
The text was updated successfully, but these errors were encountered:
All my old computers all the way back to my first 8080 in the 1970s had a modem (my first 110 baud modem predated Hayes standard!) It would be nice to be able to emulate that function.
I imagine it could be done by specifying a TCP port number and forwarding the Com1 traffic to the user's IP on that port.
But I'm sure there are many solutions that are possible.
Imagine being able to open a PPP connection on Com1 to enable Windows 3.10 to use Winsock over PPP and have the request actually go to a PPP server and work! (us users would have to provide our own Hayes emulation and PPP server.)
Or imagine a terminal client under DOS being able to access an emulated BBS, there are several that are still up on the Internet.
For security, the traffic should only be possible to send to the user's IP and not elsewhere, otherwise you become a possible ddos source.
The text was updated successfully, but these errors were encountered: