-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Server uplink feature #8
Comments
fragglet
added a commit
that referenced
this issue
Mar 10, 2022
First part of #8, although previous refactorings have been building towards this. This is not yet complete, although the basic skeleton is there.
fragglet
added a commit
that referenced
this issue
Mar 10, 2022
fragglet
added a commit
that referenced
this issue
Mar 11, 2022
fragglet
added a commit
that referenced
this issue
Mar 11, 2022
If the wrong password is used it's best to just reject the connection immediately rather than repeatedly trying to send a solution that isn't accepted. Part of #8.
fragglet
added a commit
that referenced
this issue
Mar 12, 2022
This is the last major piece of #8 now in place. Multiple protocols are now supported, and ipxbox_uplink can be used to connect to the server and forward packets back and forth. Ther are still some important TODOs left so this is not entirely complete yet.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently it's possible to bridge a local
ipxbox
server to a LAN, but there's no way to bridge to an external server. In theory a standalone "uplink" program could bridge a LAN to a remoteipxbox
server, and multiple users could do this to transparently connect their LANs and play together.It would require an extension to the dosbox protocol since that assumes you only ever have a single machine with a MAC address supplied by the server.
The text was updated successfully, but these errors were encountered: