---
name: transit-gateway-conn-routing-vsi
title: Routing in classic virtual server instances and bare metal servers
description: If you are attempting to access an IBM Cloud classic infrastructure virtual server instance or a bare metal server that has both a private network interface (`eth0`) and a public network interface (`eth1`), then the issue could be the traffic being routed to the public network interface versus the private. The routing tables for these interfaces point the default gateway to the public interface (`eth1`). Transit gateways are connected only to the private networks. You might have to add entries to route the subnets from other VPCs through the private interface.
last-updated: 2026-06-29
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/transit-gateway?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

# Routing in classic virtual server instances and bare metal servers
{: #routing-classic-vsi}

If you are attempting to access an IBM Cloud classic infrastructure virtual server instance or a bare metal server that has both a private network interface (`eth0`) and a public network interface (`eth1`), then the issue could be the traffic being routed to the public network interface versus the private. The routing tables for these interfaces point the default gateway to the public interface (`eth1`). Transit gateways are connected only to the private networks. You might have to add entries to route the subnets from other VPCs through the private interface.
{: shortdesc}