IPv4 addresses are harder to obtain, more expensive to lease and more awkward to manage directly than they used to be. Even so, plenty of real services still need IPv4: websites, applications, mail systems, VPNs, game servers, APIs, monitoring, customer equipment and compatibility with networks that are not fully IPv6-ready.

HYEHOST IPv4 via tunnel is designed for that gap. HYEHOST routes an assigned IPv4 prefix to you over a tunnel, and you use those addresses on your own server, router, VPS, lab or network without needing a physical port in the same location as the IPv4 space.

This guide explains what IPv4 via tunnel is, where it fits, how it works inside the HYEHOST panel and what customers should check when setting it up.

What IPv4 via tunnel means

IPv4 via tunnel is a routed IPv4 service delivered over a tunnel between HYEHOST and your endpoint. Instead of assigning one IPv4 address directly to a VPS interface, HYEHOST gives you a routed IPv4 prefix such as a /29, /28 or another available size. That prefix is routed to your tunnel endpoint, and you configure your side to use the addresses.

In simple terms, HYEHOST announces and routes the IPv4 space, a tunnel is created between HYEHOST and your server, your IPv4 prefix is routed across that tunnel, you assign usable IPv4 addresses on your side, and traffic flows through the tunnel to and from the internet.

HYEHOST note: IPv4 via tunnel gives you routed IPv4 without requiring you to run BGP yourself.

Why use IPv4 via tunnel?

IPv4 via tunnel is useful when you need real routed IPv4 space but do not need a full BGP transit session. It is often simpler than transit because you do not need an ASN, IRR records, ROAs or BGP configuration. You need a supported tunnel endpoint and correct routing on your side.

Common use cases include hosting websites or APIs on IPv4, adding IPv4 connectivity to infrastructure that only has IPv6 or limited IPv4, building lab networks, hosting VPN services, running monitoring systems, providing IPv4 to internal servers over a routed tunnel and using routed IPv4 space without managing BGP.

IPv4 via tunnel compared with BGP transit

IPv4 via tunnel and IP transit via tunnel are related, but they are not the same. With IP transit, you normally run BGP with HYEHOST. You announce your own prefixes, receive routes from HYEHOST and manage routing policy.

With IPv4 via tunnel, HYEHOST assigns and routes a HYEHOST IPv4 prefix to your tunnel. You do not need to announce the prefix yourself.

IPv4 via tunnel is best if you need routed IPv4 addresses, do not have an ASN, do not want to manage BGP, want a simpler setup or only need HYEHOST to route assigned IPv4 to you. IP transit is better if you have your own ASN, want to announce your own IP space, need BGP control, want default routes or full table options, or operate a network rather than just using assigned IPs.

Benefits of HYEHOST IPv4 via tunnel

HYEHOST IPv4 via tunnel is built into the HYEHOST panel, making it easier to order, manage, monitor and cancel from the same account you use for other hosting and network services.

  • Routed IPv4 without BGP.
  • Multiple tunnel type options where available.
  • Location selection.
  • Clear assigned prefix details.
  • Example configuration from the panel.
  • Traffic monitoring.
  • Reverse DNS support where available.
  • Billing and cancellation controls.
  • Faster setup than fully manual routed IPv4.

For customers already using HYEHOST VPS, transit, IPv6 leasing or dedicated services, IPv4 via tunnel fits naturally into the same panel, billing and support flow.

Available tunnel types

HYEHOST can support different tunnel types depending on location and product availability. Common tunnel types may include GRE, SIT, GRETAP, VXLAN and WireGuard.

The best tunnel type depends on your endpoint, operating system, network and use case. GRE and SIT are common for simple routed tunnel setups. WireGuard can be useful where encrypted tunnel transport is preferred. VXLAN and GRETAP may be useful for more advanced layer 2 style use cases, depending on support and configuration.

The HYEHOST panel shows the tunnel types available for the selected location.

How it works in the HYEHOST panel

The HYEHOST panel is designed to handle the service lifecycle. From the IPv4 via tunnel page, customers can view active IPv4 tunnel services, order a new tunnel, select a location, select a prefix size, choose a tunnel type, enter endpoint details, view the assigned IPv4 prefix, view HYEHOST endpoint details, review example configuration, monitor traffic usage, manage billing and cancel the service when needed.

Once provisioned, the panel gives you the details required to configure your side of the tunnel. Keep those values close while configuring your endpoint; using the wrong local address, remote address or tunnel type is one of the easiest ways to lose time.

Ordering IPv4 via tunnel

A typical order flow is straightforward:

  1. Log in to the HYEHOST panel.
  2. Open the IPv4 via tunnel section.
  3. Choose to order a new tunnel.
  4. Select the location.
  5. Choose the prefix size.
  6. Select the tunnel type.
  7. Enter your endpoint IP or hostname if required.
  8. Review pricing, included usage and plan details.
  9. Complete payment.

After payment, the panel provisions the service and displays your assigned prefix and tunnel details. If the selected product requires staff review or manual handling, the panel or support team will let you know.

Understanding the assigned IPv4 prefix

When you order IPv4 via tunnel, you receive a routed IPv4 prefix. For example, a /29 contains 8 total IPv4 addresses. Some addresses may be reserved depending on the routing design, gateway use or service rules. The panel will show the assigned prefix and any relevant tunnel addressing details.

In most routed setups, you assign one or more usable IPv4 addresses on your server, loopback interface, router, firewall or downstream system. You should not route the assigned prefix back toward HYEHOST. HYEHOST already routes the prefix to your tunnel. Your side normally needs to accept the routed prefix and ensure return traffic goes back through the tunnel.

Example Linux GRE over IPv6 concept

The exact commands depend on your service details, tunnel type, endpoint IPs and assigned prefix. A GRE over IPv6 setup generally follows this shape:

ip -6 tunnel add gre-hyehost mode ip6gre \
  local YOUR_IPV6_ENDPOINT \
  remote HYEHOST_IPV6_ENDPOINT \
  ttl 255

ip link set gre-hyehost up

ip addr add TUNNEL_POINT_TO_POINT_IP dev gre-hyehost

You can then assign an IPv4 address from your routed prefix locally:

ip addr add YOUR_ROUTED_IPV4/32 dev lo

Then make sure traffic sourced from your routed IPv4 prefix returns through the tunnel:

ip route replace default via HYEHOST_TUNNEL_GATEWAY dev gre-hyehost table 120
ip rule add from YOUR_ROUTED_PREFIX table 120 priority 120

These commands are examples only. Use the exact values and guidance shown in your HYEHOST panel for your service.

Testing your IPv4 tunnel

After configuring your tunnel, test it step by step. First, check that the tunnel interface exists:

ip addr show

Then check that your tunnel endpoint can reach the HYEHOST tunnel side:

ping HYEHOST_TUNNEL_IP

Next, assign one IPv4 address from your routed prefix and test outbound traffic:

ping -I YOUR_ROUTED_IPV4 1.1.1.1

You can also test inbound reachability from another network:

ping YOUR_ROUTED_IPV4

If outbound works but inbound does not, check firewall rules, local routing and whether the service is bound to the correct IPv4 address. If inbound works but outbound does not, check source routing and return path rules.

Common setup mistakes

Most IPv4 tunnel problems come from routing mistakes on the customer side. Common issues include assigning the IPv4 address to the wrong interface, routing the assigned prefix back toward HYEHOST, missing source-based routing, firewall rules blocking the tunnel interface, reverse path filtering dropping packets, using the wrong endpoint IP, forgetting to bring the tunnel interface up, using the wrong tunnel type or having NAT rules interfere with routed IPv4 traffic.

On Linux, reverse path filtering can sometimes interfere with tunnel traffic. If you know what you are doing, you may need to adjust rp_filter for the tunnel interface or system:

sysctl -w net.ipv4.conf.all.rp_filter=0
sysctl -w net.ipv4.conf.gre-hyehost.rp_filter=0

Only change system networking settings if you understand the impact.

Reverse DNS for IPv4 tunnel prefixes

Reverse DNS is important for some services, especially mail, monitoring, logging and reputation-sensitive applications. Where supported, the HYEHOST panel allows reverse DNS management for IPv4 tunnel services.

Good reverse DNS practice means using valid hostnames, making sure the hostname has matching forward DNS where appropriate, avoiding fake or misleading PTR records and keeping rDNS updated if service use changes.

For mail hosting, reverse DNS alone is not enough. You also need correct SPF, DKIM, DMARC, hostname configuration and responsible mail practices.

Traffic usage and 95th percentile billing

IPv4 tunnel services may include a committed usage amount and a port speed. For example, a plan may include a 95th percentile usage allowance and a higher maximum port speed. This allows normal bursts while still keeping long-term usage within the plan rules.

The panel shows usage so customers can understand how much traffic the tunnel is using. Depending on the plan, if usage exceeds the included allowance, speed limiting or other policy controls may apply for the rest of the billing cycle. Always check the product details shown during ordering.

Security considerations

Because IPv4 via tunnel gives you routed public IPv4 addresses, you are responsible for securing the services you expose. Use a firewall, expose only required ports, keep software updated, disable unused services, monitor logs, use SSH keys instead of passwords where possible and avoid open relays, open proxies or insecure services.

HYEHOST may suspend or terminate services used for abuse, spam, attacks or policy violations.

When to choose IPv4 via tunnel

Choose IPv4 via tunnel if you need one or more routed IPv4 addresses, want to use your own server or VPS as the endpoint, have IPv6 but limited IPv4, do not have an ASN, want a simpler setup than transit or need IPv4 in a specific location.

Choose IP transit instead if you need to announce your own prefixes, have your own ASN, need BGP communities or route control, need default routes or full table, or provide downstream BGP.

Why HYEHOST for IPv4 via tunnel?

HYEHOST offers IPv4 via tunnel as part of a wider hosting and network platform. Customers can combine IPv4 tunnels with VPS hosting, VDS hosting, VPS resource pools, private LANs, RIPE IPv6 leasing, ARIN IPv6 leasing, BGP services, IP transit via tunnel, dedicated servers and colocation.

This makes HYEHOST useful for customers who need more than a single hosting product. You can build a complete network setup from the same panel, with billing, support and service management in one place.

Final thoughts

IPv4 is still important, but obtaining and managing it directly can be difficult. HYEHOST IPv4 via tunnel gives customers a practical way to receive routed IPv4 space over a tunnel without needing BGP.

For developers, network operators, hosting customers and businesses, IPv4 via tunnel can be a flexible way to add IPv4 connectivity to existing infrastructure. Log in to the HYEHOST panel, open IPv4 via tunnel, select a location and prefix size, then follow the service-specific configuration shown in your panel.