• 0 Posts
  • 20 Comments
Joined 1 year ago
cake
Cake day: June 28th, 2023

help-circle
  • The industry has not acquired a single standard by now. In this regard, there are many different devices on different protocols. Many manufacturers generally link their devices only to their own cloud.

    Of the popular open standards, I would recommend zigbee. But in order for the device to be correctly identified, its sensors and parameters must be supported by the server. Zigbee2MQTT is a good choice. I use it myself. But the compatibility is not complete and you need to check the support on the developer’s website ( https://www.zigbee2mqtt.io/supported-devices/ ) or buy one device for the test.

    I recommend Tuya company. I have about 12 switches from this company and they work pretty well with zigbee2mqtt.

    The complete scheme is as follows: zigbee device <-> radio channel <-> zigbee coordimator <-> zigbee2mqtt <-> mqtt <-> homeassistant. For connect devices to zigbee2mqtt you need coordinator. SONOFF ZBDongle-E for example. Add zigbee routers if you have big square. If you server not in good place you can use wifi2zigbee coordinator. HamGeek poe zigbee 3.0 for example.







  • the idea is that: all your applications work under the same user. or at least under the same group. because this is exactly how the differentiation of rights is applied.

    A good plan is to create some kind of user in all three containers and run qbittorrent, samba and the third application under it.

    A bad plan is to run everything under a random user with 777 rights, but this is a really bad plan.

    Create a user in all three containers and work under it. That is not hard. Run qbittorent with that user. Config will be there: /home/user/.config . Then set that user for samba. I don’t know third app , but I think you can find how change user in manual.



  • You need to create an MX record in the DNS zone of your domain. Something like:

    @ IN MX 10 my.zome.
    @ IN MX 20 server1.my.zome.
    

    You can create 1 MX record or more. 10 and 20 server priority for input mails.

    Then you need to create an spf record. There are several options here. For example

    @ IN TXT "v=spf1 +a +mx -all"

    allows you to send emails from A domain records, then from MX domain records and prohibits from all other hosts.

    Theoretically, you can only create an SPF record with A but without MX and dont create MX DNS records. Although I have not tried this configuration.

    This is the minimum set after which you will get into spam, but at least the letters will reach.

    You also need to make a PTR record to avoid spam folder, but this is not possible on a dynamic IP.


  • interesting facts about LVM:

    1. You can make a volume snapshot of the system before a major change (for example, an update).

    2. You can enable caching and use HDD together with SSD cache

    3. You can build raid 0,1,5 directly on LVM (you still need modules from mdraid)

    4. Even without a raid, you can expand the partition beyond one disk to another or migrate the partition from disk to disk (without even disabling it)

    However, all this is done from the console and I do not know if there is a GUI.









  • On DNS you need A record if you have ipv4 only or A and AAAA records if you have ipv4 and ipv6.

    You DNS outside you home servers? If you have dynamic IP at home you can’t host DNS on home server.

    You have only 1 IP? You need port forwarding on you home gateway to home servers if you use somerhing like SSH. If you want access to something web based you need proxy. NGINX for example.

    How it exactly work:

    • Somewhere someone write youdomain.com in browser.
    • Browser ask local dns: who is youdomain.com
    • local dns ask another dns, and another and in one iteration request go to you dns. Or maybe some of dns have cached answer. But imagine that not.
    • You dns send answer youdomain.com is 111.222.333.444 for example. That is A record.
    • DNS work stop on that.
    • Browser send request to 111.222.333.444 with HTTP header “Host: youdomain.com” and some path. / or /something maybe.
    • Some balancer should get request and send in to right server in you home network.

    UPD: don’t show to internet something risky interfaces. Proxmox web panel or something like that. This is a real bad idea. For that type of services VPN extremely greatest. Send you DNS to public without protection not a great idea too. Including pihole. I think you will get into some botnet already on the 3rd day of work.