What's new

YazFi Ping dualband device on YazFi

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Tom Jo-Jo Junior Shabadoo

Occasional Visitor
Hello,

I recently installed YazFi hoping to avoid any trouble with all the cheap Chinese devices by isolating most on a dedicated IoT network.

I want to get a notification if any of my IP cameras becomes unresponsive and can successfully assign a dedicated IP following the below from the documentation. All good.
Code:
pc_append "dhcp-host=[MAC ADDRESS],[DESIRED HOSTNAME],[DESIRED IP ADDRESS]" $CONFIG

Now the problem is devices that are dual band, and roam freely between the 2,4/5GHz nets (who both have the same SSID). It would not be possible to reserve an IP for them. So I thought, OK I will just assign a hostname using
Code:
pc_append "dhcp-host=00:11:22:33:44:55,Cam5" $CONFIG

The camera is successfully assigned a host name, and I can initially ping it on Cam5.lan - however after a while it changes to the other band, but does not update it's IP address, maintaining 192.168.3.x when it should switch to 192.168.6.x - and at this time not available to ping or view any longer.

Am I doing something wrong here, or is it down to a limitation of YazFi or the (Reolink) camera ?
The most obvious solution would be to turn off the 5GHz network, but I would prefer not to.

/Tom
 
I don't use YazFi but if I remember correctly it creates separate interfaces for each guest network? In which case you need to specify the interface name in your dhcp-host lines.
 
I don't use YazFi but if I remember correctly it creates separate interfaces for each guest network? In which case you need to specify the interface name in your dhcp-host lines.
Yes it's correct, in this case YazFi creates subnet 192.168.3.0/24 for 2.4GHz and 192.168.6.0/24 for 5GHz.
Reading the dnsmasq documentation it says dhcp-host can have several ipadresses, but it is not clear to me how. So I would add interface wl0.2 or wl1.2 somewhere in below strings?
Code:
pc_append "dhcp-host=00:11:22:33:44:55,192.168.3.10,Cam5" $CONFIG
pc_append "dhcp-host=00:11:22:33:44:55,192.168.6.10,Cam5" $CONFIG
 
My first guess would be something like this:
Code:
dhcp-host=wl0.2,00:11:22:33:44:55,192.168.3.10,Cam5
dhcp-host=wl1.2,00:11:22:33:44:55,192.168.6.10,Cam5
 
If you post the complete contents of /etc/dnsmasq.conf I might have a better idea.
Sure, there is a lot

Code:
pid-file=/var/run/dnsmasq.pid
user=nobody
bind-dynamic
interface=br0
interface=pptp*
no-dhcp-interface=pptp*
no-resolv
servers-file=/tmp/resolv.dnsmasq
no-poll
no-negcache
cache-size=1500
min-port=4096
domain=lan
expand-hosts
bogus-priv
domain-needed
local=/lan/
dhcp-range=lan,192.168.1.33,192.168.1.62,255.255.255.0,86400s
dhcp-option=lan,3,192.168.1.1
dhcp-option=lan,15,lan
dhcp-option=lan,44,192.168.1.1
dhcp-option=lan,252,"\n"
dhcp-authoritative
interface=br1
dhcp-range=br1,192.168.101.2,192.168.101.254,255.255.255.0,86400s
dhcp-option=br1,3,192.168.101.1
interface=br2
dhcp-range=br2,192.168.102.2,192.168.102.254,255.255.255.0,86400s
dhcp-option=br2,3,192.168.102.1
dhcp-host=00:CD:FE:EB:40:47,set:00:CD:FE:EB:40:47,iPhone-6S,192.168.1.250
dhcp-host=E4:2B:34:DE:36:76,set:E4:2B:34:DE:36:76,iPad-6,192.168.1.251
dhcp-host=D0:F8:8C:7A:DC:C2,set:D0:F8:8C:7A:DC:C2,LenovoTab,192.168.1.252
address=/use-application-dns.net/
address=/_dns.resolver.arpa/
dhcp-name-match=set:wpad-ignore,wpad
dhcp-ignore-names=tag:wpad-ignore
dhcp-script=/sbin/dhcpc_lease
script-arp
edns-packet-max=1280
dhcp-option=42,193.147.107.33,130.206.3.166,150.214.94.5
dhcp-option=66,"192.168.1.5"
server=/a.files.bbci.co.uk/212.71.249.225
server=/as-hls-uk-live.akamaized.net/212.71.249.225
dhcp-host=64:90:C1:77:74:9B,192.168.3.2,XiaomiGateway3
dhcp-host=60:01:94:8E:79:E1,192.168.3.3,SonoffRFBridge
dhcp-host=wl0.2,9C:95:61:4E:F1:20,192.168.3.10,Reolink-E1-Zoom
dhcp-host=wl1.2,9C:95:61:4E:F1:20,192.168.6.10,Reolink-E1-Zoom

### Start of script-generated configuration for interface wl0.1 ###
interface=wl0.1
dhcp-range=wl0.1,192.168.2.2,192.168.2.254,255.255.255.0,86400s
dhcp-option=wl0.1,3,192.168.2.1
dhcp-option=wl0.1,6,192.168.2.1,192.168.2.1
dhcp-option=wl0.1,44,192.168.1.1
### End of script-generated configuration for interface wl0.1 ###

### Start of script-generated configuration for interface wl1.1 ###
interface=wl1.1
dhcp-range=wl1.1,192.168.5.2,192.168.5.254,255.255.255.0,86400s
dhcp-option=wl1.1,3,192.168.5.1
dhcp-option=wl1.1,6,192.168.5.1,192.168.5.1
dhcp-option=wl1.1,44,192.168.1.1
### End of script-generated configuration for interface wl1.1 ###



### Start of script-generated configuration for interface wl1.2 ###
interface=wl1.2
dhcp-range=wl1.2,192.168.6.50,192.168.6.254,255.255.255.0,86400s
dhcp-option=wl1.2,3,192.168.6.1
dhcp-option=wl1.2,6,192.168.6.1,192.168.6.1
dhcp-option=wl1.2,44,192.168.1.1
### End of script-generated configuration for interface wl1.2 ###

### Start of script-generated configuration for interface wl0.2 ###
interface=wl0.2
dhcp-range=wl0.2,192.168.3.50,192.168.3.254,255.255.255.0,86400s
dhcp-option=wl0.2,3,192.168.3.1
dhcp-option=wl0.2,6,192.168.3.1,192.168.3.1
dhcp-option=wl0.2,44,192.168.1.1
### End of script-generated configuration for interface wl0.2 ###
 
Last edited:
Well I'm out of ideas. I manually reconfigured my router as near as I could to your setup and those two dhcp-host statements worked as intended for me. I'm not using YazFi so it's not necessarily a valid test but it's the best I can do. Maybe @Jack Yaz or some other YazFi user can chime in.
 
Now the problem is devices that are dual band, and roam freely between the 2,4/5GHz nets (who both have the same SSID).

however after a while it changes to the other band
Doesn't sound like a problem with YazFi rather a problem with how you have initially setup your Guest Networks and have initially setup the IoT devices. Some questions. Why are you using the same SSID for both the 2.4GHz and 5GHz Guest Networks? Why not use different SSID names? Are both WiFi guest networks encrypted or open? If encrypted, are you using different passwords for each WiFi Guest Network? If not, why not?

Generally if you use different network SSID's and different passwords, then configure the IoT devices for only one of the networks, they cannot join the other network due to it having a different SSID name and password. Assuming you are not connecting them to both networks for some reason during setup causing the SSID/password for both networks to be saved by the IoT device.
 
Doesn't sound like a problem with YazFi rather a problem with how you have initially setup your Guest Networks and have initially setup the IoT devices. Some questions. Why are you using the same SSID for both the 2.4GHz and 5GHz Guest Networks? Why not use different SSID names? Are both WiFi guest networks encrypted or open? If encrypted, are you using different passwords for each WiFi Guest Network? If not, why not?

Generally if you use different network SSID's and different passwords, then configure the IoT devices for only one of the networks, they cannot join the other network due to it having a different SSID name and password. Assuming you are not connecting them to both networks for some reason during setup causing the SSID/password for both networks to be saved by the IoT device.
Both networks use the same SSID and password (and I would have preferred the same subnet, but it is not possible). The reason being the devices should select the best network within their capabilities. They may be moved around manually or move autonomous (i.e vacuum cleaner).
 
It seems different devices handles this setup differently.
Motorola Edge 30 phone uses the assigned host name and changes between the nets without issues updating the IP address accordingly.
Iphone 6S clings to the 5Ghz net, even when at the edge of coverage with RSSI -83 dBm, and will not change to 2.4Ghz.
The IP camera changes between the nets, but keeps the IP address it initially obtained.
 
Unfortunately it keeps hold of the 192.168.3.10 address even though it changes to the 5GHz network and should use an 192.168.6.0/24 address.
The IP camera changes between the nets, but keeps the IP address it initially obtained.
Where are you getting the information or data points from that led you to conclude that the above scenario is actually happening?

I'm asking because it doesn't make sense given the info that you have provided: the 2.4 GHz Guest Network #2 (GN2) is on a different IP subnet range (192.168.3.0/24) *and* a separate interface (wl0.2) from the ones associated with the 5 GHz GN2 (192.168.6.0/24 on wl1.2).

IOW, it's virtually impossible for a device to actually change/move to a different wireless band/interface and yet *keep* the previous IP address allocated from a different band/interface.

IMO, it's more likely that you're seeing false/wrong information either from the device itself or from somewhere in the router, which makes it *appear* as if the camera has switched to a different wireless band when in fact that's not the case at all. Perhaps the device tried to switch bands but failed, and the info you're getting is from that unsuccessful attempt.

If you can capture & share the information used perhaps we can have a better idea of what's going on.

My 2 cents.
 

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top