I have a 6in4 HE tunnelbroker for IPv6 connectivity. The tunnel endpoint update script is working properly and the tunnel is established and IPv6 local addresses are handed out on booting the router. I am then fully connected via IPv6, as evidenced by a FF add-on that displays the IP of each webpage in the address bar.
At some random point in time, but usually within 30 to 60 minutes, I lose IPv6 connectivity at my computer. Opening a command window and attempting to ping ipv6.google.com will result in 4 failures. Attempting to ping google.com will sometimes result in failures to reach google's IPv6 address and sometimes succeed in reaching their IPv4 address, so I think DNS is still working, at least part of the time. Sometimes IPv6 connectivity spontaneously restores, perhaps even several times over the course of an afternoon but eventually fails completely.
But, at the same time as pings from the computer are failing, pings from the router (using the network tools tab in the GUI) may succeed, as do tests from other computers on the local network. Eventually failures get to the point where nothing gets through. The public IPv4 address remains unchanged, and matches the tunnel endpoint address reported on the Tunnelbroker webpage.
I have tried lowering the MTU from 1480 to 1472 to 1460 as suggested in other posts. But I suspect the problem is internal rather than the tunnel itself, given simultaneous failures and successes from different machines.
I'm at a loss what to try next. Is there something in the logs I should look for that might be a clue? Or a script that can insert something into the logs to mark when a computer is no longer reachable by IPv6?
I have had two other issues, but I don't think they are related. I'll mention them here just in case though:
1. The Asus DDNS service won't connect. I think the problem is that the name was used by my previous router. I followed Asus website and called them to have the name disassociated from the previous router so I could re-use the name. Meanwhile, I came across a post by Merlin that noted the easy way was to change the name in the old router to something else, which would free up the name for use with the new. I did that and it worked for a few days then quit. I suspect Asus finally got around to doing something at their end which screwed everything up at mine.
2. The other day, when I wrote a little script to track Wan-connected events and save them to a log on an SD card in a USB adapter, the router suddenly started lagging severely. Looking at the gui interface, I noticed core4 pegged at 100%. Then it dropped to 0 and core3 jumped to 100%. Then back again, repeatedly. Core2 started getting in on the action for a bit then all 3 were running at 100%. The system log was full of errors that seemed related to writing to the SD card. I powered down the router, had a look at the card in my computer and my little log file had some strange paragraphs inserted. I rebooted the router with an actual USB stick and all has been working fine since. So I think that issue was related to either the card or the adapter.
At some random point in time, but usually within 30 to 60 minutes, I lose IPv6 connectivity at my computer. Opening a command window and attempting to ping ipv6.google.com will result in 4 failures. Attempting to ping google.com will sometimes result in failures to reach google's IPv6 address and sometimes succeed in reaching their IPv4 address, so I think DNS is still working, at least part of the time. Sometimes IPv6 connectivity spontaneously restores, perhaps even several times over the course of an afternoon but eventually fails completely.
But, at the same time as pings from the computer are failing, pings from the router (using the network tools tab in the GUI) may succeed, as do tests from other computers on the local network. Eventually failures get to the point where nothing gets through. The public IPv4 address remains unchanged, and matches the tunnel endpoint address reported on the Tunnelbroker webpage.
I have tried lowering the MTU from 1480 to 1472 to 1460 as suggested in other posts. But I suspect the problem is internal rather than the tunnel itself, given simultaneous failures and successes from different machines.
I'm at a loss what to try next. Is there something in the logs I should look for that might be a clue? Or a script that can insert something into the logs to mark when a computer is no longer reachable by IPv6?
I have had two other issues, but I don't think they are related. I'll mention them here just in case though:
1. The Asus DDNS service won't connect. I think the problem is that the name was used by my previous router. I followed Asus website and called them to have the name disassociated from the previous router so I could re-use the name. Meanwhile, I came across a post by Merlin that noted the easy way was to change the name in the old router to something else, which would free up the name for use with the new. I did that and it worked for a few days then quit. I suspect Asus finally got around to doing something at their end which screwed everything up at mine.
2. The other day, when I wrote a little script to track Wan-connected events and save them to a log on an SD card in a USB adapter, the router suddenly started lagging severely. Looking at the gui interface, I noticed core4 pegged at 100%. Then it dropped to 0 and core3 jumped to 100%. Then back again, repeatedly. Core2 started getting in on the action for a bit then all 3 were running at 100%. The system log was full of errors that seemed related to writing to the SD card. I powered down the router, had a look at the card in my computer and my little log file had some strange paragraphs inserted. I rebooted the router with an actual USB stick and all has been working fine since. So I think that issue was related to either the card or the adapter.
