192.168.0.99 is not a valid IP address

[WelshGasman]

Hi all,

Trying to add my first rule on my Hub 4.
I am trying to redirect traffic to a device in my network 192.168.0.99

In doing so, it tells me it is an invalid address? and so I cannot add the rule?

Why would it think this?

[Client62]

Does the Hub 4 first require 192.168.0.99 to be a Reserved IP ( so as to avoid a DHCP clash ) ?

[WelshGasman]

My DHCP starts at 130, as I have various devices on addresses below that.
Not occupying all of them, but a good buffer.

[legacy1]

Don't use hub in router mode go get a better router with 1Gb port put hub in modem mode

[WelshGasman]

Well until I go this hub, that is what I always did.
However with this hub I have 5G and the speeds are so much better, so I switched all my devices over to 0.x

So I would like to keep this in router mode, if at all possible.
Whilst my smart devices do not use 5G, this laptop does at around 175Mb/s

[legacy1]

Then it's not a bug it's a feature PC outside DHCP don't allow port forwarding to

[Roger_Gooner]

I believe the default DHCP reservation range is 192.168.0.10 to 192.168.0.245. What have you changed it to?

[WelshGasman]

Starts at 130 for 125 spots

[WelshGasman]

---

@legacy1 wrote:

Then it's not a bug it's a feature PC outside DHCP don't allow port forwarding to

---

Where is the logic in that.?
If anything, you would want to forward to a device with a known address that is the same all the time.
If that address changes, the forwarding fails?

[Roger_Gooner]

Why haven't you fixed the IP addresses of your devices within the DHCP reservation range - if they even need to be fixed at all. That way there wouldn't be any clashes for dynamically assigned addresses.

BTW I don't like an address ending in 255 being in the DHCP reservation range or as a static IP, make it 254.