Hurricane Electric's IPv6 Tunnel Broker Forums

Advanced search  

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Author Topic: [HELP]Mac OS X 10.8.4 ping6: sendmsg: No buffer space available  (Read 6749 times)

sleepingdust

  • Newbie
  • *
  • Posts: 6

I set my tunnel up after reboot as usual and under System Preference -> Network -> Advanced -> TCP/IP IPv6 section: I added IPv6 server IP under "router", IPv6 client IP under "IPv6 Address", Prefix Length is set to "64" (it used to make my browser work with the IPv6 tunnel connection). I'm behind NAT, so Protocol 41 is forwarded on my router and mac's firewall is off. When I tried to ping6 ipv6.google.com, I got "ping6: sendmsg: No buffer space available". After I did a "dscacheutil -flushcache" command, the error message from ping6 became "ping6: getaddrinfo -- nodename nor servname provided, or not known". test-ipv6.com says that I do not have an ipv6 connection.

I could ping6 the IPv6 server end:
Code: [Select]
bash-3.2$ ping6 -c5 2001:470:23:147::1
PING6(56=40+8+8 bytes) 2001:470:23:147::2 --> 2001:470:23:147::1
16 bytes from 2001:470:23:147::1, icmp_seq=0 hlim=64 time=94.566 ms
16 bytes from 2001:470:23:147::1, icmp_seq=1 hlim=64 time=94.908 ms
16 bytes from 2001:470:23:147::1, icmp_seq=2 hlim=64 time=95.279 ms
16 bytes from 2001:470:23:147::1, icmp_seq=3 hlim=64 time=94.661 ms
16 bytes from 2001:470:23:147::1, icmp_seq=4 hlim=64 time=94.810 ms

Here are two types of returns from ping6 ipv6.google.com

Code: [Select]
bash-3.2$ ping6 -c5 ipv6.google.com
PING6(56=40+8+8 bytes) 2001:470:23:147::2 --> 2404:6800:4005:c00::68
ping6: sendmsg: No buffer space available
ping6: wrote ipv6.l.google.com 16 chars, ret=-1
ping6: sendmsg: No buffer space available
ping6: wrote ipv6.l.google.com 16 chars, ret=-1
ping6: sendmsg: No buffer space available
ping6: wrote ipv6.l.google.com 16 chars, ret=-1
ping6: sendmsg: No buffer space available
ping6: wrote ipv6.l.google.com 16 chars, ret=-1
ping6: sendmsg: No buffer space available
ping6: wrote ipv6.l.google.com 16 chars, ret=-1

Code: [Select]
bash-3.2$ ping6 -c5 ipv6.google.com
ping6: getaddrinfo -- nodename nor servname provided, or not known

I did not change anything on my mac nor my router since the last time when I got working IPv6 tunnel from HE, the only thing I did is updating my IPv4 IP on HE's tunnel detail page with the new one that my ISP assigned to me.

Here's my ifconfig info:

Code: [Select]
bash-3.2$ ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
options=3<RXCSUM,TXCSUM>
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
stf0: flags=0<> mtu 1280
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1492
options=2b<RXCSUM,TXCSUM,VLAN_HWTAGGING,TSO4>
ether 00:1b:63:93:0e:ee
inet6 fe80::21b:63ff:fe93:eee%en0 prefixlen 64 scopeid 0x4
inet 192.168.1.141 netmask 0xffffff00 broadcast 192.168.1.255
inet6 2001:470:23:147::2 prefixlen 64
media: 1000baseT <full-duplex>
status: active
en1: flags=8823<UP,BROADCAST,SMART,SIMPLEX,MULTICAST> mtu 1500
ether 00:1c:b3:c1:d9:5e
media: autoselect (<unknown type>)
status: inactive
fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 4078
lladdr 00:1b:63:ff:fe:7a:9d:0c
media: autoselect <full-duplex>
status: inactive
gif0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1280
tunnel inet 192.168.1.141 --> 74.82.46.6
inet6 fe80::21b:63ff:fe93:eee%gif0 prefixlen 64 scopeid 0x2
inet6 2001:470:23:147::2 --> 2001:470:23:147::1 prefixlen 128

Many thanks in advance!

Sleepingdust
« Last Edit: August 29, 2013, 11:06:17 PM by sleepingdust »
Logged

kriteknetworks

  • Sr. Member
  • ****
  • Posts: 261
    • aRDy Music
Re: [HELP]Mac OS X 10.8.4 ping6: sendmsg: No buffer space available
« Reply #1 on: August 30, 2013, 03:13:08 PM »

Doing this as root?
Firewall?
NAT?
Logged

sleepingdust

  • Newbie
  • *
  • Posts: 6
Re: [HELP]Mac OS X 10.8.4 ping6: sendmsg: No buffer space available
« Reply #2 on: September 01, 2013, 03:33:01 AM »

Yes, all the commands were input as root.
Firewall off.

Basically I did not change any of the setting and the tunnel was working fine. It was just all of sudden the error message came up and I don't have any ipv6 connection at all.
Logged