Tag Info

Hot answers tagged

3

Here is a step-by-step guide for you: Temporarily disable any Firewall/Internet Security solution/packet filter on your Mac (like LittleSnitch/Hands Off!/Kaspersky Internet Security etc.) Connect to the administrative interface of your router with a working Mac. Make a note of the internal interface (probably 192.168.0.1 in your case) If your router uses ...


2

After inspecting your configuration, it seems two factors might be in play here: DNS Firewall A quick way to confirm a working internet connection but bad DNS is going to a website by using it's IP address rather than it's domain name. For example: http://91.198.174.192 which is a WikiMedia Foundation address. It should say something like "unconfigured ...


2

It doesn't have nor does it assign one. However, it may have have host names/addresses cached so you may still be able to access sites you previously visited. However, once that cache clears, you will only be able to browse by using raw IPs.


2

You can have the same SSID for multiple APs, this is how our campus network is set up, but there is a caveat that's worth knowing. When moving between APs we've noticed OS X has a tendency to "stick" to the first AP it has joined even if it's in the presence of another AP offering a stronger signal. Cycling the wi-fi can help with re-association to an AP ...


2

/Sy*/L*/Priv*/Apple8*/V*/C*/R*/airport -I | grep SSID This uses the airport CLI, with the -I flag to show information and grep for SSID shows the name of the network.


1

Your AirPort Extreme will need to "control" the network in order for this setup the way you expect. The Linksys would have to be configured as a bridge with the AirPort Extreme as the router/DHCP server. Do not that the way you have things setup currently, Time Machine will still work; however you will need to connect to the server/disk by IP address. Other ...


1

When flashing custom firmware, you need to be very careful. Some firmwares can cause hardware-software communication issues, so when you think a setting has been changed, it may not have been. DO NOT send it in for repair. You've probably already voided the warranty. Try to go back to your original firmware and see if it works. Any communication errors ...


1

Try System Preferences > Profiles. It listed my 802.1X profiles and I was able to remove them from there. Alternatively, you can manually edit configuration files in /Library/Preferences/SystemConfiguration (see this post) - grep the files located there for the name of your profile. (Using OS X Mavericks)


1

First of all, to get the UUIDs of your network sets, use PlistBuddy and perl: /usr/libexec/PlistBuddy -c "print :Sets" /Library/Preferences/SystemConfiguration/preferences.plist | perl -lne 'print $1 if /^ (\S*) =/' this should return the IDs of the network sets. For each set you can then get the name with /usr/libexec/PlistBuddy -c "print ...


1

So it turns out that the Go socketio library has a default max setting of 1000 simultaneous socket connections. Calling server.SetMaxConnection(10000) (in conjunction with an appropriately high ulimit -n, as mentioned in the question) will allow > 1000 simultaneous client connections.


1

It seems like you are pretty up on WiFi, so I won't go into all the inner workings. However, you did mention that the "handover takes ages." The handover is handled by both the device AND a controller. There is a setting (and generally not accessible by users) at what threshold the adapter begins looking for another good network. It is taking ages ...


1

Some users have reported similar problems with 10.10.2 Looking true you attempts, I would suggest following additional steps. Reset WiFi settings: Turn Off Wi-Fi from the Wireless menu item From the OS X Finder, hit Command+Shift+G and Copy/Paste the following path: /Library/Preferences/SystemConfiguration/ Select following files: ...



Only top voted, non community-wiki answers of a minimum length are eligible