lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sun, 24 Jul 2011 10:42:11 +0200
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	jsr@....edzone.net
Cc:	netdev@...r.kernel.org, davem@...emloft.net
Subject: Re: LInux kernel 3.0 sit creation bug report

Le samedi 23 juillet 2011 à 12:27 -0400, Jay Rouman a écrit :
> Kernel 3.0 (release version)
> Summary:  sit tunnel creation fails with "No buffer space available"
> 
> Example:
> 
> icebox:/home/u/jsr(3)# /sbin/ip tunnel add sit0 mode sit local 216.111.203.89 remote 209.51.18.1 ttl 255
> add tunnel sit0 failed: No buffer space available
> 
> icebox:/home/u/jsr(8)# /sbin/ifconfig sit0 inet6 tunnel ::209.51.18.1
> SIOCSIFDSTADDR: No buffer space available
> 
> Notes:
> 
> Oddly, the ifconfig example creates a working sit0.  The "ip" example
> does not.  The problem existed in rc1 but unfortunately I did not test
> sit creation then.  This was discovered when I upgraded a machine with
> an HE tunnel to the 3.0 kernel.  I am happy to do further testing or
> provide whatever additional info I can.
> 

I believe you use a deprecated (~10 years ago ?) way to setup your
tunnel, its not a linux-3.0 new behavior.

sit0 is reserved (fall back tunnel), you should use a different name.

Try :

# ip tunnel add aster mode sit local 216.111.203.89 remote 209.51.18.1 ttl 255
# ifconfig aster up

# ip tunnel
sit0: ipv6/ip  remote any  local any  ttl 64  nopmtudisc
aster: ipv6/ip  remote 209.51.18.1  local 216.111.203.89  ttl 255 


--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ