Update

I believe I’m using a pretty standard PathVector config, but I keep running into issues.

• HyeHost IPv6 Upstream can’t connect
• No IPv6 routes work
• Hurricane Electric IPv6 transit won’t work
• Tritan IPv6 transit won’t work

I suspect it has something to do with my IRR. The current version of my IRR is below. It can be frustrating to troubleshoot something that takes time to propagate.

aut-num:        AS46733
as-name:        X6C
descr:          P.O. Box 148
                Teays Valley WV 25569
                United States
member-of:      AS46733:AS-X6C
import:         from AS-X6C-UPSTREAM accept ANY
mp-import:      afi ipv6 from AS-X6C-UPSTREAM accept ANY
export:         to AS-ANY announce AS46733:AS-X6C
export:         to AS-X6C-UPSTREAM announce AS46733:AS-X6C
mp-export:      afi ipv6 to AS-ANY announce AS46733:AS-X6C
mp-export:      afi ipv6 to AS-X6C-UPSTREAM announce AS46733:AS-X6C
admin-c:        DURFE12-ARIN
tech-c:         NETWO9987-ARIN
mnt-by:         MNT-XL-116
created:        2024-08-31T13:40:44Z
last-modified:  2024-08-31T13:40:44Z
source:         ARIN

Troubleshooting

Troubleshooting these issues has taught me some helpful commands.

We’ve been running into a couple of issues where our peering sessions go down. It’s not a major issue, but we’re going to be working on stability. Also, we’ve noticed occasional issues with IPv4 on some servers and IPv6 on others.

Our peering db page is more accurate now since we started sharing our sessions directly with them.

As we build our network we continue to monitor the uptime of each node and that provider. This data will help us make longterm decisions reguarding who we rely on for our upstream.

We’ve already seen our providers dealing with a couple of issues. While we understand things happen, how the provider handles issues is what we consider most important.

Please refer to the pops page for an updated list of our points of presence.