Open
Bug 1062784
Opened 10 years ago
Updated 2 years ago
Not able to set Type Of Service field (i.e DSCP parameter) Socket option in TCP-IP Packet for an IPv6 connection
Categories
(NSPR :: NSPR, defect)
Tracking
(Not tracked)
NEW
People
(Reporter: prashantabkari, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:32.0) Gecko/20100101 Firefox/32.0 Build ID: 20140825202822 Steps to reproduce: We are trying to change the Type of Service field (Differentiated Services Code Point) in the outgoing LDAP packet on TCP-IP on an IPv6 connection. Steps to reproduce 1. Configure 2 nodes one with LDAP client and another with LDAP server. 2. Both the LDAP client and servers are on IPv6 network 3. Try to establish the LDAP connection between the 2 nodes 4. Try to change the DSCP parameter for an IPv6 packet with some value X NOTE : This works fine for an IPv4 connection Actual results: Result 1. LDAP connection is established 2. DSCP parameter is set to NULL(or 0) and not set to X NOTE : This works fine for an IPv4 connection Expected results: DSCP should have been set to value X. The client is using the following code to change the DSCP for IPv6 int ldap_sock_res = prldap_get_default_socket_info( ldap_handle,&soip ) ; if(soip.soinfo_prfd == 0) { // Log an Error } else { PRSocketOptionData optval; optval.option = PR_SockOpt_IpTypeOfService; optval.value.tos = 10; if(PR_SetSocketOption(soip.soinfo_prfd, &optval) == PR_FAILURE) { // Log an Error } } } NOTE : This works fine for an IPv4 connection
Updated•5 years ago
|
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Comment 1•2 years ago
|
||
The bug assignee is inactive on Bugzilla, so the assignee is being reset.
Assignee: wtc → nobody
Status: ASSIGNED → NEW
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•