the other me might even be better than this one

No Ident response

November 14, 2020 — Gideon Mayhak

This is a quick one, but I want to be somewhat active with posting to this blog and I figure it makes sense to document little things like this when they come up. Maybe someone will find this helpful.

The problem

When connecting to freenode, you've probably seen the message "No Ident response" and noticed a ~ next to your username@domain when joining channels. It's really a nonissue in most cases, but it annoyed me just enough that I finally decided to "fix" it when connecting from my new server.

If anyone cares, I currently use Irssi inside a tmux session. However, this should apply regardless of your IRC client of choice.

The solution

I'm using CentOS 8, but this should be similar on other systems. For CentOS, EPEL is where you'll find the appropriate package. If you haven't done so before, you will want to start with (as root or with sudo):

# dnf install epel-release

And then (again, with root privileges):

# dnf install oidentd
# systemctl enable oidentd.service
# systemctl start oidentd.service

Lastly, port 113 needs to be open on whatever firewall you're using.

"I will declare your name to my brothers."

Psalm 22:22a, WEB

Tags: freenode, how-to, server-info