Connecting a desktop wirelessly through a bridge

Hey guys, I seem to have a problem setting up my network.

I recently bought a desktop computer and I hoped to set it up on a nice, easy, wired connection. Of course, I never bothered to check whether the room had any ethernet ports or ANY sort of cable ports in it for that matter. I'd considered using a USB wireless adapter for the job, but i've heard they lag like hell during online games,and thats a real problem for me. I have no more PCI slots in my computer either, adding to the mess.

So I went out and bought a D-Link DAP-1522 Wireless Bridge in hopes of using that as a wireless adapter to connect to my home network (Which is just a Linksys WRT160N). But no matter what I try, I just cant get it to work.

Am I on the right path? or is the wireless bridge not the answer?

Thanks in advance.

Not familiar with this piece of equipment, but a wireless bridge should do what you're asking. What happens when you get into the setup of the bridge and tell it to connect to your router?
Pm me if you'd like, and we can maybe solve this quicker.

the wireless bridge is what you need.

if you don't tell us what you have done, how can we know?

you have read the How Tos above. you would not ask questions that have already been answered.

Ok, the how to is very helpful but just one thing,

how can I set the DNS server and the Default gateway that my bridge uses?

apparently you can set the default gateway but not the DNS server. the device probably uses the default gateway as the dns server. page 59 of the manual.

Ok, so my bridge now says Status:Connected in the config, but I still can't get on to the internet through it. It seems that Windows is not picking up that the bridge is a wireless device, and actually thinks its just a local LAN connection. Whenever I go into Network and Sharing Center and go to View Network Devices, I can only see my computer, nothing else. As suggested by Heckufaguy, I tried disabling wireless security and tried using DHCP, but to no avail (DHCP actually wouldn't even let me log in to the config page).

Hope this helps

Any suggestions?

traceroute an url

traceroute an IP address

if you can traceroute an IP address but not an URL you have a DNS server issue

hmmm, traceroute doesn't seem to work for either (and yes, i'm using tracert NOT traceroute in cmd).

traceroute should give you a list of the default gateways between you and the web page or IP you are trying to trace. if you get nada, the default gateway is going nowhere.

Well, if the default gateway is supposed to point to the next part of the chain in the network, how do I know what IP to use when setting the default gateway on my computer?

My Router's IP is 192.168.1.1
The Bridge's IP is 192.168.0.50
My Desktop's IP is 192.168.0.56

So when setting default gateways, I figured this is how it would look (Default Gateway is in brackets):

Desktop (192.168.0.50) ---------> Bridge (192.168.1.1) ---------> Router

is this right?

routers have two interfaces: WAN and LAN

your default gateway is the LAN side of the next router your device sees in the path to the internet.

IP setup, from the internet to the computer:

My neighbors AP setup:

WAN IP, DHCP from ISP

LAN 192.168.0.1

My bridge setup

WAN 192.168.0.250

LAN 192.168.2.1

MY AP setup:

WAN 192.168.2.2

LAN 192.168.1.16

My Computer IP:

192.168.1.25

Default gateways, from the computer to the network:

My Computer, 192.168.1.25, is connected to LAN 192.168.1.16. The default gateway of My Computer, 192.168.1.25 is 192.168.1.16

MY AP, 192.168.1.16, is connected to My bridge, LAN IP 192.168.2.2. The default gateway of My AP, 192.168.1.16. is 192.168.2.2

MY bridge, 192.168.2.2, is connected to My neighbors router LAN IP, 192.168.0.1. The default gateway of My AP, 192.168.2.2. is 192.168.0.1

default gateway is the LAN IP of the next device in the chain that is closer to the internet.

you should see a list of default gateways, in order from computer to destination URL, when you traceroute.

you should not see 192.168.2.2, 192.168.0.250 or WAN IP, DHCP from ISP when you traceroute.

Ok, so I decided to change the third octet of the IP address on my PC and wireless bridge to 1 instead of 0 (so 192.168.0.52 becomes 192.168.1.52)

this has enabled me to see other computers connected to the router, and to see the router itself, even to the point of me being able to edit the router's settings from my desktop

however, I still, for whatever reason, can NOT access the internet from my desktop. whenever I do a traceroute to my router, it shows it as being complete in one step, without the bridge showing up. But whenever I try and traceroute or ping a website (in this case google), no luck.

Next steps from here?

traceroute an IP.

a traceroute of my system, using Sam Spade. I traced Google. I could also trace 74.125.95.99, an IP belonging to google



the 6th router, 205.XXX... is the DNS server.

if I trace 74.125.95.99 when the internet isn't working, I get a similar listing, but no 205.XXX router. Indicating that the ISPs DNS is down and there is nothing I can do but wait and grumble.