Error Setsockopt Ip_tos 16 Invalid Argument - Sshd

Help Follow Us Facebook Twitter Google + LinkedIn Newsletter Instagram YouTube DirectoryNetwork InfrastructureWAN, Routing and Switching LAN, Switching and Routing Network Management Remote Access Optical Networking Getting Started with LANs IPv6 Integration and Transition EEM Scripting Other Subjects SecurityVPN Security Management Firewalling Intrusion Prevention Systems/IDS AAA, Identity and NAC Physical Security MARS Email Security Web Security Other Subjects Service ProvidersMetro MPLS Voice Over IP XR OS and Platforms Video Other Subjects Collaboration, Voice and VideoIP Telephony Video Over IP Jabber Clients Unified Communications Applications TelePresence Digital Media System Contact Center Conferencing UC Migrations Other Subjects Wireless - MobilitySecurity and Network Management Wireless IP Voice and Video Getting Started with Wireless WLCCA Other Subjects ServicesCisco ServiceGrid Connected Analytics Smart Call Home Smart Net Total Care Operations Exchange Mobile ApplicationsCisco Proximity Cisco Technical Support Online Tools and ResourcesCisco Bug Discussions Technical Documentation Ideas Cisco CLI Analyzer Support Community Help Data CenterApplication Centric Infrastructure Application Networking Intelligent Automation Server Networking Storage Networking Unified Computing Wide Area Application Services (WAAS) Other Subjects Small BusinessNetwork Storage Routers Security Surveillance Switches Voice and Conferencing Wireless Solutions and ArchitecturesBorderless Networks Collaboration Cisco User GroupsSeattle Cisco User Group (SEACUG) Silicon Valley Cisco User Group (SVCUG) Southern California Cisco User Group (SCCUG) Cisco Certifications Cisco.com Idea Center Cisco Cafe Expert CornerTop Contributors Leaderboards Cisco Live! Events Events Community CornerAwards & Recognition Behind the Scenes Feedback Forum Cisco Certifications Cisco Press Café Cisco On Demand Supp

Cisco Bug: CSCue13430 - error: setsockopt IP_TOS 16: Invalid argument: - sshd Last Modified Oct 07, 2014 Product Cisco Nexus 4000 Series Switches Known Affected Releases 4.1(2)E1(1j) Description (partial) Symptom: seeing following message in syslog: <> Conditions: when connecting via ssh to device View Bug Details in Bug Search Tool Why Is Login Required? Bug details contain sensitive information https://supportforums.cisco.com/discussion/12344681/nexus-4k-setsockopt-iptos-16-error-sshd and therefore require a Cisco.com account to be viewed. Bug Details Include Full Description (including symptoms, conditions and workarounds) Status Severity Known Fixed Releases Related Community Discussions Number of Related Support Cases Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 https://quickview.cloudapps.cisco.com/quickview/bug/CSCue13430 bugs per month without a service contract. Learn More About Cisco Service Contracts Information For Small Business Midsize Business Service Provider Executives Industries Automotive Consumer Packaged Goods Education Energy Financial Services Government Healthcare Hospitality Life Sciences Manufacturing Materials and Mining Public Sector Retail Smart+Connected Communities Sports and Entertainment Transportation Workspace Transformation Marketplace Contacts Contact Cisco Meet our Partners Find a Reseller News & Alerts Newsroom Blogs Field Notices Security Advisories Technology Trends Cloud Internet of Things (IoT) Software Defined Networking (SDN) Support Downloads Documentation Communities DevNet Learning Network Support Community Video Portal Certifications Events Industries Inside Cisco Products Service Provider Services Technology Trends TechWiseTV About Cisco Investor Relations Corporate Social Responsibility Environmental Sustainability Trust and Transparency Center The Next Wave of The Internet Our People Careers Search Jobs Life at Cisco Programs Cisco Designated VIP Program Cisco Powered Financing Options Contacts Feedback Help Site Map Terms & Conditions PrivacyPrivacy Statement CookiesCookie Policy Trademarks

openssh-client: portforwarding with either -R or -L fails with module tun loaded From: Lars Bahner Date: Wed, 21 Mar 2007 11:49:35 +0100 Message-id: <20070321104935.5023.10088.reportbug@cryptcat.e.linpro.no> Reply-to: Lars Bahner https://lists.debian.org/debian-ssh/2007/03/msg00057.html , 415697@bugs.debian.org Package: openssh-client Version: 1:4.3p2-9 Severity: important Hi, when I have the "tun" module loaded portforwarding fails with message "administratively prohibited". Usinf strace I found that ssh tries http://stackoverflow.com/questions/13886761/error-in-setsockopt-numerical-argument-out-of-domain to access /dev/net/tun prior to running in to the error: shutdown(9, 2 /* send and receive */) = -1 ENOTSOCK (Socket operation on non-socket) Then I do rmmod tun error setsockopt and Lo and behold, portforwarding works again. Strace attached -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-amd64 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages openssh-client depends on: ii adduser 3.102 Add and remove users and groups ii debconf 1.5.11 Debian configuration management error setsockopt ip_tos sy ii dpkg 1.13.25 package maintenance system for Deb ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries ii libcomer 1.39+1.40-WIP-2006.11.14+dfsg-2 common error description library ii libedit2 2.9.cvs.20050518-2.2 BSD editline and history libraries ii libkrb53 1.4.4-7 MIT Kerberos runtime libraries ii libncurs 5.5-5 Shared libraries for terminal hand ii libssl0. 0.9.8c-4 SSL shared libraries ii passwd 1:4.0.18.1-7 change and administer password and ii zlib1g 1:1.2.3-13 compression library - runtime openssh-client recommends no packages. -- no debconf information execve("/usr/bin/ssh", ["ssh", "-L", "9999:localhost:9999", "192.168.43.73"], [/* 30 vars */]) = 0 uname({sys="Linux", node="cryptcat", ...}) = 0 brk(0) = 0x54a000 access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory) mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2acad6fc1000 access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory) open("/etc/ld.so.cache", O_RDONLY) = 3 fstat(3, {st_mode=S_IFREG|0644, st_size=60849, ...}) = 0 mmap(NULL, 60849, PROT_READ, MAP_PRIVATE, 3, 0) = 0x2acad6fc3000 close(3) = 0 access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory) open("/usr/lib/libcrypto.so.0.9.8", O_RDONLY) = 3 read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\360\364"..., 640) = 640 fstat(3, {st_mode=S_IFREG|0644, st_size=1510344, ...}) = 0 mmap(NULL, 2571832, PRO

here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Error in setsockopt(): Numerical argument out of domain up vote 3 down vote favorite I have a working code running on a RedHat installed Linux with kernel 2.6.18-194.el5 #1 SMP x86_64. When I moved the code to a newly installed machine with CentOS 6.3 the same code failed with Error assigning socket option: Numerical argument out of domain The kernel version of the latter machine is 2.6.32-279.el6.x86_64 #1 SMP Below is the code of what's both working and failing in the machines, respectively. struct timeval tv; tv.tv_sec = 0; tv.tv_usec = 1500000; if (setsockopt(sockfd, SOL_SOCKET, SO_RCVTIMEO, &tv, sizeof(struct timeval)) != 0) { LM_ERR("Error assigning socket option: %s", strerror( errno )); return FALSE; } c linux sockets share|improve this question edited Dec 14 '12 at 23:03 asked Dec 14 '12 at 21:49 caruizdiaz 73129 add a comment| 2 Answers 2 active oldest votes up vote 5 down vote accepted Try using tv.tv_sec = 1; tv.tv_usec = 500000; I've seen some implementations not accepting tv_usec above 10^6. Edit: The issue is interesting enough to dig a little bit. Looking for SO_RCVTIMEO in the kernel source code I've found the following piece of code in net/core/sock.c: int sock_setsockopt(struct socket *sock, int level, int optname, char __user *optval, unsigned int optlen) { / ... / switch (optname) { / ... / case SO_RCVTIMEO: ret = sock_set_timeout(&sk->sk_rcvtimeo, optval, optlen); break; / ... / } The beginning of the sock_set_timeout() function indeed contains some range checking: static int sock_set_timeout(long *timeo_p, char __user *optval, int optlen) { struct timeval tv; if (optlen < sizeof(tv)) return -EINVAL; if (copy_from_user(&tv, optval, sizeof(tv)))