Bind to first available port

[Mathew Benson]

I know how to do this with Windows sockets, but how do I bind a UDP listen socket to the first available port?  I want to send a packet from client to the server to subscribe to data and tell the server what port to send the subscribed data to.  I don't care what port the client listens to.  If I hard code it, I can only run a single client on a PC.  I want to bind to the first available one so I can run as many clients on the same PC as I want. 
_______________________________________________
Boost-users mailing list
Boost-users@...
http://lists.boost.org/mailman/listinfo.cgi/boost-users

[Rutger ter Borg-2]

Mathew Benson wrote:

> I know how to do this with Windows sockets, but how do I bind a UDP listen
> socket to the first available port?  I want to send a packet from client
> to the server to subscribe to data and tell the server what port to send
> the
> subscribed data to.  I don't care what port the client listens to.  If I
> hard code it, I can only run a single client on a PC.  I want to bind to
> the first available one so I can run as many clients on the same PC as I
> want.

AFAIK, just bind to port 0 and you will get assigned a random port.

Cheers,

Rutger



_______________________________________________
Boost-users mailing list
Boost-users@...
http://lists.boost.org/mailman/listinfo.cgi/boost-users

[Mathew Benson]

Oh.  That makes sense.  I think that's how the native socket call is.  
Thanks.

Sent from my iPhone

On Oct 30, 2009, at 12:35 PM, Rutger ter Borg <rutger@...>  
wrote:

>
> Mathew Benson wrote:
>
>> I know how to do this with Windows sockets, but how do I bind a UDP  
>> listen
>> socket to the first available port?  I want to send a packet from  
>> client
>> to the server to subscribe to data and tell the server what port to  
>> send
>> the
>> subscribed data to.  I don't care what port the client listens to.  
>> If I
>> hard code it, I can only run a single client on a PC.  I want to  
>> bind to
>> the first available one so I can run as many clients on the same PC  
>> as I
>> want.
>
> AFAIK, just bind to port 0 and you will get assigned a random port.
>
> Cheers,
>
> Rutger
>
>
>
> _______________________________________________
> Boost-users mailing list
> Boost-users@...
> http://lists.boost.org/mailman/listinfo.cgi/boost-users

_______________________________________________
Boost-users mailing list
Boost-users@...
http://lists.boost.org/mailman/listinfo.cgi/boost-users

[Mathew Benson]

How do I read out what port was assigned?

 

On Fri, Oct 30, 2009 at 1:26 PM, Mathew Benson <mathew.benson@...> wrote:

Oh.  That makes sense.  I think that's how the native socket call is.  Thanks.

Sent from my iPhone

On Oct 30, 2009, at 12:35 PM, Rutger ter Borg <rutger@...> wrote:

Mathew Benson wrote:

I know how to do this with Windows sockets, but how do I bind a UDP listen
socket to the first available port?  I want to send a packet from client
to the server to subscribe to data and tell the server what port to send
the
subscribed data to.  I don't care what port the client listens to.  If I
hard code it, I can only run a single client on a PC.  I want to bind to
the first available one so I can run as many clients on the same PC as I
want.

AFAIK, just bind to port 0 and you will get assigned a random port.

Cheers,

Rutger



_______________________________________________
Boost-users mailing list
Boost-users@...
http://lists.boost.org/mailman/listinfo.cgi/boost-users

_______________________________________________
Boost-users mailing list
Boost-users@...
http://lists.boost.org/mailman/listinfo.cgi/boost-users

[Rutger ter Borg-2]

Mathew Benson wrote:
>
> How do I read out what port was assigned?
>

By using socket.local_endpoint.port()

Cheers,

Rutger



_______________________________________________
Boost-users mailing list
Boost-users@...
http://lists.boost.org/mailman/listinfo.cgi/boost-users