Creating a utun device occasionally returns ENOBUFS on 10.9
| Originator: | peter.sagerson | ||
| Number: | rdar://15323284 | Date Originated: | 10/25/13 |
| Status: | Open | Resolved: | |
| Product: | OS X | Product Version: | 10.9 |
| Classification: | Serious Bug | Reproducible: | Rarely |
Summary: OpenVPN recently added support for OS X's utun devices for layer 3 tunneling. On some 10.9 systems, the call to connect() fails with an errno of ENOBUFS. We have never seen this or any similar failure on 10.8. We'll update this if we manage to narrow down the circumstances at all. Steps to Reproduce: 1. Attempt to allocate a utun device on an afflicted machine. (Code would look similar to https://github.com/bbits/openvpn-utun/blob/utun/src/openvpn/tun.c#L2488). Expected Results: connect() returns 0 and allocates an available utun device. Actual Results: connect() returns -1 with an errno of ENOBUFS. Version: 10.9 Notes: We've been able to contact one customer reporting this issue. Restarting their machine did not improve the situation.
Comments
Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!