Computers & Hardware > Networking
Home network thoughts
burakkucat:
--- Quote from: Ignitionnet on September 05, 2017, 12:57:06 AM ---I'll put more detail on later.
--- End quote ---
I'm sure it will all become clear . . . eventually. ;)
niemand:
I don't want the ER-L to be doing too much DHCP detail. It doesn't seem to go well.
The EA9500 doesn't have a dedicated AP mode, so using it as a router is a good plan.
There are limits on amount of cabling available. Initially VM and BT WANs share a single cable, so VLANage needed. When either of them reach 500Mb/s throughput a second cable will be run, as the tromboning of the traffic will cause a bottleneck otherwise.
The alternative would be to connect them directly to the VM hub to pull publics, however that would break resiliency as they've only one possible route.
Switches running 4 VLANs for the most part: red, green, blue, yellow. The office switch also gets orange.
Red is the publicly addressed VM network.
Blue the BT <> ER-L network.
Green is the 192.168.0.0/24 ER-L LAN-side network.
Yellow is the 192.168.2.0/24 wireless / EA9500 LAN-side network.
Orange is a VLAN that is purely there to connect lan0 port on the SD-WAN device to the docking station up there. This goes through a switch so that the SD-WAN doesn't see the port of dropping and alarm every time the laptop is powered off.
There are 2 switches on the ground floor, one behind the TV taking the WAN feeds, another connecting to the EA9500 and to the other floors.
The link between the two ground floor switches carries red, blue and yellow. Red and blue for WAN transport, yellow to connect a couple of wired devices near the TV to the EA9500.
There's an 802.11ad LAG between ground and office, and between ground and top floor, 2 x GigE each.
The link between ground and office carries VLANs red and green. Red for public IP, green for ER-L LAN.
The link between ground and top floor carries yellow. No need for public IP, an AP is going up there which requires yellow.
Firewalling is handled by NAT in 3 places - BT modem/router, ER-L and SD-WAN's publicly addressed interface.
So this is why the design is as it is.
aesmith:
Out of interest what were the reasons for each of the two routing protocols? Also, what do you use as target(s) for your IP SLA? We seem to always be reviewing what makes a sensible target, I am still in two minds whether it's best to be checking only the local ISP or whether to test one or more targets in the wider Internet. It needs to be testing something that you don't access in normal use, or that you can go without during failover.
Navigation
[0] Message Index
[*] Previous page
Go to full version