Specifying the source port

Specifying the source port

[Ryan Whelan]

[-- Attachment #1: Type: text/plain, Size: 258 bytes --]

Hello!

When specifying an endpoint, you have to tell wg which dst port the peer is
listening on- is it possible to tell wg which source port to send traffic
from?  I've looked over the documentation and if its in there, I managed to
miss it.

Thanks!

ryan

[-- Attachment #2: Type: text/html, Size: 357 bytes --]

Re: Specifying the source port

[Jason A. Donenfeld]

[-- Attachment #1: Type: text/plain, Size: 502 bytes --]

"ListenPort", " listen-port"

On May 4, 2017 20:21, "Ryan Whelan" <rcwhelan@gmail.com> wrote:

Hello!

When specifying an endpoint, you have to tell wg which dst port the peer is
listening on- is it possible to tell wg which source port to send traffic
from?  I've looked over the documentation and if its in there, I managed to
miss it.

Thanks!

ryan

_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

[-- Attachment #2: Type: text/html, Size: 1125 bytes --]

Re: Specifying the source port

[Ryan Whelan]

[-- Attachment #1: Type: text/plain, Size: 1078 bytes --]

If i'm not mistaken that sets the listing port on one end (Peer 'A') of the
connection.  Peer 'B' needs to know what the listening port is set to, to
be able to setup the handshake.  So from peer 'B's perspective, the dst
port is the "listen-port' on Peer 'A'.... How do I set the src port for
peer 'B' so all traffic from B will come from a predicable source port?

I'm sorry if i'm not being clear- I very well might not be using the right
terminology

ryan

On Thu, May 4, 2017 at 2:35 PM, Jason A. Donenfeld <Jason@zx2c4.com> wrote:

> "ListenPort", " listen-port"
>
> On May 4, 2017 20:21, "Ryan Whelan" <rcwhelan@gmail.com> wrote:
>
> Hello!
>
> When specifying an endpoint, you have to tell wg which dst port the peer
> is listening on- is it possible to tell wg which source port to send
> traffic from?  I've looked over the documentation and if its in there, I
> managed to miss it.
>
> Thanks!
>
> ryan
>
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
>
>
>

[-- Attachment #2: Type: text/html, Size: 2187 bytes --]

Re: Specifying the source port

[Jason A. Donenfeld]

[-- Attachment #1: Type: text/plain, Size: 1328 bytes --]

My answer remains correct. Use the listen port to control the source port.
If you don't believe me, try running tcpdump and you'll see.

On May 4, 2017 20:41, "Ryan Whelan" <rcwhelan@gmail.com> wrote:

> If i'm not mistaken that sets the listing port on one end (Peer 'A') of
> the connection.  Peer 'B' needs to know what the listening port is set to,
> to be able to setup the handshake.  So from peer 'B's perspective, the dst
> port is the "listen-port' on Peer 'A'.... How do I set the src port for
> peer 'B' so all traffic from B will come from a predicable source port?
>
> I'm sorry if i'm not being clear- I very well might not be using the right
> terminology
>
> ryan
>
> On Thu, May 4, 2017 at 2:35 PM, Jason A. Donenfeld <Jason@zx2c4.com>
> wrote:
>
>> "ListenPort", " listen-port"
>>
>> On May 4, 2017 20:21, "Ryan Whelan" <rcwhelan@gmail.com> wrote:
>>
>> Hello!
>>
>> When specifying an endpoint, you have to tell wg which dst port the peer
>> is listening on- is it possible to tell wg which source port to send
>> traffic from?  I've looked over the documentation and if its in there, I
>> managed to miss it.
>>
>> Thanks!
>>
>> ryan
>>
>> _______________________________________________
>> WireGuard mailing list
>> WireGuard@lists.zx2c4.com
>> https://lists.zx2c4.com/mailman/listinfo/wireguard
>>
>>
>>
>

[-- Attachment #2: Type: text/html, Size: 2740 bytes --]

Re: Specifying the source port

[Jonathon Fernyhough]

[-- Attachment #1.1: Type: text/plain, Size: 199 bytes --]

On 04/05/17 19:41, Ryan Whelan wrote:
> How do I set the src port for peer 'B' so all traffic from B will come from a predicable source port?

I don't think that's how network stacks work... ?


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: Specifying the source port

[Ryan Whelan]

[-- Attachment #1: Type: text/plain, Size: 1605 bytes --]

I believe you- I didn't understand that it used the same port number for
both ingress and egress traffic.  I managed to miss that.

thank you much!

ryan

On Thu, May 4, 2017 at 2:43 PM, Jason A. Donenfeld <Jason@zx2c4.com> wrote:

> My answer remains correct. Use the listen port to control the source port.
> If you don't believe me, try running tcpdump and you'll see.
>
> On May 4, 2017 20:41, "Ryan Whelan" <rcwhelan@gmail.com> wrote:
>
>> If i'm not mistaken that sets the listing port on one end (Peer 'A') of
>> the connection.  Peer 'B' needs to know what the listening port is set to,
>> to be able to setup the handshake.  So from peer 'B's perspective, the dst
>> port is the "listen-port' on Peer 'A'.... How do I set the src port for
>> peer 'B' so all traffic from B will come from a predicable source port?
>>
>> I'm sorry if i'm not being clear- I very well might not be using the
>> right terminology
>>
>> ryan
>>
>> On Thu, May 4, 2017 at 2:35 PM, Jason A. Donenfeld <Jason@zx2c4.com>
>> wrote:
>>
>>> "ListenPort", " listen-port"
>>>
>>> On May 4, 2017 20:21, "Ryan Whelan" <rcwhelan@gmail.com> wrote:
>>>
>>> Hello!
>>>
>>> When specifying an endpoint, you have to tell wg which dst port the peer
>>> is listening on- is it possible to tell wg which source port to send
>>> traffic from?  I've looked over the documentation and if its in there, I
>>> managed to miss it.
>>>
>>> Thanks!
>>>
>>> ryan
>>>
>>> _______________________________________________
>>> WireGuard mailing list
>>> WireGuard@lists.zx2c4.com
>>> https://lists.zx2c4.com/mailman/listinfo/wireguard
>>>
>>>
>>>
>>

[-- Attachment #2: Type: text/html, Size: 3442 bytes --]

Re: Specifying the source port

[Jason A. Donenfeld]

[-- Attachment #1: Type: text/plain, Size: 1874 bytes --]

UDP is a bit strange like that. Everything implicitly must "listen" when
using UDP, even when the source port is ephemeral. So the listening port
and the source port concepts get smushed into one thing.

On May 4, 2017 20:47, "Ryan Whelan" <rcwhelan@gmail.com> wrote:

I believe you- I didn't understand that it used the same port number for
both ingress and egress traffic.  I managed to miss that.

thank you much!

ryan

On Thu, May 4, 2017 at 2:43 PM, Jason A. Donenfeld <Jason@zx2c4.com> wrote:

> My answer remains correct. Use the listen port to control the source port.
> If you don't believe me, try running tcpdump and you'll see.
>
> On May 4, 2017 20:41, "Ryan Whelan" <rcwhelan@gmail.com> wrote:
>
>> If i'm not mistaken that sets the listing port on one end (Peer 'A') of
>> the connection.  Peer 'B' needs to know what the listening port is set to,
>> to be able to setup the handshake.  So from peer 'B's perspective, the dst
>> port is the "listen-port' on Peer 'A'.... How do I set the src port for
>> peer 'B' so all traffic from B will come from a predicable source port?
>>
>> I'm sorry if i'm not being clear- I very well might not be using the
>> right terminology
>>
>> ryan
>>
>> On Thu, May 4, 2017 at 2:35 PM, Jason A. Donenfeld <Jason@zx2c4.com>
>> wrote:
>>
>>> "ListenPort", " listen-port"
>>>
>>> On May 4, 2017 20:21, "Ryan Whelan" <rcwhelan@gmail.com> wrote:
>>>
>>> Hello!
>>>
>>> When specifying an endpoint, you have to tell wg which dst port the peer
>>> is listening on- is it possible to tell wg which source port to send
>>> traffic from?  I've looked over the documentation and if its in there, I
>>> managed to miss it.
>>>
>>> Thanks!
>>>
>>> ryan
>>>
>>> _______________________________________________
>>> WireGuard mailing list
>>> WireGuard@lists.zx2c4.com
>>> https://lists.zx2c4.com/mailman/listinfo/wireguard
>>>
>>>
>>>
>>

[-- Attachment #2: Type: text/html, Size: 4159 bytes --]