Recent content by KMO

I drafted a solution that used a set of 5 chain subroutines containing the mark and connmark like: MEDIUM MARK --setmark 0x3/0x17 CONNMARK --setmark 0x3/0x17 And then invoked the appropriate one in each QOSO rule using goto (not jump): -g MEDIUM. That seemed to achieve the original intent of...

Ah yes, some also like having a rubbish GUI so they can tell people to stop being noobs and use the command line like a pro. ;)

The behaviour's definitely a feature, but the fact the memory meter prominently displayed on the front page shows the cache is a bug. As illustrated by this thread. It's a meter that shows nothing useful, yet is being waved in people's faces as if it does. If the meter is low, that's fine. If...

Once that starts happening, it's kind of a bit late... Wouldn't it be nice to have a memory meter that told you how close you were to that happening, rather than a basically decorative one? ;) Actually, just noticed the detail that the OP didn't say they rebooted - they just "restarted the...

LOL. (Sorry, not laughing at you, I'm laughing that this GUI confusion has come up again so rapidly). See discussion here: https://www.snbforums.com/threads/ax88u-high-ram-usage-maybe.76650/ The "RAM usage" is just it caching the files. The most recent versions of the software "fix" the...

I've also hit this, and I applied a similar fix.

Yeah, I noticed the 32-bit truncation reading the code, but assumed we weren't hitting it yet. Forgot the swap space could be bigger than 4GiB. Sure, I can fix that.

That would suggest a lack of faith in the operating system doing its job. Anyway, I've made a PR improving the memory display, making it resemble htop more. (Although htop has its own issues, and has changed behaviour a few times recently - I've submitted a PR there too).

Heh, that's one way to sort out the memory graph. :oops: Could that be the only reason that's there?

I'm bored, and irritated by it. I'll investigate how easy it is to patch.

TLDR - the "cache used" only indicates how much you've accessed the disc in the immediate past, and will change from second to second. There's no point doing any sort of comparison on it. Given that, I'd say the GUI is being unhelpful here. The graph shouldn't just be showing "used including...

Are you sure the TPLink responds to incoming pings on the WAN side? That's an option on Asus, which defaults to off. Try another device? Although disabling the firewall generally might defeat such a rule anyway.

You have correct downward routing, as shown by the fact that 192.168.50.1 can reply to the ping. So it must be the firewall (and maybe an unwanted NAT?). The TPLink is regarding the 50 network as "outside" and refusing incoming connections. You probably need to totally shut off the NAT and...

I may be slightly misunderstanding the topology here. What exactly is the TPLink configured to do? Does it have a separate WAN connection, or is your 192.168.50.0 its "WAN"? You talk about "seeing" devices. What exactly do you mean by that? Part of your post suggests there's some communication...

The TPLink needs to have a fixed address on your 192.168.50.0 network - set this up as a static entry in your Asus's DHCP table. Then you need a routing entry on the Asus router "192.168.7.0 255.255.255.0 192.168.50.xxx", where xxx is the fixed address of the TPLink.