I have setup the HE.NET tunnel that I acquired. It is installed for
use by 1:14/6, bbs.twisted-balloon.org, 2001:470:1f10:acd::2, 65.103.12.164. I can connect and send mail via IPv6. And port 24554
looks be open via Ipv6. Let me know what you see from your end.
I have setup the HE.NET tunnel that I acquired. It is installed for
use by 1:14/6, bbs.twisted-balloon.org, 2001:470:1f10:acd::2,
65.103.12.164. I can connect and send mail via IPv6. And port 24554
looks be open via Ipv6. Let me know what you see from your end.
IPv6 seems OK, but your binkp port is closed:
fido@vserv:~$ nmap -6 bbs.twisted-balloon.org -p 24554
Starting Nmap 7.40 ( https://nmap.org ) at 2019-06-18 19:22 CEST
Nmap scan report for bbs.twisted-balloon.org (2001:470:1f10:acd::2)
Host is up (0.12s latency).
Other addresses for bbs.twisted-balloon.org (not scanned): 65.103.12.164 rDNS record for 2001:470:1f10:acd::2: tunnel539534-pt.tunnel.tserv9.chi1.ipv6.he.net PORT STATE
SERVICE 24554/tcp closed binkp
Nmap done: 1 IP address (1 host up) scanned in 0.63 seconds
Firewall issue?
I have setup the HE.NET tunnel that I acquired. It is installed for
use by 1:14/6, bbs.twisted-balloon.org, 2001:470:1f10:acd::2, 65.103.12.164. I can connect and send mail via IPv6. And port 24554
looks be open via Ipv6. Let me know what you see from your end.
Hi Richard,
On 2019-06-18 19:23:36, you wrote to Jeff Smith:
Same here:I have setup the HE.NET tunnel that I acquired. It is installed forIPv6 seems OK, but your binkp port is closed:
use by 1:14/6, bbs.twisted-balloon.org, 2001:470:1f10:acd::2,
65.103.12.164. I can connect and send mail via IPv6. And port 24554
looks be open via Ipv6. Let me know what you see from your end.
fido@vserv:~$ nmap -6 bbs.twisted-balloon.org -p 24554
Starting Nmap 7.40 ( https://nmap.org ) at 2019-06-18 19:22 CEST
Nmap scan report for bbs.twisted-balloon.org (2001:470:1f10:acd::2)
Host is up (0.12s latency).
Other addresses for bbs.twisted-balloon.org (not scanned): 65.103.12.164
rDNS record for 2001:470:1f10:acd::2:
tunnel539534-pt.tunnel.tserv9.chi1.ipv6.he.net PORT STATE
SERVICE 24554/tcp closed binkp
Nmap done: 1 IP address (1 host up) scanned in 0.63 seconds
Firewall issue?
# nmap -6 bbs.twisted-balloon.org -p 24554
Starting Nmap 6.47 ( http://nmap.org ) at 2019-06-18 19:50 CEST
Nmap scan report for bbs.twisted-balloon.org (2001:470:1f10:acd::2)
Host is up (0.12s latency).
rDNS record for 2001:470:1f10:acd::2: tunnel539534-pt.tunnel.tserv9.chi1.ipv6.
e.net
PORT STATE SERVICE
24554/tcp closed binkp
Nmap done: 1 IP address (1 host up) scanned in 0.81 seconds
Bye, Wilfred.
IPv6 seems OK, but your binkp port is closed:
IPv6 seems OK, but your binkp port is closed:
IPv6 seems OK, but your binkp port is closed:
And now something else happens that is very odd:
- 21:59 [2436] SYS Ivan's BBS
- 21:59 [2436] ZYZ Ivan Ivanov
- 21:59 [2436] LOC Magadan, Russia
- 21:59 [2436] NDL 115200,TCP,BINKP
On 06-17-19 10:35, Jeff Smith wrote to Michiel Van Der Vlist <=-
Hello Michiel,
I have setup the HE.NET tunnel that I acquired. It is installed for use
by 1:14/6, bbs.twisted-balloon.org, 2001:470:1f10:acd::2,
65.103.12.164. I can connect and send mail via IPv6. And port 24554
looks be open via Ipv6. Let me know what you see from your end.
On 06-18-19 19:23, Richard Menedetter wrote to Jeff Smith <=-
IPv6 seems OK, but your binkp port is closed:
fido@vserv:~$ nmap -6 bbs.twisted-balloon.org -p 24554
On Tuesday June 18 2019 13:45, you wrote to Wilfred/Richard:
IPv6 seems OK, but your binkp port is closed:
And now something else happens that is very odd:
On 06-17-19 10:35, Jeff Smith wrote to Michiel Van Der Vlist <=-
I have setup the HE.NET tunnel that I acquired. It is installed for use
by 1:14/6, bbs.twisted-balloon.org, 2001:470:1f10:acd::2,
65.103.12.164. I can connect and send mail via IPv6. And port 24554
looks be open via Ipv6. Let me know what you see from your end.
Looks good here. :)
The system that I installed the tunnel on here is running Synchronet.
I was initially using the BinkIt mailer for SBBS. But after the
connection issues and as a test I disabled BinkIt and installed BinkD 1.1a-96. It looks to have started up upon installation while I was
editing BinkD's config file. For testing I have disabled it's
automatic loading. I will be tweaking the BinkD config to work more
easily with SBBS. SBBS is tossing the incoming mail received by BinkD.
That's odd as 1:14/6 can send and receive Fido traffic from otherIPv6 seems OK, but your binkp port is closed:
systems using IPv6. For testing I have forced Ipv6 BinkP connections
to 1:14/6 from other Fido systems here and they connect fine.
IPv6 seems OK, but your binkp port is closed:Hmm, I was able to connect to his binkp port.
fido@vserv:~$ nmap -6 bbs.twisted-balloon.org -p 24554
I have setup the HE.NET tunnel that I acquired. It is installed for
use by 1:14/6, bbs.twisted-balloon.org, 2001:470:1f10:acd::2, 65.103.12.164. I can connect and send mail via IPv6. And port 24554
looks be open via Ipv6. Let me know what you see from your end.
On 06-18-19 21:04, Jeff Smith wrote to Tony Langdon <=-
Cool. Part of the problem might have been the use of Synchronet's
BinkIt mailer. As the connection issue looks to have ceased when I
changed from BinkIt to BinkD as the mailer for Synchronet.
On 06-19-19 09:30, Richard Menedetter wrote to Tony Langdon <=-
It is open now.
It was not when I tested previously ;)
I have setup the HE.NET tunnel that I acquired. It is installed
for use by 1:14/6, bbs.twisted-balloon.org, 2001:470:1f10:acd::2,
65.103.12.164. I can connect and send mail via IPv6. And port
24554 looks be open via Ipv6. Let me know what you see from your
end.
On 06-18-19 21:04, Jeff Smith wrote to Tony Langdon <=-
Cool. Part of the problem might have been the use of Synchronet's
BinkIt mailer. As the connection issue looks to have ceased when I
changed from BinkIt to BinkD as the mailer for Synchronet.
Is Synchronet itself listening on IPv6?
On 06-19-19 12:34, Jeff Smith wrote to Tony Langdon <=-
Is Synchronet itself listening on IPv6?
Synchronet itself I don't think listens for activity on ports. Now the
BinkIT mailer that now comes with the current versions of Synchronet
does. In the past one had to setup and use BinkD as a FTN mailer. I
recall telling BinkIT to listen on both an v4 and a v6 IP and I got an error. But with a IPv6 tunnel I wouldn't think that would be necessary.
In any event BinkD seems to function fine with the IPv6 tunnel.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 296 |
Nodes: | 16 (2 / 14) |
Uptime: | 50:37:51 |
Calls: | 6,649 |
Calls today: | 1 |
Files: | 12,200 |
Messages: | 5,330,212 |