A message from our CEO about the future of Stack Overflow and Stack Exchange. Read now.

Hot answers tagged

7

As Jesse P explained, hubs do not have MAC addresses, but multiple devices connected to a hub would mean multiple MAC addresses on the switch interface, and what you suggest would detect that and prevent a situation where a hub is attaching multiple devices to a single switch interface. Unfortunately, it will be unable to detect the hub or a hub with a ...


6

As per IEEE 802.3 Clause 38, 1000BASE-SX requires OM2 (500 MHz·km for 850 nm) for max. 550 m reach. As a superset, OM4 is fine as well (there's little point buying OM2). With 10GBASE-SR the reach over OM4 is reduced to 400 m, so you're also good for an upgrade later on. There's also OM5 but it's only for higher speed WDM, not for longer reach with 850 nm. ...


3

Merakis are managed via a centralized system hosted in the cloud. DNS is the way by which the Meraki endpoints (...whether switches, firewalls, AP's or cameras) connect back to that cloud system. It's also key to said endpoints being able to reach alternate management points should failures or excessive load occur in Meraki's infrastructure.


2

As it turns out, Passthrough Mode on Meraki will not work behind an ASA. The Meraki will not forward traffic through the ASA, so TCP handshakes are broken, ie the VPN traffic sends SYN straight to the networked machine, but the networked machine responds back through the ASA, and the ASA drops the packets because it didn't get the first SYN. (The Meraki ...


2

"LAN workstation" is in the 192.168.213.0/24 subnet - the same subnet you're using for "BAY x LAN". That is a very bad design. Unless you are using destination NAT and source NAT between those locations, no communication is possible. Likely, you're using destination NAT from LAN workstation to reach "Device N", but without source NAT "Device N" tries to ...


1

I believe I have found the problem based on how you have described your configuration, but your description wasn't sufficient to provide the information I needed to notice the problem. I ended up creating a new demo account with Meraki, because I don't currently have an active Meraki installation I can access (my own demo accounts are tied to hardware with ...


1

You're looking for "1:1 NAT": https://documentation.meraki.com/MX/NAT_and_Port_Forwarding/Port_Forwarding_and_NAT_Rules_on_the_MX


1

Trunks are not appropriate for your access interfaces where you connect PCs, printers, etc. Most end-devices do not understand VLAN tags, so they will drop traffic from trunk interfaces. What you want to do is configure a trunk between the router and switch, and between the switch and any other switches. For all the other interfaces, you configure access ...


Only top voted, non community-wiki answers of a minimum length are eligible