* Specifying the source port
@ 2017-05-04 18:21 Ryan Whelan
[not found] ` <CAHmME9p0L8WjCvcrtk+8AeOxmnExSK5YhnCcNbYmxmp_Yc_ejg@mail.gmail.com>
0 siblings, 1 reply; 7+ messages in thread
From: Ryan Whelan @ 2017-05-04 18:21 UTC (permalink / raw)
To: wireguard
[-- 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 --]
^ permalink raw reply [flat|nested] 7+ messages in thread[parent not found: <CAHmME9p0L8WjCvcrtk+8AeOxmnExSK5YhnCcNbYmxmp_Yc_ejg@mail.gmail.com>]
* Re: Specifying the source port [not found] ` <CAHmME9p0L8WjCvcrtk+8AeOxmnExSK5YhnCcNbYmxmp_Yc_ejg@mail.gmail.com> @ 2017-05-04 18:35 ` Jason A. Donenfeld 2017-05-04 18:41 ` Ryan Whelan 0 siblings, 1 reply; 7+ messages in thread From: Jason A. Donenfeld @ 2017-05-04 18:35 UTC (permalink / raw) To: Ryan Whelan; +Cc: WireGuard mailing list [-- 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 --] ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Specifying the source port 2017-05-04 18:35 ` Jason A. Donenfeld @ 2017-05-04 18:41 ` Ryan Whelan 2017-05-04 18:43 ` Jason A. Donenfeld 2017-05-04 18:45 ` Jonathon Fernyhough 0 siblings, 2 replies; 7+ messages in thread From: Ryan Whelan @ 2017-05-04 18:41 UTC (permalink / raw) To: Jason A. Donenfeld; +Cc: WireGuard mailing list [-- 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 --] ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Specifying the source port 2017-05-04 18:41 ` Ryan Whelan @ 2017-05-04 18:43 ` Jason A. Donenfeld 2017-05-04 18:47 ` Ryan Whelan 2017-05-04 18:45 ` Jonathon Fernyhough 1 sibling, 1 reply; 7+ messages in thread From: Jason A. Donenfeld @ 2017-05-04 18:43 UTC (permalink / raw) To: Ryan Whelan; +Cc: WireGuard mailing list [-- 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 --] ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Specifying the source port 2017-05-04 18:43 ` Jason A. Donenfeld @ 2017-05-04 18:47 ` Ryan Whelan [not found] ` <CAHmME9rSXyOPCO1GLhWKuXTZk+b8swNmEoHeYPosWJ5vt83pmg@mail.gmail.com> 0 siblings, 1 reply; 7+ messages in thread From: Ryan Whelan @ 2017-05-04 18:47 UTC (permalink / raw) To: Jason A. Donenfeld; +Cc: WireGuard mailing list [-- 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 --] ^ permalink raw reply [flat|nested] 7+ messages in thread
[parent not found: <CAHmME9rSXyOPCO1GLhWKuXTZk+b8swNmEoHeYPosWJ5vt83pmg@mail.gmail.com>]
[parent not found: <CAHmME9oECt9DR9knvxnTynYwvRtEXvBv+U+WHjVPWWM1yGCWSQ@mail.gmail.com>]
[parent not found: <CAHmME9r=jk7dgL5nn3HZ2bFFQe-3weLcExy8V_Bor70svSZsYA@mail.gmail.com>]
* Re: Specifying the source port [not found] ` <CAHmME9r=jk7dgL5nn3HZ2bFFQe-3weLcExy8V_Bor70svSZsYA@mail.gmail.com> @ 2017-05-04 18:54 ` Jason A. Donenfeld 0 siblings, 0 replies; 7+ messages in thread From: Jason A. Donenfeld @ 2017-05-04 18:54 UTC (permalink / raw) To: Ryan Whelan; +Cc: WireGuard mailing list [-- 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 --] ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Specifying the source port 2017-05-04 18:41 ` Ryan Whelan 2017-05-04 18:43 ` Jason A. Donenfeld @ 2017-05-04 18:45 ` Jonathon Fernyhough 1 sibling, 0 replies; 7+ messages in thread From: Jonathon Fernyhough @ 2017-05-04 18:45 UTC (permalink / raw) To: wireguard [-- 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 --] ^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2017-05-04 18:44 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-05-04 18:21 Specifying the source port Ryan Whelan
[not found] ` <CAHmME9p0L8WjCvcrtk+8AeOxmnExSK5YhnCcNbYmxmp_Yc_ejg@mail.gmail.com>
2017-05-04 18:35 ` Jason A. Donenfeld
2017-05-04 18:41 ` Ryan Whelan
2017-05-04 18:43 ` Jason A. Donenfeld
2017-05-04 18:47 ` Ryan Whelan
[not found] ` <CAHmME9rSXyOPCO1GLhWKuXTZk+b8swNmEoHeYPosWJ5vt83pmg@mail.gmail.com>
[not found] ` <CAHmME9oECt9DR9knvxnTynYwvRtEXvBv+U+WHjVPWWM1yGCWSQ@mail.gmail.com>
[not found] ` <CAHmME9r=jk7dgL5nn3HZ2bFFQe-3weLcExy8V_Bor70svSZsYA@mail.gmail.com>
2017-05-04 18:54 ` Jason A. Donenfeld
2017-05-04 18:45 ` Jonathon Fernyhough
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).