Jump to content

MacOS - Connection via USB-C (Pings but no web UI)


Recommended Posts

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?

  • Like 1
Link to comment
Share on other sites

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

  • 1 month later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...