Can someone please test IPv6 binkp connectivity to sysgod.org (2002:cbce:df98::4)? Thanks.
I've had an IPv4 > IPv6 relay set up on my system for a while but there haven't been any bites.
Can someone please test IPv6 binkp connectivity to sysgod.org (2002:cbce:df98::4)? Thanks.
I've had an IPv4 > IPv6 relay set up on my system for a while but there haven't been any bites.
Can someone please test IPv6 binkp connectivity to sysgod.org (2002:cbce:df98::4)? Thanks.
I've had an IPv4 > IPv6 relay set up on my system for a while but
there haven't been any bites.
Can someone please test IPv6 binkp connectivity to sysgod.org (2002:cbce:df98::4)? Thanks.
Can someone please test IPv6 binkp connectivity to sysgod.org (2002:cbce:df98::4)? Thanks.
I've had an IPv4 > IPv6 relay set up on my system for a while but
there haven't been any bites.
If you do not advertise it by adding an AAAA record to sysgod.org....
[2002:cbce:df98::4]... 23:03 [8688] connected + 23:03 [8688]
outgoing session with 2002:cbce:df98::4 Welcome to the club!
Thanks!
How about outgoing?
Outgoing I probably won't bother with until either we start getting
enough IPv6 only nodes to cause trouble, or until my ISP goes native
IPv6 (which will be sometime around the heat death of the universe).
Do I remember correctly there being talk about a flag for v6-only
nodes?
ATM I'm using 6to4,
which for some reason my ISP managed to partially break
- it works from some of my IPs but not others (confirmed on
their end). How they managed the screw up routing for half the IPs in
the same subnet to their own 6to4 gateway is beyond me. Hopefully
they don't break it any more.
When I get a round tuit I'll set up their 6RD tunnel as well.
Kees can you please test my Ipv6 connection of Binkd i hope it works ;) 2a02:1811:901:5a00:9cdc:b4eb:e92b:aeb4 24554
I've had an IPv4 > IPv6 relay set up on my system for a while but there haven't been any bites.
Can someone please test IPv6 binkp connectivity to sysgod.org (2002:cbce:df98::4)? Thanks.
Aha! Oops ;)
I had a SRV record set up for another IP, but only configured the 6 to 4 forwarding for one of them. I've removed the SRV record for now, I'll fix it properly later.
To bad.
+ 30 Apr 12:10:47 [16607] call to 2:562/140@fidonet
30 Apr 12:10:47 [16607] trying 2a02:1811:901:5a00:9cdc:b4eb:e92b:aeb4 [2a02:1811:901:5a00:9cdc:b4eb:e92b:aeb4]:24554... ? 30 Apr 12:11:08 [16607] connection to 2:562/140@fidonet failed: Connection timed out
I get the same result if I try a telnet to that address and port number.
An initial safe setup usually does not allow incoming IPv6, so you may have to open some ports.
+ 30 Apr 12:10:47 [16607] call to 2:562/140@fidonet
30 Apr 12:10:47 [16607] trying
2a02:1811:901:5a00:9cdc:b4eb:e92b:aeb4
[2a02:1811:901:5a00:9cdc:b4eb:e92b:aeb4]:24554... ? 30 Apr 12:11:08
[16607] connection to 2:562/140@fidonet failed: Connection timed out
I get the same result if I try a telnet to that address and port
number.
An initial safe setup usually does not allow incoming IPv6, so you
may have to open some ports.
Strange i need to check my firewall again that port is open when i do it local it works and also Dyndns see my Ipv6 adress like that...
xtremebbs.dyndns.info has address 94.224.25.65
xtremebbs.dyndns.info has IPv6 address 2a02:1811:901:5a00:9038:5f7:535f:b0d1 But there a get a timeout as well.
Can you try again please i have test it with a online port scanner and now it should work, there was a problem with my firewall rule on my ISP settings!
xtremebbs.dyndns.info has address 94.224.25.65
xtremebbs.dyndns.info has IPv6 address
2a02:1811:901:5a00:9038:5f7:535f:b0d1 But there a get a timeout as well.
Yes that will not works becoss Net2BBS it running on that and can not handle Ipv6 only Ipv4
And the only ports are open for ipv4 are 1024 and 24554.
But like i told on the binkd Ipv6 24554 it should work now see my other echomail...
Hello Rudi!
30 Apr 14 08:52, you wrote to me:
Can you try again please i have test it with a online port scanner and now >> it should work, there was a problem with my firewall rule on my ISPWell that solved your problem.
settings!
Congradulations.
30 Apr 16:31:15 [18914] trying xtremebbs.dyndns.info [2a02:1811:901:5a00:9038:5f7:535f:b0d1]...
30 Apr 16:31:15 [18914] connected
+ 30 Apr 16:31:15 [18914] outgoing session with 2a02:1811:901:5a00:9038:5f7:535f:b0d1
- 30 Apr 16:31:15 [18914] OPT CRAM-MD5-a8bc873029850f2de9364c60ad99caee
+ 30 Apr 16:31:15 [18914] Remote requests MD mode
- 30 Apr 16:31:15 [18914] SYS X-TReMe BBS
- 30 Apr 16:31:15 [18914] ZYZ The Doctor
- 30 Apr 16:31:15 [18914] LOC Leuven, Belgium
- 30 Apr 16:31:15 [18914] NDL 115200,TCP,BINKP
- 30 Apr 16:31:15 [18914] TIME Wed, 30 Apr 2014 16:31:12 +0200
- 30 Apr 16:31:15 [18914] VER binkd/1.1a-49/Win32 binkp/1.1
+ 30 Apr 16:31:15 [18914] addr: 2:562/140@fidonet
- 30 Apr 16:31:15 [18914] OPT EXTCMD
+ 30 Apr 16:31:15 [18914] done (to 2:562/140@fidonet, OK, S/R: 0/0 (0/0 bytes)
30 Apr 16:31:15 [18914] session closed, quitting...
Can someone please test IPv6 binkp connectivity to sysgod.org (2002:cbce:df98::4)? Thanks.
host sysgod.org
sysgod.org has address 203.206.223.152
sysgod.org has IPv6 address 2002:cbce:df98::4
But binkd finds:
+ 29 Apr 23:01:40 [27824] call to 3:712/848@fidonet
29 Apr 23:01:40 [27824] trying sysgod.org [2002:cbce:df9b::1]...
[2002:cbce:df98::4]... 23:03 [8688] connected + 23:03 [8688] outgoing session with 2002:cbce:df98::4
Welcome to the club!
How about outgoing?
Do have EleBBS support for Ip6 ?
I am a bit surprised the ISPs down undah don't put more pressure on
it. APNIC was the first RIR to deplete its IPv4 stock three years ago.
By now IPv4 adresses should be scarse in the ASIAN-PACIFIC region.
The brokennes of 6to4 is the main reason why most OS's/applications
first try IPv4 instead of IPv6. Windows normally tries IPv6 first, but
if the destination is a 6to4 tunnel, it only tries IPv6 if Ipv4 fails.
Forget about 6RD.
I suggest you get a decent 6in4 or AYIYA tunnel from a decent tunnel broker like he.net or SixXs.
Ping6 works, with very slow response, but doesn't seem to resolve
to an IPv6 address properly?
Traceroute6 doesn't work at all.
Doesn't surprise me.. 6to4 can be a bit like that since it depends on often public gateways and anycast routing. I'll get a proper tunnel set
up when I get a chance.
No. If the Net2BBS thing doesn't work out I'll see what I can do.
I had a SRV record set up for another IP, but only configured the 6 to
4 forwarding for one of them. I've removed the SRV record for now,
I'll fix it properly later.
2a02:1811:901:5a00:9cdc:b4eb:e92b:aeb4 24554
I had a SRV record set up for another IP, but only configured the 6 to
4 forwarding for one of them. I've removed the SRV record for now,
I'll fix it properly later.
just one hostname with both a and aaaa, then its solved, post the hostname in nodelist, be happy
"dig linode.junc.eu a"
"dig linode.junc.eu aaaa"
this way, just with your own hostname :)
I am a bit surprised the ISPs down undah don't put more pressure
on it. APNIC was the first RIR to deplete its IPv4 stock three
years ago. By now IPv4 adresses should be scarse in the
ASIAN-PACIFIC region.
I think we got in early while there were still plenty of addresses to
go around.
Developing countries with larger populations/growing
markets weren't so lucky. I hear China's been on the IPv6 bandwagon
for a while.
The brokennes of 6to4 is the main reason why most
OS's/applications first try IPv4 instead of IPv6.
Windows normally tries IPv6 first, but if the destination is a 6to4
tunnel, it only tries IPv6 if Ipv4 fails.
That's rather intelligent of them. *stunned*
Forget about 6RD.
What's wrong with 6RD?
I suggest you get a decent 6in4 or AYIYA tunnel from a decent
tunnel broker like he.net or SixXs.
Hurricane don't have any local POPs.
Six have one in NZ and they support RDNS, so that might be the way to
go. None of the other tunnel providers in Oz do RDNS so they're out.
Sysop: | Nelgin |
---|---|
Location: | Plano, TX |
Users: | 615 |
Nodes: | 10 (1 / 9) |
Uptime: | 53:36:40 |
Calls: | 9,850 |
Calls today: | 5 |
Files: | 96,973 |
Messages: | 1,080,731 |
Posted today: | 1 |