Subj : telnet/vmodem/sio/os2
To   : Tommi Koivula
From : mark lewis
Date : Tue Sep 26 2017 01:01 pm

 On 2017 Sep 26 07:46:38, you wrote to All:

 TK> Hello All,

 TK> What would be the easiest way to make FD to call to a non-standard telnet
 TK> port with vmodem/sio on os/2 system? Vmodem/SIO needs the port number 
after
 TK> the host name, separated by _space_. I cannot find a correct format of
 TK> PHONE statement in FDNODE.CTL. The space character seems to be the problem
 TK> now.

i use environment variables so i have entries like this in FDNODE.CTL...


  PHONE   2:2448/400   $[tobiasB1]


my DIAL section is like this...


  DIAL  /  011-
    ; internet stuff
    #            internet
    0000-        internet/:155
    000-         internet
    V            internet#

    ; local dial translations
    blahblahblah
  END


then in my scripts i have the following (effectively an override) ""number"" 
for 2:2448/400...


  set tobiasB1=#fido.softeq.org 60177


decoding this from the ""number"" "#fido.softeq.org 60177"... the '#' is dial 
translated by FD to "internet" so it knows which way to go... frontdoor also 
displays this as the number for the system... if the number were


  Vfido.softeq.org 60177


the 'V' would be dial translated to "internet#"... using SIO and vmodem on 
OS/2, the first one basically just strips off the '#' sign... when vmodem sees 
the number it knows that it is an outbound telnet protocol dial... the second 
one converts the "V" to a "#" which vmodem sees as the indicator for a vmodem 
protocol connection... providing this capability like this allows each system 
to use whatever virtual modem software they want and to set whatever that 
software uses for telnet, vmodem or other protocols that may be used...


BUG: using the 'V' or 'v' you cannot have a domain that also starts with a 'V' 
or 'v'... a different character would need to be used in the overrides (and 
nodelist) to indicate vmodem protocol connections... this was perfect for the 
000- (and 0000-) prefixed numbers in the nodelist... as long as they don't 
conflict with any country codes, everything is fine... one's local setup would 
protect them anyway...


in my DIAL translation above, the "0000-" prefix automatically adds port 155 to 
the telnet number... it is just an example, though... i think that vmodem on 
155 would be something like


  V0-        internet#/:155


in this case, i would be using a number like V0-fido.softeq.org for the 
connection...

one problem with my method is that i have to maintain the list somehow... 
coming up with environment variable names can be rough if there's a lot of 
them... currently the nodelist indicates only 200+ ITN nodes... environment 
space is also not endless... i did try using the FTN formatted address but my 
OS/2 didn't like that for some reason... maybe i'll revisit it some time...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it 
wrong...
.... Age needn't necessarily be a bar to immaturity.
---
 * Origin:  (1:3634/12.73)

.