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?
Does the Hub 4 first require 192.168.0.99 to be a Reserved IP ( so as to avoid a DHCP clash ) ?
My DHCP starts at 130, as I have various devices on addresses below that.
Not occupying all of them, but a good buffer.
I believe the default DHCP reservation range is 192.168.0.10 to 192.168.0.245. What have you changed it to?
Don't use hub in router mode go get a better router with 1Gb port put hub in modem mode
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
Then it's not a bug it's a feature PC outside DHCP don't allow port forwarding to
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?
So you buy a better router?
Lets see the logic...yes lets say two people work on the firmware for the hubs one say you know what would be cool! if a device has a IP that can't have ports forwarded to it, second person goes yes if the IP is out side the DHCP range we can do that other goes hmm do you see any problems in doing that...not that I can think of...
Starts at 130 for 125 spots
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.
For devices that don't support DHCP static IPs are the only option.
That is true, but for most punters which devices enable you to set a static IP address? I can set one for my NAS but practically all my other devices have no means of permitting this. So, in most cases a fixed IP address within the DHCP reservation range is the only option, which I do for my NAS as my media player needs that IP address to stream my videos.
really its nothing to do with VM, EVERY time you add a device that your router identifies as new and it increments the last digits by 1 i've only hit 42 since 2009
so if you've not use/reached 99 it wont find it
OK, I just quickly created a rule on address 132, which is in the DHCP range and it accepted it.
So any forwarding has to be with the DHCP pool. 🙄
Three attempts to edit before I can, on this site?
A better error message would have helped.
another try at posting
the 99 suffix is way out of range for the normal course of events
routers assign the last two digits incrementally, new device registered = current +1
i've only reached the 40's since 2009
Hi Gasman greeting from Torchwood @ sevenforums
Not really. I have my NVR on 120.
My NAS boxes are 101 and 102.
