- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
DHCP assignment

- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
DHCP assignment
I have a couple of devices that connect with a static IP outside of the DHCP range of my LAX20. Problem is, any time I try to connect a device after this static device connects, DHCP assigns a dynamic device with an invalid IP in-line with the static address. The dynamically assigned device cannot access the internet, etc. and when I try to "Renew DHCP Lease," it will correct it initially, but then switch back the faulty address. Perhaps a fix and firmware update is required? Or is there something I can do to keep this static IP from messing up the DHCP server. Removing it is not an option. As of now, shutting down and rebooting the static device is the fix, but it's rather unelegant.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: DHCP assignment
> I have a couple of devices that connect with a static IP outside of
> the DHCP range of my LAX20. [...]
It might be easire to make sense of this if you revealed some actual
addresses. What, exactly, is "the DHCP range of my LAX20"? What are
these "static IP [addresses]"? What's the LAN IP address of the LAX20?
Do you mean really "static", as in configured on the device itself,
and not reserved-dynamic (configured on the DHCP server on the router)?
> [...] any time I try to connect a device after this static device
> connects, DHCP assigns a dynamic device with an invalid IP in-line with
> the static address.
Again, actual addresses?
> [...] Perhaps a fix and firmware update is required? [...]
"update" from _what_?

- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: DHCP assignment
My LAX20 is Firmware Version V1.1.4.20_2.0.45.
My address range the router assignes is from 192.168.0.1 to 192.168.0.254.
I have two devices that with fixed addresses (static IPs) of 10.3.100.211 and 10.26.74.234. These addresses are indeed static within each device and cannot be changed. They are designed to be able to "talk" to each other when they are direct connected together or to "find" each other on a network as they work specifically together via ethernet.
The problem is, when either of these devices are powered on and take their static IP addresses in the router, any device that connects to the router AFTER doesn't get assigned an IP address in the range of 192168.0.1 to 192.168.0.254. Currently, I have one such device attached and it is receiving a dynamically served address of 10.22.0.57 from the router. All LAN services are available to the device, but WAN services don't appear to be. For example, it cannot connect to the internet through a web browser: the browser displays "server not available". Email also doesn't work.
Turning OFF the devices with staticIPs solves the problem and the router sorts everything out, fixing the 10.22.0.57 to an address within the range of 192.168.0.1-254. I can then turn those devices back on and everything is fine. Until another device tries to connect, that is, in which case it needs to be cycled again.
My current work around is to create address reservations in the router for every dynamically addressed device. This way, the router is forced to give a predetermined address with in the DHCP IP range of 192.168.0.1 to 192.168.0.254. However, if an unknown device were to connect, I either have to create a new reservation for it, or power cycle the staticIP devices to sort it out. Neither of those solutions is very convenient.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: DHCP assignment
> My address range the router assignes is from 192.168.0.1 to
> 192.168.0.254.
That's the DHCP pool? ".2" - ".254" would make more sense if the
router itself is at ".1". Otherwise, that's plausible.
> I have two devices [...]
Not a very detailed description. Not detailed enough, either.
> [...] that with fixed addresses (static IPs) of 10.3.100.211 and
> 10.26.74.234. [...]
That would present a problem, if the LAX20 LAN is "192.168.0.*".
Also, the only way that a device at "10.3.a.b" could communicate with
a device at "10.26.c.d" would be if they're using a subnet like
"10.0.0.0/8", and I would expect your LAX20 to have trouble with
any subnet mask narrower than "/24".
> [...] These addresses are indeed static within each device and cannot
> be changed.
That's pretty hard to believe. I can't remember ever seeing a device
with permanent/unchangeable IP parameters. Of course, all I know about
your "these devices" is that they're apparently trouble-makers.
> [...] They are designed to be able to "talk" to each other when they
> are direct connected together or to "find" each other on a network as
> they work specifically together via ethernet.
Also not easy to believe, as stated.
> The problem is, when either of these devices are powered on and take
> their static IP addresses in the router, any device that connects to the
> router AFTER doesn't get assigned an IP address in the range of
> 192168.0.1 to 192.168.0.254. [...]
The simple explanation for that would be that at least one of your
(unspecified) "these devices" is running its own DHCP server, and your
"any device that connect" is getting its IP parameters from a DHCP
server other than the one in your LAX20. Running multiple,
uncoordinated DHCP servers on one LAN segment is an invitation to
disaster. And, apparently, someone accepted your invitation.
> [...] Currently, I have one such device attached and it is receiving a
> dynamically served address of 10.22.0.57 from the router. [...]
What leads you to believe that that address is coming "from the
router", and not from some other device? I'd bet that the LAX20 has
nothing to do with any "10.x.y.z" address.
> [...] All LAN services are available to the device, but WAN services
> don't appear to be. [...]
Of course not. The LAX20 (router section) would not communicate with
devices which have IP addresses off its LAN subnet ("192.168.0.0/24"),
even if they're using the same Ethernet segment.
> My current work around [...]
I wouldn't try to find a work-around. I'd try to configure my LAN
devices is some way which makes sense. That is, so that they all use
the same IP subnet.
> [...] Neither of those solutions is very convenient.
I wouldn't call either of them a "solution".
If your (unspecified) "these devices" are really as anti-social as
you claim, then I'd look into building them their own, separate Ethernet
network, and keeping them as far away as possible from the LAX20 LAN.
Conceivably, some VLAN tagging scheme could be employed (with more
exotic network-switch/router devices), which might provide the required
logical isolation without requiring physical isolation, but arranging
that would exceed my expertise.
In principle, the LAX20 could be configured to use "10.0.0.0/8" for
its LAN, but you'd still need to deal with the apparent (but obscure)
DHCP server which, I claim, must be running someplace (else). And, as
cautioned above, I would not expect an LAX20 to work well with a "/8"
subnet mask.
If you expect your (unspecified) "these devices" to communicate with
devices on the LAX20 LAN, rather than ignore them, then I'd start by
looking for some actual information on your (unspecified) "these
devices", rather than what looks to me like the folklore ("fixed
addresses", "cannot be changed") upon which you currently seem to rely.

- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: DHCP assignment
> Do you work for Netgear?
No. Those who do tend to have a Netgear-logo icon by their names.
See, for example, the pinned topics at the head of the forum list. If
you want to contact Netgear support, then try:
Look! One of us is willing to answer a direct question (even when
it's not relevant). (Look for "?", above, if _you_ want to try it.)
• Introducing NETGEAR WiFi 7 Orbi 770 Series and Nighthawk RS300
• What is the difference between WiFi 6 and WiFi 7?
• Yes! WiFi 7 is backwards compatible with other Wifi devices? Learn more