Not possible to set static IPs in VLAN (network with different subnet)?

[vmachiel]

Hi,

So: when I setup a GNP, and have it on a different VLAN (52), can I not set static IPs for certain clients? When I go to the LAN setings and DHCP, I see my device in the client list. When I select it, I see its IP (192.168.52.101). But when I try to set it as static, it says it’s not valid…

Is it not possible? Or do I need a plugin or something?

 

[bennor]

See YazDHCP which now supports Guest Network Pro manual IP addresses when one has set Guest Network Pro's Use same subnet as main network to off:

https://www.snbforums.com/threads/y...of-dhcp-reservations.94827/page-4#post-971788

If not using YazDHCP, one could use the Guest Network Pro Profile's Advanced Setting section Manually assign IP address around the DHCP list option to set manual reservations.

Otherwise, use the forum search feature to find the various past discussions on using the dnsmasq-INDEX.conf.add or dnsmasq-sdn.postconf to set a Guest Network Pro's manual IP reservation. For example, one such past post on using dnsmasq-INDEX.conf.add to set Guest Network Pro reservations:
https://www.snbforums.com/threads/a...-4-is-now-available.94651/page-26#post-958305

It is expected behavior that when Guest Network Pro's Use same subnet as main network is disabled (set to off) one cannot normally (without using YazDHCP) set Guest Network Pro client reservations through the LAN > DHCP Server section.

 

[CaptainSTX]

Hi,

So: when I setup a GNP, and have it on a different VLAN (52), can I not set static IPs for certain clients? When I go to the LAN setings and DHCP, I see my device in the client list. When I select it, I see its IP (192.168.52.101). But when I try to set it as static, it says it’s not valid…

Is it not possible? Or do I need a plugin or something?

If you are running a router with Guest Network Pro you can assign static IPs within a subnet under advanced settings directly using the GUI.

 

[bbunge]

You do not set client static IP's at the router. You set reserved IP's. Static IP addresses are set at the client and the client disregards DHCP.
There is a difference!

 

[CaptainSTX]

You do not set client static IP's at the router. You set reserved IP's. Static IP addresses are set at the client and the client disregards DHCP.
There is a difference!

You are correct however to answer the OPs question succinctly it was simpler to answer their question as written and not provide an explanation and also correct their technical semantics.

 

[jksmurf]

See YazDHCP…

… Guest Network Pro Profile's Advanced Setting section Manually assign IP address around the DHCP list …

… using the dnsmasq-INDEX.conf.add or dnsmasq-sdn.postconf to set a Guest Network Pro's manual IP reservation. …

It is expected behavior that when Guest Network Pro's Use same subnet as main network is disabled (set to off) one cannot normally (without using YazDHCP) set Guest Network Pro client reservations through the LAN > DHCP Server section.

As usual @bennor has nailed all the options for manual assignments (as they are called in the Router’s DHCP menu), although I’d suggest the order (in terms of simplicity) would be:

1. GNP native Manual Assignments (input via GNP, Advanced Settings), noting these are limited to 32 and 32 is not guaranteed)
2. YazDHCP
3. WinSCP (or SSH) into your router and create the files mentioned in the format referred to by @bennor.

Whilst I was using method (3) for a while after coming up short with (1), my personal preference is now (2) YazDHCP due to numbers but also the ability to export, amend and import the manual assignments. Very neat.

On @bennor’s last point I am not sure this is absolutely correct as on one of my two independent systems I have reservations for the Main (Primary) Wi-Fi and a GNP Wi-Fi profile (same subnet as Primary) in the native LAN, DHCP, Manually Assigned IP list and I believe that the assignments work across both profiles. In my other network I use YazDHCP but there, the GNP Wi-Fi is on a different subnet.

Whilst I do use static DHCPs on my Shelly IoT devices (apologies to use up all the terminologies in one post…) and noting my IoT network is on the same subnet as the Main (Primary), in the extract below the Samsung Dryer (which does not have a static IP and thus a good example) has a manually assigned IP in the “Primary” manual assignments list under LAN, DHCP and seems to happily show up in the client list as using 192.168.47.110., as assigned.

At the risk of veering away from the OPs query, I’d be curious to understand under what conditions this does not work.