Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Charter 6RD connection not working in latest snaps

    Scheduled Pinned Locked Moved
    2.1 Snapshot Feedback and Problems - RETIRED
    10
    39
    12.5k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S
      SebastianLee
      last edited by

      Didn't have much luck, none of those worked.

      route add -inet6 default 2602💯44b8:yyyy::1
      route: writing to routing socket: File exists
      add net default: gateway 2602💯44b8:yyyy::1: route already in table

      ping6 2607:f428:1::5353:1
      –- 2607:f428:1::5353:1 ping6 statistics ---
      12 packets transmitted, 0 packets received, 100.0% packet loss

      ping6 ipv6.google.com
      --- ipv6.l.google.com ping6 statistics ---
      12 packets transmitted, 0 packets received, 100.0% packet loss

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

      ping6 2607:f428:1::5353:1
      –- 2607:f428:1::5353:1 ping6 statistics ---
      5 packets transmitted, 0 packets received, 100.0% packet loss

      ping6 ipv6.google.com
      --- ipv6.l.google.com ping6 statistics ---
      6 packets transmitted, 0 packets received, 100.0% packet loss

      route add -inet6 default  2602💯44b8:yyyy::68.114.165.1
      route: writing to routing socket: File exists
      add net default: gateway 2602💯44b8:yyyy::68.114.165.1: route already in table

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

      ping6 ipv6.google.com
      --- ipv6.l.google.com ping6 statistics ---
      10 packets transmitted, 0 packets received, 100.0% packet loss

      1 Reply Last reply Reply Quote 0
      • E
        eri--
        last edited by

        Ah you should delete the default gateway before trying route add :)

        or issue 'route change' instead of 'route add'

        1 Reply Last reply Reply Quote 0
        • S
          SebastianLee
          last edited by

          Same result

          route change -inet6 default 2602💯44b8:yyyy::1
          change net default: gateway 2602💯44b8:yyyy::1

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

          ifconfig wan_stf inet6 2602💯44b8: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  2602💯44b8:yyyy::68.114.165.1
          change net default: gateway 2602💯44b8:yyyy::68.114.165.1

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

          1 Reply Last reply Reply Quote 0
          • E
            eri--
            last edited by

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

            1 Reply Last reply Reply Quote 0
            • C
              cmb
              last edited by

              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.

              1 Reply Last reply Reply Quote 0
              • C
                cmb
                last edited by

                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.

                1 Reply Last reply Reply Quote 0
                • W
                  weekleyj
                  last edited by

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

                  1 Reply Last reply Reply Quote 0
                  • S
                    survive
                    last edited by

                    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

                    1 Reply Last reply Reply Quote 0
                    • C
                      cmb
                      last edited by

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

                      1 Reply Last reply Reply Quote 0
                      • P
                        Pertan
                        last edited by

                        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.

                        Country: Sweden | ISP: Telia FiberLAN

                        1 Reply Last reply Reply Quote 0
                        • M
                          MaxPF
                          last edited by

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

                          1 Reply Last reply Reply Quote 0
                          • D
                            ddggttff3
                            last edited by

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

                            1 Reply Last reply Reply Quote 0
                            • S
                              survive
                              last edited by

                              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

                              1 Reply Last reply Reply Quote 0
                              • M
                                maxinfo
                                last edited by

                                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.

                                1 Reply Last reply Reply Quote 0
                                • swinnS
                                  swinn
                                  last edited by

                                  @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.

                                  1 Reply Last reply Reply Quote 0
                                  • M
                                    maxinfo
                                    last edited by

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

                                    Thanks much

                                    1 Reply Last reply Reply Quote 0
                                    • S
                                      survive
                                      last edited by

                                      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

                                      1 Reply Last reply Reply Quote 0
                                      • M
                                        maxinfo
                                        last edited by

                                        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.

                                        1 Reply Last reply Reply Quote 0
                                        • C
                                          cmb
                                          last edited by

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

                                          1 Reply Last reply Reply Quote 0
                                          • First post
                                            Last post
                                          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.