Hi Tommi,

. The space character seems to be the

problem now

I would first think of the dial translation that also strips and adds prefixes.
Haven't done this for a long time, but it's maybe worth looking at.

ius
--- AfterShock/Android 1.6.5
* Origin: .-==o[# R o B O t S - B B S #]o==-. (2:292/854.200)

Hello Conrad!

26 Sep 17 12:18, you wrote to me:

I would first think of the dial translation that also strips and adds prefixes.

Yes. But how to strip or add a space? :)

'Tommi

---
* Origin: A point of news://rbb.bbs.fi (2:221/360.8110)

Hi Tommi!

I would first think of the dial translation that also strips and adds
prefixes.

Yes. But how to strip or add a space? :)

Em, err... well, I... hmm....

[silently leaving the room, pretending to go to the restroom] :-D

Cheers,

ius
--- AfterShock/Android 1.6.5
* Origin: .-==o[# RoBOtS - BBS #]o==. (2:292/854.200)

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

Hello All,

What would be the easiest way to make FD to call to a non-standard telnet port with vmodem/sio on os/2 system? Vmodem/SIO needs the port number

after

the host name, separated by _space_. I cannot find a correct format of PHONE statement in FDNODE.CTL. The space character seems to be the problem 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)

26 Sep 17 13:01, you wrote to me:

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

Hello All,

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

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

PHONE 2:2448/400 $[tobiasB1]

Ok, I'll try that.

Waiting for INA support in FD. ;)

'Tommi

---
* Origin: A point of news://rbb.bbs.fi (2:221/360.8110)

Hello, Conrad J. Koehler.
On 26/09/2017 15.47 you wrote:

Hi Tommi!

I would first think of the dial translation that also strips and adds
prefixes.

Yes. But how to strip or add a space? :)

Em, err... well, I... hmm....
[silently leaving the room, pretending to go to the restroom] :-D

;D

--
Tommi
--- Hotdoged/2.13.5/Android
* Origin: Android 7.0; SM-G390F Build/NRD90M (2:221/6.1)

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

I can make a private nodelist with phone entry that contains the
space character. That way FD dials out ok. But that is not very
easy way. :)

If you cannot get this to work, let me know and I'll compile a version which translates a given character (% perhaps) to spaces.

Many functions in FD exist and/or behave the way they do for a reason. If you read the documentation from top to bottom (I'm not asking you to :)), you'll see there are a *lot* of flexibility and configuration options. That is not to say that things are not missing.

Things are missing. And they will be addressed. That is why I'm here.



-joho

---
* Origin: reboot.defsol.com (2:20/4609)

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

I can make a private nodelist with phone entry that contains the
space character. That way FD dials out ok. But that is not very
easy way. :)

If you cannot get this to work, let me know and I'll compile a
version which translates a given character (% perhaps) to spaces.

That would be the easiest way, or course. :)

Many functions in FD exist and/or behave the way they do for a
reason. If you read the documentation from top to bottom (I'm not
asking you to :)), you'll see there are a *lot* of flexibility and configuration options. That is not to say that things are not
missing.

Support for INA flags would be also nice. In that case FD could dial IP nodes without any special configuration.

Things are missing. And they will be addressed. That is why I'm here.

:D

'Tommi

---
* Origin: * rbb.fidonet.fi * (2:221/360)