ironclaw Posted May 18, 2022 Share Posted May 18, 2022 Before anyone asks, yes, I am aware that MacOS has issues with connecting to the Pineapple but I feel like I'm close here. I installed the latest AXIS AX88772C driver for MacOS 12 and setup the adapter with a manual IP of 172.16.42.42 and subnet of 255.255.0.0. All other fields are blank. The adapter is the first in terms of priority in the Network settings. Ping ping 172.16.42.42 PING 172.16.42.42 (172.16.42.42): 56 data bytes 64 bytes from 172.16.42.42: icmp_seq=0 ttl=64 time=0.068 ms 64 bytes from 172.16.42.42: icmp_seq=1 ttl=64 time=0.100 ms 64 bytes from 172.16.42.42: icmp_seq=2 ttl=64 time=0.161 ms 64 bytes from 172.16.42.42: icmp_seq=3 ttl=64 time=0.179 ms 64 bytes from 172.16.42.42: icmp_seq=4 ttl=64 time=0.177 ms 64 bytes from 172.16.42.42: icmp_seq=5 ttl=64 time=0.184 ms 64 bytes from 172.16.42.42: icmp_seq=6 ttl=64 time=0.081 ms ^C --- 172.16.42.42 ping statistics --- 7 packets transmitted, 7 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 0.068/0.136/0.184/0.047 ms Ifconfig en6: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500 options=6463<RXCSUM,TXCSUM,TSO4,TSO6,CHANNEL_IO,PARTIAL_CSUM,ZEROINVERT_CSUM> ether 00:13:37:a7:70:91 inet 172.16.42.42 netmask 0xffff0000 broadcast 172.16.255.255 nd6 options=201<PERFORMNUD,DAD> media: autoselect (100baseTX <full-duplex,flow-control>) status: active However, I cannot access the UI at http://172.16.42.1:1471/ from any browser, and a ping of that address fails. If I connect via the management wifi, the Pineapple networking tab lists: eth0 169.254.213.10/16 Up,Broadcast,Multicast br-lan 172.16.42.1/24 Up,Broadcast,Multicast Am I close to getting a connection here, or am I missing some major roadblock that makes this impossible? If I'm not mistaken, shouldn't eth0 be a different address? Link to comment Share on other sites More sharing options...
dark_pyrro Posted May 18, 2022 Share Posted May 18, 2022 eth0 shouldn't get an IP address of its own. eth0 is bridged to br-lan in /etc/config/network. You're getting an "APIPA" address. This might be because of the issues you have posted in the 1.1.1 firmware thread. Not entirely sure it's because you have thrown in MacOS in the mix, but it might affect it all since it's tagged as not supported if running on newer version of the OS (as you mentioned). Link to comment Share on other sites More sharing options...
ironclaw Posted May 18, 2022 Author Share Posted May 18, 2022 Thanks dark_pyrro. I'll try swap the firmware and see if it's persists, that would help rule out the Pineapple. I'm guessing it's MacOS specific. Link to comment Share on other sites More sharing options...
Aaron Outhier Posted June 30, 2022 Share Posted June 30, 2022 Also, if you set your Mac to be at IP 172.16.42.42, and then you ping that same address, you’re pinging yourself. The pineapple is usually at 172.16.42.1 . Link to comment Share on other sites More sharing options...
DramaKing Posted July 19, 2022 Share Posted July 19, 2022 On 5/17/2022 at 7:25 PM, ironclaw said: Before anyone asks, yes, I am aware that MacOS has issues with connecting to the Pineapple but I feel like I'm close here. I installed the latest AXIS AX88772C driver for MacOS 12 and setup the adapter with a manual IP of 172.16.42.42 and subnet of 255.255.0.0. All other fields are blank. The adapter is the first in terms of priority in the Network settings. Ping ping 172.16.42.42 PING 172.16.42.42 (172.16.42.42): 56 data bytes 64 bytes from 172.16.42.42: icmp_seq=0 ttl=64 time=0.068 ms 64 bytes from 172.16.42.42: icmp_seq=1 ttl=64 time=0.100 ms 64 bytes from 172.16.42.42: icmp_seq=2 ttl=64 time=0.161 ms 64 bytes from 172.16.42.42: icmp_seq=3 ttl=64 time=0.179 ms 64 bytes from 172.16.42.42: icmp_seq=4 ttl=64 time=0.177 ms 64 bytes from 172.16.42.42: icmp_seq=5 ttl=64 time=0.184 ms 64 bytes from 172.16.42.42: icmp_seq=6 ttl=64 time=0.081 ms ^C --- 172.16.42.42 ping statistics --- 7 packets transmitted, 7 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 0.068/0.136/0.184/0.047 ms Ifconfig en6: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500 options=6463<RXCSUM,TXCSUM,TSO4,TSO6,CHANNEL_IO,PARTIAL_CSUM,ZEROINVERT_CSUM> ether 00:13:37:a7:70:91 inet 172.16.42.42 netmask 0xffff0000 broadcast 172.16.255.255 nd6 options=201<PERFORMNUD,DAD> media: autoselect (100baseTX <full-duplex,flow-control>) status: active However, I cannot access the UI at http://172.16.42.1:1471/ from any browser, and a ping of that address fails. If I connect via the management wifi, the Pineapple networking tab lists: eth0 169.254.213.10/16 Up,Broadcast,Multicast br-lan 172.16.42.1/24 Up,Broadcast,Multicast Am I close to getting a connection here, or am I missing some major roadblock that makes this impossible? If I'm not mistaken, shouldn't eth0 be a different address? Hopefully you've figured this out already, but the correct subnet mask is 255.255.255.0. On 6/29/2022 at 10:51 PM, Aaron Outhier said: Also, if you set your Mac to be at IP 172.16.42.42, and then you ping that same address, you’re pinging yourself. The pineapple is usually at 172.16.42.1 . He only did that to verify that the adapter was configured correctly. As stated, the Mac was unable to reach 172.16.42.1. Link to comment Share on other sites More sharing options...
luckman212 Posted March 12, 2023 Share Posted March 12, 2023 I wish I'd known about the problems with the ASIX AX88772C on recent macOS — I just got my Pineapple Mark VII and within minutes of unboxing it I hit the driver issue. Would have been nice if this was more prominent on the ordering / sales pages, instead I didn't see it until I stumbled onto https://docs.hak5.org/wifi-pineapple/faq/macos-support Anyway, I wrestled with it for a couple of hours before giving up. Seems these drivers are just dead on macOS 13. Makes the unit a lot less useful, as the only way to talk to the unit is over the management WiFi which is 2.4G only and the bridge to the internet is very slow and sometimes doesn't work well, so I end up having to do a dance of hopping between my real WiFi and then bouncing back over to the Pineapple. As a test I fired up UTM and grabbed the Debian 11 Xfce image and attached the AX88772C to it—boom works immediately and without any additional drivers. Anyone ever figure out a workaround? Is ASIX working on a proper driver for macOS 13? Link to comment Share on other sites More sharing options...
dark_pyrro Posted March 12, 2023 Share Posted March 12, 2023 The only known workaround is using a VM (if no other OS is available other than MacOS of a recent version). There's no information around that tells if ASIX is working on any new driver. Link to comment Share on other sites More sharing options...
luckman212 Posted March 12, 2023 Share Posted March 12, 2023 Okay. It's weird that the AX88178 and AX88772A/B are supported by Apple's native AppleUSBEthernet or AppleUserECM drivers, but the "C" variant is notably omitted. I guess we can only hope that one day this thing is natively supported by Apple's driver. Won't hold my breath. 😷 Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.