---
title: "Inspect VPC Subnet Attachments"
description: "Inspect Exoscale VPC Subnet attachments, find assigned private IPv4 addresses, and check an instance interface and DHCP configuration."
url: https://community.exoscale.com/product/networking/vpc/how-to/inspect-subnet-attachments/
product: "VPC"
section: product
last_updated: 2026-10-26
---
> For AI agents: the documentation index is at https://community.exoscale.com/llms.txt. Every page is available as markdown at `<page URL>index.md` or with `Accept: text/markdown`.

# Inspect VPC Subnet Attachments

Use these checks after attaching Compute instances to a VPC Subnet.

## List Instances Attached to the Subnet

Show the Subnet to see its attached instances and their VPC addresses:
```console
$ exo networking vpc subnet show my-first-vpc my-first-subnet
┼────────────────┼──────────────────────────────────────┼
│   VPC SUBNET   │                                      │
┼────────────────┼──────────────────────────────────────┼
│ ID             │ d557ef4e-c481-4ba4-872e-4c6b53705be8 │
│ Name           │ my-first-subnet                      │
│ Description    │                                      │
│ Zone           │ ch-gva-2                             │
│ Created At     │ 2026-09-09 07:32:39 +0000 UTC        │
│ Address Family │ inet4                                │
│ Address Space  │ private                              │
│ IPv4 Block     │ 10.42.0.0/16                         │
│ Labels         │ n/a                                  │
│ Instances      │                                      │
│                │   instance-A   10.42.145.150         │
│                │   instance-B   10.42.13.243          │
│                │                                      │
┼────────────────┼──────────────────────────────────────┼
```
## Check the VPC Interface and DHCP

Attaching a VPC Subnet creates a new virtual interface on the instance. View it with `ip a`:
```console
ubuntu@instance-A:~$ ip -c a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
	link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
	inet 127.0.0.1/8 scope host lo
	   valid_lft forever preferred_lft forever
	inet6 ::1/128 scope host noprefixroute
	   valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
	link/ether 06:88:42:00:00:bb brd ff:ff:ff:ff:ff:ff
	altname enp3s0
	altname enx0688420000bb
	inet 85.217.161.220/23 metric 100 brd 85.217.161.255 scope global eth0
	   valid_lft forever preferred_lft forever
	inet6 fe80::488:42ff:fe00:bb/64 scope link proto kernel_ll
	   valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
	link/ether 0e:00:00:01:90:26 brd ff:ff:ff:ff:ff:ff
	altname enp7s0
	altname enx0e0000019026
	inet 10.42.145.150/32 metric 1024 scope global dynamic eth1
	   valid_lft 86252sec preferred_lft 86252sec
	inet6 fe80::c00:ff:fe01:9026/64 scope link proto kernel_ll
	   valid_lft forever preferred_lft forever
```

The interface receives its IP address and configuration through DHCP. Modern templates, such as Ubuntu 26.04, start DHCP automatically. On older templates, start it with `dhcpcd` or `dhclient`, or configure netplan or your instance network manager.