strflag should not allow nil values
justincormack opened this issue · comments
Justin Cormack commented
we used IPPROTO.TCP which was not defined , and was then passed to a strflag, returning 0. Several issues there...
But you must choose a strflag, 0 is not a sane default. Changing it breaks lots of stuff though, may need explicit default.