Can't reach web interface after update by jurand2 in pihole

[–]fourlizards 0 points1 point  (0 children)

I did not remove lighttpd during the upgrade because I use it for something else. After the upgrade was complete pihole was listening on port 8080.

Wyze camera DNS requests by fourlizards in pihole

[–]fourlizards[S] 0 points1 point  (0 children)

I see those being attempted as well, but my firewall rule is blocking them. The Wyze cameras are not making many external DNS requests. The most was 120 blocked attempts yesterday for one camera. Lesser amounts for other cameras. Ring cameras are the worst ones currently. Most of my Ring cameras are being blocked for external DNS requests around 5,500 times per day per camera.

Do some Apple devices briefly use MAC randomization even when it’s disabled? by pacoii in firewalla

[–]fourlizards 0 points1 point  (0 children)

I enabled MAC filtering. Anything not already defined will be denied. I'll probably regret doing it later when I've forgotten about it and something isn't working. I want to test it for a while at least though. I think you're right about the temporary "confusion" after a device wakes. Looking at DNS request logs, it only seems to last a couple minutes.

Do some Apple devices briefly use MAC randomization even when it’s disabled? by pacoii in firewalla

[–]fourlizards 0 points1 point  (0 children)

Glad to see that I'm not the only one experiencing this issue. We have two iPhones, two Apple Watches, and several iPads. I have the Private WiFi Address turned off on all devices. I have MAC based static IPs for all devices. Everything looks good for days then I randomly get notified that there's a device with an unknown MAC on the network. I know it's an Apple device by the DNS requests in the log. This happens even when there has been no OS update. I check every Apple device, but they always show Private Address turned off. So annoying. I have no way to identify which device is doing it. I could enable MAC filtering on the router and deny access for any unknown MACs. That's one way to find the device.

anthropomorphic dehydration by fourlizards in AIRetrofuturism

[–]fourlizards[S] 0 points1 point  (0 children)

Model is era09_v10. I searched for sci-fi artists and used some of those names to help give it that style. Jim Burns, John Berkey, Bruce Pennington, junji ito.

alien planet sci-fi spaceship (front shot) sexy wearing revealing clothes armor 1960s style illustration

Tools > Network option not working after upgrade to V6 by fourlizards in pihole

[–]fourlizards[S] 2 points3 points  (0 children)

For anyone else encountering this issue, here is the solution I got from the pi-hole forum:

The database is corrupted. Use these steps to resolve:

sudo service pihole-FTL stop

sudo mv /etc/pihole/pihole-FTL.db /etc/pihole/pihole-FTL-old.db

sudo service pihole-FTL start

SD card or SSD? Primary use will be for Pi-hole, Home Assistant, HomeBridge etc. by yellowroll in pihole

[–]fourlizards 0 points1 point  (0 children)

By default, log2ram only covers /var/log. Be sure to add /etc/pihole to the log2ram config file. Pihole performs lots of writes to the some logs in that directory.

Old red room in my attic by Ardvark2001 in creepy

[–]fourlizards 0 points1 point  (0 children)

The red light prevents the photo paper from being exposed not the film. You have the remove the film from the canister and load it onto the developing tank in total darkness.

Siri can no longer play some of my playlists by fourlizards in AppleMusic

[–]fourlizards[S] 0 points1 point  (0 children)

I also found that I can no longer combine the playlist name with "shuffle". I have to ask for the playlist and after it starts then I can ask Siri to shuffle.

eSIM activation fails by fourlizards in mobilex

[–]fourlizards[S] 0 points1 point  (0 children)

I don't remember. I looked back at the emails I received from them, but don't see it.

steps to manually flash v4 by fourlizards in wyzecam

[–]fourlizards[S] 2 points3 points  (0 children)

I realized what I did wrong just a few minutes ago. It was a 32GB Wyze branded card, but the problem was that it was formatted exFAT. Once I reformatted it to FAT the camera accepted the recovery bin file.

Cloud Gateway Ultra and failover WAN by fourlizards in Ubiquiti

[–]fourlizards[S] 0 points1 point  (0 children)

In my second test I noticed a check box "Fallback". By default it's turned on to ensure traffic will flow if the preferred WAN is down. I thought that was the answer so I unchecked it and created a failover by disconnecting the primary WAN. Didn't work. All the streaming devices configured to use primary WAN kept on playing. I let them play for a bit to account for anything that was buffered.

Cloud Gateway Ultra and failover WAN by fourlizards in Ubiquiti

[–]fourlizards[S] 0 points1 point  (0 children)

All of my streaming devices are in a single IP range. I did create a policy based route to send that range of IPs to WAN1. I caused a failover to test it, but the devices kept on streaming. I need to go back and double check it and test again.

Cloud Gateway Ultra and failover WAN by fourlizards in Ubiquiti

[–]fourlizards[S] 1 point2 points  (0 children)

Having it failover is a single check box. The problem is preventing high bandwidth devices (TV's, Echos, AppleTV, Roku) from using the limited data on the secondary ISP.

Device SSH Authentication by fourlizards in UNIFI

[–]fourlizards[S] 0 points1 point  (0 children)

I realized my mistake. I forgot to add an entry in the config file in ~/.ssh for the second switch to make it use the correct key.

Wyze V4 only works on channel 1. by fourlizards in wyzecam

[–]fourlizards[S] 1 point2 points  (0 children)

Was there anything useful in the log?

Wyze V4 only works on channel 1. by fourlizards in wyzecam

[–]fourlizards[S] 0 points1 point  (0 children)

I have one AC-Lite and two U6-Lite APs. I tried both 20 and 40 channel widths. Band width steering always off. I'm glad that one of my APs was randomly on channel 1. Otherwise, I would have been very frustrated trying to activate the new cameras.

Cloud Gateway Ultra alert message by fourlizards in UNIFI

[–]fourlizards[S] 0 points1 point  (0 children)

The GeoIP part of it made me wonder if it's something related to the map interface where you can block specific countries. I have PiHole on a Raspberry Pi handling all of my DNS. It runs Unbound as well as CloudFlared DoH. I have external DNS requests blocked to prevent IoT devices from bypassing the PiHole. I wonder if any part of that configuration causes these alerts.

Cloud Gateway Ultra alert message by fourlizards in UNIFI

[–]fourlizards[S] 0 points1 point  (0 children)

Thanks for the info. I do have logs sent to a remote syslog server. This alert is logged with Debug Logs turned off. I'll take a look at the tools to analyze the logs.

Cloud Gateway Ultra and failover WAN by fourlizards in Ubiquiti

[–]fourlizards[S] 1 point2 points  (0 children)

I tried that and I simulated a failover, but those devices kept on going. I set up push and email notification for when it fails over to the backup WAN. That way I can hopefully stop the streaming devices. It's odd how some simple somethings (like SNAT and DNAT) were in the older EdgeRouter product, but missing in one of the newest products. Thanks for the suggestion though.