Hello everybody!

Still playing around with ifcico and my dial-in modem.

After a reboot it seems that the segfaults are gone, for whatever reasons.

However, I still get no working connect or more exactly a valid connection. Here is connection made from my Amiga using TrapDoor 1.83 to Linux running ifcico 2.14tx8.10-23:

/var/log/ifmail/ifdebug <==

statemachine rx_define_type entering nextchar (2)
statemachine rx_define_type entering waitchar (1)
statemachine rx_define_type entering nextchar (2)
statemachine rx_define_type entering waitchar (1)
statemachine rx_define_type entering nextchar (2)
statemachine rx_define_type entering waitchar (1)
statemachine rx_define_type entering nextchar (2)
statemachine rx_define_type entering waitchar (1)
statemachine rx_define_type entering nextchar (2)
statemachine rx_define_type entering waitchar (1)
statemachine rx_define_type entering nextchar (2)
statemachine rx_define_type entering waitchar (1)
statemachine rx_define_type entering nextchar (2)
statemachine rx_define_type entering waitchar (1)
statemachine rx_define_type entering nextchar (2)
statemachine rx_define_type entering waitchar (1)
statemachine rx_define_type entering nextchar (2)
statemachine rx_define_type entering waitchar (1)
statemachine rx_define_type entering nextchar (2)
statemachine rx_define_type entering checkemsi (3)
check "EMSI_DAT00D1" for being EMSI inquery or data
statemachine rx_define_type entering getdat (4)
try get emsi_dat packet starting with "EMSI_DAT00D1"
statemachine rx_define_type exit success (1)
start inbound EMSI session
statemachine rxemsi start checkpkt (4)
statemachine rxemsi entering checkpkt (4)
statemachine rxemsi entering checkdat (5)
got data packet: "{EMSI}{2:2452/413.2}{secret}{8N1,PUA}{TDZ,DZA,ZAP,ZMO,ARC,XMA,NRQ}{39}{TrapDoor}{1.85}{24374}{IDENT}{[AmigaXess Point 2, Georgsmarienhuette, GER][][Ingo Juergensmann][-Unpublished-][57600][]}{TRX#}{[59D4BD6E]}"
remote address: 2:2452/413.2
try locking node 2:2452/413.2
using domain "(null)" for outbound
this is our primary domain
bsy file name is "/var/spool/ftn/outb/0994019d.pnt/00000002.bsy"
creating directory tree for "/var/spool/ftn/outb/0994019d.pnt/aa13027"

/var/log/ifmail/iflog <==

Oct 04 10:52:45 local ifcico.ttyS0[13027]: start inbound EMSI session
Oct 04 10:52:45 local ifcico.ttyS0[13027]: remote address:

/var/log/ifmail/ifdebug <==

mkdir("/var") errno 17
mkdir("/var/spool") errno 17
mkdir("/var/spool/ftn") errno 17

/var/log/ifmail/iflog <==

/var/log/ifmail/ifdebug <==

mkdir("/var/spool/ftn/outb") errno 17
mkdir("/var/spool/ftn/outb/0994019d.pnt") errno 17
.bsy file present, check staleness
opened bsy file for pid 4767
found stale bsy file for 2:2452/413.2, unlink

/var/log/ifmail/iflog <==

Oct 04 10:52:45 local ifcico.ttyS0[13027]: found stale bsy file for , unlink

/var/log/ifmail/ifdebug <==

created lock OK
remote password: secret
unrecognized EMSI proto/option code: "TDZ"

/var/log/ifmail/iflog <==

Oct 04 10:52:46 local ifcico.ttyS0[13027]: remote password: (none)
Oct 04 10:52:46 local ifcico.ttyS0[13027]: unrecognized EMSI proto/option code:
""

/var/log/ifmail/ifdebug <==

remote uses: TrapDoor [39] version 1.85/24374

Basically this looks good to me: TrapDoor is sending EMSI packet and a password
and ifcico recognizes this password in /var/log/ifmail/ifdebug, but then again in the following /var/log/ifmail/iflog entry the password is "(none)".

What is going wrong here?

Any help is appreciated! :)

Ingo


--- GoldED+/LNX 1.1.5--b20170303
* Origin: AmigaXess - back in FidoNet after 17 years (2:2452/413)

Hello Ingo!

04 Oct 2017 13:42, Ingo Juergensmann wrote to All:

remote uses: TrapDoor [39] version 1.85/24374

there is 2 patches to trapdoor on aminet :=)

why not update it ?

try emsi here on my node please

use port 24554 !

eq my qico have all on that port number

----- qico begins -----
# binkp = 24554
# tfido = 60179
# fido = 60177

service binkp
{
disable = no
protocol = tcp
flags = IPv4
port = 24554
socket_type = stream
wait = no
user = xpoint
server = /usr/sbin/qico
server_args = -a auto
# binkp
per_source = 1
instances = 1
}
----- qico ends -----

note my server_args :=)


Regards Benny

... 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)

Hello Benny!

04 Oct 17 21:34, you wrote to me:

04 Oct 2017 13:42, Ingo Juergensmann wrote to All:

remote uses: TrapDoor [39] version 1.85/24374

there is 2 patches to trapdoor on aminet :=)

Remember my posting in AmigaNet regarding the patches for Trapdoor?

Anyway, this is not about the Trapdoor side not working, but it's the Linux side that is not working. I already connected successfully to other nodes with IFC flag from my Trapdoor installation.

use port 24554 !

Well, that number behind the Trapdoor version is not the port number, but the serial number of my TD license key. Port 24554 would be binkd port anyway and ifcico over TCP is operating on port 60177 as shown below by your config snippet:

----- qico begins -----
# binkp = 24554
# tfido = 60179
# fido = 60177

note my server_args :=)

How do they translate from qico to ifcico?

Ingo


--- GoldED+/LNX 1.1.5--b20170303
* Origin: AmigaXess - back in FidoNet after 17 years (2:2452/413)

Hello Ingo!

05 Oct 2017 00:15, Ingo Juergensmann wrote to Benny Pedersen:

Well, that number behind the Trapdoor version is not the port number,
but the serial number of my TD license key. Port 24554 would be binkd port anyway and ifcico over TCP is operating on port 60177 as shown
below by your config snippet:

ignorant

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 kernel :=)

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

How do they translate from qico to ifcico?

qico in -a auto handles all ftn protocols, why not try it ?


Regards Benny

... 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)