Subj : IPv6 here?
To   : Andrew Leary
From : Kees van Eeten
Date : Wed Apr 20 2016 18:12:22

Hello Andrew!

19 Apr 16 19:52, you wrote to me:

 AL> One of these days I need to grab a copy of the ifcico source code and see
 AL> about figuring that out.  While I'm at it I can probably add in CRC mode
 AL> support and the NR mode fixes I'm working on with mbcico now.

 Are you talking about ifcico or qico?

 AL> IPv6 is another feature that Michiel Broek added to mbcico.  In fact,
 AL> MBSE's support for IPv6 is the main reason I took the time to figure out
 AL> how to make IPv6 work, first using a tunnel, and then native IPv6 support
 AL> once my ISP enabled it.

 As incoming IPv6 is mainly served bij the inet daemon, I can probably handle
 incoming calls on ifcico. There may be minor problems in the logging part,
 where the may be reverse resolution ob the ip address.

 For implementing IPv6 on outgoing session, mbcico as well as the IPv6
 patches for qico, by Andre Gruenenberg, may give a lead.

 On the other hand plenty of exaples can be found on how to convert a
 IPv4 application to IPv6.

 I never researched a segfault error I get when using flags in ifcico. It may
 be caused by the code not being 64 bit safe. I think the same happend when
 I tried qico on a 64 bit system.

 It is all listed on my round tuit, together with many other idea's.

 As I mentioned in another message I used ifcico as my main mailer for
 POTS, X75 and IPv4, before Binkd. I stopped supporting X75 when Eicon changed
 their interface on ther 4port serverboards. No nodes connected to X75 anyway.

 I can probably get it going when there is a need. With a lot of tinkering,
 the software (modem) on the Eicon board can support almost anything that one
 can send over ISDN.

Kees

--- GoldED+/LNX 1.1.5
 * Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)

.