4·
1 month agoYtTags is another useful tool
Boris NotTooBadinov
Greetings from great nation of Pottsylvania. I go where and do what Fearless Leader tells. Am master of disguise and aliases. I will have great success as long as moose and squirrel do not interfere
- 0 Posts
- 5 Comments
Joined 1 year ago
Cake day: July 7th, 2023
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
You could try ZeroTier. I’ve not used it personally, but it’s free if you host your own instance. Your traffic gets routed through that VM, and everything behaves like it’s on the same LAN
1·1 year agoOne other thing I forgot is to verify a LAN device can ping the router IP, but I’m guessing you’ve already verified that. This is starting to sound like a FW issue
It’s been years since I setup my openwrt router, but here is some advice verifying your FW config
tl;dr Your WAN interface may be defined as ‘wan’ in your FW rules, since ‘WAN’ != ‘wan’ - correcting the case may solve the issue
Off the top of my head, this is low hanging fruit:
- Verify your LAN devices are pulling dhcp or alternatively put a static IP on one of them
- Verify the/a correct default gateway is set on the LAN side (should be the internal IP of your router)
- Verify DNS (ping 1.1.1.1 from a LAN device, if you can, then make sure you’ve configured DNS servers for the LAN side within the router)
Had a similar issue with tlp recently. I just happened to notice the laptop battery was at 100%, and said it was charging. I double and triple checked the config file, but the tlp-stat -b still showed the thresholds at 90%-100%.
Turns out tlp, at some point, started ignoring /etc/tlp.conf, and was pointing to /etc/default/tlp