-
There should definitely only be one DHCP server in the setup.
I think what I would do in this situation is as follows..
Set available addresses in the router to 1.2 to 1.10 or thereabouts.
Switch off DHCP server in the modem.
Set TCP/IP address in the modem to 192.168.1.100 or something similar. Needs to be in the same range as the router but outside of the available address pool.
But please wait for other opinions before testing this. I'm far from being a network guru myself..Posted 3 years ago # -
moosepucky wrote:Thanks for putting all of this 'geek-greek" in to real words
Here again, these are default. Should I restrict/limit the ending IP address (change it from 254 to 6 or the # of devices I will have in the network) or will it not matter if I disable the router as a DHCP server?
Figure out how many devices you expect to have on your network and set your IP address to that range: Start 192.168.1.10 Stop 192.168.1.20 will give you 10 IP addresses to dish out as needed.
Why start at .10? Because this way you can manually assign .2 through .9 to static IPs. You would assign a static IP to devices such as DVRs, NAS, printers, etc....
All other devices attached to the router are now set to get their IP address dynamicly....
Good. Makes life easy.
Questions:
It seems every device is set to be a DHCP server? Should only the modem or router do this or should no device do this if I use all static IP addresses (i.e. disable DHCP in all devices)? If you use only static IP addresses, set your router and modem to not act as a DHCP server. Although, I would recommend setting aside two or three addresses (as above) to handle the odd visitor.
My understanding is that the router will be xxx.xxx.1.1 and I need to assign all of the other attached devices starting at xxx.xxx.1.2 and forward? Yep. You can start assigning from any number though: .1.20 or .1.142 or .1.253. Don't use .255 though. Its reserved.
All devices use the same subnet mask? Yes. If you want to make life easy for yourself. If you want to make life horribly difficult for yourself, you can set your subnet mask to something like 255.255.255.255 and then your computer will only be able to see itself. Life would start to sound like a very long and loud sucking noise at that point.
All devices should use the DSL modem IP as the gateway? A better bet would be the router's address of 192.168.1.1.
I found this interesting article on DNS servers:
http://vpncasestudy.com/download/usefuldoc/dns_tips.pdf
It is interesting and I was wondering if this was something that I should do and where to do it?
There's not much need to play with DNS server settings at this point unless you only want to enable it and establish that IP address in each device.
Outside of creating a unique workgroup name and making sure that everyone uses that same name I have done nothing (well every time I try to do something it gets real quiet and very dark around here)....Posted 3 years ago # -
Well I managed to close down my home network for several hours.
After resetting all of the hardware via their little buttons on the back I am back again.
Looks like my issue is with the gateway. When I select obtain everything works but when I try to feed an IP address and gateway everything shuts downMesses made. Jobs left undone. FREE estimates.Posted 3 years ago # -
moosepucky wrote:Thanks for putting all of this 'geek-greek" in to real words

Before I get myself permanently off line by diddling around I want to make sure I understand each of the hardware's settings...
I'll start off by listing the settings then ask the questions at the end.
DSL modem (LAN settings):
This are the current settings
http://www.turtle-web.com/misc/dsl-lan.gif
I do not believe that I have made any changes from the default settings.
The DHCP options are "Server" "None" "Relay"
There is no assigned primary or secondary DNS server.
Set the DHCP option to "None". As David says, you should only have one DHCP server on your network, and the modem will get its address from the ISP. The "normal" situation is to use the router as the LAN's DHCP server.moosepucky wrote:
Router settings (Netgear max wireless... which I still have not gotten to work as a wireless router but that is for another time
)
http://www.turtle-web.com/misc/router-lan.gif
Here again, these are default. Should I restrict/limit the ending IP address (change it from 254 to 6 or the # of devices I will have in the network) or will it not matter if I disable the router as a DHCP server?
Leave the router as the DHCP server. As I said above, the modem will receive its settings from the ISP, and the DHCP protocol doesn't go from the router through the WAN port anyway; I'm not even sure it'll go the other way, anyway. The DHCP range should be large enough to accommodate all the computers and other network devices you'll connect to the router. It should also leave enough addresses for the fixed IP devices you intend to connect. Alternatively, you can use the "address reservation" system to allocate fixed IP addresses through the DHCP mechanism (that's generally what I do, except for servers and of course for DHCP-incapable devices).moosepucky wrote:
All other devices attached to the router are now set to get their IP address dynamicly....
Questions:
It seems every device is set to be a DHCP server? Should only the modem or router do this or should no device do this if I use all static IP addresses (i.e. disable DHCP in all devices)?
See abovemoosepucky wrote:My understanding is that the router will be xxx.xxx.1.1 and I need to assign all of the other attached devices starting at xxx.xxx.1.2 and forward?
All devices use the same subnet mask?
Yes, and yesmoosepucky wrote:
All devices should use the DSL modem IP as the gateway?
No, use the router's IP. None of your LAN devices are going to see the modem, as they're all connected to the router, whose main purpose is to isolate the LAN from the outside world.moosepucky wrote:"If those who say bad things about me knew what I think of them, they'd say even worse." (Sacha Guitry)
------------------------------------------------
"Earth is the cradle of mankind. Nobody can live in the cradle forever" (Constantin Tsiolkovski)Posted 3 years ago # -
I am obviously missing some important part of the puzzle here...... The light bulb has not gone "click" yet
This is what my router and this machine's settings look like and once I click OK everything goes dark
When I select obtain IP it gets assigned xx.xxx.x.12 and everything comes back online
Are there another DHCP servers that I need to turn off besides the one in the modem?Posted 3 years ago # -
Pierre wrote:
Alternatively, you can use the "address reservation" system to allocate fixed IP addresses through the DHCP mechanism (that's generally what I do, except for servers and of course for DHCP-incapable devices).
So... I can keep all computers set to obtain IP and reserver an IP for that machine within the router DHCP section?
This seems to be a lot simpler than what I am trying to do.
Reserving an IP via the router DHCP will make sure that device will always be at that IP so I can count on that IP to always be a specific machine or device?Posted 3 years ago # -
moosepucky wrote:So... I can keep all computers set to obtain IP and reserver an IP for that machine within the router DHCP section?
This seems to be a lot simpler than what I am trying to do.
Reserving an IP via the router DHCP will make sure that device will always be at that IP so I can count on that IP to always be a specific machine or device?
That is correct. The "reservation" associates a given MAC address with a specific IP, and also makes sure that no other network device gets the reserved address when the reserved MAC isn't connected, unless all other addresses are exhausted, which is quite unlikely with a range of 253 possible addresses. In addition, a DHCP server has a "time to live" (TTL) parameter, so that any given MAC address will receive the same IP if it reconnects within that time again unless all other addresses are exhausted. On consumer routers that TTL is generally 48 hours to a week, non-configurable. On corporate routers the TTL is usually configurable, and the routing table can be flushed.
Edit: the MAC address is the "physical" address of the network card, manufacturer-assigned and guaranteed to be unique.Posted 3 years ago # -
Just a thought, given what I've seen so far..
where is the system getting DNS addresses?Posted 3 years ago # -
Pierre wrote:Edit: the MAC address is the "physical" address of the network card, manufacturer-assigned and guaranteed to be unique.
..but from what I've read, easily spoofed by the properly-equipped hacker.Posted 3 years ago # -
Billy wrote:..but from what I've read, easily spoofed by the properly-equipped hacker.
no worries. they're all out on scooters with aerials on their heads..
..somewhere else.Posted 3 years ago # -
Well that was fun. Another couple hours off line and all reset back to default again.
For some reason when I start making changes I have to default the dsl modem before I get back online.
Last time I reset the DHCP back to start passing out IP address from 10 to 2. All dark until I reset the modem back to defaults then connected back online again.
I'll play around more tomorrow when I am fresher. Too late and too old to continue tonightPosted 3 years ago # -
Billy wrote:..but from what I've read, easily spoofed by the properly-equipped hacker.
True, but first they have to be able to read it. If you're connecting with WPA2 encryption, there isn't yet a computer that can decrypt it fast enough to be dangerous, even the NSA's. And of course this only applies to wireless connections. In order to break into a wired network, you'd need physical access to the wire, and the risk is too much for the average road warrior. They'd only do this if they know the data they can steal (or the damage they can cause) is worth a jail sentence. That's a job for the IM force (the original one, not the one from the movies
)Posted 3 years ago # -
Since he is using a dsl modem/router, why not use the lan port on the wireless router to the dsl modem? You can still assign static ip's etc to the lan.
As I recall (and it's been awhile) that works.
I have dsl at the office, and am using the WAN port. All I had to do was wire connect one computer the dsl modem/router and get internet. Shut everything off, remove the computer and put in the wireless router using the WAN port, connect that computer to the LAN on the wireless, pop in the software for my router, added my username, password, static ip, and clone the MAC of that computer, everthing worked fine from there.
Don't recall shutting off DHCP on the dsl modem/router. Perhaps that was it's default. That is also BellSouth business internet. I actually have English speaking techs who know what they are doing and answer the phone. Ah, just remembered, I had to call them and do the setup with them when we did this.Politicians and diapers have one thing in common. They both should be changed regularly and for the same reason.Posted 3 years ago # -
Looks like it may take a bit for the IP addresses to get released so that the ones I reserved for each machine will be assigned. If over the next few days this does not work I will be back trying to set static IP addresses for these 5 machines.
Recapping:
All machines are set to obtain an IP (dynamic not static)
The router is set to be the DHCP server
reserved 5 IP addresses in the router DHCP for the 5 machines connected to the network
The modem has DHCP server disabled
Looking at the modem settings I find that filters can be applied. Any of these useful (or harmful)? Should any be set?
I've gone back in and once again disabled the DHCP server in the modem
It seems that this setting is the one that has been causing all the problems. If I make any changes to any other device as far as IP addressing I lose the modem and internet connection. I have to reset the modem (hard reset back to default settings) before I can get back on line.
Latest.....
Yep... turning off DHCP in the modem is a solid guarantee of it disappearing.
Powered down the computers and router to try to get the IP addresses that were assigned released so that the ones I reserved would be assigned and .....pow..... modem completely disappeared. Could not access it via its IP to log in. Had to hard reset again.
I think this has been the issue all along. For some reason the modem "thinks" it needs to be a DHCP server also.
DSL modem is a ZyXEL 660.
When I rebooted the router it forgot all of the assigned IP addresses I set up.... Is this normal/typical?[/hr][/hr][/hr]Posted 3 years ago # -
moosepucky wrote:Looking at the modem settings I find that filters can be applied. Any of these useful (or harmful)? Should any be set? http://www.turtle-web.com/misc/modem-filters.gif
The only filter that could usefully be enabled is the ping one, but you will also lose the ability to ping addresses.moosepucky wrote:When I rebooted the router it forgot all of the assigned IP addresses I set up.... Is this normal/typical?
Definitely not. Only a reset should be able to remove these assignments. You did commit the changes before logging out of the router's setup, didn't you?Posted 3 years ago #

