Livingston PortMaster 3 » History » Version 11
laforge, 02/20/2022 10:02 AM
| 1 | 1 | laforge | h1. Livingston Portmaster 3 |
|---|---|---|---|
| 2 | 2 | laforge | |
| 3 | 5 | laforge | @laforge bought two Livingston Portmaster 3 PM3A-1E, which are RAS (Remote Access Server) that |
| 4 | 2 | laforge | * terminates one 1E line (30 B-channels) |
| 5 | * provides ISDN dial-up on those channels |
||
| 6 | * provides DSP based modems in case analog modem calls should be handled. |
||
| 7 | |||
| 8 | More details to follow. |
||
| 9 | 3 | laforge | |
| 10 | h2. Documentation |
||
| 11 | |||
| 12 | * attachment:portmaster3_hardware_installation.pdf |
||
| 13 | * attachment:portmaster3_configuration.pdf |
||
| 14 | 4 | laforge | * more below (Attachments) |
| 15 | 6 | laforge | |
| 16 | h2. Spare Parts / Mods |
||
| 17 | |||
| 18 | h3. Fan |
||
| 19 | |||
| 20 | 7 | laforge | 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. |
| 21 | 6 | laforge | |
| 22 | 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) |
||
| 23 | |||
| 24 | 1 | laforge | 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... |
| 25 | 7 | laforge | |
| 26 | h3. Power Supply |
||
| 27 | |||
| 28 | 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). |
||
| 29 | |||
| 30 | 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. |
||
| 31 | |||
| 32 | {{thumbnail(PM3-PSU-1.jpg)}} |
||
| 33 | 8 | laforge | {{thumbnail(PM3-PSU-4.jpg)}} |
| 34 | {{thumbnail(PM3-PSU-2.jpg)}} |
||
| 35 | 10 | laforge | |
| 36 | h2. Configuration |
||
| 37 | |||
| 38 | h3. route to different telpnet hosts based on called party number |
||
| 39 | |||
| 40 | 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: |
||
| 41 | * automatic forwarding of all calls to one global telnet/rlogin host |
||
| 42 | * allowing the users to enter the hostname for telnet themselves |
||
| 43 | 11 | laforge | * providing a list of pre-configured telnet desinations to all users (this was used at the 36C3 retronetowrking installation, see [[retro-bbs:36C3]]) |
| 44 | 1 | laforge | |
| 45 | 11 | laforge | |
| 46 | 10 | laforge | 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. |
| 47 | |||
| 48 | Details in |
||
| 49 | * Page 4-17 of the PM3A Radius for Unix manual |
||
| 50 | ** PM3A sends _access-request_ with |
||
| 51 | *** User-Name=SETUP.Calling-Station-Id/No-Call-ID |
||
| 52 | *** Service-Type=Call-Check |
||
| 53 | *** Called-Station-Id=SETUP.Called-Station-Id |
||
| 54 | ** Radius sends response with |
||
| 55 | *** Login-IP-Host pointing to IP of telnet/rlogin |
||
| 56 | *** Login-Service=(Telnet,Rlogin,TCP-Clear) |
||
| 57 | *** Login-TCP-Port pointing to IP of telnet/rlogin |
||
| 58 | 1 | laforge | *** Service-Type=Login-User |
| 59 | 10 | laforge | * Page 3-4 of the PortMaster Command Line Reference |
| 60 | 11 | laforge | ** @set call-check on@ |
