For your management /29, is this correct? 10.1.1.0/29
RouterA = 10.1.1.1/30 RadioA = 10.1.1.2/29 RadioB = 10.1.1.5/29 RouterB = 10.1.1.6/30 The /30 you use for routing is public, correct? On Thu, Aug 11, 2016 at 5:10 PM, Cassidy B. Larson <[email protected]> wrote: > A lot of times we want to login to side “B” when the link between A and B > is down…but we can’t unless each side is advertised as a /30..but I want > the two radio’s to see each other when they’re up. > > So what I’ve done most recently is: > .1 = Router A (configured as /30) > .2 = Radio A (configured as /29, GW set to .1) > .5 = Radio B (configured as /29 GW set to .6) > .6 = Router B (configured as /30) > > Then I just run OSPF on a separate /30 across that path on a separate > VLAN. The above is just for MGMT of the radios. > > > > On Aug 11, 2016, at 3:02 PM, Christopher Gray <[email protected]> > wrote: > > How do you setup radio addresses so both ends of a link can be accessed > (via loop) when the link is down? > > *What I've been doing... and how it doesn't work:* > I've been setting up OSPF links using a /29. > > Router A -- Radio A ~~ Radio B -- Router B > > Devices get addresses: > > - .1 - Router A > - .2 - Router B > - .3 - Radio A (Gateway set to .1) > - .4 - Radio B (Gateway set to .2) > - .5 - Spare (used when swapping links) > - .6 - Spare (used when swapping links) > > This feels very clean, and works nicely when the link is up or when there > is no network loop. However, when the link goes down, if I am connected > near Router A, all traffic for that /29 is routed through Router A, and I > have no access to the B side. Then, I can only access the B side if I > connect closer to Router B. > > Suggestions? > > Thanks - Chris > > >
