Hey everyone, hope your weekends have started off nicely.
Following on from the mass of helpful suggestions I received in response to
my earlier post asking for BBS client suggestions, I have got hold of a couple of lantronix UDS-10 devices & have finally got my retro 286 setup to use one with dos comms software as nice functional BBS client.
Thought I would share my setup here, as there are few mistakes/traps to avoid & although the UDS-10 doesn't do DNS, there is a way around that so you can
'dial' your favorite telnet BBSes using their DNS names & not have have to
find their IP address to dial.
So first of you need the following to get started:
1 - A lantronix UDS-10, I got mine off ebay pretty cheap. There seem to be a
lot of them there.
2 - The UDS-10 user guide:
https://www.lantronix.com/wp-content/uploads/pdf/UDS10-UDS100_UG.pdf. This is critical to understanding how to setup the network, com port an a number
of other parameters. I advise that you look through this. I will be referring to various tables in this document throughout.
3 - A null modem cable wired as per the user guide. This may not be needed, a standard null modem cable may work, however I have not tried this. I didn't have a null modem cable with the correct connectors so I ended up just making one as per the user guide....
4 - A `server` computer/vm with a static IP address & internet connectivity which will be used to run tcpser as an ip232 server. I used a linux VM, though you should be able to do this in windows as well, I have not tried.
5 - tcpser. There seem to be various versions of this about. I compiled from source using this version:
https://github.com/fozztexx/tcpser
Ok so first of all, setting up the UDS-10. The initial setup can be a bit fiddly so you'll need a bit of patience.
The initial setup:
1 - Connect your UDS-10 to PC with working serial port, obvious I know, however I found out that one of my com ports was broken in a very odd way after much pointless messing about... also turn the UDS-10 on.
2 - Connect to that port with whatever comms sofware you prefer at 9600 baud, 8 bits, no parity, 1 stop bit & no flow control.
3 - This is a bit fiddly, while holding down the x key in your terminal software, reset the UDS-10. If you do this just right, this will force the UDS-10 into a failsafe setup mode & you should see a message in your terminal software asking your to press enter to enter setup mode.
4 - Set factory default with option '7' & save and exit with '9'
5 - The UDS-1o will restart & you'll need to repeat step 3 again to enter setup mode.
6 - Setup the Server configuration (network setup, ip address ect) with option '0' and you will be prompted for the following:
6.1 - IP address. If you intend to use DHCP to assign the UDS-10 an IP, set this to 000.000.000.000
6.2 - Set Gateway IP Address. Not needed for this setup, answer N.
6.3 - Netmask: Number of Bits for Host Part. Depends on your network setup. My network is a class C network, so for me this is 8. If you are unsure what to set, get your netmask & look up the correct value in table 5-1 & 5-2 of the UDS-10 user guide.
6.4 - Change telnet config password: If you want to use a password for the telnet config (we enable this later) set it here. Its only 4 chars though... 6.5 - Change DHCP device name: set this to whatever you want. It will appear in your DCHP server's (usually our internet router/modem) list of active leases.
7 - Channel 1 configuration, option '1'. This is where we setup com port settings, handshaking & configure the UDS-10 to connect to our server.
7.1 - Baud rate: I'd advise you stick to 9600 initially & experiment with increasing it later once you are happy everything is working correctly.
7.2 - I/F Mode: I advise '4C' which is RS-232, 8 bit, no parity, 1 stop bit. See tables 5-3 & 5-4 of the user guide for more info on this setting.
7.3 - Flow (Flow Control): Initially '00' (no flow control) is probably fine, once you start experimenting with higher baud rates you'll probably need to
set this to something else, I ended up using '02' (RTS/CTS) at higher speeds with my terminal software configured accordingly. See Table 5-5 for more info. 7.4 - Port No: This is the port for incoming connections, I left this
set to the default of 10001. Knowing this setting is helpful for debugging.
7.5 - Connect Mode: Set to 'C5' to enable incoming connections & to auto connect to the configured remote IP (that is coming up). See table 5-6 for
more info.
7.6 - Remote IP Address: This is the IP address of your server computer/VM.
7.7 - Remote Port: The remote port that you'll configure tcpser to list for connections on. I used '10002'. Make sure it is a port that is unused for anything else on your server.
7.8 - DisConMode: I left this at the default of '00'. There is a massive table on pages 64-65 of the user guide that shows all the options available for this setting.
7.9 - FlushMode: Again I left this at the default of '00'. The possible settings are covered in an even larger table than DisConMode that spans
pages 66 to 71 of the user guide.
7.10 DisConnTime: I used the '00' the default value to disable inactivity timeout. If you want to set a timeout, specify it in 'minutes:seconds'
format.
7.11 SendChar 1 & SendChar 2: I left both set at the default of '00'. There is more information about this setting on page 35 of the guide.
8 - Security option '6'
I won't go through this in detail, however ensure that "telnet setup" is not disabled & I advise disabling the web setup as it is unlikely to work & needs
a web browser from the windows 98 period running a really old and insecure version of java to work......
9 - Save and exit the setup with '9'.
Now that you have made these changes, I advise checking a few things out first before going any further.
1 - The USD-10 should now be configurable via telnet at port 9999 on its IP address. Check that this works.
2 - Check that you can send/recieve data with the UDS-10. Connect your terminal/comms software to it via com port & on another computer on your network, establish a telnet connection with the UDS-10's port (10001 if you followed these instructions). You should be able to send messages from the telnet client to your terminal software and back if all is working correctly.
Ok now for the final bit, setup your server. This is pretty simple.
1 - Get tcpser from
https://github.com/fozztexx/tcpser, I just used git to clone it & ran 'make' to compile it on my linux vm server.
2 - Run tcpser configured for the correct baud & to listen on the port that you configured your UDS-10 for in step 7.7 above. If you followed my suggested settings this will be 10002. So the command to run is:
tcpser -v 10002 -s 9600 -l 4
-v set the port to listen to for incoming ip232 connections
-s sets baud rate and should be equal to what you set the UDS-10's serial port to.
-l set the logging level. Use higher numbers to get more info about what tcpser is doing.
And that's it! with all this setup, reset your UDS-10 & open your terminal/comms software and try dialing a telnet BBS of choice with: ATDTbbs.roonsbbs.hu:1212 <- replace with your BBS of choice!
At the server end you should see messages like this from tcpser in the
console:
ip232 device configured
Connection accepted from xxx.xxx.xxx.xxx <- your UDS-10's IP address
Link has come up
taking modem off hook
Connecting line
Connecting to somebbs.that.i.dialed established
Detected telnet
Pretty quickly you should see the BBS you dialed displayed in all it's glory!
I've used this setup to get RIPterm for dos working on my 286 retro build & so far have got it working fine at 38400 baud without any problems. When I get more time I will try this setup with GTO power BBS's terminal sofware as I believe it will also supports RIPscript & looks like it could be a bit more flexible as a terminal client.
If you are not able to use high baud rates, check what UART you've got on your com port, (I used a program called UART, I believe I found it on Titantic BBS ttb.rgbbs.info) & if you have 16550A or better, use a tool like 16550 (also available at titanic) to enable the UART's fifo buffers. This helped in my case.
Anyhow I hope this of interest to some of you & should make it easier for others to get online using one of these UDS-10 devices.
... It's not that I mind being chained in the basement...
--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: 2o fOr beeRS bbS>>20ForBeers.com:1337 (21:2/150)