D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-826L => Topic started by: clee290 on August 05, 2015, 09:39:56 PM
-
Hi everyone,
So I'm trying to make my PC the main priority on the network for everything, basically. It's really just for gaming, but I'll just say it's for everything for the time being :P
Anyways, I followed, or did my best to follow, @FuzzyNutz's @FurryNutz's guide here (http://forums.dlink.com/index.php?topic=44869.0), but my QoS settings were a bit different than the screenshots in his guide.
One thing that I'm not sure about is the Remote IP range. I had entered 0.0.0.1 to 255.255.255.254 like in the guide, but when trying to save, I got an error saying that the first number had to be between 1 and 255. So I changed it to 1.0.0.1, but then an error saying the 4th number had to be between 1 and 254 even though I already had it at 1. Anyways, so I left it at 0.0.0.0 to 255.255.255.255 and I'm just wondering if this remote IP range should cover everything, essentially.
Here's a screenshot, if it helps:
(http://i.imgur.com/NZzyabe.png)
-
Link>Welcome! (http://forums.dlink.com/index.php?topic=48135.0)
- What Hardware version is your router? Look at sticker under the router case.
- Link>What Firmware (http://forums.dlink.com/index.php?topic=47512.0) version is currently loaded? Found on the routers web page under status.
- 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?
You need to set the priority to 50 instead of 1 or you'll starve the other devices for bandwidth.
Then create one more rule for OTHER DEVICE using same scenario. Accept give the range of IP addresses, from and to, and give a 128 priority. I recommend using 192.168.0.101 for your gaming PC then use .102 thru what ever the last IP address is used on the device list. That way you can keep the IP address sequence in order and not have conflicting problems with the rules in the Local IP address Range section.
The Remote IP address configuration is good.
-
Thank you for the response, I will check on the things you asked about in a little bit.
Are local IPs generally 100 and above (well, the 4th part - 192.168.0.100)? Could it not be under? I do see a device at 100, so I guess I should take that for my main PC, then set the IP range for others to 101 to whatever?
-
Depending on the default DHCP IP address pool, yes, usually starting at .100 thru .199 on D-Link routers. You can use and would be preferred to use .199 for your gaming PC or console and then use .100 thru .### for the Other Devices.
-
Alright thank you!
And for the other stuff you asked about:
Hardware version: A1
Firmware: 1.02
Region: Canada
ISP: Bell with DSL
Modem: Sagemcom 2864
-
I recommend bridging the ISP modem if it's not already:
- If the ISP modem has a built in router, it's best to bridge the modem. Having 2 routers on the same line can cause connection problems: Link>Double NAT (http://www.practicallynetworked.com/networking/fixing_double_nat.htm) and How NAT Works (http://computer.howstuffworks.com/nat.htm). Call the ISP and ask to see if the ISP modem can be bridged. To tell if the modem is bridged or not, look at the routers web page, Status/Device Info/Wan Section, if there is a 192.168.0.# address in the WAN IP address field, then the modem is not bridged. If the modem can't be bridged then see if the modem has a DMZ option and input the IP address the router gets from the modem and put that into the modems DMZ. Also check the routers DHCP IP address maybe conflicting with the ISP modems IP address of 192.168.0.1. Check to see if this is the same on the ISP modem, and if modem can't be bridged, change the DIR router to 192.168.1.1 or .0.254.
Example of a D-Link router configured for PPPoE with ISP Modem bridged: PPPoE Configuration on a Router (http://forums.dlink.com/index.php?topic=56344.msg219023#msg219023)
-
Alright, I will do a bit of research on how to get it into bridge mode. Thanks again for all the help!
-
YA, you'll need to do this to get QoS and NAT OPEN status to work right.
Keep us posted on how it goes...