RTRMON RTRMON v2.1.6 -Jul 5, 2025- Monitor your Router's Health (New: AMTM, Network Conn/Bandwidth/Diag + Port Scanner + Speedtest) - Wireguard v2.2.04 Beta!

[Viktor Jaep]

Some minor but important updates to RTRMON heading your way... 2.1.6 released today!

NOTE: Upon running RTRMON, you may be presented with a screen that indicates your setup is incomplete, or that you're missing entware dependencies. The "column" entware tool is now a required component, so please hit the "Force Reinstall Entware Dependencies", and let everything reinstall to ensure all tools are in place to allow RTRMON to do it's thing!

What's new?
v2.1.6 - (July 5, 2025)
- PATCH: Included a much needed "export PATH" statement to ensure the script knows where to look for commonly installed entware tools. Not having this could cause confusion, as the script might use a similar older or newer tool installed in a different location on the router.
- PATCH: Included a check for the "column" entware tool. This tool is necessary for the display of data on page #7 (wireless/wired devices), and originally thought it was included with our FW by default. Apparently not the case, and will now get installed on a new RTRMON install, or will complain its missing and ask you to reinstall through the "Force Reinstall Entware Dependencies" menu item.
- PATCH: General bugfixes and UI cleanup items.

Download link (or update directly within RTRMON or AMTM):

curl --retry 3 "https://raw.githubusercontent.com/ViktorJp/RTRMON/master/rtrmon.sh" -o "/jffs/scripts/rtrmon.sh" && chmod 755 "/jffs/scripts/rtrmon.sh"

Significant Screenshots:
None today!

 

[scootertramp]

This is not a result of RTRMON latest update but, I would like to see if this can be fixed.
iftop errors when running from RTRMON or running iftop from command line.

Error when running RTRMON:

Refresh (C)urrent Network Statistics

[Updating WAN( ) LAN( ) VPN( ) Statistics ... Please stand by...]Bus error
[Updating WAN(X) LAN( ) VPN( ) Statistics ... Please stand by...]Bus error
Refresh (C)urrent Statistics | Stats Age: 0 Minute(s) ago

From the messages file:

2025-07-05T19:30:41.545008-04:00 rt-ax92u kernel[-]: Unhandled fault: alignment fault (0x92000021) at 0x00000000f65000ae
2025-07-05T19:30:41.601287-04:00 rt-ax92u kernel[-]: potentially unexpected fatal signal 7.
2025-07-05T19:30:41.601287-04:00 rt-ax92u kernel[-]: CPU: 0 PID: 30113 Comm: iftop Tainted: P O 4.1.51 #2
2025-07-05T19:30:41.601287-04:00 rt-ax92u kernel[-]: Hardware name: Broadcom-v8A (DT)
2025-07-05T19:30:41.601287-04:00 rt-ax92u kernel[-]: task: ffffffc004de4ac0 ti: ffffffc008dfc000 task.ti: ffffffc008dfc000
2025-07-05T19:30:41.601287-04:00 rt-ax92u kernel[-]: PC is at 0x133e4
2025-07-05T19:30:41.601287-04:00 rt-ax92u kernel[-]: LR is at 0x132dc
2025-07-05T19:30:41.601287-04:00 rt-ax92u kernel[-]: pc : [<00000000000133e4>] lr : [<00000000000132dc>] pstate: 600c0010
2025-07-05T19:30:41.601287-04:00 rt-ax92u kernel[-]: sp : 00000000f64fe8e8
2025-07-05T19:30:41.601287-04:00 rt-ax92u kernel[-]: x12: 0000000000000000
2025-07-05T19:30:41.602670-04:00 rt-ax92u kernel[-]: x11: 0000000000000000 x10: 0000000000013cf0
2025-07-05T19:30:41.602670-04:00 rt-ax92u kernel[-]: x9 : 0000000000000064 x8 : 0000000000000100
2025-07-05T19:30:41.602670-04:00 rt-ax92u kernel[-]: x7 : 0000000000000001 x6 : 0000000000000000
2025-07-05T19:30:41.602670-04:00 rt-ax92u kernel[-]: x5 : 00000000f64fe924 x4 : 00000000f65000a2
2025-07-05T19:30:41.602670-04:00 rt-ax92u kernel[-]: x3 : 000000000000d37c x2 : 00000000000001bb
2025-07-05T19:30:41.602670-04:00 rt-ax92u kernel[-]: x1 : 0000000000000000 x0 : 00000000f64fe924

The above error from the messages file is the same when running iftop from command line.

Kernel: RT-AX92U (aarch64) Kernel-4.1.51
Firmware: 3004.388.9_2-gnuton1
AMTM: 6.1
RTRMON: 2.1.6

I did try running "Force Reinstall Entware Dependencies" but, it did not help.

 

[Viktor Jaep]

This is not a result of RTRMON latest update but, I would like to see if this can be fixed.
iftop errors when running from RTRMON or running iftop from command line.

Error when running RTRMON:

Refresh (C)urrent Network Statistics

[Updating WAN( ) LAN( ) VPN( ) Statistics ... Please stand by...]Bus error
[Updating WAN(X) LAN( ) VPN( ) Statistics ... Please stand by...]Bus error
Refresh (C)urrent Statistics | Stats Age: 0 Minute(s) ago

From the messages file:

2025-07-05T19:30:41.545008-04:00 rt-ax92u kernel[-]: Unhandled fault: alignment fault (0x92000021) at 0x00000000f65000ae
2025-07-05T19:30:41.601287-04:00 rt-ax92u kernel[-]: potentially unexpected fatal signal 7.
2025-07-05T19:30:41.601287-04:00 rt-ax92u kernel[-]: CPU: 0 PID: 30113 Comm: iftop Tainted: P O 4.1.51 #2
2025-07-05T19:30:41.601287-04:00 rt-ax92u kernel[-]: Hardware name: Broadcom-v8A (DT)
2025-07-05T19:30:41.601287-04:00 rt-ax92u kernel[-]: task: ffffffc004de4ac0 ti: ffffffc008dfc000 task.ti: ffffffc008dfc000
2025-07-05T19:30:41.601287-04:00 rt-ax92u kernel[-]: PC is at 0x133e4
2025-07-05T19:30:41.601287-04:00 rt-ax92u kernel[-]: LR is at 0x132dc
2025-07-05T19:30:41.601287-04:00 rt-ax92u kernel[-]: pc : [<00000000000133e4>] lr : [<00000000000132dc>] pstate: 600c0010
2025-07-05T19:30:41.601287-04:00 rt-ax92u kernel[-]: sp : 00000000f64fe8e8
2025-07-05T19:30:41.601287-04:00 rt-ax92u kernel[-]: x12: 0000000000000000
2025-07-05T19:30:41.602670-04:00 rt-ax92u kernel[-]: x11: 0000000000000000 x10: 0000000000013cf0
2025-07-05T19:30:41.602670-04:00 rt-ax92u kernel[-]: x9 : 0000000000000064 x8 : 0000000000000100
2025-07-05T19:30:41.602670-04:00 rt-ax92u kernel[-]: x7 : 0000000000000001 x6 : 0000000000000000
2025-07-05T19:30:41.602670-04:00 rt-ax92u kernel[-]: x5 : 00000000f64fe924 x4 : 00000000f65000a2
2025-07-05T19:30:41.602670-04:00 rt-ax92u kernel[-]: x3 : 000000000000d37c x2 : 00000000000001bb
2025-07-05T19:30:41.602670-04:00 rt-ax92u kernel[-]: x1 : 0000000000000000 x0 : 00000000f64fe924

The above error from the messages file is the same when running iftop from command line.

Kernel: RT-AX92U (aarch64) Kernel-4.1.51
Firmware: 3004.388.9_2-gnuton1
AMTM: 6.1
RTRMON: 2.1.6

I did try running "Force Reinstall Entware Dependencies" but, it did not help.

I'm sorry @scootertramp ... Hate to tell you this... but when you start seeing "<name of binary> Tainted", that's usually bad news. I've not ever been to able to recover from something like this without a full USB wipe (possibly a bad USB) and/or a full router wipe and reset. Something in the OS has gone bad, and the only way out is a full reinstall.

Would welcome any other assistance or opinions from the community if you've had luck recovering from something like this without a full wipe + reinstall?

 

[scootertramp]

I'm sorry @scootertramp ... Hate to tell you this... but when you start seeing "<name of binary> Tainted", that's usually bad news. I've not ever been to able to recover from something like this without a full USB wipe (possibly a bad USB) and/or a full router wipe and reset. Something in the OS has gone bad, and the only way out is a full reinstall.

Would welcome any other assistance or opinions from the community if you've had luck recovering from something like this without a full wipe + reinstall?

Thanks. but I think that's a rabbit hole I would rather avoid. Everything else I am using on this router appears to be working well.
I tried RTRMON on one of my XT8 routers to see how it fairs there as well. I am seeing the following errors when running RTRMON.

cat: can't open '/sys/class/net//statistics/rx_bytes': No such file or directory
cat: can't open '/sys/class/net//statistics/tx_bytes': No such file or directory

On the XT8 iftop seems to be running better, but I get a few odd messages there as well.
When quitting iftop:
XXXXXXX@zenwifi-xt8up:/tmp/home/root# iftop
interface: archer
Unable to get IP address for interface: archer
ioctl(SIOCGIFADDR): Cannot assign requested address
MAC address is: 00:00:00:00:00:00

and in the messages file:
2025-07-06T08:11:54.928670-04:00 zenwifi-xt8up kernel[-]: protocol 0000 is buggy, dev archer
2025-07-06T08:11:55.480667-04:00 zenwifi-xt8up kernel[-]: protocol 0000 is buggy, dev archer

XT8 Info:
ZenWiFi_XT8 (armv7l) Kernel-4.1.52
Firmware: 3004.388.9_2-gnuton1
AMTM: 6.1
RTRMON: 2.1.6

 

[Viktor Jaep]

Thanks. but I think that's a rabbit hole I would rather avoid. Everything else I am using on this router appears to be working well.
I tried RTRMON on one of my XT8 routers to see how it fairs there as well. I am seeing the following errors when running RTRMON.

I'm just saying, from my experience. When this happened to me, it started out with one tool, but then it quickly started multiplying to the point where I was unable to use some commonly-used tools making for a frustrating experience. Whatever is going bad on your router, isn't going to stop until you take some action.

cat: can't open '/sys/class/net//statistics/rx_bytes': No such file or directory
cat: can't open '/sys/class/net//statistics/tx_bytes': No such file or directory

This is pretty rare, but for some reason RTRMON can't determine what your WAN0 interface name is (usually eth0). Luckily, you can override this to the correct value under the settings menu. Try picking the right one from this list, and should make a difference for you.

On the XT8 iftop seems to be running better, but I get a few odd messages there as well.
When quitting iftop:
XXXXXXX@zenwifi-xt8up:/tmp/home/root# iftop
interface: archer
Unable to get IP address for interface: archer
ioctl(SIOCGIFADDR): Cannot assign requested address
MAC address is: 00:00:00:00:00:00

and in the messages file:
2025-07-06T08:11:54.928670-04:00 zenwifi-xt8up kernel[-]: protocol 0000 is buggy, dev archer
2025-07-06T08:11:55.480667-04:00 zenwifi-xt8up kernel[-]: protocol 0000 is buggy, dev archer

This may have something to do with your strange eth0 interface issue. Doesn't seem like iftop likes it either. Seems like it tried to pick one called "archer", but there wasn't an IP address assigned to it, so it wasn't able to gather any data. Once you figure out the correct interface name for WAN0, you can use that in the iftop commandline as well, and force it to use that.

I haven't had many report back from the XT8 side, running on gnuton, but we could very well be dealing with a compatibility issue here.

 

[scootertramp]

I'm just saying, from my experience. When this happened to me, it started out with one tool, but then it quickly started multiplying to the point where I was unable to use some commonly-used tools making for a frustrating experience. Whatever is going bad on your router, isn't going to stop until you take some action.


This is pretty rare, but for some reason RTRMON can't determine what your WAN0 interface name is (usually eth0). Luckily, you can override this to the correct value under the settings menu. Try picking the right one from this list, and should make a difference for you.

View attachment 66529



This may have something to do with your strange eth0 interface issue. Doesn't seem like iftop likes it either. Seems like it tried to pick one called "archer", but there wasn't an IP address assigned to it, so it wasn't able to gather any data. Once you figure out the correct interface name for WAN0, you can use that in the iftop commandline as well, and force it to use that.

I haven't had many report back from the XT8 side, running on gnuton, but we could very well be dealing with a compatibility issue here.

@Viktor Jaep

Assigning an interface works fine for both RTRMON and iftop on the XT8. I used br0 since that is using the routers ip address.

For now I will skip the rabbit hole on the AX92U and take the blue pill. I am not sure how long the AX92U will be a viable router
as it has been on the EOL list for quite some time. Back last November I started to look for a replacement because of EOL and
had not had any firmware updates for about a year. To my surprise ASUS was still pushing them on their site and there was a new firmware
update. Since then there have been like two more firmware updates.

Thanks for your input and I will see where things stand when the blue pill wears off.

 

[Viktor Jaep]

Assigning an interface works fine for both RTRMON and iftop on the XT8. I used br0 since that is using the routers ip address.

Glad that worked for ya.

For now I will skip the rabbit hole on the AX92U and take the blue pill. I am not sure how long the AX92U will be a viable router
as it has been on the EOL list for quite some time. Back last November I started to look for a replacement because of EOL and
had not had any firmware updates for about a year. To my surprise ASUS was still pushing them on their site and there was a new firmware
update. Since then there have been like two more firmware updates.

Thanks for your input and I will see where things stand when the blue pill wears off.

Absolutely... let me know how it goes! Hopefully some upcoming sales will be enticing enough to pull that trigger on a new router in the near future.

 

[Viktor Jaep]

Just a quick update... while VPNMON-R3 is getting thoroughly run through the ringer before a final release, I'm beginning work on RTRMON, and getting it ready to support Wireguard. Progress is being made!

 

[Viktor Jaep]

Pleased to announce the first RTRMON v2.2.0 beta 2 release! Wireguard is now supported! For those running Wireguard, please give it a whirl, and send any feedback you may have!

What's new!
v2.2.02b - (TBA)
- MINOR: This release adds compatibility with Wireguard connections! New functionality has been added under: Page 2 - Network connections, now adding any Wireguard connections to the bottom of the list. Page 4 - Speed Test, now allowing you to speed test your WAN, VPN and Wireguard connections. Page 6 - Top 10 Network/Bandwidth connections, now showing established connections running across your Wireguard tunnels. Operations Menu, now showing additional keyboard options to allow you to quickly jump to a Wireguard speed test.
- PATCH: Many, many behind the scenes additions, optimizations and fixes, but could probably use a lot more! But hey it works!
- PATCH: Minor fixes and adding some more dev/nulls around certain commands to keep occasional messages from popping up in the main UI.

Beta Download link:

curl --retry 3 "https://raw.githubusercontent.com/ViktorJp/RTRMON/develop/rtrmon.sh" -o "/jffs/scripts/rtrmon.sh" && chmod 755 "/jffs/scripts/rtrmon.sh"

Significant Screenshots:

 

[CaptainSTX]

Pleased to announce the first RTRMON v2.2.0 beta 1 release! Wireguard is now supported! For those running Wireguard, please give it a whirl, and send any feedback you may have!

What's new!
v2.2.01b - (TBA)
- MINOR: This release adds compatibility with Wireguard connections! New functionality has been added under: Page 2 - Network connections, now adding any Wireguard connections to the bottom of the list. Page 4 - Speed Test, now allowing you to speed test your WAN, VPN and Wireguard connections. Page 6 - Top 10 Network/Bandwidth connections, now showing established connections running across your Wireguard tunnels. Operations Menu, now showing additional keyboard options to allow you to quickly jump to a Wireguard speed test.
- PATCH: Many, many behind the scenes additions, optimizations and fixes, but could probably use a lot more! But hey it works!

Beta Download link:

curl --retry 3 "https://raw.githubusercontent.com/ViktorJp/RTRMON/develop/rtrmon.sh" -o "/jffs/scripts/rtrmon.sh" && chmod 755 "/jffs/scripts/rtrmon.sh"

Significant Screenshots:

View attachment 66972

Loaded the Beta and with three WG clients everything seems to be working fine. Thanks for the update.

 

[ZebMcKayhan]

Page 4 - Speed Test, now allowing you to speed test your WAN, VPN and Wireguard connections.

Great stuff!

However, if I try the Wireguard speeds test on my rt-ax86u pro running 388.8_4:

Setting my Wireguard interfaces rp_filter to loose seems to fix this

So, guessing you need to workaround rp_filter.
Not sure why I get the socket error but it seems consistent for both wgc1 and wgc2 and messes up the server parsing.

I've tried running the speedtest with normal output but it does not give any more clue.

 

[Viktor Jaep]

Great stuff!

However, if I try the Wireguard speeds test on my rt-ax86u pro running 388.8_4:
View attachment 67058
Setting my Wireguard interfaces rp_filter to loose seems to fix this
View attachment 67059
So, guessing you need to workaround rp_filter.
Not sure why I get the socket error but it seems consistent for both wgc1 and wgc2 and messes up the server parsing.
View attachment 67061
I've tried running the speedtest with normal output but it does not give any more clue.

Thanks for this... yeah, I don't get any of those socket error issues when I run speedtests on my "regular" WG tunnels. It's almost as if it's trying to determine the best server to test, and keeps bouncing between them as they give you errors.

I was reading something that suggested that perhaps if IPv6 is involved, it could cause these errors. Are you running that?

The other suggestion is to use a specific server to test against?

 

[ZebMcKayhan]

I was reading something that suggested that perhaps if IPv6 is involved, it could cause these errors. Are you running that?

Yes, I'm running ipv6 on router itself but not on lan.

Wgc1 and wgc2 are both dual stack and wgc1 even uses ipv6 for server clients as they are via dual stack vps.

I did check the speedtest --help about if one can force ipv4 but did not find anything.
I also did add the ip -6 rule but no difference.

It's wierd that I get these socket errors but the test still works. And that is on 2 separate tunnels with different country outputs. But both tunnels are from the same supplier altough it seems far-fetched that this should be a vpn supplier issue.

I wonder if I can get more detailed output...

 

[ZebMcKayhan]

It's almost as if it's trying to determine the best server to test, and keeps bouncing between them as they give you errors.

This is how it looks if I run without csv option:

Not really useful. But I tested to specify the server and then the errors are gone:

So you might be on to something.

Edit:
Listing servers close to my exit:

But when testing, several of these gets the socket error:

 

[Viktor Jaep]

Yes, I'm running ipv6 on router itself but not on lan.

Wgc1 and wgc2 are both dual stack and wgc1 even uses ipv6 for server clients as they are via dual stack vps.

I did check the speedtest --help about if one can force ipv4 but did not find anything.
I also did add the ip -6 rule but no difference.

It's wierd that I get these socket errors but the test still works. And that is on 2 separate tunnels with different country outputs. But both tunnels are from the same supplier altough it seems far-fetched that this should be a vpn supplier issue.

I wonder if I can get more detailed output...

Thanks for all this info... what if you specified your IPv4 IP using the --ip switch? Perhaps that would make it behave?

 

[ZebMcKayhan]

Thanks for all this info... what if you specified your IPv4 IP using the --ip switch? Perhaps that would make it behave?

Interesting idea. My wgc1 ipv4 is 10.0.71.4, so:

Tested both with rp_filter set to loose and ip rule with same result. Specifying both interface and ip just throws an error.

But you are right about this is probably an ipv6 thingy. All servers that work only have ipv4 (all I have managed to check). Both asus and merlin fw imports dual stack configs and set it up if ipv6 is enabled but it's probably not widely used due to vpndirector not accepting ipv6.

If I try to ping an ipv6 using wgc1 it also fails while ipv4 works if rp_filter is set to loose or routing rule is added.

I wonder why these things don't work for ipv6.

 

[Viktor Jaep]

Interesting idea. My wgc1 ipv4 is 10.0.71.4, so:
View attachment 67072

Tested both with rp_filter set to loose and ip rule with same result. Specifying both interface and ip just throws an error.

But you are right about this is probably an ipv6 thingy. All servers that work only have ipv4 (all I have managed to check). Both asus and merlin fw imports dual stack configs and set it up if ipv6 is enabled but it's probably not widely used due to vpndirector not accepting ipv6.

If I try to ping an ipv6 using wgc1 it also fails while ipv4 works if rp_filter is set to loose or routing rule is added.

I wonder why these things don't work for ipv6.

Looks like others have this problem as well... https://www.sweharris.org/post/2023-04-29-netns-ip4only/

But wow, I wish there was an easier workaround.

I wonder why these things don't work for ipv6.

And this is exactly why I just have IPv6 turned off at the router/WAN level. Not worth the hassle and serious data leak risks.

Well, I made the change to help with the rp_filter... but it feels a bit incomplete not knowing how else to get around the limitations of this speedtest cli binary. We can't specify IPv4 or IPv6... we can't specify it to only use IPv4 test servers... the only possible way around it where you might be able to prevent these errors from popping up is to explicitly use a custom test server that you know only works for IPv4. Sadly.

Perhaps I'll reach out to them and see if I can lodge a bug report/complaint.

 

[Viktor Jaep]

What's new!
v2.2.04b - (TBA)
- MINOR: This release adds compatibility with Wireguard connections! New functionality has been added under: Page 2 - Network connections, now adding any Wireguard connections to the bottom of the list. Page 4 - Speed Test, now allowing you to speed test your WAN, VPN and Wireguard connections. Page 6 - Top 10 Network/Bandwidth connections, now showing established connections running across your Wireguard tunnels. Operations Menu, now showing additional keyboard options to allow you to quickly jump to a Wireguard speed test.
- PATCH: Many, many behind the scenes additions, optimizations and fixes, but could probably use a lot more! But hey it works!
- PATCH: Minor fixes and adding some more dev/nulls around certain commands to keep occasional messages from popping up in the main UI.
- PATCH: Added the rp_filter compatibility statements per @ZebMcKayhan for during use of the speedtest. Added additional ip rule filters to handle IPv6 as it the output was displaying errors and causing some display issues.

Beta Download link:

curl --retry 3 "https://raw.githubusercontent.com/ViktorJp/RTRMON/develop/rtrmon.sh" -o "/jffs/scripts/rtrmon.sh" && chmod 755 "/jffs/scripts/rtrmon.sh"

Significant Screenshots:

Showing an example of the newly available Wireguard interfaces available to speedtest against...

 

[ZebMcKayhan]

Looks like others have this problem as well... https://www.sweharris.org/post/2023-04-29-netns-ip4only/

Yep, I saw that to.

And this is exactly why I just have IPv6 turned off at the router/WAN level. Not worth the hassle and serious data leak risks.

I'm using it for my server as I'm behind cgnat. For ipv4 connection is via a VPS but for ipv6 it is direct. Since my vps is dual stack I'm getting a whole heap of issues if my router is not (apps like netflix or outlook stops working). I could remake the vps but I rather not.
By turning off ipv6 RA on the router my lan does not get ipv6 so there are no leaks.

But wow, I wish there was an easier workaround.

Me too. but its not only an issue with speedtest as ping ipv6 fails to, so its more of an ipv6 issue. I wonder if @RMerlin gets the same issue in the newer fw if dual stack wg is used. I wonder how he got around this issue.

The issue resolves itself as it traverses the servers. It's only the parsing of the server text that gives it away. Possibly you could look into the parsing and display a proper server and perhaps with some additional Warning if this is found?

PATCH: Added the rp_filter compatibility statements per @ZebMcKayhan for during use of the speedtest. IMPORTANT NOTE: If you're running IPv6 across your Wireguard tunnels, you may encounter some "incompatibilities" uncovered in the Ookla Speedtest CLI binary by @ZebMcKayhan. It will complain and throw errors.

Great! The rp_filter issue is now gone.

 

[Viktor Jaep]

I'm using it for my server as I'm behind cgnat. For ipv4 connection is via a VPS but for ipv6 it is direct. Since my vps is dual stack I'm getting a whole heap of issues if my router is not (apps like netflix or outlook stops working). I could remake the vps but I rather not.
By turning off ipv6 RA on the router my lan does not get ipv6 so there are no leaks.

Yeah, I'm not saying it doesn't have its uses and purpose, like in your case, I wholeheartedly support you with your amazing setup! Just saying, that for those who don't truly have a need for it, introducing something like this just really adds a lot more complexity and unknowns.

Me too. but its not only an issue with speedtest as ping ipv6 fails to, so its more of an ipv6 issue. I wonder if @RMerlin gets the same issue in the newer fw if dual stack wg is used. I wonder how he got around this issue.

The issue resolves itself as it traverses the servers. It's only the parsing of the server text that gives it away. Possibly you could look into the parsing and display a proper server and perhaps with some additional Warning if this is found?

I'd be curious as well.

Could you please copy the exact output you get with errors and all? I can see if I can write a crazy filter to get rid of it all. That might be a good bandaid in the interim.

Great! The rp_filter issue is now gone.

Awesome. At least there's 1 step forward. LOL Thanks for your help on this!