networkingTreunas involves several ISPs, load balancing, and potentially additional features...
networkingTreunas involves several ISPs, load balancing, and potentially additional features...
The VLAN configurations look unusual. Are you handling two ports for the clients? What are the routing settings between the primary VLAN and the storage VLAN? Are all clients linked to the storage VLAN? If yes, adding another VLAN here doesn’t seem necessary. It seems like you’re connecting two gateways to the switch, which could create problems. I’d expect a router or firewall that supports multiple ISPs.
I don't get any of this. It seems Gemini gave me a confusing message. I checked again with Gemini. The site details show one WAN port, three WAN/LAN ports, and one LAN port. It looks like the main ISP connects to the first WAN port, while two of the three WAN/LAN ports send traffic to it, and the LAN port goes to a managed switch. I set up a VLAN for Truenas Storage and configured the rest of the PC. That should be the main idea. I'm new to networking, so I asked the forums in case someone with similar experience could assist.
It’s wise to understand how it functions before implementation. The diagram showing a second ISP router connected directly to the switch is usually not ideal. I’d prefer to skip managing VLANs and subnets until I grasp the basics or understand the purpose better. I’d also consider stopping AI tools since they aren’t well equipped for proper network setup.
This diagram is confusing and doesn’t make sense. You need to draw your own connections. If something breaks and you’re unsure how to fix it, it’s a big problem. What does the green arrow mean between the server and the PC? Are you using a physical cable? If you can’t understand this network layout, you shouldn’t be using it. Why are you trying to set up multiple VLANs on the same subnet?
For a straightforward setup, AI seems to complicate things unnecessarily and create confusion. Your configuration isn’t too complex. In short, you need a basic gigabit LAN where one device acts as a NAS and connects via an uplink to a multi-WAN router. You’re likely aiming for policy-based routing, meaning certain clients should follow specific WAN paths. The ER605 supports Omada, allowing many configurations through the Omada dashboard—policy routing included. You probably don’t need VLAN switches unless you want network segmentation, since Omada’s policy routing can handle IPs.
Yes, that approach works. You won’t need a managed switch and can manage VLANs using Omada with an unmanaged switch. It’s practical to test it first before finalizing. Two separate VLANs can still interact if properly configured, and you might consider simplifying by focusing on load balancing rather than strict VLAN policies.
You keep mentioning VLANs without showing their purpose. I understand you're unsure why they matter, especially since you've been told they're unnecessary. Can you plan to implement VLANs using the same equipment? Given Omada's capabilities, it seems feasible. The policy-based routing setup is straightforward in Omada. Did you miss the link? It's already included in the platform. You'll still need to arrange load balancing from the start, but policy routing can be configured later.
The Policy Routing link wasn’t included. The network is configured correctly, and everything else functions properly except for the connection between one ISP and Omada.