[erlang-questions] 17.3, ssl and raw options?
Roger Lipscombe
roger@REDACTED
Tue Oct 7 16:33:28 CEST 2014
On 7 October 2014 14:38, Roger Lipscombe <roger@REDACTED> wrote:
> In Erlang R16B03-1, I've been passing raw options to ssl:listen as
> follows, and it's been working fine:
>
> % The constants are defined elsewhere.
> LOpts = [{raw, ?IPPROTO_TCP, ?TCP_MAXSEG, <<MSS:32/native>>} | ...],
> {ok, LSocket} = ssl:listen(0, LOpts)
>
> In Erlang 17.3, this fails with
> {option_not_a_key_value_tuple,{raw,6,2,<<64,2,0,0>>}}
>
> How do I pass a raw option to ssl:listen in Erlang 17.3?
Oh, and ssl:setopts doesn't appear to be sufficient. TCP_MAXSEG must
be set when the socket is initially opened, before listen is called.
More information about the erlang-questions
mailing list