|From||Benny Pedersen||2:230/0.0||Date Write||2017-10-05 05:22:21|
|To||Ingo Juergensmann||0:0/0.0||Date Arrived||2017-10-05 07:11:16|
|Subj||ifcico story continues|
05 Oct 2017 00:15, Ingo Juergensmann wrote to Benny Pedersen:
IJ> Well, that number behind the Trapdoor version is not the port number,
IJ> but the serial number of my TD license key. Port 24554 would be binkd
IJ> port anyway and ifcico over TCP is operating on port 60177 as shown
IJ> below by your config snippet:
EMSI works on every port over 1023
BINKP works on every port over 1023
why should i need to open 2 diffrent ports for stream tcp ?
wake up :)
note i found a small bug in my xinetd config -a binkp disables other protocols
so emsi did not work, but in -a auto it works in single open port, bravo
qico does not need to know what ipv4 and ipv6 is, aslong data protocol is
working on top of modems or tcp :=)
so even my qico would work very well with ipv10 when its availble on linux
for traplist.cfg use f0.n230.z2.binkp.net as my static hostname, cant remember
if telser.device handles dns resolve ?
for trapdoor its just using telser.device instaed of you serial device
do not use hostname from nodelist, that would be a fail, or you would have to
change traplist.cfg every time i change hostnames :=)
atleast that is the basic, if telser.device does not handle dns resolve, use ip
addr as hostname in traplist.cfg and make sure it uses port 24554 here
IJ> How do they translate from qico to ifcico?
qico in -a auto handles all ftn protocols, why not try it ?
... there can only be one way of life, and it works :)
--- Msged/LNX 6.2.0 (Linux/3.10.107-gentoo-r1 (i686))
* Origin: I will always keep a PC running CPM 3.0 (2:230/0)