4 ms·
The more obvious (to me at least) way to solve this is to not mix broadcast domains/subnets on a switch without keeping them in separate VLANs. I would assume t
by xxpor 4y ago
The more obvious (to me at least) way to solve this is to not mix broadcast domains/subnets on a switch without keeping them in separate VLANs. I would assume the router and the NAS box would support tagging/untagging, and then you could keep the ISP network on the default untagged vlan.
- deleted 4y ago[deleted]
- archi42 4y agoThat's exactly the right solution to the issue. As it stands, any client can talk to the modem and mess up connectivity. And as it turns out, simple switches with VLAN capability aren't expensive either. The magic of VLANs then allows putting everything on one physical interface for the router. This essentially turns the switch into a port multiplexer for the firewall (10GBe comes in handy there). Also useful in case the router is a VM, since only a single NIC needs to be passed to it.
- jaredhallen 4y agoIt's not specified what subnet the switch on eth3 is on, but assuming they're on the 10.42.42 network, then I wonder why not just plug the router into the modem, then add a sufficiently large switch behind the router to hold everything on the 10.42.42 block? Unless I'm missing something.
- toast0 4y agoHaving one subnet per broadcast domain is nice, but not always achievable with the equipment at hand. I wonder if it would work better if you used a single interface on the Linux box for both subnets? That's how I've always run multiple subnets and it seems to work ok? Having two interfaces on the same broadcast domain that aren't combined into an aggregate interface seems to be asking for trouble anyway? Although, if it's just the Linux box and the NAS on 10/8 (or whatever), you could connect linux:eth2 to nas, perhaps? There's a lot about this particular network that hasn't been described.