Selfhosted

58291 readers

403 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

help debugging LAN -> WAN connection (lemmy.dbzer0.com)

submitted 4 days ago* (last edited 4 days ago) by ExcessShiv@lemmy.dbzer0.com to c/selfhosted@lemmy.world

22 comments fedilink hide all child comments

I have been seeing periodic drops in internet access from LAN connected devices lately (last 2 months), and I haven't been able to figure about exactly what is going on. There doesn't seem to be a pattern, and it resolves itself after a few hours.

I can access the internet from my router
All devices on LAN can reach each other, both wired and WiFi
All devices on LAN can reach router, both wired and WiFi
I haven't changed anything in router settings
I haven't added new devices to my local network
I can't find any IP conflicts
It's a simple flat network with two APs, a single switch, no VLAN separation

you are viewing a single comment's thread
view the rest of the comments

[–] tal@lemmy.today 2 points 4 days ago* (last edited 4 days ago)

Yes this works when I’m having issues.

Okay, gotcha. In that case, my guess is that the most-likely issue is with the DNS daemon that OpenWRT is using, which is most-likely dnsmasq.

You could confirm that your DNS configuration on the LAN hosts is actually using OpenWRT as the DNS server if you wanted

I could walk through that, if you're not sure. But from a test-when-it's-happening situation, I'd probably:

Install dig on the Mint box, if it's not already installed. That's a DNS diagnostic program that doesn't use your system resolving mechanism, talks directly to DNS, so it cuts out any other factors. It'll be in the bind9-dnsutils package.
```
  $ sudo apt install bind9-dnsutils
```

Install dig on the OpenWRT box.

  $ opkg update
  $ opkg install bind-dig

Confirm that you can successfully run it on both the OpenWrt box and your laptop when there are no problems (your router's LAN address probably being something like 192.168.1.1):
```
  $ dig @your-router-LAN-address www.google.com
```
Confirm that you can successfully run it on both the OpenWrt box and your laptop when there are no problems using whatever outside DNS server you have the OpenWrt box set to use (assuming 1.1.1.1 here):
```
  $ dig @1.1.1.1 www.google.com
```
Next time you have problems, repeat the above. If both the dig on your OpenWrt box and on your laptop using the OpenWrt DNS server now fail, then it's probably pretty safe to say that it's the DNS server on the OpenWrt box at fault. If just the one on your laptop fails, then it's going to be a communication issue between your LAN box and the OpenWrt DNS server.

Assuming that the problem is the OpenWrt DNS server, and assuming that it's dnsmasq, to troubleshoot further, I might try looking at its logs, or installing tcpdump on the OpenWrt box and running that, something like $ tcpdump -nvvv -i any udp port domain. That should let you see both the incoming DNS queries going to the OpenWrt DNS server as well as the queries that it is sending upstream (the -n will prevent tcpdump from itself sending DNS queries to look up IP addresses, which would generate more noise, the -vvv to show all possible information about the packets, and the -i any to show all packets on all interfaces). That'll let you see whether it's getting flooded with DNS queries and to see what queries it's sending to the upstream DNS server out on the Internet.

That won't alone solve your problem, but it'd be the next step I'd try to narrow down what's going on.