One of the first rules is to never use VLAN 1. Ever Never. MT does snooping on it (as do many other brands) and it does nothing but make issues.
As to why the other is not working, Change the VLAN first. IIRC I had the same issue with a quick setup using RB750s with a RB250 between them. Then do packet sniffing on the port to see if the tagged ID packets are getting to the other side. If they are check MTU and etc settings. Exactly what hardware is between R2 and R3 On Fri, Aug 3, 2012 at 8:11 PM, Rory McCann <[email protected]> wrote: > Hi guys, > > So, today has been one of those days. The fans died in my core router and I > didn't have a spare on hand or configured. In order to get things back > online for my company, I simply set up an RB750 with some of the basics of > our config (using backups as reference). > > I've got 90% of the things working, however for whatever reason, static > routes are broken. I have two routes that need to be in place - one for a > subnet that is behind a router on a LAN interface and another for a subnet > that gets created when the router dials up a PPTP connection. Seemed pretty > straight forward and it worked like a champ before. Not so much now. :( > > I've found that I have one-way traffic. The remote routers can > see/ping/whatever the devices and IPs at the core, but the new "temporary" > core router can't ping either of these remote routers that act as the > gateways for these routes. > > I've looked over the configs about 200x now and I am sure they are correct, > I just can't figure out why they aren't working. It's especially frustrating > that one-way communication is working. Here's a basic run down of the config > > Router 1 (core) > ether1 is WAN > ether 2 has two VLANs, vlan1=192.168.1.0/24, vlan15=192.168.15.0/27 > ether 3 had two VLANs, vlan25=192.168.25.0/27, vlan35=192.168.35.0/27 > > Router 2 (secondary) > It's connected to the network on VLAN1 using a 192.168.1.x address. Core > cannot ping this device, however other devices on VLAN1 can communicate > without issues. > It has a secondary network 192.168.55.0/28. Neither core router or VLAN1 > devices can ping. > > Router 3 (remote) > Connected via PPTP, assigned an address in 192.168.2.0/28 > Static route automatically is added via secret on the core router. Network > is 192.168.88.0/29 > Can ping anything on VLAN1 from this device (static "return route" works > fine). Core and VLAN1 cannot ping anything behind this device. Can't even > ping 192.168.2.x address assigned to the PPTP client. > > I've rebooted things. I've removed and recreated routes and I'm absolutely > stumped. I can't figure out what is happening. Ideas? > > -- > Rory McCann > Minn-Kota Ag Products > P: 701-403-4877 | E: [email protected] > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > <http://www.butchevans.com/pipermail/mikrotik/attachments/20120803/52bb16c4/attachment.html> > _______________________________________________ > Mikrotik mailing list > [email protected] > http://www.butchevans.com/mailman/listinfo/mikrotik > > Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS _______________________________________________ Mikrotik mailing list [email protected] http://www.butchevans.com/mailman/listinfo/mikrotik Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS
