Forum: Ruby-core [ruby-trunk - Bug #7476][Open] missing "IP_TRANSPARENT" constant for IP sockets.

Issue #7476 has been reported by elico (Eliezer Croitoru).

----------------------------------------
Bug #7476: missing "IP_TRANSPARENT" constant for IP sockets.
https://bugs.ruby-lang.org/issues/7476

Author: elico (Eliezer Croitoru)
Status: Open
Priority: Normal
Assignee:
Category:
Target version:
ruby -v: 1.9.3


There is a missing constant for IP_TRANSPARENT on linux.
to set the TPROXY on a socket I use:
s.setsockopt(Socket::SOL_IP, 19, 1)
The 19 suppose to be as a constant named: IP_TRANSPARENT or 
Socket::IP_TRANSPARENT.

Issue #7476 has been updated by ko1 (Koichi Sasada).

Target version changed from 2.0.0 to 2.1.0

ping -> akr
----------------------------------------
Feature #7476: missing "IP_TRANSPARENT" constant for IP sockets.
https://bugs.ruby-lang.org/issues/7476#change-36913

Author: elico (Eliezer Croitoru)
Status: Assigned
Priority: Normal
Assignee: akr (Akira Tanaka)
Category: ext
Target version: 2.1.0


There is a missing constant for IP_TRANSPARENT on linux.
to set the TPROXY on a socket I use:
s.setsockopt(Socket::SOL_IP, 19, 1)
The 19 suppose to be as a constant named: IP_TRANSPARENT or 
Socket::IP_TRANSPARENT.

2013/2/24 ko1 (Koichi Sasada) <redmine@ruby-lang.org>:

> Feature #7476: missing "IP_TRANSPARENT" constant for IP sockets.
> https://bugs.ruby-lang.org/issues/7476#change-36913

> There is a missing constant for IP_TRANSPARENT on linux.
> to set the TPROXY on a socket I use:
> s.setsockopt(Socket::SOL_IP, 19, 1)
> The 19 suppose to be as a constant named: IP_TRANSPARENT or 
Socket::IP_TRANSPARENT.

This is Linux-specific and only defined in linux headers
such as /usr/include/linux/in.h.

I'm not sure applications can safely use such headers.

Tanaka Akira <akr@fsij.org> wrote:
> This is Linux-specific and only defined in linux headers
> such as /usr/include/linux/in.h.
>
> I'm not sure applications can safely use such headers.

We already have Linux-specific constants (e.g. TCP_CORK) and
*BSD-specific constants (e.g. TCP_NOPUSH), so I don't think we should
make it hard for users to take advantage of non-portable features on
their favorite OS.

I vote for adding IP_TRANSPARENT (and any other OS-specific constants
users request).

2013/4/3 Eric Wong <normalperson@yhbt.net>:

>> This is Linux-specific and only defined in linux headers
>> such as /usr/include/linux/in.h.
>>
>> I'm not sure applications can safely use such headers.
>
> We already have Linux-specific constants (e.g. TCP_CORK) and
> *BSD-specific constants (e.g. TCP_NOPUSH), so I don't think we should
> make it hard for users to take advantage of non-portable features on
> their favorite OS.

It is not my concern.
TCP_CORK is defined in /usr/include/netinet/tcp.h which is a glibc 
header.