D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-868L => Topic started by: theholmboy on November 21, 2013, 01:07:30 PM
-
When I first got my router with Firmware v1.01, under Network Settings, I was able to set the Router Address to 192.168.1.1 with subnet mask to 255.255.0.0 (My bro-in-law and I have joined networks). I updated to Firmware v1.02 and it kept the settings, but in doing some configuration changes as part of some troubleshooting, I temporarily set the subnet mask to 255.255.255.0 and when I tried to set it back to 255.255.0.0, I kept getting the error "The network id of LAN-1 is the same with LAN-2." =(
I searched this error online and found that this was an issue with a previous D-Link router, which was fixed with a Firmware update. I found the v1.04 firmware and updated to it, but the issue remained, even with it set back to factory defaults. At that point, I disconnected the device from the network with a single cable going directly to the laptop I am operating from. I then reset the device back to factory defaults and then downgraded to Firmware 1.00. With router settings completely empty and not connected to the network, I again attempted 192.168.1.1 - 255.255.0.0 with the same error. I progressively moved through firmwares v1.01 & v1.02, each time doing the same thing. At one point, I tried 10.0.0.1 - 255.255.0.0 and it allowed it. I basically found through trial-and-error that it will not allow me to use any 192.168.x.x address with subnet 255.255.0.0. (I also emailed D-Link about this problem, who asked me to call their support and I also called, spending "an hour of futility" trying things I had already tried). A fix for this in the next firmware update would be much appreciated.
Thanks! RHH
-
Link>Welcome! (http://forums.dlink.com/index.php?topic=41537.0)
- What region are you located?
Internet Service Provider and Modem Configurations
- What ISP Service do you have? Cable or DSL?
- What ISP Modem Mfr. and model # do you have?
Does your ISP modem have a built in router by chance?
Ensure that the Routers IP address does differ from the LAN side IP address pool. If your using 192.168.0.1 on the LAN side, the routers IP address should not be the same. Using 192.168.1.1 should be ok. However the SNM should be 255.255.255.0 for this class IP pool.
What happens if you and your brother use the same .255.0 SNM instead of .0.0?
Check out a SNM Calculator for valid IPs and Classes:
http://www.subnet-calculator.com/cidr.php (http://www.subnet-calculator.com/cidr.php)
I don't believe network standards may allow for using that kind of subnet mask with a Class C IP address pool. Most SNM I see for this Class is 255.255.255.0, .192, .224, .240, .248, or .252. This may have been a bug originally that allowed you to use .0.0 and was fixed in later code and is now not allowed due to D-Link following Networking standards. You'll need to contact D-Link support and ask for level 2 or higher support and find out if this is the case.
Let us know what you find out.
When I first got my router with Firmware v1.01, under Network Settings, I was able to set the Router Address to 192.168.1.1 with subnet mask to 255.255.0.0 (My bro-in-law and I have joined networks). I updated to Firmware v1.02 and it kept the settings, but in doing some configuration changes as part of some troubleshooting, I temporarily set the subnet mask to 255.255.255.0 and when I tried to set it back to 255.255.0.0, I kept getting the error "The network id of LAN-1 is the same with LAN-2." =(
I searched this error online and found that this was an issue with a previous D-Link router, which was fixed with a Firmware update. Knowing this, I disconnected the device from the network with a single cable going directly to the laptop I am operating from. I then reset the device back to factory defaults and then downgraded to Firmware 1.00. With router settings completely empty and not connected to the network, I again attempted 192.168.1.1 - 255.255.0.0 with the same error. I progressively moved through firmwares v1.01 & v1.02, each time doing the same thing. At one point, I tried 10.0.0.1 - 255.255.0.0 and it allowed it. I basically found through trial-and-error that it will not allow me to use any 192.168.x.x address with subnet 255.255.0.0. (I also emailed D-Link about this problem, who asked me to call their support and I also called, spending "an hour of futility" trying things I had already tried). A fix for this in the next firmware update would be much appreciated.
Thanks! RHH
-
Any status on this ???