What's new

YazFi YazFi - enhanced AsusWRT-Merlin Guest WiFi inc. SSID <-> VPN Client

  • 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!

All I'm trying to run is a Guest Wireless 2G connection of the RT-AX88U Router, no VPN, very basic. Here is what my system log continues to spam until I disable the guest wireless: PART 1 of 2 for CODE

Code:
Feb  7 13:18:33 rc_service: cfg_server 1318:notify_rc restart_wireless;restart_qos;restart_firewall;
Feb  7 13:18:33 custom_script: Running /jffs/scripts/service-event (args: restart wireless) - max timeout = 120s
Feb  7 13:18:34 YazFi: Wireless restarted - sleeping 30s before running YazFi
Feb  7 13:18:35 kernel: br0: port 6(eth6) entered STP off state
Feb  7 13:18:35 kernel: device eth6 left promiscuous mode
Feb  7 13:18:35 kernel: br0: port 6(eth6) entered STP off state
Feb  7 13:18:35 kernel: br0: port 7(eth7) entered STP off state
Feb  7 13:18:35 kernel: device eth7 left promiscuous mode
Feb  7 13:18:35 kernel: br0: port 7(eth7) entered STP off state
Feb  7 13:18:35 kernel: ubi1: attaching mtd9
Feb  7 13:18:35 kernel: ubi1: scanning is finished
Feb  7 13:18:35 kernel: ubi1: attached mtd9 (name "misc1", size 8 MiB)
Feb  7 13:18:35 kernel: ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
Feb  7 13:18:35 kernel: ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
Feb  7 13:18:35 kernel: ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096
Feb  7 13:18:35 kernel: ubi1: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
Feb  7 13:18:35 kernel: ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
Feb  7 13:18:35 kernel: ubi1: max/mean erase counter: 58/30, WL threshold: 4096, image sequence number: 1862459137
Feb  7 13:18:35 kernel: ubi1: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 4
Feb  7 13:18:35 kernel: ubi1: background thread "ubi_bgt1d" started, PID 9518
Feb  7 13:18:36 kernel: UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 9535
Feb  7 13:18:36 kernel: UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "nvram"
Feb  7 13:18:36 kernel: UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
Feb  7 13:18:36 kernel: UBIFS (ubi1:0): FS size: 5840896 bytes (5 MiB, 46 LEBs), journal size 1015809 bytes (0 MiB, 6 LEBs)
Feb  7 13:18:36 kernel: UBIFS (ubi1:0): reserved for root: 275879 bytes (269 KiB)
Feb  7 13:18:36 kernel: UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID <REMOVED BY JS>, small LPT model
Feb  7 13:18:37 kernel: UBIFS (ubi1:0): un-mount UBI device 1
Feb  7 13:18:37 kernel: UBIFS (ubi1:0): background thread "ubifs_bgt1_0" stops
Feb  7 13:18:37 kernel: ubi1: detaching mtd9
Feb  7 13:18:37 kernel: ubi1: mtd9 is detached
Feb  7 13:18:38 kernel: ubi1: attaching mtd9
Feb  7 13:18:38 kernel: ubi1: scanning is finished
Feb  7 13:18:38 kernel: ubi1: attached mtd9 (name "misc1", size 8 MiB)
Feb  7 13:18:38 kernel: ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
Feb  7 13:18:38 kernel: ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
Feb  7 13:18:38 kernel: ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096
Feb  7 13:18:38 kernel: ubi1: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
Feb  7 13:18:38 kernel: ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
Feb  7 13:18:38 kernel: ubi1: max/mean erase counter: 58/30, WL threshold: 4096, image sequence number: 1862459137
Feb  7 13:18:38 kernel: ubi1: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 4
Feb  7 13:18:38 kernel: ubi1: background thread "ubi_bgt1d" started, PID 9594
Feb  7 13:18:39 kernel: UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 9615
Feb  7 13:18:39 kernel: UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "nvram"
Feb  7 13:18:39 kernel: UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
Feb  7 13:18:39 kernel: UBIFS (ubi1:0): FS size: 5840896 bytes (5 MiB, 46 LEBs), journal size 1015809 bytes (0 MiB, 6 LEBs)
Feb  7 13:18:39 kernel: UBIFS (ubi1:0): reserved for root: 275879 bytes (269 KiB)
Feb  7 13:18:39 kernel: UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID <REMOVED BY JS>, small LPT model
Feb  7 13:18:39 kernel: UBIFS (ubi1:0): un-mount UBI device 1
Feb  7 13:18:39 kernel: UBIFS (ubi1:0): background thread "ubifs_bgt1_0" stops
Feb  7 13:18:39 kernel: ubi1: detaching mtd9
Feb  7 13:18:39 kernel: ubi1: mtd9 is detached
[\CODE]
Do you mean disabling in the router's UI? For some reason the firewall is restarting when wireless is being restarted. Something is making YazFi want to restart the wireless interfaces, which should not be needed. I'll check the logic
 
Do you mean disabling in the router's UI? For some reason the firewall is restarting when wireless is being restarted. Something is making YazFi want to restart the wireless interfaces, which should not be needed. I'll check the logic

Yes disabling in the Router's UI, and thanks for looking into this. I have my AC3100 setup with a guest wireless network already by manual setup via other posted threads, but I wanted to give the YazFi a try on a brand new router, since it sounded quite easy to setup
 
Yes disabling in the Router's UI, and thanks for looking into this. I have my AC3100 setup with a guest wireless network already by manual setup via other posted threads, but I wanted to give the YazFi a try on a brand new router, since it sounded quite easy to setup
Can you try
Code:
/jffs/scripts/YazFi forceupdate
and try again please?
 
Code:
admin@BVAX88U:/tmp/home/root# /jffs/scripts/YazFi forceupdate
YazFi: Welcome to YazFi v2.3.10, a script by JackYaz

YazFi: Downloading latest version (v2.3.10) of YazFi

YazFi: YazFi successfully updated - restarting firewall to apply update

Tried again and still with the same errors as previously shown
 
Code:
admin@BVAX88U:/tmp/home/root# /jffs/scripts/YazFi forceupdate
YazFi: Welcome to YazFi v2.3.10, a script by JackYaz

YazFi: Downloading latest version (v2.3.10) of YazFi

YazFi: YazFi successfully updated - restarting firewall to apply update

Tried again and still with the same errors as previously shown
Continuously looping?

Can you provide the output of
Code:
nvram get wl0.1_ap_isolate

Also the contents of

/jffs/scripts/firewall-start
/jffs/scripts/service-event
 
Continuously looping?

Can you provide the output of
Code:
nvram get wl0.1_ap_isolate

Also the contents of

/jffs/scripts/firewall-start
/jffs/scripts/service-event

one moment it is this:
Code:
admin@BVAX88U:/tmp/home/root# nvram get wl0.1_ap_isolate
1

and then it changes to this:
Code:
admin@BVAX88U:/tmp/home/root# nvram get wl0.1_ap_isolate
0


Also the contents of

/jffs/scripts/firewall-start
Code:
#!/bin/sh

/jffs/scripts/FreshJR_QOS -start $1 &









/jffs/scripts/YazFi # YazFi Guest Networks


/jffs/scripts/service-event
Code:
#!/bin/sh









/jffs/scripts/YazFi bounceclients "$1" "$2" & # YazFi Guest Networks
 
one moment it is this:
Code:
admin@BVAX88U:/tmp/home/root# nvram get wl0.1_ap_isolate
1

and then it changes to this:
Code:
admin@BVAX88U:/tmp/home/root# nvram get wl0.1_ap_isolate
0


Also the contents of

/jffs/scripts/firewall-start
Code:
#!/bin/sh

/jffs/scripts/FreshJR_QOS -start $1 &









/jffs/scripts/YazFi # YazFi Guest Networks


/jffs/scripts/service-event
Code:
#!/bin/sh









/jffs/scripts/YazFi bounceclients "$1" "$2" & # YazFi Guest Networks
Thanks. With the network off, can you try
Code:
nvram set wl0.1_ap_isolate=1
nvram commit

and then turn the network back on?

Could you also send

Code:
nvram show | grep isolate
please?
 
Thanks. With the network off, can you try
Code:
nvram set wl0.1_ap_isolate=1
nvram commit

and then turn the network back on?

Could you also send

Code:
nvram show | grep isolate
please?

Code:
admin@BVAX88U:/tmp/home/root# nvram show | grep isolate
size: 64079 bytes (66993 left)
wl0.1_ap_isolate=1
wl0.2_ap_isolate=0
wl0.3_ap_isolate=0
wl0_ap_isolate=0
wl1.1_ap_isolate=0
wl1.2_ap_isolate=0
wl1.3_ap_isolate=0
wl1_ap_isolate=0
wl2.1_ap_isolate=0
wl2.2_ap_isolate=0
wl2.3_ap_isolate=0
wl_ap_isolate=1

and system log continuously logs same errors
 
Code:
admin@BVAX88U:/tmp/home/root# nvram show | grep isolate
size: 64079 bytes (66993 left)
wl0.1_ap_isolate=1
wl0.2_ap_isolate=0
wl0.3_ap_isolate=0
wl0_ap_isolate=0
wl1.1_ap_isolate=0
wl1.2_ap_isolate=0
wl1.3_ap_isolate=0
wl1_ap_isolate=0
wl2.1_ap_isolate=0
wl2.2_ap_isolate=0
wl2.3_ap_isolate=0
wl_ap_isolate=1

and system log continuously logs same errors
Hm. Essentially, the wireless is being restarted because that ap_isolate setting isn't sticking (presumably it still alternates?)
 
Hm. Essentially, the wireless is being restarted because that ap_isolate setting isn't sticking (presumably it still alternates?)

Yes it is still alternating when the Guest Network 1 is enabled in the GUI. When it is shutoff, its value stays at =1
 
Yes it is still alternating when the Guest Network 1 is enabled in the GUI. When it is shutoff, its value stays at =1
Can you send a screenshot of the Guest's configuration please (both summary and detailed - be sure to redact the password), as well as your YazFi.config?
 
Can you send a screenshot of the Guest's configuration please (both summary and detailed - be sure to redact the password), as well as your YazFi.config?

upload_2019-2-7_15-48-19.png

upload_2019-2-7_15-53-36.png


Added @.txt to config file in order to upload
 

Attachments

  • YazFi.config.txt
    4.8 KB · Views: 330
Unfortunately I'm not open to screensharing sessions, but would be more than happy to make any script edits you request, and test them out?
 
Unfortunately I'm not open to screensharing sessions, but would be more than happy to make any script edits you request, and test them out?
Sure, I'll put them together in the morning (11pm here currently!)
Thanks for working with me thus far
 
Sounds good, have a good night, and if there is a way to force a test script down to my RT-AX88U with a command, I can help test that way, so as not to affect others. It's 4pm here currently so we will be 7hrs apart, and I'll be available tomorrow to test.
 
Sounds good, have a good night, and if there is a way to force a test script down to my RT-AX88U with a command, I can help test that way, so as not to affect others. It's 4pm here currently so we will be 7hrs apart, and I'll be available tomorrow to test.
Sorry for the delay. Can you comment out the 2 YazFi lines in /jffs/scripts/service-event and /jffs/scripts/firewall-start and then try turning on the guest network?

Can you confirm what wl0.1_ap_isolate is set as, both after turning on the guest and issuing a service restart_wireless please?
 
Sorry for the delay. Can you comment out the 2 YazFi lines in /jffs/scripts/service-event and /jffs/scripts/firewall-start and then try turning on the guest network?

Can you confirm what wl0.1_ap_isolate is set as, both after turning on the guest and issuing a service restart_wireless please?

With both service-event and firewall-start YazFi lines commented out, the guest wifi works as designed by ASUS, but it gives me an IP address on my internal network, but does not allow me to talk to any other internal network clients, which is not what I want, I would like the network isolated in its own Subnet, for future use like VPN's and such, but just to start off as an isolated Guest wireless network.

The command:

Code:
nvram get wl0.1_ap_isolate

returns a "0" and never changes, and the system log never repeats after enabling the guest wireless network
 
With both service-event and firewall-start YazFi lines commented out, the guest wifi works as designed by ASUS, but it gives me an IP address on my internal network, but does not allow me to talk to any other internal network clients, which is not what I want, I would like the network isolated in its own Subnet, for future use like VPN's and such, but just to start off as an isolated Guest wireless network.

The command:

Code:
nvram get wl0.1_ap_isolate

returns a "0" and never changes, and the system log never repeats after enabling the guest wireless network
OK - that setting seems broken perhaps (@RMerlin ?) - I'll patch YazFi to ignore it for the AX88U
 

Similar threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

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