• Date
    Wuz314159
  • Date
  • Replies 3 replies
  • Subscribers 106 subscribers
  • Views 80 views
  • Users 0 members are here

Odd DHCP stuff

Had an issue with one of my gateways. I had it configured with a static IP.

When I go to use it this week, it had a Dynamic IP nowhere near our IP range. (10.101.*.*)

Subnet on the console is 255.0.0.0, so it should not have been able to communicate with the gateway, but the gateway was sending DMX through the proper universes. I could not access the gateway via Concert.

After an hour of troubleshooting, I gave up and grabbed a new switch & hooked that up between console (DHCP server) gateway & laptop. Everything worked & I could reset it.

It seems as if there was another DHCP server on my house network, but I can't physically find anything on the network I built. House switch is a TP Link TL-SL1218P POE.Unmanaged. and the Gateway worked.

Why else could this have happened?

Parents

  • 169.254.x.x is a Link-Local IP address.  The gateway falls back there in any of several DHCP server-less scenarios: it boots without a cached IP; it is reset to defaults; the lease for its existing IP expires. 

    No need to look for another server. Link-Local is a funky thing where devices pick a random IP on the range, check to make sure no one else is using it, and then just take it as their own.

Reply

  • 169.254.x.x is a Link-Local IP address.  The gateway falls back there in any of several DHCP server-less scenarios: it boots without a cached IP; it is reset to defaults; the lease for its existing IP expires. 

    No need to look for another server. Link-Local is a funky thing where devices pick a random IP on the range, check to make sure no one else is using it, and then just take it as their own.

Children
No Data
Related

www.etcconnect.com