• 0 Posts
  • 102 Comments
Joined 2 years ago
cake
Cake day: June 16th, 2023

help-circle

  • I can think of some commercial audio processors that can help with that, but they are super pricey.

    I can’t think of a linux application that has this capability. If there is something out there that offers AEC (acoustic echo cancellation) on linux with two mic inputs, id also be interested.

    One way to help with this as far as inexpensive hardware is to make sure you’re using cardioid dynamic microphones, and not omnidirectional condenser microphones. Cardioid dynamic mics generally pick up audio directionally, like from the “front”. You have to be right up on the mic in order to have it record any type of audio. They generally wont pick up environmental sound from anything more than a few feet away. You can just point them away from noise you don’t want to pick up.






  • You need VLANs if you want separate networks on the SAME router. But if you have separate routers, then you don’t need VLANs.

    You will need two wireless access points. If the router you mentioned has two wireless access points built in, then just set one to connect to the shared network, and the other will act as an AP for your private network. Then the router can be configured to send WAN traffic out of the shared network AP.

    If you use a router that only has a single AP built in, then you will need to purchase and additional AP to plug into one of your router’s LAN ports so that it has two total.

    Some routers might have the ability to create multiple wireless networks on one router, but be sure the hardware can handle the load. I know my ubiquity UDR can create up to 5 wireless networks on that single device before you run into performance issues.


  • Honestly, if you’re using your own router, you won’t need to worry about VLANs as long as your router separates your private network from the shared one.

    For example, if the shared network is 192.168.0.0/24, you can make your private network 192.168.5.0/24 and have your router’s firewall block incoming traffic from 192.168.0.0/24. Only allow WAN traffic out, and allow return traffic.

    Then have your router or connected server act as the authoritative DNS and DHCP servers for the 192.168.5.0/24 private network.

    One wireless AP will be used in client mode to connect to the 192.168.0.0/24 shared network. The other wireless AP will be used as an access point for other devices to connect to the 192.168.5.0/24 private network.








  • There are quite a few reasons to avoid flatpaks tbh.

    • You have no control over the dependencies. A flatpack can include a very old dependency and there is nothing you can do about it. You are at the mercy of the developer.

    • Many Flatpak applications available on flathub are not effectively sandboxed by default. Do not rely on the provided process isolation without first reviewing the related flatpak permission manifest for common sandbox escape issues.

    • Running untrusted code is never safe; sandboxing cannot change this. It can be a false sense of security.

    • It is generally not a good idea to run unattended updates via systemd, as the applications can get new permissions without the user aware of the changes. See this blogpost for examples

    • Flatpak does not run on the linux-hardened kernel unless you do additional kernel modifications that could have negative security implications.