Setup & config

In the dashboard, open the project that owns the server and select Solana. The ShredStream panel lists the project's eligible servers and shows each delivery state.

Select Enable for the server that will consume the feed. A newly provisioned server already has its private interface and address, so enabling only changes relay discovery and does not reboot it.

Wait until the row shows On and a destination such as10.250.0.x:20001. Then allow up to 60 seconds for the relay to refresh its destination list.

Connect to the selected server over SSH and run the bounded checks below. The packet capture exits after five packets or 15 seconds and does not write the feed to disk.

# Confirm the private ShredStream address existsip -4 -br addr | grep '10.250.0.' # Capture five packets, then stop automaticallysudo timeout 15 tcpdump -ni any   'udp and dst port 20001'   -c 5 # After starting your own consumer, confirm it is listeningss -lunp | grep ':20001'

Shred datagrams are normally close to the network MTU and arrive at high volume. Seeing packets confirms network delivery; it does not mean a decoder or application is running.

Configure your application to bind UDP port 20001 on the server. The feed is raw binary data, so a generic HTTP, WebSocket, or JSON client cannot consume it.

Select Disable to remove the server from relay discovery. Delivery stops after the next refresh, normally within 30-60 seconds. The private address remains assigned, so enabling the same server later does not require another reboot.