> ## Documentation Index
> Fetch the complete documentation index at: https://rexrex.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Inspect Network Peers

> Show established peer sessions, directions, trust flags, and protocol capabilities.

Use `network peers` to inspect the remote clients with established devp2p sessions on the node.

## Command

```sh theme={null}
rex network peers
```

## Example Output

```text theme={null}
NETWORK PEERS

Connected:  1
Inbound:    0
Outbound:   1
Trusted:    0
Static:     0

PEER 1
  ID:            8915d6ec2f53ede650d5b9bea77d7756f177092171648ee1d8cbc550d334fa7a
  Client:        reth/v2.3.0/x86_64-unknown-linux-gnu
  Direction:     outbound
  Remote:        192.0.2.10:30303
  Local:         192.0.2.20:49152
  Trusted:       no
  Static:        no
  Capabilities:  eth/69, snap/1
  Protocols:     eth, snap
  Enode:         enode://44826a...@192.0.2.10:30303
  ENR:           enr:-IS4Q...
```

When no sessions are established, Rex prints the zero-valued summary followed by `No established peers.`

## Reading the Report

* `inbound` means the remote peer opened the connection to this node; `outbound` means this node dialed the peer.
* `trusted` means the peer belongs to the trusted peer set.
* `static` means the peer was configured as a static node rather than discovered dynamically.
* capabilities such as `eth/69` and `snap/1` are the negotiated devp2p subprotocol versions.

The command calls `admin_peers`. The report describes currently established sessions, not every node in the discovery table and not a history of disconnected peers.

<Warning>
  `admin_peers` is read-only, but the surrounding `admin` namespace is sensitive. Expose it only on a trusted interface.
</Warning>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.