Recent content by custmblt

Really weird but yes maybe just a bug!! Glad you have it working even if its not the way you prefer. Update if you learn anything new.

If it does it again, white list the device from your VPN. I'm no network expert by any stretch but the old saying ; (less is more) sounds like that might be working. Try just using only one VPN connection and if my memory serves me correctly, you are using both OPVN and WGC. Are they both active...

Ive had this as well several times, no idea why but ended completely removing SkyNet then reinstalling it and a reboot... all was well.

Im not entirely sure what's going on. It maybe easier to just reinstall the factory firmware. Its possible your iptables are just all messed up, maybe some else can chime in with some ideas. As far as only using vpn on specific devices and not all? I don't know, never set up like that I'm sure...

Just wanted to give an update. Appears the problem as been identified by dave14305, thank you Dave. You can learn more here about it: Prevent wrong client name in Get_LocalName() Looking forward to the new release that corrects this.

I figured a picture might be helpful, In the VPN Director it should look like this but in your case it would be 10.0.1.0 subnet notice the 3 at the bottom that say OVPN1 you will have only one( 10.0.1.0/24) for the local IP and your (VPN) connection for IFACE. I have two others because I have...

I forgot to mention that the subnet you are using maybe in conflict with your VPN provider. I have seen this before with PIA and others. I would recommend you stick with 192.168.50.1 as I believe that's default for you anyways. Also when you add the 10.0.1.1/24 in your VPN director you only...

I have mine setup as all say WAN in the IFACE column with the only one exception being your VPN all devices (10.0.1.1/24) Then on devices that connected to the subnet with be behind the VPN. Then all devices that you don't want to be covered bu the VPN add them in the same windows like you did...

Are you behind a VPN? I had the same problem and had whitelist the device in the VPN director. Like you mine worked fine for several years and then after a firmware update, it just stopped. After giving the camera module unfiltered VPN traffic all was good. Of course this only make sense if you...

Dave, checked the statistics page this morning and its empty now but the sys log shows a few blocks and a mess of what look like errors but I will admit I have no clue what I'm looking at. Normally the log look fairly clean just not this time. I'm hesitant to post the log here could I directly...

Well, good news to report and so far no more confused names. :) The network will get loaded down with devices tomorrow so that will be the true test!. That said normally it would have already got all mixed up by now so there's hope. Thanks so much for the help, Ill keep the post updated if...

I'll let the router run on the network for 12 or so hours, then once everything gets messed up again I'll try the command and post results. I sure appreciate the interest you have shown in helping, thank you.

I gave that a try, indeed it cleared all customization's that I did but then locked up the router and i could no longer customize any of the device names any more, that's no good. Anyway I already did a factory restore with no customization to the host names and or device names. Still had the...

Well, I gave that a shot but cant see that its changed anything but just freeze the router up using the following `nvram set custom_clientlist=""; nvram commit" also tried nvram set custom_clientlist=; nvram commit in either case no change that I can see. Ill reboot and check back.

I replaced login name with Asterisk's this came back: Promptly_***********-@RT-AX86U_Pro-AC78:/tmp/home/root# nvram get custom_clientlist | grep -ioE "<.*>" | sed -E 's/.*<([^>]+)>[^<]*$/\1/; s/[^a-zA-Z0-9.-]//g' then hit enter and this came back: OOMA-PHONE...