Seems very strange that it gets the local routes but not the remote routes - not sure how RIP works as it's been a long time since I've touched it. Most everyone does OSPF.
Make sure you have the latest Ubiquiti firmware - a LOT of posts regarding multicast and routing protocols were addressed. http://www.ubnt.com/support/downloads Also, welcome to the ranks of poster! Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 On Tue, Jul 13, 2010 at 6:52 PM, Nick Olsen <n...@brevardwireless.com>wrote: > Every ubnt ptp backhaul we have is running apWDS/stationWDS and we pass > OSPF over them all day, Both ways. > What firmware are you using? were running 5.2.1 Beta 2 > But we upgrade as soon as they come out, So we should have hit the bug at > one point... > > Nick Olsen > Network Operations > (321) 205-1100 x106 > > > > ------------------------------ > *From*: "Dennis Burgess" <dmburg...@linktechs.net> > *Sent*: Tuesday, July 13, 2010 6:40 PM > *To*: "WISPA General List" <wireless@wispa.org> > > *Subject*: Re: [WISPA] Problems with UBNT Rocket + Mikrotik combo > > > yep, known bug with UBNT, make sure you have the latest firmware as > well, as even if you setup a WDS link, it would not pass OSPF protocol > one way. > > ----------------------------------------------------------- > Dennis Burgess, CCNA, A+, Mikrotik Certified Trainer > Link Technologies, Inc -- Mikrotik & WISP Support Services > Office: 314-735-0270 Website: http://www.linktechs.net > LIVE On-Line Mikrotik Training - Author of "Learn RouterOS" > > -----Original Message----- > From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On > Behalf Of Justin Mann > Sent: Tuesday, July 13, 2010 5:17 PM > To: wireless@wispa.org > Subject: Re: [WISPA] Problems with UBNT Rocket + Mikrotik combo > > > > I will attempt that. It didn't occur to me before; Star backhauls have > no WDS configuration as it automatically puts clients in WDS mode if > they are compatible, but it's an obvious reason as to why it would > happen. Thank you for your assistance. > > On 07/13/2010 03:14 PM, Jason Bailey wrote: > > change to ap-wds and sta-wds ;) > > > > --- On *Tue, 7/13/10, Justin Mann /<justinl...@unwiredwest.com>/* > wrote: > > > > > > From: Justin Mann <justinl...@unwiredwest.com> > > Subject: [WISPA] Problems with UBNT Rocket + Mikrotik combo > > To: wireless@wispa.org > > Date: Tuesday, July 13, 2010, 6:08 PM > > > > Hello, > > > > My name is Justin. I work for Mark Nash, whom I'm sure you have > heard > > from before. I'm his company's engineer. This is my first time > > writing > > into or reading the WISPA list; Mark suggested that some people > here > > might be able to help me with a particular issue we have been > > experiencing. If anyone here has suggestions as to what the issue > > would > > be, I would appreciate it. > > > > Here is my scenario. We have two sites; we will call them "A" and > "B". > > > > At site "A" we have a Mikrotik router, running RouterOS v4.5. At > site > > "B" we have 3 StarOS access points. > > > > Each access point has a /30 on it's ethernet side, shared with the > > router, and uses RIP. We have a bridged StarOS backhaul between > > them. It > > works pleasantly; the router has never failed to pick up the > remote > > networks on the access points before. Recently, we have wanted to > > replace our StarOS backhauls with UBNT Rocket backhauls. > > > > When we attempted to do this, we encountered a very strange bug > > with no > > workaround I could find. When we switch to the Rocket backhaul, we > > can > > no longer communicate with remote networks. Now, both the APs and > the > > Router are still running RIP - and you can look at the RIP routing > > information and see that the router has indeed received the > > downstream > > routes. However, we can only communicate with the /30s. If we > > attempted > > to reach the remote networks, it returns as unreachable - and if > we > > attempt to trace those networks, it seems that the Mikrotik router > is > > attempting to route traffic to an internal-only address assigned > > to the > > Rocket backhaul devices. > > > > Example. Network 1.0.0.0/24 is on the far side of Access point A. > > With > > the StarOS bridged backhauls, the Mikrotik router successfully > adds a > > route to its kernel routing table to route 1.0.0.0/24 through the > /30 > > assigned to the access point. In our failure scenario with the > > Rockets, > > the same route is successfully received via RIP, and you can see > that > > 1.0.0.0/24 is still pointing correctly to the /30. However, when > the > > router actually attempts to forward a packet, it forwards the > > packet to > > an internal-only address assigned to the Rocket Backhauls, an > address > > that does not appear ANYWHERE in the router's routing table. > > > > What makes it more difficult is that even static routes do not > > work. If > > RIP is disabled on the respective devices, and a static route is > > entered, it still fails to work - it even fails to work if you > > completely remove the internal network from the router, and leave > > only > > the /30s on the interface, with a static route. The router still > > cannot > > communicate with downstream networks - only the /30 directly > > connected > > to it. this only happens with the UBNT rocket AP is in place. > > > > Currently, the rockets are configured as bridges, in AP and > Station > > mode, with AirMax enabled. > > > > If anyone has any advice I would appreciate it. > > > > > > > ------------------------------------------------------------------------ > -------- > > WISPA Wants You! Join today! > > http://signup.wispa.org/ > > > ------------------------------------------------------------------------ > -------- > > > > WISPA Wireless List: wireless@wispa.org > > <http://us.mc525.mail.yahoo.com/mc/compose?to=wirel...@wispa.org> > > > > Subscribe/Unsubscribe: > > http://lists.wispa.org/mailman/listinfo/wireless > > > > Archives: http://lists.wispa.org/pipermail/wireless/ > > > > > > > > > > > > > ------------------------------------------------------------------------ > -------- > > WISPA Wants You! Join today! > > http://signup.wispa.org/ > > > ------------------------------------------------------------------------ > -------- > > > > WISPA Wireless List: wireless@wispa.org > > > > Subscribe/Unsubscribe: > > http://lists.wispa.org/mailman/listinfo/wireless > > > > Archives: http://lists.wispa.org/pipermail/wireless/ > > > > ------------------------------------------------------------------------ > -------- > WISPA Wants You! Join today! > http://signup.wispa.org/ > ------------------------------------------------------------------------ > -------- > > WISPA Wireless List: wireless@wispa.org > > Subscribe/Unsubscribe: > http://lists.wispa.org/mailman/listinfo/wireless > > Archives: http://lists.wispa.org/pipermail/wireless/ > > > > -------------------------------------------------------------------------------- > WISPA Wants You! Join today! > http://signup.wispa.org/ > > -------------------------------------------------------------------------------- > > WISPA Wireless List: wireless@wispa.org > > Subscribe/Unsubscribe: > http://lists.wispa.org/mailman/listinfo/wireless > > Archives: http://lists.wispa.org/pipermail/wireless/ > > > > > -------------------------------------------------------------------------------- > WISPA Wants You! Join today! > http://signup.wispa.org/ > > -------------------------------------------------------------------------------- > > WISPA Wireless List: wireless@wispa.org > > Subscribe/Unsubscribe: > http://lists.wispa.org/mailman/listinfo/wireless > > Archives: http://lists.wispa.org/pipermail/wireless/ >
-------------------------------------------------------------------------------- WISPA Wants You! Join today! http://signup.wispa.org/ -------------------------------------------------------------------------------- WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
