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

help-circle







  • Its more about the hardware than software.

    • Able to have enough processing power to utilize the max speed that my ISP provides, while having IDS/IPS and other services enabled.
    • Port segregation so that each port can be on its own network with a full speed backplane.
    • PoE capabilities
    • SPF ports to utilize both fiber and copper connections
    • Multiple networks across many wireless access points

  • I freakin love OpenWRT. I used it for a solid 5-6 years on some consumer grade routers and learned a lot about managing networks.

    Ive since moved to more powerful enterprise network gear because OpenWRT opened that door for me and taught me what is possible. I might not ever go back to it, but I will always recommend OpenWRT to people who want to rice out their routers and get the most out of it.




  • 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 UDM 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.






  • Good read.

    I would just like to add some additional information that favors changing your SSH port to something other than the default. When crawlers are going around the internet looking for vulnerable SSH servers, they’re more than likely going to have an IP range and specifically look for port 22.

    Now can they go through and scan your IP and all of its ports to look for the SSH service? Yes. But you will statistically have less interactions with bad actors this way since they might specifically be looking for port 22.