Does the wireless access point basically connect a computer to that network, where as a wireless router is a router with an access point?
Wireless Access Point
- Thread starter macrules34
- Start date
Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
If I have 2 physical networks and 1 WAN I take it I would need 1 router and an access point in each physical network?
Hm, what do you mean by "physical network" here? Do you intend any logical separation between them (like, some machines on one net can't reach some machines on the other one)? If you want to pass traffic selectively between two networks then in the general case you need a router between them; though if your needs are simple, VLAN-capable ethernet switches might be good enough.
Likewise, you might or might not need multiple access points depending on what it is you want to do. (Not to mention whether you are trying to cover an area large enough that a single AP physically can't reach it all with decent signal.)
You really need to give a lot more detail if you want a useful answer.
Likewise, you might or might not need multiple access points depending on what it is you want to do. (Not to mention whether you are trying to cover an area large enough that a single AP physically can't reach it all with decent signal.)
You really need to give a lot more detail if you want a useful answer.
All networks (3 networks, Network A and B can connect to each-other, Network C (Mgmt) can access A & B, but A & B can’t access C) in the same room, each has its own switch. And all must be able to connect to the internet.
Hmm ... if you want one-way access like that, I think you need a router to enforce it. VLAN switches can enforce hard separation between different subnets, but what you seem to want here is that a TCP connection A<=>C can exist if a node on C initiates it but not if a node on A initiates it. That requires stateful filtering, which is generally router functionality.
You might still want VLAN-aware switches and APs though, so that one physical infrastructure can serve all these networks. In my own home network, there's switches and APs serving three VLANs: main, guest, and IoT. The switches and APs enforce strict separation between those VLANs, but my router will forward connections between two VLANs as long as something on the main VLAN initiates it. So I don't need separate wires, switches, or APs for different logical networks. And there's only one router, which also handles connections out to the internet.
I'm still unclear on what's the distinction between networks A and B in your description. They sound like they should be one logical network.
You might still want VLAN-aware switches and APs though, so that one physical infrastructure can serve all these networks. In my own home network, there's switches and APs serving three VLANs: main, guest, and IoT. The switches and APs enforce strict separation between those VLANs, but my router will forward connections between two VLANs as long as something on the main VLAN initiates it. So I don't need separate wires, switches, or APs for different logical networks. And there's only one router, which also handles connections out to the internet.
I'm still unclear on what's the distinction between networks A and B in your description. They sound like they should be one logical network.
Network A would be a group of Mac Pro's running MacOS with UTM virtualization. Network B will have 9x HP T740's that will run proxmox with various VMs and Containers. Network C is used to have the management activities.
So ... what is the point of separating those two groups of machines, especially if you want them to be able to reach each other? I can understand wanting a locked-down management VLAN, but I'm still not seeing the reason to draw a line between A and B.
Why? Seems like you're merely adding complication to your life. You already said you didn't want any actual logical separation between those networks.
Meh. To my mind, the interesting thing about a WAN interface is exactly what firewall rules will you use to keep baddies out of your LAN while still doing what you need to do. This example of two LANs that you want fully open to each other raises exactly none of the hard problems. Still, you evidently have your own agenda, so feel free to get on with it.
Actual home lab stuff! fantastic, love to see this type of experimentation!
If you are going to go with physical switches for A, B, and C and they are all in 1 location, get yourself a "management" PC that supports remote access (RDP and/or VNC and ssh). the mgmt pc has three network interfaces, each connected to A, B, and C, you can then get the POV of each side and access the trusted interface of the router and/or firewalls you use to connect A and B. Use ethernet between the firewalls.
edit -
Oh and if you want to get fancier, get a router that can sit between the firewalls of A and B.
POV is Point of View. If you want to understand how wans, routing protocols and the like operate then making observationsfrom each network (point of view) while you experiment may be useful (if you learn in this fashion). Hence my suggestion for a three interface system.
edited for various stupid spelling, grammar, and auto correct stupidity.
I think it really depends on what you are trying to simulate and then learn.
my first bit of advice is start simple then do more as you find areas you want to experiment with or learn about. voyage of discovery and all that.
as far as Internet connectivity... going to depend on whether your ISP issues multiple public IP's or a single one. You may also want to decide early on whether you are learning about ipv4 or ipv6, trying to do both without having a basic handle one of them may be frustrating. YMMV.
you can simulate WAN space using private IP's. you could have your Internet firewall that connects to. your ISP. that could connect that to a central router. the central router could have a connection to networks A, B, C. Your internal firewalls can connect to your central router.
others have suggested learning a bit about "smart" switches... those can be layer 2 (osi stack model), and/or layer 3 (sometimes or more). if they are layer 3 then you can think of them as a router, some smart switches (like an ICX6610) can run many of the protocols you might run in a public or private WAN environment or even on the internet-web-thingies... ;-)...
my next advice: start small, break it, fix it, learn, add more networks, add more firewalls, add another network, firewalls, or routers rinse wash repeat.
there isn't really a recipe for this and there really isn't an overall how-to per se (unless you look at vendor certification tracks for example cisco's, ccna, ccnp, ccie etc.), but there is information scattered all over and if book learning or videos are your thing, then Cisco, Brocade, others have plenty of documentation, and videos out there to watch.
my last bit of advice is foundation & fundamentals are important.
I think it really depends on what you are trying to simulate and then learn.
my first bit of advice is start simple then do more as you find areas you want to experiment with or learn about. voyage of discovery and all that.
as far as Internet connectivity... going to depend on whether your ISP issues multiple public IP's or a single one. You may also want to decide early on whether you are learning about ipv4 or ipv6, trying to do both without having a basic handle one of them may be frustrating. YMMV.
you can simulate WAN space using private IP's. you could have your Internet firewall that connects to. your ISP. that could connect that to a central router. the central router could have a connection to networks A, B, C. Your internal firewalls can connect to your central router.
others have suggested learning a bit about "smart" switches... those can be layer 2 (osi stack model), and/or layer 3 (sometimes or more). if they are layer 3 then you can think of them as a router, some smart switches (like an ICX6610) can run many of the protocols you might run in a public or private WAN environment or even on the internet-web-thingies... ;-)...
my next advice: start small, break it, fix it, learn, add more networks, add more firewalls, add another network, firewalls, or routers rinse wash repeat.
there isn't really a recipe for this and there really isn't an overall how-to per se (unless you look at vendor certification tracks for example cisco's, ccna, ccnp, ccie etc.), but there is information scattered all over and if book learning or videos are your thing, then Cisco, Brocade, others have plenty of documentation, and videos out there to watch.
my last bit of advice is foundation & fundamentals are important.