I know this thread is old, but I'd like to leave here what solved the problem for me. You need to check if you have the same security in both access points. For example, I had one access point secured with WPA/WPA2 and another with WPA2 only. After changing both to the same, everything was fine.
To check your access points' security, you can do this:
Yes, this is possible and actually quite simple. To prevent the Time Capsule from acting as a WiFi access point or router, and use it only as a backup disk, just open the AirPort Utility app on a Mac (Applications -> Utilities -> AirPort Utility) and do the following:
Select your Time Capsule and hit Edit.
Go to the tab labeled Wireless (not Network as ...
This answer is a quick summary of what the fields mean in the routing table display of netstat. You can find all this information directly from the netstat man page (man netstat) or for an excellent primer, see FreeBSD's Handbook Chapter 31.2 - Gateways and Routes. (Apple's netstat is derived from the BSD version).
The flags field shows a collection ...
Your issue is being caused by OS X's handling of a wi-fi parameter commonly referred to as roaming threshold. This parameter dictates the point at which an OS will switch to a stronger signal. Windows gives easy access to this parameter, example here, but no simple option exists in OS X.
This document from NYU suggests OS X has "aggressive" roaming ...
I suggest to use networksetup which works persistent and also in separate network locations.
First, open your terminal of choice i.e. iTerm2.app or Terminal.app
list your network locations:
choose your desired network location:
sudo networksetup -switchtolocation <locationofchoice>
list "devices" called ...
Just to clarify, the term "router" is incorrect here mostly because it is used incorrectly by manufacturers who sell products in the retail market.
A router is neither compatible nor incompatible with Time Machine. A router simply routes network traffic (packets) from one network to another.
What these retail "routers" actually are is an ...
You only need a router if you want to "route" a network connection to more than 1 device.
If you only want to have 1 device connected to your network then you don't need a router. If you add another network-enabled device (TV, printer, another computer, etc), then you will need a router to share & control the network traffic.
The newest OS X Server versions don't provide any tools to enable NAT/Routing in OS X.
To get NAT working without using Internet Sharing you have to use a pf rule and create a plist to enable forwarding and load the pf rule:
Below I assume en0: the interface connected to the cable modem and en1: the interface connected to the LAN. DHCP and DNS are set up ...
You should actually do BOTH of the things suggested by the other answers.
Go into Wireless tab and set the mode to Off so that it doesn't create a WiFi network anymore.
Go into Network tab and set it to Off (Bridge Mode) so that it doesn't run a DHCP server/NAT anymore. Otherwise it will try to create its own subnet for any devices connected via its ports. ...
It should be possible to create a bridge with en0 and en2 and enable net.inet.ip.forwarding to get rid of all routing problems. The bridge acts more or less as another switch between en0 and en2.
Disable Internet Sharing
remove the gateway in the en2 settings of the Mac mini and change the IP-address to an available one in 192.168.88.0/24 (e.g. 192.168.88....
Note: Someone please edit this to include only default commands
Covered in this answer
DHCP (Range, reservations, mask, router, lease time)
Option 1: com.apple.nat.plist
sudo cp /Library/Preferences/SystemConfiguration/com.apple.nat.plist /Library/Preferences/SystemConfiguration/...
1. Wireless interference
The most common cause of what you describe here is a common wireless
This probability is pretty high if your network loss of performance
was closely related with the move of wirelessly connected
computer or of pieces of furniture made of metal or glass (these cause
many radiofrequency reflections).
If you want ...
I've been trying to figure out the pattern here as well. I found this doc by Apple to be very helpful:
It explains pretty plainly:
macOS clients monitor and maintain the current BSSID’s connection
until the RSSI crosses the -75 dBm threshold. After RSSI crosses that
threshold, macOS scans for roam candidate BSSIDs ...
Going into keychain and deleting the entry for the wifi network solved it. Just connected to the network again and entered my credentials.
There was something wrong with either the password (I doubt this) or the authentication mechanism that was somehow paired with the keychain entry.
Anyway, this also means that going the manual way, as suggested by ...
Below is a network diagram based on what I have read thus far. I have made some assumptions about the IP numbering conventions, but that will have no effect on the overall scenario.
I am assuming that you are using two different subnets rather than 2 different classes of networks. But, either way, you have two very different network IP addressing schemes ...
I don't know if I am a "serious Mac user" but I do use my Mac "seriously".
The instructions you got fit pretty much all OSes (Windows, macOS, Linux). It just depends on the software that you use
What those instructions are telling you is to use an RS-232 connection to talk to the router. This type of maintenance has been around since at least the 1970s ...
Almost all wifi products are backwards compatible (I can't think of any that aren't). Specifically regarding the iPhone SE, the site GSM Arena lists the full specs for the iPhone SE's wifi modem: Wi-Fi 802.11 a/b/g/n/ac, hotspot.
Time Machine is not accessing the internet. Your ISP or your modem are incorrectly categorizing the traffic as network traffic.
Time Machine operates entirely between your computer and the drive itself (necessarily communicating to the device the drive is plugged into). There's no intermediary servers.
You will need to pursue solutions specific to your modem ...
The order of your internet connections is reversed.
For internet connection sharing to work it should be:
"Share your connection from Ethernet"
"To computers using Wi-Fi".
Here are the instructions:
What you are trying to do is indeed possible, but it requieres a lot of work to get it working.
I thought about that for a while and it is a great Idea to use a mac as Wifi-Router, especially in Virtual-Test-Environments. But Mac OS X does not work like that.
The reason for that is, that Mac OS X only starts the service, if you really have Internet ...
As Rob says, "Default Host" is what you are looking for. The current version (as of June 2015) of the Airport Utilty App (iOS) uses the following path:
Open Airport Utility
Select the Airport
Click 'DHCP and NAT'
Click 'Default Host', and enter the IP address you want.
And the Airport Utility App (Mac) uses this path:
Apple uses the wording "Default Host" for a DMZ.
Open AirPort Utility
Select the AirPort
Click the Network tab
Click "Enable default host at"
enter the local IP you wish to use and done.
I hope you have the same version and same options visible as I do...