Livingston PortMaster 3 » History » Revision 12
Revision 11 (laforge, 02/20/2022 10:02 AM) → Revision 12/22 (laforge, 02/20/2022 02:56 PM)
h1. Livingston Portmaster 3 @laforge bought two Livingston Portmaster 3 PM3A-1E, which are RAS (Remote Access Server) that * terminates one 1E line (30 B-channels) * provides ISDN dial-up on those channels * provides DSP based modems in case analog modem calls should be handled. More details to follow. h2. Documentation * attachment:portmaster3_hardware_installation.pdf * attachment:portmaster3_configuration.pdf * more below (Attachments) h2. Electronics / Pictures {{thumbnail(Livingston_Portmaster3_front.jpg)}} {{thumbnail(Livingston_Portmaster3_top.jpg)}} {{thumbnail()}} {{thumbnail()}} {{thumbnail()}} h2. Spare Parts / Mods h3. Fan The original fan is a Fonsan DFB0812M (DC 12V 0.1A) fan by DELTA ELECTRONICS INC. The specs seem to state 2600 RPM / 24.8 dB(A) / 29 cfm. I found it too noisy and replaced it with a Noctua NF-A8 FLX with L.N.A (reduced to 1650 rpm / 12.9 dB(A) / 24 cfm) Fun fact: The PM3 actually seems to have a 5V -> 12V DC/DC upconverter just for the fan - instead of simply using a 5V fan... h3. Power Supply One of @laforge's PM3A-E1 had a broken power supply. The oroginal PSU is an ASTEC LPS1112 rated for 5V/22A output (80W convection cooled, 1120W with 30cfm forced air). It was replaced with a Mean Well LRS-150F-5. Mechanical assembly via a custom adapter plate that was fabricated easily from a small piece of aluminium sheet metal with a few drill holes. {{thumbnail(PM3-PSU-1.jpg)}} {{thumbnail(PM3-PSU-4.jpg)}} {{thumbnail(PM3-PSU-2.jpg)}} h2. Configuration h3. route to different telpnet hosts based on called party number Assuming one wants to use a PM3 to act as modem bamk for accessing differnt [virtualized] BBSs over telnet, the problem is how to route the inbound call to a specific telnet IP address. The non-radius stand-alone configuration of the PM3 only permits either: * automatic forwarding of all calls to one global telnet/rlogin host * allowing the users to enter the hostname for telnet themselves * providing a list of pre-configured telnet desinations to all users (this was used at the 36C3 retronetowrking installation, see [[retro-bbs:36C3]]) However, with the _Call-Check_ radius feature, it should be possibl to receive the called + calling identity before the call is even accepted, and the nin return provide the telnet IP/port to which the call shall be routed. Details in * Page 4-17 of the PM3A Radius for Unix manual ** PM3A sends _access-request_ with *** User-Name=SETUP.Calling-Station-Id/No-Call-ID *** Service-Type=Call-Check *** Called-Station-Id=SETUP.Called-Station-Id ** Radius sends response with *** Login-IP-Host pointing to IP of telnet/rlogin *** Login-Service=(Telnet,Rlogin,TCP-Clear) *** Login-TCP-Port pointing to IP of telnet/rlogin *** Service-Type=Login-User * Page 3-4 of the PortMaster Command Line Reference ** @set call-check on@