When using rvictl, I notice that it creates 2 interfaces. One of which establishes a link local connection between the iPhone and the Mac. What is this connection for? Why is it so talkative? and why can I only bring one of the created interfaces down but not the other?
When I try to bring down the interfaces with the ifconfig enX down command it stops the DHCP requests and several TCP DUP ACK, but the other interface is persistent and will not stop talking.
Can someone explain what type of traffic is being transmitted between the Mac and the iPhone?
In the Xcode 15 timeframe Apple changed the way that the Mac and iPhone communicate for the purposes of development, Finder sync, and so on. How this used to work, and how it now works, are all considered to implementation details. If you’re curious about the current setup, you can glean a lot from the devicectl online help:
% xcrun devicectl
OVERVIEW: Core Device Device Control: a command line utility for exercising
Core Device functionality.
…
While this is all implementation detail, that doesn’t make it totally invisible. This extra interface is a classic example of that. rvictl needs to talk to the device and the standard mechanism for talking to the device now uses the network.
TN3158 Resolving Xcode 15 device connection issues and TN3165 Packet Filter is not API both discuss other ways that this change was not 100% transparent.
Is this setup causing you problems in some way? If so, please explain what those are and I’ll see if there’s a way around them.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"