Reboot of VPN300 with group WILDCARD FQDN (Videos) not applying for BWM.

PeterUK

Reboot of VPN300 with group WILDCARD FQDN (Videos) like *nflxvideo.net and *googlevideo.com  not applying for BWM.

VPN300 with V5.02(ABFC.0) 

BWM rule

incoming DMZ

outgoing WAN

Destination Videos

Guaranteed Bandwidth

inbound 51200kbps priority 1

maximize bandwidth usage checked

outbound 3200kbps priority 1

maximize bandwidth usage checked

Test conditions 

Free Download Manager 5

https://www.freedownloadmanager.org/

running 

ubuntu-21.04-desktop-amd64.iso.torrent   

https://ubuntu.com/download/alternative-downloads#bittorrents

Then run a 4K video from YouTube pickup by FQDN *googlevideo.com

https://www.youtube.com/watch?v=G1hKzCkywM8&t=486s

and it buffers

workaround

Change BWM rule above for Destination to a single FQDN ok then change back to group (videos)

no buffering when running bittorrent and 4K video. 

Zyxel_Stanley

Hi @PeterUK
I will send private message to you for further check in this case.

Zyxel_Stanley

Hi @PeterUK  

The Wildcard FQDN will cache DNS query those pass through by ZyWALL, and save it in system cache.

Before Wildcard FQDN up to date IP address, it is unable to apply BWM setting in system.

You can have a check if IP list has renewed in cache list after reboot. (Monitor > system status > FQDN Object)

Or try to flush DNS cache on your PC and re-connect video again.

PeterUK

Thats not the problem I have to BWM rule above then reboot the VPN300 when booted go to watch a 4K video with bittorrent running DNS is done the IP of the steam is listed in Monitor > system status > FQDN Object but the BWM rule is not applying. That why I have to do the workaround as above.

Zyxel_Stanley

Hi @PeterUK  

Can you left only WILDCARD FQDN object in BMW rule, and double confirm if there is log entry after rebooting the device?

PeterUK

Not sure what your asking me to do?

I do see on a reboot with the group  FQDN

The BWM rule 2 will not take effect, due to /destination/ group object are empty.

Which is normal because DNS has not happened   

I did some more tests with rebooting with a group Destination FQDN for BWM and there is a problem. I then used a single FQDN not in a group *googlevideo.com and rebooted and the BWM rule worked fine so the problem is if you do a group of FQDN for BWM on a reboot.

Zyxel_Stanley

Hi @PeterUK
I will send private message to you for further check in this case.

Zyxel_Stanley

This issue is because BWM function did not renew IP address automatically, so caused BWM rule did not work. It will fix in FCS firmware in the future.

PeterUK

Broken again in  VPN300_5.30(ABFC.0)

PeterUK

Fix in 

V5.30(ABFC.0)ITS-22WK16-2022-05-19-220401321

Zyxel_Stanley

Hi @PeterUK
It's good know the new firmware resolved the symptom.The issue is a side effect from the other fix.
So it caused wildcard FQDN doesn't work in BWM rule. Whatever, the solution will fixed in next formal release.