up vote 5 down vote favorite
1
share [g+] share [fb]

I have a client bridge (LinkSys WRT54GL router with DD-WRT firmware). I specified an IP address of 192.168.1.2 for the device, however, when I run ipconfig, the default gateway is now 192.168.0.1. Similarly, when I try to connect to http://192.168.1.2, I can't access the administrative page for the router.

Any ideas?

link|improve this question
Would tracert give you any ideas? In other words, trace to your ISPs DNS, for example, and see what IPs you hit on the way. – Michael Todd Jan 6 '10 at 18:42
A bridge is a layer2 device. not a layer3 device. traceroute operates at layer3. – user23307 Jan 17 '10 at 22:33
feedback

6 Answers

I have a client bridge

ok..

the default gateway is now 192.168.0.1.

because you have a bridge and your DHCP information comes from the router...

when I try to connect to http://192.168.1.2, I can't access the administrative page for the router.

because you are on the 192.168.0 network and neither your machine or your router knows anything about the 192.168.1 network. Do this:

  1. temporarily assign your computer an address of 192.168.1.100
  2. login to 192.168.1.2, reconfigure it to use 192.168.0.2(or just tell it to use dhcp)
  3. set your machine back to dhcp
  4. profit!
link|improve this answer
feedback

You could perform a ping scan ( http://superuser.com/questions/45687/how-can-i-ping-a-range-of-ips-simultaneously ).

Then you would know which addresses might be your device.

link|improve this answer
I'll try this and let you know how it works. – David Jan 6 '10 at 9:03
feedback

You can force the settings of the default gateway in your adapter properties.

Is it possible that you still have this set from how your previous connection was set up?

link|improve this answer
feedback

Make sure you connect from a wired computer.

link|improve this answer
feedback

Are you using DHCP on the client computer? The router should normally be the gateway (or the x.x.x.1 in your subnet) assigned; In this case, 192.168.0.1. Have you tried clearing any caches on the client? Ex. "repair" the connection. Are the administrative pages available on both sides of the bridge?

link|improve this answer
feedback

Funny prerequisite question, are you sure you're on the right wireless network? Sorry, but experience has taught me to always ask that first.

The question to answer would be where did the current default gateway address from. Run "ipconfig /all" and check to see if it says "DHCP Enabled.....Yes".

If not, then go into your TCP/IP properties and enable DHCP or manually configure the client IP settings.

If it is DHCP enabled the "DHCP Server...." field will identify the server it got the address from, try pinging, and connecting to that address via HTTP and HTTPS. If any of those work you probably have multiple devices in router mode on your network, find and remove the rogue.

If the server doesn't answer up then you probably have old info in there. Run "ipconfig /release" to let go of the old DHCP lease, then run "ipconfig /all" to make sure you see an unconfigured interface, finally run "ipconfig /renew" to get a new address, hopefully you will now see usable addresses.

If you are still not working, try configuring your client manually and seeing if you can access the router and everything works, if so your DHCP server may be flaked out. Make sure it is configured correctly and restart it.

Good luck

link|improve this answer
feedback

Your Answer

 
or
required, but never shown