telot Posted October 11, 2015 Posted October 11, 2015 (edited) Hey all - have any other mac users upgraded to El Capitan? I did last week, and since then my Lan Turtle won't show up in the Network Preferences pane any more. I made sure my lan turtle wasn't borked by plugging it into an old Mountain Lion mac I have - works like a charm and shows right up as a USB Ethernet adapter. On my El Cap machine, I can pass the device to a VM in virtual box, so I know El Cap is seeing the device, it just doesn't populate it or receive an IP address from it. Any ideas? Thanks! telot Edit: Feels odd, but I marked my reply below as Best Answer for future searchers. Edited October 16, 2015 by telot Quote
Darren Kitchen Posted October 12, 2015 Posted October 12, 2015 You say the device shows up. Can you statically assign an IP address in the 172.16.84.x range? Unfortunately I don't have a Mac to test. Quote
Solution telot Posted October 12, 2015 Author Solution Posted October 12, 2015 No prob Darren. To clarify, the device was visible to Virtualbox, and gave the option to pass it through to a VM. It wasn't visible to OSX's network preferences screen (so no option to set a static). I was however able to download the driver from realtek's site and get it working. This might inhibit a pentest against an el capitan victim, but for my own testing it works just dandy! http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=14&PFid=55&Level=5&Conn=4&DownTypeID=3&GetDown=false telot Quote
Darren Kitchen Posted October 12, 2015 Posted October 12, 2015 That's interesting. I've only ever noticed this behavior once before which was with a Windows 7 box in testing. As it turns out if the copy of Windows hasn't been activated (or in this case has expired) it won't allow Windows Update to fetch the WHQL driver. I don't have the Mac experience to know if there's something similar going on here since you're running a copy in a VM - just speculating. If I get a chance I might test on a macbook at the Apple store next time I'm around the shops. Quote
barry99705 Posted October 13, 2015 Posted October 13, 2015 Makes sense. The driver wasn't built in. It is an Apple product, they only want to play nice with their own hardware. Quote
Mr-Protocol Posted October 13, 2015 Posted October 13, 2015 I have an El Capitan mac at work. I will bring my turtle into work and test it on my lunch break. If I have time, I will test the VM passthrough. We have seen issues with passthrough with virtualbox in the past with the turtle though. Telot, what was the OS in the VM? Kali? Quote
Darren Kitchen Posted October 13, 2015 Posted October 13, 2015 Makes sense. The driver wasn't built in. It is an Apple product, they only want to play nice with their own hardware. Sure, but it was built in on Yosemite. Quote
denningsrogue Posted October 13, 2015 Posted October 13, 2015 Same issue here. Works under Mavericks; doesn't under El Capitan. Quote
Mr-Protocol Posted October 13, 2015 Posted October 13, 2015 I tried plugging in the lanturtle into my El Capitan (basically fresh install) and it would not detect as an ethernet adapter. Running ifconfig did not show it up, nor did dmesg. I did not try in a VM since I did not have one setup and had no time to set one up. Quote
telot Posted October 14, 2015 Author Posted October 14, 2015 Hey Mr-P! Long time no see (figuratively speaking of course)! I was running in a Win7 VM (not activated). To clarify, I was just going to the Devices menu in virtual box, to USB Devices, and I saw the generic description "USB to Ethernet Adapter" - ready for pass through. It's all good Darren - as long as its working for testing on my OS X box, thats all I need. If others are doing a legit pentest in a mac-heavy environment, they might have to pair their attack with a USB Rubbery ducky that has a script to download the drivers (and restart...could be tricky). Thanks for verifying this for me denningsrogue and Mr P - its nice to know I'm not the only one. telot Quote
Mr-Protocol Posted October 15, 2015 Posted October 15, 2015 I discovered my turtle may be broken. Getting a replacement one here shortly. Then I will re-test with El Capitan at work and see if I can get a VM configured. Stay tuned :P. Quote
triple-h Posted October 26, 2015 Posted October 26, 2015 Hi Darren, Thanks to telot, I went to Realtek's site and downloaded the driver for MAC OS X El Capitan. This at least got the LAN Turtle recognized by the OS with a DHCP address of 192.168.1.10: But then, when I try to login from my terminal to 192.168.1.10, I get: MacBook-Pro:~ triple-h$ ssh root@192.168.1.10 ssh: connect to host 192.168.1.10 port 22: Operation timed out OK, so, what if I manually configure the IP address to 172.16.84.1? Nope, I still get: MacBook-Pro:~ triple-h$ ssh root@172.16.84.100 ssh: connect to host 172.16.84.100 port 22: Operation timed out Any other ideas? Thanks. Quote
Mr-Protocol Posted October 27, 2015 Posted October 27, 2015 The LAN turtle is 172.16.84.1 from the USB side and should DHCP that to the machine you have it plugged into. And you cannot SSH from the outside (Ethernet) port by default. Unless you are trying to SSH to another host through the turtle? Quote
triple-h Posted February 1, 2016 Posted February 1, 2016 I wanted to say that the solution to this was just getting a replacement LANturtle. Now, everything is working great. Quote
youngd24 Posted April 20, 2017 Posted April 20, 2017 Brand new to the Lan Turtle and here but wanted to offer thanks for the driver link, worked on my Mac with El Capitan and I can see the Turtle now. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.