As promised I'll explain everything very simplified. Click on the images to see them more clearly, as some lines are cut.

Let's assume this setup



So in this, A and B are endpoints. Notice that I also put in the ports.

So the Hub is configured as 0->1->2->0 let's say. That's by default anyway.

So now let's assume the Mainframe is sending a packet to endpoint A.
The packet starts at the mainframe, goes through port 0 right?
Since our configuration is as above, then the packet enters at 0 and exits at 1 (0->1)



So the packet will reach endpoint A. Simple.



But now let's assume the packet is intended for endpoint B. The same as above will happen, however, it will reach the wrong endpoint. So it will bounce back.

However, this time, it will enter the hub through a different port.



So since our Hub is configured 0->1->2->0, and now it's entering at port 1, it will follow the line 1->2 therefore exit at port 2.



So THEN it will reach endpoint B.

This is what happens with just 2 endpoints and 1 hub. In the game you will have a ton of hubs and endpoints to manage, so the diagram would look more like:



So yeah, you will have to watch these hubs separately, to connect them and configure them appropriately. But now let's go to filters next.

So now that we've seen how hubs work, let's see filters real fast. Let's assume this setup:



See that "super long way down" line? You can assume that this line is very long. Therefore, like we said before, a packet intended for endpoint Aa or Ab, will travel down that line, reach Ba, travel back, reach Bb, travel back, reach Bc, travel back, reach the original hub, and THEN travel to Aa or Ab.

Sure, you might configure the first hub to favor the shorter line first (and you should) but that's not gonna help when the packet is already a lot further in the network.

So this is where a filter comes in play.



See what I wrote there? If a packet's adress doesn't start with B, send back. Therefore, in this simple scenario, when the packet enters the filter, it's gonna ask this question. Do I have to go this super long way down? Will it matter? Or will I just come back anyway? Lol.

So the point of this filter is to avoid going this way, if it's not intended to reach any of those endpoints.

And since the packet might attempt to go back up due to the hub, and the network will get more complicated than this anyway, we could add another filter for the packets that bounce back, with the statement "If a packet's address doesn't start with A, send back.



Note that this time I added a circle, to indicate the port that it checks (and also corrected the typo lol). We want the packets going down to start with B, and the packets going up to start with A.

So now, let's use real game indicators.



This is actually something I've used.

So this is the same logic as above. Packet reaches the first filter, filter asks, where are you going, packet says 0.0.0.1, so filter says "what are you doing going down here, go back". Similarly a packet that is trying to go back, the second filter will ask it, it will say an adress like 0.0.3.x so the filter will say "Why are you even trying to go back there, you came all this way, go back to the hub" kinda.

Obviously, there are more parameters to Filters, especially once you upgrade them, such as what to do if there is packet collision. I'm not covering these because it gets more complicated, and it's really self-evident what these do once you get the basics.