Jump to content


Photo

Barracuda VPN Mac Issues

VPN Client

  • Please log in to reply
6 replies to this topic

#1 Adam Schappell

Adam Schappell
  • Members
  • 1 posts

Posted 05 June 2019 - 10:43 AM

Hello

 

Has anyone had any issues installing the VPN Client on MacOS? Everytime I try to install or connect I get these errors:

 

Open failed: No such file or directory ERROR
 
Open tap device ERROR
 
Thank you


#2 Gavin Chappell

Gavin Chappell
  • Moderators
  • 426 posts
  • LocationNottingham, UK

Posted 05 June 2019 - 11:19 AM

This sounds like the "new" (since 10.12) security system that stops unauthorised kernel extensions being loaded into the macOS kernel. Support can help you walk through this if you open a ticket with them.



#3 Gavin Chappell

Gavin Chappell
  • Moderators
  • 426 posts
  • LocationNottingham, UK

Posted 05 June 2019 - 11:29 AM

Just to confirm, is this with the Barracuda SSL VPN, or the Barracuda CloudGen Firewall?



#4 Larry King

Larry King
  • Members
  • 1 posts

Posted 30 August 2019 - 12:24 PM

I'm having the exact same problem.

  • Barracuda VPN Client, 5.0.2.7. 
  • MacBook Pro, running macOS Mojave 10.14.6. 

Every time I try to connect, I get:

 

Open Failed: No Such File Or Directory 

Open tap device

 

Is there a solution on the Mac?

 

Alternatively, if I install the Windows version of the VPN Client, could I use it in Parallels?  Or would I hit the same problem?

 

Thanks!



#5 Mark Shanley

Mark Shanley
  • Members
  • 15 posts

Posted 11 November 2019 - 05:43 AM

Hi Larry,

This is an issue with "Gatekeeper" on the mac. When you try to run the VPN client open the system preferences on the mac. Then security and click to allow the application. yes it will work with Paralles if the network is a bridge.

The error below is because the Barracuda VPN software does not have permisssion to create/open the tap device (virtual adaptor for VPN). 

 

Open Failed: No Such File Or Directory 

Open tap device



#6 sEmPtive

sEmPtive
  • Members
  • 1 posts

Posted 13 November 2019 - 05:18 PM

This sounds like the "new" (since 10.12) security system that stops unauthorised kernel extensions being loaded into the macOS kernel. Support can help you walk through this if you open a ticket with them.

 

 

That's what I had hoped, too – but I have since been unable to get macOS to prompt me and found myself unable to open a ticket with support. Here's what my logs say:

Untrusted kexts are not allowed
Kext with invalid signature (-67061) denied: /Library/StagedExtensions/Library/Extensions/[…].kext
Bundle (/Library/Extensions/tun.kext) failed to validate, deleting: /Library/StagedExtensions/Library/Extensions/[…].kext
Unable to stage kext (/Library/Extensions/tun.kext) to secure location.

Untrusted kexts are not allowed
Kext with invalid signature (-67061) denied: /Library/StagedExtensions/Library/Extensions/[…].kext
Bundle (/Library/Extensions/tap.kext) failed to validate, deleting: /Library/StagedExtensions/Library/Extensions/[…].kext
Unable to stage kext (/Library/Extensions/tap.kext) to secure location.

I do have a couple of other kernel extensions loaded, but none of the ones known to cause issues with tap/tun:

$ kextstat | grep -v com.apple Index Refs Address Size Wired Name (Version) UUID <Linked Against>
75 0 0xffffff7f80e71000 0x185000 0x185000 at.obdev.nke.LittleSnitch (5430) 7462BC7A-1330-3F92-A73F-3FBFE331C74A <8 6 5 3 1>
166 3 0xffffff7f84211000 0xf0000 0xf0000 org.virtualbox.kext.VBoxDrv (6.0.14) 53BAF3B2-AB27-321B-9DF8-7A1395C58923 <8 6 5 3 1>
169 0 0xffffff7f84301000 0x8000 0x8000 org.virtualbox.kext.VBoxUSB (6.0.14) CE24428E-4F6D-3690-89CC-1575AA093D8D <168 166 54 8 6 5 3 1>
170 0 0xffffff7f84309000 0x5000 0x5000 org.virtualbox.kext.VBoxNetFlt (6.0.14) 895E2094-4B8F-349F-8951-BF361447E6C5 <166 8 6 5 3 1>
172 0 0xffffff7f8430e000 0x6000 0x6000 org.virtualbox.kext.VBoxNetAdp (6.0.14) 38B6099A-ED14-3D29-87D4-DF1A3E4168CF <166 6 5 1>
178 0 0xffffff7f81002000 0x6000 0x6000 com.getdropbox.dropbox.kext (1.10.3) F29DD0CB-48D6-311A-9B69-E39CF775493C <8 6 5 2 1>
180 0 0xffffff7f84383000 0x19000 0x19000 com.github.osxfuse.filesystems.osxfuse (3.10.3) AF3874A9-CF4E-39BF-A807-F61D1E6FABBF <8 6 5 3 1>

Does anyone know what "the solution" might be?



#7 Gavin Chappell

Gavin Chappell
  • Moderators
  • 426 posts
  • LocationNottingham, UK

Posted 13 November 2019 - 06:42 PM

The lines about untrusted kexts still sound like the security features that have already been mentioned. Although I do also see that you have a bunch of other kexts, macOS has historically had limits on how many "device slots" are present meaning that only so many of these kexts can be loaded at once. It's not impossible (although I don't know for sure) that you simply have no device slots free to load any more. It may be worth you unloading a couple that you don't need (for example maybe quitting LittleSnitch and the Dropbox client then unloading their kexts) and then trying the VPN client again to see if freeing up slots fixes your issue.