Quick HYEHOST path: Start with HYEHOST IP Transit if you need BGP over tunnel, pair it with RIPE IPv6 leasing or ARIN IPv6 services if you need clean IPv6 space, and use AS47272 network information when checking routing context.

BGP can feel difficult to get started with.

You need an ASN, IP space, route objects, RPKI, a router, a tunnel, filters, and enough patience to understand why a route is accepted in one place but not visible somewhere else yet. For new network operators, hobby networks, students, small labs, and early-stage projects, the hardest part is often finding a practical way to learn without committing to expensive full transit.

That is why free IPv6 transit over tunnel is useful.

It gives ASN holders a way to practice real BGP, announce IPv6 prefixes, test filters, build router configs, and understand internet routing using a controlled tunnel-based service. It is not a replacement for paid dual-stack transit, but it is a strong starting point for learning and lightweight IPv6 networks.

This guide explains what free IPv6 transit is, how BGP over tunnel works, what you need before ordering, the mistakes that cause sessions to fail, and how HYEHOST makes the process easier from the panel.

What Is IPv6 Transit?

IP transit is a service where one network allows another network to reach the wider internet through BGP.

In a normal transit relationship:

  • Your network has an ASN.
  • You announce prefixes to the transit provider.
  • The provider accepts your routes if they pass filtering.
  • The provider announces those routes onward where appropriate.
  • Your network receives routes back, such as a default route, default plus local routes, or a full table.

IPv6 transit is the same idea, but only for IPv6 routes.

This is useful because IPv6 address space is widely available, clean IPv6 routing is easier to start with than IPv4, and many network operators use IPv6 labs as their first real BGP experience.

What Is BGP Over Tunnel?

BGP over tunnel means the BGP session runs across a tunnel rather than a physical cross-connect.

Instead of connecting routers in the same datacenter, the customer creates a tunnel from their router or server to the HYEHOST transit location. The BGP session then peers over the private tunnel IPs.

Common tunnel types include:

  • WireGuard.
  • GRE.
  • GRETAP.
  • SIT.
  • VXLAN.

For many users, WireGuard is the easiest because it works well behind NAT and gives a clean encrypted tunnel. GRE and other tunnel types are useful for users who already run routers or want a more traditional network setup.

Free IPv6 Transit vs Paid Dual-Stack Transit

Free IPv6 transit is designed for learning, testing and lightweight IPv6 use.

It usually means:

  • IPv6 only.
  • A limited commit.
  • No IPv4 transit.
  • BGP included.
  • Tunnel-based delivery.
  • Basic export options.
  • Abuse and idle-session cleanup rules.

Paid dual-stack transit is different.

It can include:

  • IPv4 and IPv6.
  • Higher commits.
  • More production-focused usage.
  • Paid bandwidth.
  • More flexibility for real services.
  • Upgrade paths.

The important point is that free IPv6 transit is still real BGP. You still need correct IRR and RPKI, and you still need a router configuration that actually announces your prefix.

Service fit: Free IPv6 transit is best for learning and lightweight IPv6 routing. For production dual-stack routing, higher commit, or customer-facing network use, compare the paid options on our IP Transit page.

What You Need Before Ordering Free IPv6 Transit

Before ordering, make sure you have the basics ready.

1. An ASN

You need an Autonomous System Number. This is your network identity in BGP.

The ASN must be yours or properly authorized for you to use. If your ASN has no valid routing data, the panel may block or review the order.

2. IPv6 Prefixes

You need IPv6 prefixes that your ASN is allowed to announce.

These might be:

  • Your own allocated IPv6 space.
  • Assigned space from a provider.
  • Leased IPv6 space.
  • A prefix from HYEHOST IPv6 leasing.

The prefix must be suitable for internet routing. Very small or invalid prefix sizes may not be accepted.

3. IRR Route6 Objects

IRR route objects tell networks which ASN is expected to originate a prefix.

For IPv6, this is usually a route6 object.

If your prefix is 2001:db8:1234::/48 and your ASN is AS64500, route filtering systems expect to see a route6 object matching that relationship.

Without correct IRR, routes may be filtered.

4. RPKI ROA

RPKI helps prove which ASN is allowed to originate a prefix.

A ROA includes:

  • Prefix.
  • Origin ASN.
  • Max length.

The max length is important. If your ROA is for /40 with max length /40, then a /48 announcement under it may be invalid. If you plan to announce more specifics, the max length must allow them.

5. A Router or Server

You need somewhere to run the tunnel and BGP.

Common options:

  • Debian or Ubuntu VPS with Bird.
  • FRRouting on Linux.
  • MikroTik CHR.
  • VyOS.
  • JunOS, RouterOS, OpenBSD, or another routing platform.

Linux with Bird or FRR is a common starting point because it is flexible and well documented.

HYEHOST Services That Pair With Free IPv6 Transit

Many people find this guide while searching for a free IPv6 transit provider, a BGP tunnel provider, or a way to learn BGP with an ASN. The useful next step depends on what you already have.

  • IP Transit is the main HYEHOST page for BGP over tunnel, IPv6 transit and dual-stack transit options.
  • RIPE IPv6 leasing is useful if you need clean IPv6 space that can be routed with the right records.
  • ARIN IPv6 services are useful for customers who need ARIN-region IPv6 options, SWIP and delegated rDNS.
  • IPv4 via tunnel is different from BGP transit, but it can help if you need routed IPv4 without operating your own BGP session.
  • Cloud VPS or VDS Hosting can be used as a router, lab box or BGP testing host when the workload needs compute as well as transit.

Those pieces reflect how customers actually build small networks: IP space, tunnel transport, a router, validation records and a panel that keeps the service details visible.

How the Tunnel Fits In

The tunnel is only the transport path.

It does not replace BGP. It does not automatically announce prefixes. It simply creates a path between your router and HYEHOST.

Think of the setup in layers:

  1. Underlay internet connection.
  2. Tunnel interface.
  3. Tunnel IP addresses.
  4. BGP session over the tunnel.
  5. Route announcements.
  6. HYEHOST route filtering.
  7. Upstream propagation.

If layer 2 is broken, BGP will not establish.

If BGP establishes but routes are not accepted, the issue is usually IRR, RPKI, import limits, AS-SET, prefix length, or your router not actually exporting the route.

If HYEHOST accepts the route but the route is not visible everywhere yet, upstream filters may need time to update.

WireGuard for BGP Transit

WireGuard is often the easiest tunnel option.

A typical WireGuard transit setup has:

  • Your private key.
  • Your public key entered in the panel.
  • HYEHOST server public key.
  • HYEHOST endpoint IP and port.
  • Your tunnel IPv6 address.
  • HYEHOST tunnel IPv6 address.
  • AllowedIPs for the HYEHOST tunnel peer.

For a transit tunnel, be careful with AllowedIPs.

Many VPN tutorials use:

  • 0.0.0.0/0
  • ::/0

That routes all traffic through the tunnel. For BGP transit, that may not be what you want. In many setups, you only need the HYEHOST tunnel peer address in AllowedIPs so the BGP session can establish. Your own announced prefixes are then handled by BGP and HYEHOST-side filtering.

If you are behind NAT, PersistentKeepalive = 25 is normally helpful.

GRE and Other Tunnel Types

GRE is common for routed tunnel setups.

For GRE:

  • Local address is your public endpoint.
  • Remote address is the HYEHOST endpoint.
  • The tunnel interface gets your assigned tunnel IP.
  • BGP peers to the HYEHOST tunnel IP.

If the underlay is IPv6, Linux uses ip6gre.

GRETAP and VXLAN are more layer-2 oriented. They can be useful, but they are usually not required for a basic routed BGP session.

SIT is for IPv6 over IPv4. It is not for IPv4 transit.

The most important rule is to separate the public endpoint from the BGP neighbour address. The public endpoint brings up the tunnel; the BGP neighbour is normally the HYEHOST tunnel address.

Choosing Export Mode

Transit services often offer different export modes.

Common options:

  • Default route only.
  • Default plus local routes.
  • Full table.

For beginners, default route is usually enough. Your router sends unknown destinations to HYEHOST without needing a large routing table.

Default plus local routes can be useful when you want a default route plus HYEHOST/downstream/local visibility.

Full table is more advanced. It requires more memory, more CPU, and better router tuning. Do not select full table just because it sounds more serious. Use it when you actually need it.

Common Reasons BGP Over Tunnel Fails

The tunnel is not up

Check:

  • Can you ping the HYEHOST tunnel IP?
  • Is the tunnel interface up?
  • Is the endpoint IP correct?
  • Is the WireGuard public key correct?
  • Is NAT blocking return traffic?
  • Is the firewall allowing the tunnel protocol or UDP port?

The BGP neighbour IP is wrong

Do not peer to the public endpoint IP unless the panel specifically says to.

Peer to the assigned HYEHOST tunnel address.

The local ASN is wrong

Your router should use your ASN. The neighbour ASN should be HYEHOST, normally AS47272 unless the service context says otherwise.

The route is not being exported

Your BGP daemon may establish but export zero prefixes.

Check:

  • Does the route exist in your local routing table?
  • Does Bird/FRR have a static route for it?
  • Does your export filter allow it?
  • Is the source protocol included?
  • Is the prefix length allowed?

IRR or RPKI is wrong

If filters reject your prefix, check:

  • Route6 object exists.
  • Origin ASN matches.
  • ROA is valid.
  • ROA max length allows the prefix size.
  • AS-SET contains the right ASN if you use an AS-SET.

Import limits are exceeded

If you announce more prefixes than your session limit allows, some routes may be filtered or ignored. Keep announcements clean and intentional.

Upstream filters have not updated yet

Even after HYEHOST accepts your route, upstream networks may take time to update filters. In some cases this can take up to 12 hours.

That is normal in transit operations. The key is to confirm the route is accepted by HYEHOST first.

A Simple Bird Example Structure

This is not a copy-paste config for every setup, but it shows the structure.

router id 192.0.2.10;

define MY_AS = 64500;
define HYEHOST_AS = 47272;
define HYEHOST_V6 = 2001:db8:ffff::1;

protocol static announce_v6 {
  ipv6;
  route 2001:db8:1234::/48 blackhole;
}

filter export_to_hyehost {
  if net = 2001:db8:1234::/48 then accept;
  reject;
}

protocol bgp hyehost_v6 {
  local as MY_AS;
  neighbor HYEHOST_V6 as HYEHOST_AS;
  source address 2001:db8:ffff::2;

  ipv6 {
    import all;
    export filter export_to_hyehost;
  };
}

In a real setup, replace:

  • Your ASN.
  • HYEHOST tunnel neighbour.
  • Your tunnel source address.
  • Your actual prefix.
  • Import/export policy.

If using FRR, MikroTik or VyOS, the structure is similar even though the syntax differs.

How HYEHOST Helps

HYEHOST provides a panel-based flow for ordering and managing transit sessions.

Depending on location and service type, the panel can show:

  • Location selection.
  • Tunnel type.
  • Tunnel endpoint details.
  • Assigned tunnel IPs.
  • BGP ASN.
  • Export mode.
  • Session status.
  • Usage.
  • Route information.
  • Admin and support visibility.

For users learning BGP, this is important because the hard part is not just getting a tunnel. The hard part is knowing which layer is broken when something does not work.

HYEHOST also includes a network helper inside the panel for BGP and transit configuration review. It is designed to help users understand whether they are configuring normal VPS BGP or transit via tunnel, because those are different setups.

When to Upgrade From Free IPv6 Transit

Free IPv6 transit is a starting point. Upgrade when you need:

  • IPv4 transit.
  • Higher commit.
  • Production traffic.
  • More predictable commercial terms.
  • More bandwidth.
  • Dual-stack routing.
  • More advanced routing requirements.

If you are just learning IPv6 BGP, free transit is useful. If you are running customer-facing production networks, paid transit is usually the better fit.

Best Practices Before Opening a Support Ticket

If your session does not work, collect:

  • Tunnel type.
  • Router software.
  • Whether the tunnel peer pings.
  • BGP state.
  • Exported prefix list.
  • IRR route6 object.
  • ROA status.
  • Any Bird/FRR/MikroTik logs.
  • Whether you are IPv6-only or dual-stack.

Do not paste private keys, passwords or API tokens.

Support can help faster when the layers are clear:

  1. Tunnel up?
  2. BGP established?
  3. Prefix exported?
  4. Prefix accepted?
  5. Prefix visible upstream?

Final Thoughts

Free IPv6 transit over tunnel is one of the best ways to learn real BGP without starting with expensive dedicated connectivity.

It teaches the important parts:

  • ASN ownership.
  • Tunnel transport.
  • BGP peering.
  • Route export.
  • IRR.
  • RPKI.
  • Prefix filtering.
  • Upstream propagation.

The main thing is to remember that BGP over tunnel has two separate jobs: the tunnel must work, and BGP must be configured correctly over that tunnel.

HYEHOST free IPv6 transit is designed to make that learning path easier while still keeping the routing environment controlled and abuse-resistant. Start with IPv6, keep your filters clean, understand each layer, and upgrade when your network needs more.

Free IPv6 Transit FAQ

Can I get free IPv6 transit over a tunnel with my own ASN?

Yes. HYEHOST free IPv6 transit is designed for ASN holders who want to learn and test real IPv6 BGP over a tunnel. You still need valid routing data, including the right origin ASN, IRR route6 objects and RPKI ROA where applicable.

Which tunnel types can be used for IPv6 BGP transit?

HYEHOST can support tunnel options such as WireGuard, GRE, SIT and VXLAN depending on the location and service. WireGuard is often easiest for users behind NAT, while GRE and SIT are common for more traditional routed tunnel setups.

Do I need IRR and RPKI for free IPv6 transit?

Yes. Clean IRR and RPKI data are important because HYEHOST route filters use routing authorization data to decide whether your IPv6 prefix should be accepted and announced onward.

When should I upgrade from free IPv6 transit to paid IP transit?

Upgrade when you need production traffic, higher commits, IPv4 or dual-stack routing, stronger commercial terms, or more advanced routing requirements than a learning-focused IPv6-only transit session.

Ready to compare options? Review HYEHOST IP Transit for BGP transit, IPv4 Tunnels for routed IPv4 without BGP, or Network Info for AS47272 infrastructure context.

Related HYEHOST pages