Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[duffman]

I'm not so sure providing a local lan is that secure. If one resident has a rogue infected computer it could spread like wild fire. Plus unencrypted traffic is exposed. Do these residents know that you could monitor all their traffic. I know you probably don't but they should know that it is a possibility.

[dwong604]

Hi, i registered an account so i can post on this forum.  I'm having the exact same problem as the OP. 
Here is a little background:

I live in a town house complex, there's about 30 other units in my area and some apartment buildings within range.  My cable provider is Shaw and I have a dedicated modem in my suite.  From the modem i have my DIR-655 connected.  All wired computers are fine.  Once in awhile, my wireless computers will be picking up a different subnet.  By default i'm on 192.168.10.x however sometimes i'm getting 192.168.100.x
I've changed the SSID on my wireless, flashed to the newest firmware and i've also done a factory reset on the router, still the same issue. 
When i get the wrong IP address, i'm able to bring up the gateway's logon page through IE, however i don't have the password for the page. 

Any suggestions?

[kthaddock]

If you picking different subnet then it's your ISP-problem to solve. You getting IP ip from your ISP.

[EddieZ]

No way the router changes subnet on its own. ISP determines your IP.

[dwong604]

Thanks for the reply guys, i'm pretty sure i'm not getting an IP from an ISP. First off, all wired computers are working, so that means that my router is handling DHCP properly.  With my wireless devices, i'm connected through a specific SSID.  (My ssid is actually all digits, everybody else that is broadcasting their SSID, all letters, there are one or two that are alphanumeric, but none are all numeric. 
Its a hit and miss with my situation and i'm noticing it more on my two apple computers then my windows 7 laptop.  It shows that i'm connected to the right IP address, but when i logon to the gateway its a different "gateway" name. 

[lurobi]

I have the same problem If I attempt to change the router's IP to 192.168.0.1.  When I changed the IP, The DHCP settings changed as well.  But clients kept getting assigned IP addresses of 192.168.0.x, even though the router displayed them as having 192.168.1.y (x and y were not the same).

I wasn't able to solve this, and had to change the router's IP back to 192.168.0.1.

This problem only affected my wired connections, and persisted through reboots and resets.

EDIT: Nope, I had a second DHCP server handing out IPs on my network.  Not the router's problem.

[EddieZ]

Check for double DHCP on the LAN.

Also, there is a difference between the DIR gui LAN IP and the DHCP range IP. Also (double DHCP) the modem or device supplying the WAN address also plays a role. So you need to mention here what your setup is: dynamic, static etc.

[lurobi]

Check for double DHCP on the LAN.

After you said that it occurred to me that months ago I had run a dhcp server for the 192.168.0.0 subnet on one of my computers.  Sure enough it was still up and probably competing with the dlink to assign IPs.

[RickNCN]

Yeah, pretty weird this problem, until you see the simple reason for it:

Somewhere on your LAN there is a device with a DHCP server running.

Simple test: disconnect all other ethernet wires from your wifi router and try again. Problem disappears.

 So it happens like this: once you authenticate on your wireless network, you are also on your LAN. There is then another device, either another router or another server or PC connected to it with a DHCP server running. You would *think* your wifi router would "get to" your pc first and assign the DHCP lease, but maybe it was busy with other traffic for a millisecond and the other DHCP server responded to the broadcast packet for DHCP. So it assigns the address it knows which may or may not be different than your own router.

The most common reason is someone is using a router as a switch. They are plugging a cable from your router into a LAN port on their router to "share" it with a few more PCs. This will work, but the downside is that DHCP is usually enabled on the LAN ports of a router by default so it messes up all other PCs on that network. What that person *should* do is connect your network wire into their WAN port. That way, you act as their "Internet Provider" and their network is private from your network and your LAN never "sees" their DHCP server.