Our News Team @ 11 with host Snot Flickerman


Yes, I can hear you, Clem Fandango!

  • 0 Posts
  • 211 Comments
Joined 3 years ago
cake
Cake day: October 24th, 2023

help-circle

  • On reddit if a post was deleted I could still interact with the thread, even if the content of the post itself was gone.

    So it was a bit more elegant, imho, as it allows continued discussion and being able to link to the thread without it being completely nuked.

    I also think that set expectations for how people expected it to work here, where the post contents and author would be nuked but the thread could still be accessed by hotlink.












  • Wow, usually people lose their shit and complain that Element is too complex and that me and the devs are being assholes asking them to use it… You know kind of like all the people here on the Fediverse who think we need to make it bigger and bring in everyone from everywhere and that the devs and users who defend them are awful for not focusing on user interface first and making it less confusing to choose a server…

    Anyway, thanks for being on team reasonable, because I’m with you on this 100%, but I can’t change how little people want to learn anything sadly so I make compromises with people who cant or wont learn how to do things. It sucks, people really don’t seem to understand that security and convenience are a balance, and every time people argue for shit to be easier they’re actually arguing for everything to be less secure. You sacrifice security for convenience, every time, and the opposite happens because you can sacrifice convenience for increased security measures. Security has to be complex by nature to be effective, and the core of Matrix is being a secure, encrypted protocol, which they have already actually put a ton of work into making easier for fucking normies. Yet, it’s never enough for people. Always screams of “It’s too complex! I hate thinking!”




  • Yes, consumer routers are much lower powered because they’re built to be a router so they can simplify it to the basics needed just for routing. The trade-off is that most off-the-shelf consumer routers don’t support V-LANs. The person you were responding to notes they have a Mikrotic device, which is one of the most popular series of devices for people to put OpenWRT on. (EDIT: Memory was foggy it’s actually devices with MediaTech CPUs is what I am thinking of) The major downside here when it comes to exposing devices to the internet is you lose the strong firewall. Part of why the OPNsense firewall is stronger than what a consumer firewall even with OpenWRT on it is because it isn’t just built to be a router, and being much beefier allows it to handle much more complex firewall rules and things like packet inspection or intrusion detection. OpenWRTdevice has a basic firewall which will do the job, for sure, but I am definitely on the side of using something a little bit more powerful for more firewall features and options. You’d probably still be relatively safe with OpenWRT/, but the low power of the devices may make them less robust depending on how many users you plan on having, in which OPNsense’s beefy nature makes it more robust for more data passing through.

    EDIT: Those Mikrotik devices OP is referring to are different than what I was thinking of, but they also have a good price point and are dedicated routing appliances thus lower power draw (many of them support Power over Ethernet). Their OS isn’t as open as any of the others though, however it offers a full featured enterprise grade router OS. A good choice for someone who isn’t as savvy off the bat, although you lose the powerful firewall.

    https://mikrotik.com/products/group/ethernet-routers

    They also have a demo of their RouterOS which seems like it’s very full-featured: https://demo.mt.lv/


  • Yeah, get your new OPNsense device fully set up through the guide, and it will act as a router and firewall. Once it’s ready to go, plug it in with ethernet to the Verizon router (with the ethernet connected to your OPNsense going into the WAN port) and make sure it’s picking up internet from the Verizon router. Once you’re sure it is, then go into your Verizon router’s settings and turn on bridge mode. The internet should auto-reconfigure for your new router to grab the IP from the modem by passing through the Verizon router.

    If for whatever reason this doesn’t work, you can regain access to the Verizon router by doing a factory reset (as you won’t be able to view it’s settings as it no longer has an IP on the network in bridge mode). So don’t be afraid of it, worst that can happen is a factory reset. Just back up your settings beforehand (either manually writing them down or exporting a config file) so you can restore them easily.


  • I am pretty sure both switches will need to be managed because you will need a trunk between the firewall and the first switch and a trunk between the first switch and the second switch. A trunk needs to be defined on both ends, and with an unmanaged switch in between the firewall and managed switch I am fairly sure that’s not possible.

    There are two types of ways VLANs communicate, and that’s through trunk ports and access ports. Trunking ports basically bundle all the VLANs together and send them to the next destination, such as another switch. Access ports are for giving access to end devices for a specific VLAN.

    So I am fairly sure you’ll need a trunk between Firewall and Living Room Switch and a trunk between Living Room and Office Switch. It’s been a minute since I did work with VLANs myself though, so others feel free to correct me.

    Related, I am also fairly sure the router itself will need VLAN support so while it’s understandable to not want to replace it, it may be a requirement and most consumer routers don’t come with VLAN support. Options are finding a router that supports alternative firmware like OpenWRT or DD-WRT which adds VLAN support or go whole hog and set up OPNsense or PFSense and essentially build your own router/firewall.

    EDIT: I just looked at the Home Network Guy’s guide you linked to. His guide is helping you build a combination router and firewall with OPNsense. If you really need to keep the Verizon router, check if the Verizon router has an option called “Bridge mode” where you can bridge the connection to your own router/firewall and basically turn the Verizon router into a dummy passthrough device that the network just sort of passes through and otherwise ignores.


  • Where do all the lovely self-hosters here turn when they want to chat networking or server hardware?

    I know this might seem like a strange answer, but… IRC channels on private torrent trackers. Many of the people on these sites actively have large and complex setups running. There often is a lot of talk about hardware for servers and networking in those IRC channels. Or at least there is on the trackers I am on.

    I know that’s not necessarily a helpful answer to anyone not already in the private torrent tracker community, since its often quite a task to get involved if you aren’t already. However, it’s one that I have had great success with, personally. To anyone who already is on a private torrent tracker, if you haven’t checked out the IRC, give it a shot and see.

    Oh and don’t forget you can self-host The Lounge for a self-hosted web-based IRC client.