Tunnel adapter Local Area Connection:
Connection-specific DNS Suffix . :
IPv6 Address. . . . . . . . . . . : fd03:b3bf:62ca:8812:7521:fab0:5455:8c10
Link-local IPv6 Address . . . . . : fe80::f817:b5b5:82b:dff7%9
IPv4 Address. . . . . . . . . . . : 169.254.145.77
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . :
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . :
IPv6 Address. . . . . . . . . . . :
2002:4ac:d3:1:c71:c459:6cce:9fea
Temporary IPv6 Address. . . . . . :
2002:4ac:d3:1:29ec:3e3c:daf:23a4
Link-local IPv6 Address . . . . . : fe80::c71:c459:6cce:9fea%3
IPv4 Address. . . . . . . . . . . : 192.168.0.187
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : fe80::12fe:edff:feaf:8afc%3
192.168.0.1
Tunnel adapter Local Area Connection* 11:
Connection-specific DNS Suffix . :
IPv6 Address. . . . . . . . . . . : 2001:0:5ef5:79fd:8d7:2503:3f57:ff44
Link-local IPv6 Address . . . . . : fe80::8d7:2503:3f57:ff44%5
Default Gateway . . . . . . . . . :
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
IPv6 Address. . . . . . . . . . . :
2002:4ac:d3:1:6c73:241b:d0fd:4fbb
Temporary IPv6 Address. . . . . . :
2002:4ac:d3:1:8048:f754:3c9d:18cc
Link-local IPv6 Address . . . . . : fe80::6c73:241b:d0fd:4fbb%8
IPv4 Address. . . . . . . . . . . : 192.168.0.101
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : fe80::12fe:edff:feaf:8afc%8
192.168.0.1
Again, two 6to4 addresses, one created by the privacy extensions. And the link-local address.
So, I'm guessing that NO IPv6 connection exists to or from this
system? Like I
mentioned. this is completely new to me <G> I am using the stock
router
software. I picked this one because apparently it can be flashed
with third
party software like Open-WRT.
No native IPv6 ;-) 6to4 and Teredo are tunneling methods.
OpenWrt is great! Tons of features and even the trunk version is rock solid.
I knew that was a tunnel, but setting it to 6to4 was the only way I got any address showing, so I thought I would try that. I have no idea how to go further.
OpenWrt is great! Tons of features and even the trunk version is
rock solid.
Maybe I will give it a try. Cant do any worse then what is on it now. Having problems staying connected to my BBS from the main computer on my network. I have not tried the other ones yet. I start a message answer, and am stopped dead, and shut down. Frustrating. It may be coincidence but who knows.
It seems that it can be worse. Open WRT for my TPLink model AC1750,
will not support the 5 Ghz protocol. Only the 2.4 side. Should
have purchased the cheaper model it looks like. Also, I was having problems staying connected via telnet, even on the same machine, with
IPv6 enable. I shut it off. Had to reboot the router to make the
change, and now it all works. Perhaps a coincedence, which I will
test later on, but now I can at least read and reply to my mail.
--- SBBSecho 2.27-Win32
* Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)
If you bought a newer router, it will take open source firmware developers a little time to get ahold of that specific router and make sure the firmware works for it. I got an Asus RT-AC68R somewhat recently and DD-WRT was the same deal. At the time it didn't support 5ghz and a few other features, but I'm sure it does now.
Anyhow, keep an eye on the development of OpenWRT for your router, it will be fully supported soon most likely.
As far as your issue.. I could possibly see that happening if you don't have native IPv6 (or a tunnel setup, for that matter) and enable IPv6 anyways. What you experienced probably shouldn't happen, but I suppose it could.
Until you actually have native IPv6 or a tunnel setup, I'd keep it disabled as it doesn't do any good for you anyways.
It seems that it can be worse. Open WRT for my TPLink model AC1750,
will not
support the 5 Ghz protocol. Only the 2.4 side. Should have
purchased the
cheaper model it looks like. Also, I was having problems staying
Let's check http://wiki.openwrt.org/toh/tp-link/tl-wdr7500:
For the Archer C7 v1.x and WDR7500 v2.x, the 5GHz 802.11a/n/ac functionality is not supported, and likely will never be, since support for the AR1A (v1) variant of QCA9880 chip is not included in the open source ath10k driver. The Archer C7 v2.x uses the BR4A (v2) variant which is supported in ath10k.
The 5GHz module seems to be a Mini PCIe. So you could replace it with something supported, but would have to add the driver manually, I assume. If that's too much hassle, the TL-WDR4300 (about EUR 50) is fully supported and got also dual band.
Sysop: | Nelgin |
---|---|
Location: | Plano, TX |
Users: | 611 |
Nodes: | 10 (1 / 9) |
Uptime: | 48:44:42 |
Calls: | 9,831 |
Files: | 16,216 |
Messages: | 1,080,209 |