returned

joined 1 year ago
sorted by: new top controversial old
Devices getting router IP as DNS in c/selfhosted@lemmy.world
[–] returned@sh.itjust.works 1 points 11 months ago* (last edited 11 months ago)

Then I'd recommend turning off the DHCP server on the Asus router and enabling it on the PiHole... inside the PiHole DHCP server configuration set your routers IP as a gateway address, and set the PiHole address as the DNS. This way, PiHole will manage the IP addresses in your network, which might be a better option overall.

I'm an advanced Mikrotik user overall, one thing they had not been great about is WiFi but their networking capabilities have always been amazing but had a steep learning curve if you'd be using their more advanced options. Though Mikrotik has finally released their WiFi6 devices whose WiFi is finally getting competitive with other WiFi router manufacturers. I can recommend hAP AX2 or hAP AX3, and definitely check their Youtube channel for getting their tutorials.

Mikrotik is definitely my go-to recommendation if you also want to learn networking fundamentals because it's affordable and yet incredibly advanced whichever model you get because they all have pretty much the same RouterOS software within them. There's even more things to thinker about ever since the release of their RouterOS 7 which is now based on Linux 5 kernels compared to their old RouterOS 6 which was based on Linux 3 kernels.

You can even run PiHole on the Mikrotik router itself

Devices getting router IP as DNS in c/selfhosted@lemmy.world
[–] returned@sh.itjust.works 2 points 11 months ago (2 children)

Some devices get confused if there is only one DNS server provided by the DHCP... Maybe try setting your PiHole IP for both "Primary" and "Alternative" DNS server

Devices getting router IP as DNS in c/selfhosted@lemmy.world
[–] returned@sh.itjust.works 15 points 11 months ago* (last edited 11 months ago) (11 children)

The DHCP server pushes the DNS configuration to the clients. Is your Asus router running the DHCP server? If so, in DHCP configuration, set the DNS to point to your Pi-Hole

Reolink Doorbell with 2-way communication in c/homeassistant@lemmy.world
[–] returned@sh.itjust.works 1 points 11 months ago

So can you explain to me in simple terms how the Doorbell, go2rtc, Frigate and HA are operating together? So I could at least know in what direction I should try and make them work together

Reolink Doorbell with 2-way communication in c/homeassistant@lemmy.world
[–] returned@sh.itjust.works 1 points 11 months ago (1 children)

Thanks for the suggestion, but still feels like a vague suggestion... will it work when there's only Android devices available? How do I add a camera to it when I don't have the HomeKit code to add the camera? I have no clue what to do

22
Reolink Doorbell with 2-way communication (sh.itjust.works)
 

Hello guys! I've tried tinkering for couple of hours to get this to work, but I haven't had much luck.

Using the Reolink Doorbell PoE camera with their official app haven't brought me much luck with it's 2-way communication... there's too much of a lag with about 5-10 seconds RTT and is often unstable. I thought it was because of my internet connection but I've gotten an FTTH recently and it's still the same.

I've managed to install HACS without issue, I've tried out the go2rtc and I wanted to get the Frigate card to work with it but with not much luck... I've tried Googling what other people have done but it can get so confusing and difficult to get some sense out of it and I end up making even less sense out of it in the end..

Did anyone had experience with it? What was your final solution to get the 2-way audio to work?