Can someone please check if you get an IPv6 connection with 2:203/0 on port 24555.
It shouldn't work, but I get some strange info in the log file indicating otherwise...
It shouldn't work, but I get some strange info in the log file
indicating otherwise...
Very strange. Well then I guess it's time to say good by to Argus
and Relay6 and become 100% binkd...
Bj”rn Felten wrote to Michiel van der Vlist <=-
Now, all of a sudden it works. I have no idea why it didn't work at first -- and also no idea why it works now. It really shouldn't, but it does. Via the built-in router program on an XP installation from 1998. Yeah, well, with SP3 of course, but just the same...
LOL! Yeah, really?
The first experiments with binkd in "full" mode was discouraging as
it appeared like IPv6 didn't work on incoming calls.
Now, all of a sudden it works. I have no idea why it didn't work at first -- and also no idea why it works now.
It really shouldn't, but it does. Via the built-in router program on
an XP installation from 1998. Yeah, well, with SP3 of course, but just
the same...
Nah, just like me he'll still perform a few tasks. E.g. taking care
of telnet calls to my BBS. So the POTS modem will be there a few years more.
I think that the last successful mailer call via POTS was this one.
8-)
14-Nov-2014 12:18:14 RING
14-Nov-2014 12:18:14 Answering call
^ 14-Nov-2014 12:18:34 CONNECT 9600 V42bis
14-Nov-2014 12:18:35 EMSI data receive
= 14-Nov-2014 12:18:36 Station : fido.vlist.eu
= 14-Nov-2014 12:18:36 Address : 2:280/5555.4
: 14-Nov-2014 12:18:36 SysOp : Michiel van der Vlist from
No, Argus does.
So if I need it running for telnet I can as well
let it keep on listening to the POTS line.
Ofcourse he does, his net has POTS only nodes just as net 2:280 has one.
LOL! A BBS program from the early 1990s, barely Y2K updated but
nothing more? You've gotta be kidding? :)
No, Argus plus Netfoss, but I think the IPv6 is thanks to Relay6.
Anyway, it took a helluva time to get it working, so I'm not
inclined to shut it down now. Why don't you try it out if you get a
few moments to spare? A blast from the past for sure...
All calls on my land line number from 1974 go via VoIP. On my
account I have two numbers, the second one is set to my BBS number
from 1989.
One is the regular one, the other is the modem connected one. I pay SEK69 (EUR7:50) per month -- calling costs included -- for the entire package whether I use both numbers or only one,
so why give one of them up?
Besides that, how long do you think it'll take before all the connecting nodes here are using the latest nodelist information? This
can be really interesting.
Yeah, you probably know the answer to that?
So if not for that reason, I'll be stuck with the old Argus 24554
port end for quite some time now, don't you think? 8-)
Ofcourse he does, his net has POTS only nodes just as net 2:280 has
one.
It has? Nodes? As in plural? The only one I can see is my own 203/208, and that still can accept a POTS call AFAIK.
Have you tried it out? It would be nice to see another successful POTS call in the log file after the 17 months since Michiel's call... 8-)
Anyone?
It seems to work, after I installed the password.
But it is not worth the trouble.
The time it takes to activate the modem
exceeds the full session time I have, when I connect using Binkp.
19-Apr-2016 19:31:55 RING
19-Apr-2016 19:32:22 Session completed successfully
19-Apr-2016 19:31:55 RING
19-Apr-2016 19:32:22 Session completed successfully
27 seconds wasn't all that bad for a POTS call, was it? I've seen much worse in the POTS era where we had far better modems on much better
lines than my present VoIP line.
Can someone please give my POTS line another try and see if you can do even better than Kees?
.
--- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1.16) Gecko/20101125
* Origin: news://eljaco.se (2:203/2)
Of course it isn't! But if you only have POTS that's all you can use.
The time it takes to activate the modem
exceeds the full session time I have, when I connect using Binkp.
Yes indeed. But the entire world is not so happy that they have internet connection the way we have. Some of them even have dial-up connections.
19-Apr-2016 19:31:55 RING
19-Apr-2016 19:31:55 Answering call
^ 19-Apr-2016 19:32:10 CONNECT 9600 V42bis
19-Apr-2016 19:32:12 EMSI data receive
= 19-Apr-2016 19:32:12 Station : == Double Dutch ==
= 19-Apr-2016 19:32:12 Address : 2:280/5003 2:280/0 77:8500/2
: 19-Apr-2016 19:32:12 SysOp : Kees van.Eeten from Heerhugowaard, The Netherlands
: 19-Apr-2016 19:32:12 Number : 31-72-5723988
: 19-Apr-2016 19:32:12 Flags : 33600,CM,XA,MO,V32B,V42B,X75,IBN,IFC,U,ENC
: 19-Apr-2016 19:32:12 Mailer : ifcico/2.14-tx8.10/Mon Dec 29 16:41:39 2014
: 19-Apr-2016 19:32:12 EMSI Addon : TZUTC [+0200]
= 19-Apr-2016 19:32:12 Time : 19-Apr-2016 19:32:11
19-Apr-2016 19:32:12 Password-protected session (auth=plain)
19-Apr-2016 19:32:12 Nothing for them
19-Apr-2016 19:32:12 EMSI data send
19-Apr-2016 19:32:13 Handshake time - 3 seconds
19-Apr-2016 19:32:13 Establishing Hydra transfer protocol
[ 19-Apr-2016 19:32:15 Hyd: Other's AppInfo="ifcico,2.14-tx8.10"
[ 19-Apr-2016 19:32:15 Hyd: Other's HydraRev=01-Dec-1992, flags: C32
19-Apr-2016 19:32:15 SEND: End of batch
19-Apr-2016 19:32:16 RECE: End of batch
19-Apr-2016 19:32:17 Hydra transfer protocol complete
19-Apr-2016 19:32:18 SEND: End of batch
19-Apr-2016 19:32:19 RECE: End of batch
19-Apr-2016 19:32:20 Hydra transfer protocol complete
* 19-Apr-2016 19:32:22 Session completed successfully
I just love the Hydra thing there,
well done ifcico... 8-)
And ofcourse ipv6 is missing.
I just love the Hydra thing there,
Yes Arjen Lentz was a weird guy, but a very creative deceloper.
It has served me well for over 16 years. The last couple of years I
had an issue with the programs. I node using Frontdoor and some
virtual modem could not exchange files. The derivative mbcico modified
by Michiel Broek of MBSE fame, worked perfectly. I did not manage tosingle out the difference that made mbcico work.
Now the node has switched to something supporting Binkp and I am back
to just running Binkd/ifcico. There are some other issues witfh
ifcico, but they donot really bother me. And ofcourse ipv6 is missing.
IPv6 is another feature that Michiel Broek added to mbcico. In fact, MBSE's support for IPv6 is the main reason I took the time to figure out how to make IPv6 work, first using a tunnel, and then native IPv6
support once my ISP enabled it.
One of these days I need to grab a copy of the ifcico source code and see about figuring that out. While I'm at it I can probably add in CRC mode support and the NR mode fixes I'm working on with mbcico now.
IPv6 is another feature that Michiel Broek added to mbcico. In fact, MBSE's support for IPv6 is the main reason I took the time to figure out how to make IPv6 work, first using a tunnel, and then native IPv6 support once my ISP enabled it.
Come to think of it, surely Arjen wasn't the only Hydra developer? I know for sure that JoHo (of FrontDoor) was involved in some way -- and maybe even Mats Wallin too?
After all, wasn't FrontDoor the first mailer to support the Hydra
--
the first ever truly duplex file conversation protocol ever?
Anyway, as a programmer that has written many programs for the
Psion
WorkAbout using the Hydra protocol I can only say that I'm truly impressed by the works of Arjen if he was really the only "inventor".
I am now in real need if IPv6 for ifcico, there are Hundreds of nodes that
want to use IFC and ITN over IPv6, it would give a boost to Fidonet :)))))
I am now in real need if IPv6 for ifcico, there are Hundreds of
nodes that want to use IFC and ITN over IPv6, it would give a boost
to Fidonet :)))))
ITN mailer waiting for your hydra session at [2001:470:1f15:cb0:f1d0:2:221:0]
:)
I am now in real need if IPv6 for ifcico, there are Hundreds of
nodes that want to use IFC and ITN over IPv6, it would give a boost
to Fidonet :)))))
On the socket side the changes should be quite simple, but the configuration stuff might need some effort. If you like, I could you give you the source of a sample network daemon supporting IPv4 and IPv6 (even interface scopes). I've written that one a few years ago.
I am now in real need if IPv6 for ifcico, there are Hundreds of nodes
that
want to use IFC and ITN over IPv6, it would give a boost to Fidonet
:)))))
ITN mailer waiting for your hydra session at [2001:470:1f15:cb0:f1d0:2:221:0]
ITN mailer waiting for your hydra session at
[2001:470:1f15:cb0:f1d0:2:221:0]
:)
I can probably say the same for
[2001:980:42ea:1:f1d0:2:280:5003]
But I cannot do a outgoing sessions using IPv6.
I can probably say the same for
[2001:980:42ea:1:f1d0:2:280:5003]
No telnet connection. :(
But I cannot do a outgoing sessions using IPv6.
I just made outgoing ipv6 telnet connection with Taurus (argus clone) via privoxy to my Xenia/2. :)
But it was not very convenient, because Taurus wants to resolve first and it does not accept ipv6 addresses. I needed to set up a dns name which resolves AAAA only.
At yhe time I used Dutchie and Henk Wevers was quick to include Hydra
and ofcourse Xenia by Arjen himself supported the protocol.
I am now in real need if IPv6 for ifcico, there are Hundreds of nodes that want to use IFC and ITN over IPv6, it would give a boost to
Fidonet :)))))
The only connects I get are from script kiddies using port knocking software.
The only connects I get are from script kiddies using port knocking
software.
I think most of us get our share of those.
The only connects I get are from script kiddies using port knocking
software.
I think most of us get our share of those.
LOL! Tell me about it. More than half of the incoming connections
here are from #23 script kiddies. For a few months I even disabled #23 here, but then again, that meant that I could no longer accept telnet calls to my BBS so now it's enabled again.
If only I could understand what those #23 calls are supposed to accomplish...
It was added to BinkleyTerm as well, in addition to Janus, which was Binkley's bidirectional transfer protocol.
Contact me via NetMail. MBSE's mbcico was originally based on ifcico, so backporting the IPv6 changes shouldn't be that difficult.
The only connects I get are from script kiddies using port knocking
software.
I think most of us get our share of those.
The only connects I get are from script kiddies using port knocking
software.
I think most of us get our share of those.
LOL! Tell me about it. More than half of the incoming connections here are from #23 script kiddies. For a few months I even disabled #23 here, but then again, that meant that I could no longer accept telnet calls to my BBS so now it's enabled again.
If only I could understand what those #23 calls are supposed to accomplish...
From my logs it looks as though they think that they'll log in as root (after guessing the password).
The scripts do not know what to do with an EMSI response. ;)
I can probably say the same for
[2001:980:42ea:1:f1d0:2:280:5003]
No telnet connection. :(
No, port 23 is certainly not available.
60177 and 60179 should be reachable, but there could be a firewall issue.
Sysop: | Nelgin |
---|---|
Location: | Plano, TX |
Users: | 510 |
Nodes: | 10 (1 / 9) |
Uptime: | 121:41:58 |
Calls: | 8,198 |
Calls today: | 5 |
Files: | 15,442 |
Messages: | 913,546 |
Posted today: | 8 |