Charter 6RD connection not working in latest snaps

SebastianLee

Same result

route change -inet6 default 260244b8:yyyy::1
change net default: gateway 260244b8:yyyy::1

ping6 2607:f428:1::5353:1
6 packets transmitted, 0 packets received, 100.0% packet loss

ifconfig wan_stf inet6 260244b8:yyyy:0::1/32
ifconfig: ioctl (SIOCAIFADDR): File exists

ping6 2607:f428:1::5353:1
3 packets transmitted, 0 packets received, 100.0% packet loss

route change -inet6 default 260244b8:yyyy::68.114.165.1
change net default: gateway 260244b8:yyyy::68.114.165.1

ping6 2607:f428:1::5353:1
7 packets transmitted, 0 packets received, 100.0% packet loss

eri--

Can you give me access to the system as well its easier that way.

cmb

I'm pretty sure the 6rd patch change on January 25 broke these. I just reverted those.

edit: change backed out, don't upgrade to Saturday's snapshot if using 6rd.

cmb

Don't upgrade if using 6rd at all for the moment. That change resulted in a kernel panic reboot loop when connecting to 6rd on Saturday's snapshot. I reverted things back to where they were a couple days ago. Sunday's snapshot should be fine, but probably want to wait to hear back from someone here.

weekleyj

No Panic with the latest, but no IPv6. I've run the tests prescribed earlier (manually setting routes) with no effect.

survive

Hi guys,

Just tried the April 4th snapshot and it looks like 6RD is still broken.

Is there anything I can do to help you get the information you need to resolve this? Log files, remote access? Just let me know what you need and I would be happy to provide it.

-Will

cmb

Ermal has access to a system on my network that's now broken and can work from that.

Pertan

It looks like it's still broken with the April 17th snapshot. I get a IP from my ISP tunnel, but i cant ping any other machine on the internet using ping6 through ssh.

MaxPF

I have the same issue with 6RD tunnel on Rogers.

ddggttff3

Still not working with charter 6rd as of the May 10th build. Any updates on this?

survive

Hi ddggttff3,

The ticket I opened back on 3\15 was accepted, but hasn't been touched since. The only thing I've heard (via another post) is that they have a box that exhibits the same issue at the shop & they can work on it in-house, so there's no need for remote access to a customer machine.

-Will

maxinfo

Anyone know where I can find the January 27th snapshot to revert so I can test the 6RD with it? I'm running it with Centrylink/Quest.

swinn

@maxinfo:

Anyone know where I can find the January 27th snapshot to revert so I can test the 6RD with it? I'm running it with Centrylink/Quest.

I have the Jan 22 x86 build if you want it. 6RD was working with it. If I remember right, it broke with the 1/24/13 build.

maxinfo

Yea I'd love to give it a shot. Can you PM me a dropbox link or something similar?

Thanks much

survive

Hi guys,

Sure do wish they could figure out what changed with that build & sort this out. I'd love to see how much better 2.1 is after 5 months!

-Will

maxinfo

Thanks Swinn. The Jan 22 build is working well. The Centurylink gateway doesn't respond to ping but I can route and just changed the monitor IP by 2 hops down. Hopefully the 6rd problem will get worked out eventually but running beta software I expect things like this.

Thanks again for the help.

cmb

Should work with tomorrow's snapshot, my test system is fixed now.