Can't install plugin on macOS High Sierra 10.13.5

[tonifirnandes]

Can't install plugin on macOS High Sierra 10.13.5

[tomml]

Seems not working for new Apple M1 chip? Could anyone confirm?

[AlmirKadric]

Hi @tonifirnandes ,
If you follow the exact instructions there it should work (I did the same thing a few days ago on my new macbook pro). After you attempt the installation, it will fail with the above message. If you then go to your Systems Preferences -> Security & Privacy (1st Tab - General) you will see an additional button near the Allow apps downloaded from: (see attached image)

Clicking this button will approve the installation, from there you can go and run the installation for tuntap again and it should install without issues.

Please let me know if this solves your problem, or if you run into any other issues.

[rhickstedjr]

I have the kext loaded (net.sf.tuntaposx.tap) but can't create the tap interface (trying to use for simh to get my VAX network operational):

Note: installed via brew:

brew cask install tuntap

192-168-2-122:BIN rickhicksted2$ uname -a
Darwin Ricks-MBP-2 17.7.0 Darwin Kernel Version 17.7.0: Fri Jul 6 19:54:51 PDT 2018; root:xnu-4570.71.3~2/RELEASE_X86_64 x86_64

192-168-2-122:BIN rickhicksted2$ kextstat |grep -e tun -e tap
170 0 0xffffff7f80ea4000 0x7000 0x7000 net.sf.tuntaposx.tun (1.0) 95DD963D-E23D-3B0F-8DE8-A4D2F6BFA5CC <7 5 4 1>
171 0 0xffffff7f80b0f000 0x7000 0x7000 net.sf.tuntaposx.tap (1.0) 23FDB715-3D0D-3A26-ACBA-E3794C231CB7 <7 5 4 1>
192-168-2-122:BIN rickhicksted2$

192-168-2-122:BIN rickhicksted2$ ifconfig tap0 10.0.0.1
ifconfig: interface tap0 does not exist

192-168-2-122:BIN rickhicksted2$ ls -l /dev/tap*
crw-rw---- 1 root wheel 32, 0 Aug 10 23:19 /dev/tap0
crw-rw---- 1 root wheel 32, 1 Aug 10 23:19 /dev/tap1
crw-rw---- 1 root wheel 32, 10 Aug 10 23:19 /dev/tap10
crw-rw---- 1 root wheel 32, 11 Aug 10 23:19 /dev/tap11
crw-rw---- 1 root wheel 32, 12 Aug 10 23:19 /dev/tap12
crw-rw---- 1 root wheel 32, 13 Aug 10 23:19 /dev/tap13
crw-rw---- 1 root wheel 32, 14 Aug 10 23:19 /dev/tap14
crw-rw---- 1 root wheel 32, 15 Aug 10 23:19 /dev/tap15
crw-rw---- 1 root wheel 32, 2 Aug 10 23:19 /dev/tap2
crw-rw---- 1 root wheel 32, 3 Aug 10 23:19 /dev/tap3
crw-rw---- 1 root wheel 32, 4 Aug 10 23:19 /dev/tap4
crw-rw---- 1 root wheel 32, 5 Aug 10 23:19 /dev/tap5
crw-rw---- 1 root wheel 32, 6 Aug 10 23:19 /dev/tap6
crw-rw---- 1 root wheel 32, 7 Aug 10 23:19 /dev/tap7
crw-rw---- 1 root wheel 32, 8 Aug 10 23:19 /dev/tap8
crw-rw---- 1 root wheel 32, 9 Aug 10 23:19 /dev/tap9

192-168-2-122:BIN rickhicksted2$ cat bridge.sh
sudo ifconfig bridge1 create
sudo ifconfig bridge1 up addm tap0
sudo ifconfig bridge1 up addm en0
192-168-2-122:BIN rickhicksted2$ ./bridge.sh
Password:
ifconfig: BRDGADD tap0: No such file or directory

Any ideas?

Thanks,

Rick

[chenyanlei]

Hi @tonifirnandes
I have encountered the same problem, have you solved it?

[AlmirKadric]

@rhickstedjr apologies for the late reply. Will answer this anyway for others to have some reference. If the tap interface doesn't appear within ifconfig it means that docker hasn't bound to it. To resolve this restart docker-for-mac manually. Also to help further diagnose the issue the following information should be provided:

• ls -l /Applications/Docker.app/Contents/Resources/bin/ to make sure the shim was properly installed and configured
• ls -l /dev/tap* to make sure docker has access to tap interface
• ifconfig to make sure docker connected to the tap interface
• netstat -rn to make sure routes were set to the containers over the tap interface
• docker run --rm --privileged --pid=host --net=host alpine ifconfig to make docker created the target interface
• docker run --rm --privileged --pid=host debian nsenter -t 1 -m -u -n -i iptables-save to make sure the docker host allows routing
• docker inspect <<Container_id>> to make sure your container is configure to use all of the above

[AlmirKadric]

@chenyanlei can you provide the above information and I'll help you with your issue as well

[AlmirKadric]

@chenyanlei @tonifirnandes are you still facing issues
I would like to clean up this issue
if i dont get a response by next i will be closing the issue

[AlmirKadric]

closed due to inactivity

[km1562]

I have the same problem for M1 chip