Community
  • About AlexGregoire
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Re: Welcome! Please introduce yourself.

by in Community Tips & Tricks
‎07-12-2019 11:17 AM
3 Kudos
‎07-12-2019 11:17 AM
3 Kudos
Hello, I'm here as Alex.  I'm a network engineer for a rural governmental partnership with over a 100 local offices spread across my district. I'm administrate the entire WAN from end user to the home campus border. As the sole networking specialist; in one day I can be called to troubleshoot a WAN connection, plan a new building addition's communications wiring, enforce wireless usage standards, and install an unplanned cloud-based phone. And each office is different. We've been using Cisco VPN to connect the branch offices to the home campus - we're switching to Meraki because I frankly don't have enough time to admin a Cisco system, and we need a system that my colleagues can access and make changes to that's fault-tolerant, flexible, and easily understood.  As I write this, we've put a handful offices on the system, and we're ironing the last of the beta bugs. A fun fact . . I have a degree in art. So don't be surprised that I prefer to do my documentation in visuals. ... View more

Re: Shared Network dilemma

by in Security / SD-WAN
‎07-10-2019 01:41 PM
‎07-10-2019 01:41 PM
The 2nd network's admin (a contractor) says that while the SonicWall can do VLANs, they're not configured for it. I confirmed the static LAN IP and their static routing is still 192.168.0.135 as before with the Cisco, so using the same settings on Meraki should work. <br>Troubleshooting late yesterday he attempted to sidestep the VLAN tagging issue by making a VLAN 2 on his router with the subnet 192.168.1.0/24, bridge interface IP 192.168.1.135, and having it static route everything from 192.168.0.0/24 both ways, leaving the original network unchanged and un-disrupted. Still no joy. ... View more

Re: Shared Network dilemma

by in Security / SD-WAN
‎07-09-2019 07:36 PM
‎07-09-2019 07:36 PM
The 1841 was used only for our network, LAN 10.0.0.0. Clients on their network, 192,168.0.0., could print to 10.0.0.0 printers. ... View more

Re: Shared Network dilemma

by in Security / SD-WAN
‎07-09-2019 07:34 PM
1 Kudo
‎07-09-2019 07:34 PM
1 Kudo
"they" = I'm assuming this is the bridging port from our network to theirs. Which is yes, the bridging port is set to VLAN 2. Or does every port that services a 10.0.0.0 client who needs access to the file server in 192.168.0.0 needs to be set to VLAN 2 as the native? ... View more

Shared Network dilemma

by in Security / SD-WAN
‎07-09-2019 01:32 PM
‎07-09-2019 01:32 PM
I have branch office using a 10.0.0.0/24 LAN subnet with a Meraki MX appliance. The LAN connects back to the home office on VPN and everything works great. The problem is that they share physical space with a cooperative 2nd office that I'm not the admin of, and the two offices share printers and a local NAS file server. The 2nd network is a SonicWall on a flat network LAN of 192.168.0.0/24 with no VLANs defined.   The previous Cisco 1841 router simply did this to make it work: interface FastEthernet0/0 description 2ND LAN Interface ip address 192.168.0.135 255.255.255.0 no ip redirects no ip unreachables no ip proxy-arp ip virtual-reassembly duplex auto speed auto   I've tried defining the 2nd network as VLAN 2 with the correct LAN & same IP, verified the physical port connection, made sure the port is trunking, but no joy. I've got to be missing an obvious solution here because it's not supposed to be this hard. (or so I'm told) ... View more
© 2020 Meraki