LSylvester
Hey guys,
I have a UDP server listening for connections. When receiving a message from the handle_info, ie:
def handle_info({:udp, socket, ip, in_port, packet}, state) do
the ip and in_port are the IP and port of the server that the socket is listening on (192.168.1.1). I expected it to be the IP and port of the peer sending messages.
How do I get the IP and port of the sender?
Many thanks,
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Bringing learning, work and compliance together since 1987.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #ai
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixirconf-us
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #security
- #metaprogramming
Our Sponsors
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Master modern tools, write cleaner code, and tackle real-world challenges.
Bringing learning, work and compliance together since 1987.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 4- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
entone
Should be able to call
:inet.peername(socket)LSylvester
Okay, actually, using
:inet:peername(socket)returns{:error, :enotconn}because the socket is passive.entone
Ah, too bad. I have an old udp server and I was able to use the ip and port from the handle_info to reply to the client, but that was on a much older version of erlang and elixir, not sure if something changed, or it was the way my network interface was configured.
To be sure, your server and client are on different physical machines, correct?
lucaong
Strange, the documentation says that the IP and port are the ones of the sender of the packet:
@LSylvester did you manage to solve this?