# Reads network addresses in /proc

DevFeed: [Reads network addresses in /proc](<https://devfeed.tech/articles/reads-network-addresses-in-proc-26078.md>)

Original publisher: [Read original article](<https://blog.arkey.fr/2020/10/23/read-network-addresses-in-procfs/>)

Author: brice.dutheil@gmail.com (Brice Dutheil)

Published: 2020-10-23T21:25:32Z

Content type: tutorial

Language: en

Sources: [The Coffee Workshop](<https://devfeed.tech/sources/the-coffee-workshop.md>)

Topics: [Network](<https://devfeed.tech/topics/network.md>), [container](<https://devfeed.tech/topics/container.md>), [Process](<https://devfeed.tech/topics/process.md>), [Script](<https://devfeed.tech/topics/script.md>)

Tags: [container](<https://devfeed.tech/tags/container.md>), [network](<https://devfeed.tech/tags/network.md>), [process](<https://devfeed.tech/tags/process.md>), [script](<https://devfeed.tech/tags/script.md>)

## AI overview

This tutorial explains how to read network addresses and related connection information from procfs when common network utilities are unavailable in a read-only container. It demonstrates using shell tools such as awk and sed to filter ports, convert hexadecimal addresses, remove duplicates, and inspect connection states.

## Source excerpt

If you happen to be on a read-only container that doesn't have the usual network utilities, like netstat, ss (socket stat), lsof, etc. then your only option is to leverage procfs, however, procfs displays some data in hexadecimal.