Forums
New posts
Articles
Product Reviews
Policies
FAQ
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Menu
Log in
Register
Install the app
Install
Forums
Digital Lifestyle
Internet, Networking, and Wireless
WiFi AND Ethernet
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="MacInWin" data-source="post: 1741856"><p>Lisa, I know what subnets are and how they work. And I can set up a separate subnet, if that's what helps. But I don't see any way to tell the watch to change from one subnet to another. That is, I don't see any WiFi controls on the watch at all. Just on/off. What I plan to do next is to take my MBP and my watch away from the WiFi altogether, to see if the watch and Mac communicate directly, or if everything has to go through the router. As I said, what I think is happening is that the combination of watch, iPhone and Mac communicate to first make sure I'm me, then that all of them are in the same iCloud account and that the passwords for that iCloud account are correctly entered on all three. Given all of that, the Mac then "trusts" the watch to unlock the Mac. If you look at the Apple watch user guide here: <a href="http://help.apple.com/watch/#/apd0443fb403" target="_blank">http://help.apple.com/watch/#/apd0443fb403</a> it does NOT say you can unlock a Mac without the iPhone nearby. That's why I'm testing that theory today. </p><p></p><p>But the real problem is not the subnet, I think. The problem is that assigning two IPs to the MBP, one Wifi and one Ethernet, works for a while, but then the system gets confused and downloads stall, web pages balk and generally the system gets mucked up. Shutting off the WiFi fixes the problem, but then the login doesn't work. I don't think changing subnets will fix the stalling, balking and mucking up. I think the problem is having two IP numbers in the same system.</p><p></p><p>I did look at Knock, BTW. Nice solution, thanks for pointing it out. Will keep that in mind if this gets irritating enough.</p></blockquote><p></p>
[QUOTE="MacInWin, post: 1741856"] Lisa, I know what subnets are and how they work. And I can set up a separate subnet, if that's what helps. But I don't see any way to tell the watch to change from one subnet to another. That is, I don't see any WiFi controls on the watch at all. Just on/off. What I plan to do next is to take my MBP and my watch away from the WiFi altogether, to see if the watch and Mac communicate directly, or if everything has to go through the router. As I said, what I think is happening is that the combination of watch, iPhone and Mac communicate to first make sure I'm me, then that all of them are in the same iCloud account and that the passwords for that iCloud account are correctly entered on all three. Given all of that, the Mac then "trusts" the watch to unlock the Mac. If you look at the Apple watch user guide here: [url]http://help.apple.com/watch/#/apd0443fb403[/url] it does NOT say you can unlock a Mac without the iPhone nearby. That's why I'm testing that theory today. But the real problem is not the subnet, I think. The problem is that assigning two IPs to the MBP, one Wifi and one Ethernet, works for a while, but then the system gets confused and downloads stall, web pages balk and generally the system gets mucked up. Shutting off the WiFi fixes the problem, but then the login doesn't work. I don't think changing subnets will fix the stalling, balking and mucking up. I think the problem is having two IP numbers in the same system. I did look at Knock, BTW. Nice solution, thanks for pointing it out. Will keep that in mind if this gets irritating enough. [/QUOTE]
Verification
Post reply
Forums
Digital Lifestyle
Internet, Networking, and Wireless
WiFi AND Ethernet
Top