How to allow specific IP access in Nginx?

Cannot get IP address from router's wireless signal?

• I am trying to access the internet wirelessly on my new laptop from the family computer's wireless router. Despite the fact that the laptop can access it perfectly fine, and I apparently typed in the correct password for the wireless (I purposely typed in an incorrect password, and sure enough, when the password is incorrect it says so; it does not tell me the password I am using is incorrect). Once accessed, the status tells me that I have "limited access" to the signal, and I am unable to connect to the internet at all. I recall I had this problem with an earlier laptop, years ago; we ended up having to call Verizon and eventually the solution was to hook the two computers together (I can't remember with what), and to allow access to the IP address from the family computer, but it was so many years ago, and the layout of the computers has changed so much since then, I can't remember specifically what we did. Presumably I can access other wireless signals just fine; it's just a strange security encryption on our router that's stopping it. Does anyone have any idea?

• Answer:

  Connect to the router with one of the computers that works. (Look in the documentation for the router's address - different manufacturers use different addresses.) Make sure that the DHCP server has at least one slot open. (If you have only 2 slots, and you have 2 computers already connected, a third one won't get an IP address so it can't get to the internet. [It'll get a 169 address, which means "no address".]) Make sure that the TYPE of password you're using is the one the router wants. Putting in a WEP passphrase when the router wants a WPA password (or using TKIP encryption when the router wants AES) won't work. Make sure the laptop is set to automatically get an IP address for its wireless connection. If the router is in the 192 range and the laptop is set to a fixed address in the 10 range, for example, you won't get internet connectivity. Connecting one computer to another one is putting a band-aid on a severed artery. It's not fixing the problem, it's just not letting you see it. (I wouldn't even call it an emergency measure - it's technically doable, but - for many reasons - you just don't want that "solution". but considering the level of expertise ar Verizon's "tech support" center, it's amazing that they gave you that much help. The "tech support" is one of the reasons I refuse to use Verizon. My computer knows more about tech support than their tech support people. Even my old dead one does.)