ovpn_peer_skb_to_sockaddr(9)

💖 ovpn_peer_skb_to_sockaddr 💖

Okay bestie, welcome to the ovpn_peer_skb_to_sockaddr(9) page in the Kernel API Manual. This is the moment where we fill a sockaddr with the skb source address, and yes, that is literally the whole name energy.

✨ NAME ✨

ovpn_peer_skb_to_sockaddr — fill sockaddr with skb source address. Like, take the source address from the skb and put it into the sockaddr. That's the assignment, and it ate. 💅

🌸 SYNOPSIS 🌸

int ovpn_peer_skb_to_sockaddr (struct sk_buff *skb , struct
       sockaddr_storage *ss );

🎀 ARGUMENTS 🎀

• skb — the packet to extract data from. This is the packet bestie; it's where the data comes from.
• ss — the sockaddr to fill. This is the sockaddr that gets filled.

⭐ RETURN ⭐

Sockaddr length on success, or -1 otherwise. No cap: success gives you the sockaddr length; anything else is -1.

👑 SEE ALSO 👑

Kernel file ./drivers/net/ovpn/peer.c — plus all the SEE ALSO besties: ovpn_peer_keepalive_set(9), ovpn_peer_keepalive_send(9), ovpn_peer_new(9), ovpn_peer_reset_sockaddr(9), ovpn_peer_endpoints_update(9), ovpn_peer_release_rcu(9), ovpn_peer_release(9), ovpn_peer_release_kref(9), ovpn_nexthop_from_skb4(9), ovpn_nexthop_from_skb6(9), ovpn_peer_get_by_vpn_addr4(9), ovpn_peer_get_by_vpn_addr6(9), ovpn_peer_vpn_addr_conflict4(9), ovpn_peer_vpn_addr_conflict6(9), ovpn_peer_transp_match(9), ovpn_peer_get_by_transp_addr_p2p(9), ovpn_peer_get_by_transp_addr(9), ovpn_peer_get_by_id_p2p(9), ovpn_peer_get_by_id(9), ovpn_peer_get_by_dst(9), ovpn_nexthop_from_rt4(9), ovpn_nexthop_from_rt6(9), ovpn_peer_check_by_src(9), ovpn_peer_add_mp(9), ovpn_peer_add_p2p(9), ovpn_peer_add(9), ovpn_peer_del_mp(9), ovpn_peer_del_p2p(9), ovpn_peer_del(9), ovpn_peer_release_p2p(9), ovpn_peers_free(9), ovpn_peer_keepalive_work(9) — iykyk. 💜

This page lives in ./drivers/net/ovpn and is dated October 2026. Bye bestie, go be iconic with those sockaddrs. 🫶💖