Re: [RFC PATCH v2 2/3] ipv6: Support setting src port in sendmsg().

2024-09-23 Thread Jakub Sitnicki
On Mon, Sep 23, 2024 at 03:45 PM GMT, David Laight wrote: > From: Jakub Sitnicki >> Sent: 23 September 2024 15:56 >> >> On Mon, Sep 23, 2024 at 01:08 PM GMT, David Laight wrote: >> > From: Tiago Lam >> >> [...] >> >> >> To limit its usage, a reverse socket lookup is performed to check if the >>

RE: [RFC PATCH v2 2/3] ipv6: Support setting src port in sendmsg().

2024-09-23 Thread David Laight
From: Jakub Sitnicki > Sent: 23 September 2024 15:56 > > On Mon, Sep 23, 2024 at 01:08 PM GMT, David Laight wrote: > > From: Tiago Lam > > [...] > > >> To limit its usage, a reverse socket lookup is performed to check if the > >> configured egress source address and/or port have any ingress sk_

Re: [RFC PATCH v2 2/3] ipv6: Support setting src port in sendmsg().

2024-09-23 Thread Jakub Sitnicki
On Mon, Sep 23, 2024 at 01:08 PM GMT, David Laight wrote: > From: Tiago Lam [...] >> To limit its usage, a reverse socket lookup is performed to check if the >> configured egress source address and/or port have any ingress sk_lookup >> match. If it does, traffic is allowed to proceed, otherwise

RE: [RFC PATCH v2 2/3] ipv6: Support setting src port in sendmsg().

2024-09-23 Thread David Laight
From: Tiago Lam > Sent: 20 September 2024 18:02 > > This follows the same rationale provided for the ipv4 counterpart, where > the sendmsg() path is also extended here to support the IPV6_ORIGDSTADDR > ancillary message to be able to specify a source address/port. This > allows users to configure

Re: [RFC PATCH v2 2/3] ipv6: Support setting src port in sendmsg().

2024-09-21 Thread Willem de Bruijn
Tiago Lam wrote: > This follows the same rationale provided for the ipv4 counterpart, where > the sendmsg() path is also extended here to support the IPV6_ORIGDSTADDR > ancillary message to be able to specify a source address/port. This > allows users to configure the source address and/or port egr