0

Please note that I've only a rudimentary understanding of wifi/technology overall so I may very well be asking of you a ridiculously silly question and I can only pray you will all be gentle in response... Please also note that I have reached out to both Apple and Shaw Cable's Support teams but was advised by Apple that I may be a bit more advanced than I feel I am & that my question was beyond their purview. I must say the technician I first spoke with was very patient and passed me on to his Senior Advisor who was the same. He ran through a number of checks with me but felt I'd already done all he could think to try & advised only those working with Apple's AirPort & the like might know what I'm seeing but, because the the only product I have is an iPhone, I would find no help there... He did agree that I ought to try posting to their own forum but I've yet to see any response there after doing inasmuch... I ran into a similar issue with Shaw who said it doesn't seem to be connected to the Cisco Router I have through them so... I am now posting here - the only forum I've found w/ access to well written/helpful Q & A's of a slightly similar nature.

The above said, I am wondering if someone might explain in layman's terms if possible (I will do my very best to follow if not though!) what the unknown FE80::%awdl0 & %utun0 connections/devices are that I keep seeing displayed (SEE TODAYS OUTPUT BELOW as per the System Status app by Techet) while using an iPhone 6 (10.0.2) connected to Virgin Mobile &/or Shaw Cable's residential wifi (a Cisco DPC3825 DOCSIS 3.0 Data Gateway). The majority appears self-explanatory; however, beyond my Cisco Router (192.168.0.1 & MAC 7c:b2:1b:2f:fe:79) and iPhone (fe80::44d:be56:426:6fd4%en0 & MAC 8:74:2:c5:30:d or 08:74:c5:30:0d), I'm baffled as to the purpose of/need for the unknown fe80::54b9:68ff:fe04:8702%awdl0 and fe80::cff5:2ecb:a2ed:7683%utun0 connections/devices? PLEASE SEE TODAYS OUTPUT BELOW. Both change when I reset the router itself OR iPhone network connections and from what I've read, utun0 may refer to a VPN connection, something called MDNS Responder & another called Back to My Mac but I don't have these things set up as far as I know and I am neither signed in to, nor do I back up to iCloud/iTunes from my device. 

Subsequent to doing my utmost to gain at least some understanding of wifi, IPv4, IPv6 & MAC addressing, etc. I took the following steps to bolster security/rid myself of the unknown connections but didn't succeed:

  • Reset the Cisco Router;

  • Changed the default administrator password to something new, brought the maximum number of DHCP users to one & changed both the SSID & it's password before also disabling SSID broadcasting; 

  • Turned SPI & IPv6 Firewall Protection to High & On (respectively), turned on IP Flood Detection and blocked Fragmented IP Packets, Port Scan Detection & Anonymous Internet Requests;

  • Disabled IPSec & PPTP Passthrough;

  • Ensured the VPN Tunnel List is empty & IPSec VPN Tunnel is disabled;

  • "Forgot" my wifi network & reset the Network Settings on my iPhone but found the unknown connections to be dynamic (they changed when I took this step) & persistent; 

  • Performed reverse searches for these fe80::(string of 16 alpha-numeric digits in quartets)%awdl0 & %utun0 addresses to no avail;

  • Using the MAC displayed under the %awdl0 string & those found by converting the %utun0 addresses to MAC's, I again had no luck discerning their device types via reverse searches;

  • Blocked said MAC's via Cisco's Wireless/Mac Filter & Access Restrictions/MAC Address Filtering pages (e.g. I'd block 56:b9:68:4:87:02 and CD:F5:2E:ED:76:83 per today's output SEE BELOW of Destination: fe80::54b9:68ff:fe04:8702%awdl0 Gateway: 56:b9:68:4:87:2nd Destination: fe80::%utun0/64 Gateway: fe80::cff5:2ecb:a2ed:7683%utun0) but was again obviously thwarted as these addresses will change;

  • Blocked all but/permitted only my iPhone's MAC (08:74:02:c5:30:0d or 8:74:2:c5:30:d) but continue to see the unknown addresses/connections;

  • Double & triple checked that I've no VPN configurations, profiles and the like on my iPhone;

  • Thinking perhaps it is some type of backup, I disabled all options in iCloud, then signed out of iCloud, etc. on my device and ensured the device was deleted/deauthorized, etc. on iCloud.com and via my Apple ID account;

  • Also turned off all possible location services/applied full restrictions & ensured changes cannot be made;

  • Applied Do Not Track, blocked cookies, wiped caches, etc. in Safari;

  • Performed a complete Factory Reset of my iPhone several times and first created a new Apple ID using all of the above settings but still saw these connections arise so I then performed another Factory Reset, applied all of the above and have not created/signed into/backed up to any iCloud/Apple ID;

  • And so on and so on as nauseam... All to no avail. 


In an aside, both Apple and Shaw inquired as to the reasoning behind my question/worry wondering if perhaps I was asking merely out of curiosity or if it's due to my belief that something malicious/nefarious going on. I answered that I am both curious about this and I am concerned for security. I have always been über security conscious but have become even more so when a recent lover managed to read through personal emails & texts on my iPhone before the one minute inactivity time-frame had expired (when it shuts down & requires a passcode/Touch ID). I believe I've done all can to tighten security & one cannot expect perfection but... I remain troubled by these unknown connections/devices & doubly so as I am clearly out of my depth... I always feel best (as I am sure other so as well) when I understand what it is I am looking at but, despite all of my attempts at either understanding or resolving this, I remain at a loss...

To reiterate, may someone explain what a utun0 connection is and why I might be connecting to it? As stated above, these connections change but as per today's output, the connections in question are: fe80::54b9:68ff:fe04:8702%awdl0 (MAC: 56:b9:68:4:87:2) and fe80::cff5:2ecb:a2ed:7683%utun0

TODAY'S OUTPUT WHILE CONNECTED TO SHAW WIFI:

Internet:

  • destination: default gateway: 192.168.0.1 netif: en0 flags: UGSc refs: 40 use: 0 mtu: 1500 expire: -1

  • destination: 127 gateway: 127.0.0.1 netif: lo0 flags: UCS refs: 1 use: 0 mtu: 16384 expire: -1

  • destination: 127.0.0.1 gateway: 127.0.0.1 netif: lo0 flags: UH refs: 1 use: 0 mtu: 16384 expire: -1

  • destination: 192.168.0 gateway: link#8 netif: en0 flags: UCS refs: 1 use: 0 mtu: 1500 expire: -1

  • destination: 192.168.0.1/32 gateway: link#8 netif: en0 flags: UCS refs: 2 use: 0 mtu: 1500 expire: -1

  • destination: 192.168.0.1 gateway: 7c:b2:1b:2f:fe:79 netif: en0 flags: UHLWIir refs: 40 use: 0 mtu: 1500 expire: 1196

  • destination: 192.168.0.10/32 gateway: link#8 netif: en0 flags: UCS refs: 1 use: 0 mtu: 1500 expire: -1

  • destination: 224.0.0/4 gateway: link#8 netif: en0 flags: UmCS refs: 1 use: 0 mtu: 1500 expire: -1

  • destination: 255.255.255.255/32 gateway: link#8 netif: en0 flags: UCS refs: 1 use: 0 mtu: 1500 expire: -1

Internet6:

  • destination: default gateway: fe80::%utun0 netif: utun0 flags: UGcI refs: 1 use: 0 mtu: 2000 expire: -1

  • destination: ::1 gateway: ::1 netif: lo0 flags: UHL refs: 1 use: 0 mtu: 16384 expire: -1

  • destination: fe80::%lo0/64 gateway: fe80::1%lo0 netif: lo0 flags: UcI refs: 2 use: 0 mtu: 16384 expire: -1

  • destination: fe80::1%lo0 gateway: link#1 netif: lo0 flags: UHLI refs: 1 use: 0 mtu: 16384 expire: -1

  • destination: fe80::%en0/64 gateway: link#8 netif: en0 flags: UCI refs: 2 use: 0 mtu: 1500 expire: -1

  • destination: fe80::8a1:e930:1b2e:725a%en0 gateway: 8:74:2:c5:30:d netif: lo0 flags: UHLI refs: 1 use: 0 mtu: 16384 expire: -1

  • destination: fe80::%awdl0/64 gateway: link#10 netif: awdl0 flags: UCI refs: 2 use: 0 mtu: 1484 expire: -1

  • destination: fe80::54b9:68ff:fe04:8702%awdl0 gateway: 56:b9:68:4:87:2 netif: lo0 flags: UHLI refs: 1 use: 0 mtu: 16384 expire: -1

  • destination: fe80::%utun0/64 gateway: fe80::cff5:2ecb:a2ed:7683%utun0 netif: utun0 flags: UcI refs: 3 use: 0 mtu: 2000 expire: -1

  • destination: fe80::cff5:2ecb:a2ed:7683%utun0 gateway: link#14 netif: lo0 flags: UHLI refs: 1 use: 0 mtu: 16384 expire: -1

  • destination: ff01::%lo0/32 gateway: ::1 netif: lo0 flags: UmCI refs: 1 use: 0 mtu: 16384 expire: -1

  • destination: ff01::%en0/32 gateway: link#8 netif: en0 flags: UmCI refs: 1 use: 0 mtu: 1500 expire: -1

  • destination: ff01::%awdl0/32 gateway: link#10 netif: awdl0 flags: UmCI refs: 1 use: 0 mtu: 1484 expire: -1

  • destination: ff01::%utun0/32 gateway: fe80::cff5:2ecb:a2ed:7683%utun0 netif: utun0 flags: UmCI refs: 1 use: 0 mtu: 2000 expire: -1

  • destination: ff02::%lo0/32 gateway: ::1 netif: lo0 flags: UmCI refs: 1 use: 0 mtu: 16384 expire: -1

  • destination: ff02::%en0/32 gateway: link#8 netif: en0 flags: UmCI refs: 1 use: 0 mtu: 1500 expire: -1

  • destination: ff02::%awdl0/32 gateway: link#10 netif: awdl0 flags: UmCI refs: 1 use: 0 mtu: 1484 expire: -1

  • destination: ff02::%utun0/32 gateway: fe80::cff5:2ecb:a2ed:7683%utun0 netif: utun0 flags: UmCI refs: 1 use: 0 mtu: 2000 expire: -1

  • TL;DR. At least structure it so someone will read it. – Xavierjazz Nov 4 '16 at 1:47
  • My apologies. The structure was lost when I copies & pasted it here. Will revise now. – Anjaztazia Kalashnikova Nov 4 '16 at 3:43
  • I've now restructured it and it appears readable from my iPhone; however, please advise if it's still a jumble on your end. Thank you in advance for any assistance. – Anjaztazia Kalashnikova Nov 4 '16 at 4:32

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Browse other questions tagged or ask your own question.