• 0 Posts
  • 16 Comments
Joined 3 years ago
cake
Cake day: July 1st, 2023

help-circle







  • I have been using various Debian-flavored Linux variets for several years in both desktop and server.

    Recently I got a System76 laptop for work because they are food quality, repairable, and mostly “just work”. The main issue I have run into is Cisco Secure Client (formerly AnyConnect) simply breaks in Ubuntu/PoP. If I do get it to install by ignoring Cisco’s shitty instructions, it either won’t route traffic once connected or corrupt itself attempting to auto-update.

    It is purely a Cisco issue because they don’t put much effort into their Linux VPN software. Other VPNs not only work easily, but can also integrate into PoP Cosmic. Cisco and their restrictive nature just make the process impossible.

    Heck, you can’t even download their VPN software without a Cisco contract. So if my company doesn’t provide the correct version or distro package, there is no way for me to get it. Since most people on the helpdesk don’t know anything about Linux, they simply provide the generic Linux.tar.gz file instead of the DEB or RPM files.

    I gave up and installed Windows on a second NVMe.



  • I have used Docker Swarm in my homelab for years without big issues, you just have to be aware of its limitations. For example, I use SWAG for my reverse proxy and it works better as a compose deployment on an individual docker node because then it can identify incoming IPs. All of the backend communication runs on internal networks, which helps isolate them.

    I like using Swarm at home because it is simple and easy while providing good scalability and security (yes, I know podman would be more secure, but I haven’t taken that plunge yet).

    That being said, Docker Swarm isn’t used in the industry much. So if you are looking to expand on your IT skills, K8s is the way.


  • Each network is different. I did this for my network which has multiple subnets and internal DNS servers sitting on the “server” subnet. The “server” subnet is excluded, since devices in there are more tightly controlled (and it would create a routing loop).

    Granted, it may not be the best way, but here is how I did it:

    • Create Firewall Alias group (type: hosts) with IP addresses of internal DNS servers (PiHoles, in my case).
    • Create Firewall Alis group (type: URL Table IPs) for external DNS over HTTPs servers (content: https://raw.githubusercontent.com/jpgpi250/piholemanual/master/DOHipv4.txt)
    • Create NAT Port Forward to route all traffic on port 53 to the alias (TCP/UDP, source: network, destination: !network on port 53, redirect target: DNS alias, redirect port: 53) for each network
    • Each network (except the “server” network) has the below rule set (order is important)
      • Allow TCP/UDP 53 to DNS alias
      • Drop all TCP/UDP 53
      • Drop all TCP/UDP 853
      • Drop all TCP/UDP 443 traffic to external DNS over HTTPs alias group

    Since NAT port forward rules are processed before interface/network rules, any device using port 53 for DNS (regardless of the IP address they have set) will automatically (and transparently) get redirected to my PiHole servers. The drops are in place so devices that try to use other common DNS methods are blocked. Generally, those devices will then default to the DHCP DNS servers.

    I have been running this config for a few years and have found a few downsides:

    • You can’t visit websites that have the same addresses as their DNS hosts, ie: https://1.1.1.1
    • Although https://github.com/jpgpi250/piholemanual is updated regularly, it has contained the odd false-positive (GitHub pages had a weird overlap at one point) breaking legitimate HTTPS traffic
    • My PiHole servers are configured to allow queries from all origins (theoretical security risk)

    Hope this helps! And remember to be careful when messing with DNS and clear those caches when testing.






  • Nomad64@lemmy.worldtoSelfhosted@lemmy.worldProxmox Clusters worth it?
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    3 years ago

    The primary reason to virtualize is to maximize the “bang for your buck” on your hardware. Containers are great, but have their limits.

    So long as you have a desire to learn it (and the budget), I say dive in with Proxmox and see how you can put that hardware to use. VMWare ESXi is more common in a business/enterprise setting, but costs money to for anything beyond the basic functionality after the evaluation period.