Your IPv6 has problems?
Your IPv6 has problems?
Hello Joe,
- 22:57 [320] incoming from 69.165.170.121 (51198)
+ 22:57 [2068] incoming session with 69.165.170.121
- 22:57 [2068] SYS The Lion's Den
- 22:57 [2068] ZYZ Joe Delahaye
- 22:57 [2068] LOC Trenton, Ont. Cdn
- 22:57 [2068] NDL 115200,TCP,BINKP
- 22:57 [2068] TIME Fri, 4 Dec 2015 16:57:43 -0500
- 22:57 [2068] VER binkd/1.1a-73/Win32 binkp/1.1
+ 22:57 [2068] addr: 1:249/303@fidonet
+ 22:57 [2068] addr: 1:249/300@fidonet
+ 22:57 [2068] addr: 1:249/0@fidonet
+ 22:57 [2068] addr: 1:12/0@fidonet
Your IPv6 has problems?
No AAAA's.
No AAAA's.
No, there is no AAAA, because darktech.org is not set up for that as
yet. That is why I could only transmit in IPV6. Now it seems that something has changed, and appears to be getting worse, while testing
my IPv6 connection.
and appears to be getting worse, while testing my IPv6 connection.
Did your ISP actually email you to tell you IPv6 was available to you now? Or did it just *work* one day? I went through this at one point, where native IPv6
was working, but within a couple weeks it was shut off on me. I'm guessing my ISP was just testing it publicly at that time, but when I called to ask why it wasn't available any more, they said it wasn't "officially" supported yet, and that I would receive an email when it was. So I ended up going back to my he.net tunnel until that happens.
ping ipv4.google.com
ping6 ipv6.google.com
if both is pingelble it works, dont know what options on windows do the ipv6 ping, but on linux this is it
Your IPv6 has problems?
So it seems. I just did a test on IPV6 Test. I'll reset the router
and see what happens.
IPv6 is considered a Beta project. However, I was given a native
connection, complete with seperate login to the IPv6 server, and the numbers to use.
I shot off an email to support today to ask if
changes were made. I'm still logged into both servers, and rebooted
both modem and router several times.
I shot off an email to support today to ask if
changes were made. I'm still logged into both servers, and
rebooted both modem and router several times.
They're probably just going to say that the IPv6 connection may be
spotty at times as they work on it, but at least they're keeping it
active for you.
Mine was great for about 3 weeks and then *poof* it was just gone in
an instant.
I didn't notice it for a few days, and when I realized it hadn't come
back in about a week, I just went back to my old setup.
Until I get an email from them stating it's up full time, or however they're planning on announcing it to the public.. I'll stick with my stable and reliable tunnel.
Mine was great for about 3 weeks and then *poof* it was just gone
in an instant.
Bummer, but your situation is still better than mine. My ISP has
announced that they will roll out IPv6 "later this year". They have
been announcing that for five years now and from my POV, there is
little or no indication that anything is happening at all!
Alledgedly theur have been some tests in other regions, but nothing is
happening here.
I didn't notice it for a few days, and when I realized it hadn't
come back in about a week, I just went back to my old setup.
Well, at least something visible is happening at your end...
Until I get an email from them stating it's up full time, or
however they're planning on announcing it to the public.. I'll
stick with my stable and reliable tunnel.
I would do the same. Don't cancel those tunnels yet...
It seems to be up again, at least for outgoing:
- 06 Dec 01:01:03 [320] incoming from 2607:f2c0:f00e:4200:ccd:2101:cc13:2f35 (51634)
+ 06 Dec 01:01:03 [2916] incoming session with 2607:f2c0:f00e:4200:ccd:2101:cc13:2f35
- 06 Dec 01:01:03 [2916] SYS The Lion's Den
- 06 Dec 01:01:03 [2916] ZYZ Joe Delahaye
- 06 Dec 01:01:03 [2916] LOC Trenton, Ont. Cdn
- 06 Dec 01:01:03 [2916] NDL 115200,TCP,BINKP
- 06 Dec 01:01:03 [2916] TIME Sat, 5 Dec 2015 19:01:03 -0500
Outgoing also works:
+ 13:04 [828] outgoing session with 2607:f2c0:f00e:4200:f9e0:b9ff:6166:c8ef:24554
- 13:04 [828] OPT CRAM-MD5-0d5467028d9dda1769fc9eca88e330ee
+ 13:04 [828] Remote requests MD mode
- 13:04 [828] SYS The Lion's Den
- 13:04 [828] ZYZ Joe Delahaye
- 13:04 [828] LOC Trenton, Ont. Cdn
- 13:04 [828] NDL 115200,TCP,BINKP
- 13:04 [828] TIME Sun, 6 Dec 2015 07:04:17 -0500
But... for that to work I need to enter the literal IPv6 adress in my binkd.cfg.
You apparently have not managed yet to create an AAAA record for lionsdem.darktech.org. What is te problem?
IPv6 is considered a Beta project. However, I was given a native
Which means they're still very actively working to perfect it, which also means
the connectivity could be shoddy at times.
It seems to be up again, at least for outgoing:
Here is the answer I got from tech support today
Hi Joe,
Looks like this happened when a core router was turned up and it was missing a specific IPv6 configuration which has now been fixed. It would've effected certain routes and depended on hitting the right LNS
to make a connection.
Sorry for the inconvenience this may have caused,
Sorry for the inconvenience this may have caused,
Wow. I'm actually quite impressed with that response. :)
Here is the answer I got from tech support today
Looks like this happened when a core router was turned up and it was missing a specific IPv6 configuration which has now been fixed. It would've effected certain routes and depended on hitting the right LNS
to make a connection.
Looks like this happened when a core router was turned up and it was
missing a specific IPv6 configuration which has now been fixed. It
would've effected certain routes and depended on hitting the right
LNS to make a connection.
A surprisingly straight response. And if you haven't noticed it yet, they are running a L2TP setup.
You could have fooled me :) I know very little about that side of
the system. I don`t even know what an L2TP setup is.
There are two ways to get the PPPoE from the DSLAM to the access router. The old one is ATM and the newer one is L2TP. ATM requires an ATM network with ATM switches. L2TP is a tunnel protocol for OSI layer 2 and is IP based. The LNS ( L2TP Network Server) is the access router and endpoint of the L2TP tunnel with your PPPoE. It's just a virtual interface on that router.
Well, I learned something, but if it will stay in my head is another question :)
I don`t even know what an L2TP setup is.
Well, I learned something, but if it will stay in my head is another
question :)
Wait 'til I start talking BGP to you :)
Wait 'til I start talking BGP to you :)It will likely go right over my head <G>
Time for some IPv6 service again? 8-)
? 05 Apr 15:21:30 [1852] connection to 2:221/1@fidonet failed: {W32 API error 10060} Connection timed out
05 Apr 15:21:30 [1852] trying rbb.ath.cx [88.114.128.113]:24554...
05 Apr 15:21:30 [1852] connected
rebooted it, please see what happens.
You may also use the static addresses:
Sysop: | Nelgin |
---|---|
Location: | Plano, TX |
Users: | 509 |
Nodes: | 10 (1 / 9) |
Uptime: | 107:26:02 |
Calls: | 8,193 |
Files: | 15,442 |
Messages: | 913,134 |