[asterisk-bugs] [JIRA] Commented: (ASTERISK-20202) IP_MTU_DISCOVER incorrect work

ddkprog (JIRA) noreply at issues.asterisk.org
Fri Aug 10 09:50:07 CDT 2012


    [ https://issues.asterisk.org/jira/browse/ASTERISK-20202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=195645#comment-195645 ] 

ddkprog commented on ASTERISK-20202:
------------------------------------

this code from linux kernel seems should be enough to understand that IPPROTO_IP socket param not affective for socket.
should be SOL_IP.
plz forward my issue to developers.
thx!

http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=blob_plain;f=net/ipv4/ip_sockglue.c;hb=HEAD

int ip_setsockopt(struct sock *sk, int level,
		int optname, char __user *optval, unsigned int optlen)
{
	int err;

	if (level != SOL_IP)
		return -ENOPROTOOPT;

	err = do_ip_setsockopt(sk, level, optname, optval, optlen);

> IP_MTU_DISCOVER incorrect work
> ------------------------------
>
>                 Key: ASTERISK-20202
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20202
>             Project: Asterisk
>          Issue Type: Information Request
>      Security Level: None
>          Components: Channels/chan_iax2
>    Affects Versions: SVN
>         Environment: linux
>            Reporter: ddkprog
>            Assignee: ddkprog
>         Attachments: utils.c.diff
>
>
> IP_MTU_DISCOVER should used with SOL_IP not with IPPROTO_IP !
> see at iputils/ping sources and test
> you can replace in iputils/ping SOL_IP -> IPPROTO_IP, and try to ping -M options to see than IPPROTO_IP not work.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira



More information about the asterisk-bugs mailing list