mpleasan88
Occasional Visitor
@Jack Yaz, did you download the diagnostic files? Any suggestions?Can you use option d to generate diagnostics and share them with me please? PM, or Dropbox/other filesharing site
@Jack Yaz, did you download the diagnostic files? Any suggestions?Can you use option d to generate diagnostics and share them with me please? PM, or Dropbox/other filesharing site
YazFi uses OpenVPN onlyi have this working on my ac3100 on an openvpn profile.
i would like to try it using PPTP my VPN provider does support.
openvpn is very slow on the ac3100, so i'm hoping pptp will be faster
as i don't care about perfect privacy, simply keeping my wan private.
i know ac2900 openvpn would be faster, but i can't afford the change.
i was able to disable the openvpn and boot start, and enable
the PPTP profile which autostarts on it's own, but i see problems;
1. yazfi itself does not seem to see/use the PPTP profile
2. everyone's DNS access seems gone (i use merlin's DoT)
this includes other wifi ssid (not yazfi'd) and wired lan.
could someone point me in the right direction on this troubleshoot,
or does yazfi simply depend on openvpn and won't vlan active pptp.
of course i already tested the PPTP profile info using a VPN client PC
and it works fine (including it's own google dns) so it's not that.
while in use in the router, the connection status show it's active.
YazFi uses OpenVPN only
Ok, I forwarded a link of the screenshot of the Policy Rules. I can't seem to find how to upload a file within this forum.Just replied to your PM. Day job got in the way, sorry!
=============Leary at first of installing, seemed too easy/simple.... but made the plunge anyway.
It was easy. Very basic config to simply create WiFi access through a unique network address.
Will let the new setup settle in before making additional changes to reserve addresses and assign device names. Further testing in the morning.
Thanks!
============
I did need to re-edit the config file as the assumption that the router would be #.#.#.1 was incorrect. (i did wonder why that address was missing between the IPADDR and DHCPSTART)
Since NetworkMap is closed source its hard to say what its doing. The 1 true source of which IP a device has will be reported on the device itself=============
=============
Been checking screens/logs and I'm unsure if what is being reported is "as it should be". Realize there is some magic being performed so what I'm seeing could be totally fine, but to pacify my concerns here's what I have...
YazFi / 2 displays
INTERFACE: wl0.1
SSID: GUESTSSID24
HOSTNAME IP ADDRESS MAC
Unknown 172.16.#.# ##:##:##:##:##:##
System Log / Wireless Log displays
View attachment 20892
And Network Map / Clients displays
View attachment 20886
OK, this is what I expect. GuestSSID on its own network address not to show up.
But then why does this happen...
YazFi / 2 displays
INTERFACE: wl1.1
SSID: GUESTSSID5
HOSTNAME IP ADDRESS MAC
Unknown 172.16.#.# ##:##:##:##:##:##
System Log / Wireless Log displays
View attachment 20888
And Network Map / Clients displays
View attachment 20891
There's actually a few GUESTSSID devices that show up in the list; all with a non-guest IP and reported as STATIC.
Probably unnecessary, but did perform the following to have a 'clean' environment and reconfirm the result.
- All DHCP reservations deleted
- Enable manual assignment DISABLED
- DHCP stopped
- Device(s) WiFi configuration deleted
- YazFi uninstalled
- Router rebooted
- YazFi installed
- YazFi started
- DHCP started
- Device(s) configured on WiFi
Normal? or at least expected behavior?
Peculiar as the IP is reported as STATIC, although the device is DHCP and assigned to the GUESTSSID5 network. If the address eventually be released and drop from the list it would be good, but as STATIC it remains.
What started me down the rabbit hole was the tons of AUTH/DEAUTH entries in the System Log / General Log file. Believe the previous DHCP reservations of devices on the non-guest network was causing issues making the device ping-pong on/off the GUEST network. (obviously impacting download speed)
================
================
Did one more check on the router and found another anomaly... (sorry)
YazFi / 2 is now displaying
INTERFACE: wl0.1
SSID: GUESTSSID24
HOSTNAME IP ADDRESS MAC
Unknown 172.16.#.# ##:##:##:##:##:##
Unknown ##:##:##:##:##:##
---------------------------------------------------------------------------
INTERFACE: wl1.1
SSID: GUESTSSID5
HOSTNAME IP ADDRESS MAC
Unknown ##:##:##:##:##:##
Unknown 172.16.#.# ##:##:##:##:##:##
---------------------------------------------------------------------------
IP addresses are being reported via System Log / Wireless Log and System Log / DHCP Leases
Ok, better stop here...
It would be worth removing the script and manually policy routing a client through VPN to see what speed you get. If no better, check that hardware acceleration is enabled etc.Hello!
first. Big thanks/kudos to the developer for this bad a$$ script. Was contemplating going down a PFSENSE rabbit hole before I found this solution
my question now is, why are my speeds so dang slow?!
Used openvpn On stock fw and was getting about 20-30 mbps down while connected to the vpn
since installing Merlin and using yazfi (didn’t test speeds before installing the script) my speeds are like 7-8mbps down
baseline: running on 500 up/down from frontier
Hw: ASUS 66-B1
any ideas on what it could be? I’ve spent the last 5 days researching this sub/ the google and tried changing settings. Adding custom confits to opvn files etc and nothing has worked
thanks in advance!
It would be worth removing the script and manually policy routing a client through VPN to see what speed you get. If no better, check that hardware acceleration is enabled etc.
Pinging of the router is enabled currently and non-configurable. Some devices like Smart Tvs decided they had no internet connection if they couldn't ping the gateway IP. Go figure!Hi Jack,
I've been using your script since you released it and it helped me a lot organizing my Wifi-Devices!
Recently I discovered that even with all parameters set to the strictest setting, I was able to ping my router at 192.168.1.1 from the isolated guest network (192.168.10.x) and pixelserv-tls at 192.168.1.2. I believe that it has nothing to do with your script, but rather with the setup of my network. I am running double NAT, so my router with YazFi (A) is behind another router (B)(both in router mode). Now there is a static route configured on B to forward all 192.168.1.x packets to A.
My guess was that packets went from my guest network out to B and then B sends them back to A (this time my main net), because of the static route.
Is there anything I can do to prevent this? Or is this intended behaviour?
Thank you in advance!
Hm. Guess amtm is looking at the old location still. I was asked to update in preparation for an amtm update that's due out soon. It should get resolved with that.And a re-install of YazFi from within amtm fails ... but chill for a while ... YazFi is still there alive and well ... but access is only through. @Jack YazCode:/jffs/scripts/YazFi
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!