Site 33:


10.100.33.0/24  (.1 local radio, .2 local router, .101 remote radio, .102
remote router)



Site 34:



10.100.34.0/24  (.1 local radio, .2 local router, .101 remote radio, .102
remote router)




If these are talking to one another with this scheme, the routers may be
able to have multiple IPs but very few radios allow multiple IPs on the
device


Site 33 local radio is 10.100.33.1 to site 33, but that same radio to site
34 would be 10.100.34.101

On Wed, Aug 26, 2015 at 12:59 PM, Hass, Douglas A. <[email protected]> wrote:

>
>
> Back to your original question, though—you would have to renumber if
> you’re already using a /24 on an interface and now want to carve *that
> particular* /24 up in /29s.
>
>
>
> But if you’re using private IP space, why limit yourself to /29s
> everywhere?  Particularly if each site would have a site number, you could
> easily do:
>
>
>
> Site 33:
>
>
>
> 10.100.33.0/24  (.1 local radio, .2 local router, .101 remote radio, .102
> remote router)
>
>
>
> Site 34:
>
>
>
> 10.100.34.0/24  (.1 local radio, .2 local router, .101 remote radio, .102
> remote router)
>
>
>
> And so on…
>
>
>
> Leave yourself plenty of room and route bigger subnets.  The site
> numbering idea might end up a little confusing, though, since “Site 33” is
> really TWO physical sites, and “Site 34” in my example above is TWO
> physical sites, one of which you’ve already called part of Site 33.
>
>
>
> Doug
>
>
>
>
>
> *From:* Af [mailto:[email protected]] *On Behalf Of *Tim Reichhart
> *Sent:* Wednesday, August 26, 2015 12:32 PM
> *To:* [email protected]
>
> *Subject:* Re: [AFMUG] Issues with doing /29 inside of routerboard
>
>
>
> Mike
> basically rob haas was helping me out on this he sent me an little cheat
> sheet like this:
>
>
>
> a /29 – 255.255.255.248 is what I use on the backhauls
>
> Each Site is assign a site number – say 33
>
> Every site is assigned a /24 for management with my IP scheme of
> 10.100.site.X
>
> The first backhauls would fall into 10.100.33.0/29 so:
>
> 10.100.33.1 – Local radio
>
> 10.100.33.2 – Local Router
>
> 10.100.33.3 – Remote Radio
>
> 10.100.33.4 – Remote Router
>
>
>
> The next backhaul would be out of 10.100.33.8/29 so:
>
> 10.100.33.9 – Local Radio
>
> 10.100.33.10 – Local Router
>
> 10.100.33.11 – Remote Radio
>
> 10.100.33.12 – Remote Router
>
>
>
> basically I want break down the ip's down for backhauls.
>
>
>
> Tim
>
> ------------------------------
>
> -----Original Message-----
> From: "Mike Hammett" <[email protected]>
> To: [email protected]
> Date: 08/26/15 01:23 PM
> Subject: Re: [AFMUG] Issues with doing /29 inside of routerboard
>
> Can you tell us the bigger picture of what's going on so we can help
> better?
>
>
>
> -----
> Mike Hammett
> Intelligent Computing Solutions
> http://www.ics-il.com
>
>
>
> ------------------------------
>
>  *From:* "Tim Reichhart" <[email protected]>
> *To:* [email protected]
> *Sent:* Wednesday, August 26, 2015 12:09:01 PM
> *Subject:* Re: [AFMUG] Issues with doing /29 inside of routerboard
>
>
> I was told to take that /24 and break it down to /29. But I didn't see an
> way to make work without readdressing whole subnet.
>
> Tim
>
> -----Original Message-----
> Subject: Re: [AFMUG] Issues with doing /29 inside of routerboard
> From: "Mike Hammett" <[email protected]>
> To: [email protected]
> Date: 2015/08/26 18:59:54
>
> I did not, no.
>
>
>
>
> -----
> Mike Hammett
> Intelligent Computing Solutions
> http://www.ics-il.com
>
>
>  From: "Josh Luthman" <[email protected]>
> To: [email protected]
> Sent: Wednesday, August 26, 2015 11:58:27 AM
> Subject: Re: [AFMUG] Issues with doing /29 inside of routerboard
>
>
> Did you mean a /29 on eth1?
> Josh Luthman
> Office: 937-552-2340
> Direct: 937-552-2343
> 1100 Wayne St
> Suite 1337
> Troy, OH 45373On Aug 26, 2015 12:53 PM, "Mike Hammett" <[email protected]>
> wrote:
>
> You can't have overlapping subnets.
>
>
>
> -----
> Mike Hammett
> Intelligent Computing Solutions
> http://www.ics-il.com
>
>
>  From: "Tim Reichhart" <[email protected]>
> To: [email protected]
> Sent: Wednesday, August 26, 2015 11:52:43 AM
> Subject: [AFMUG] Issues with doing /29 inside of routerboard
>
> Hi guys
> I am having bit of an issue getting /29 to work in routerboard. What I am
> looking to do is put 172.16.2.x/29 on ether2 but I already have
> 172.16.2.1/24on ether1. So I don't know what I am missing here.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *Douglas A. Hass*
> Associate
> 312.786.6502
> [email protected]
>
> *Franczek Radelet P.C.*
>
> 300 South Wacker Drive
> Suite 3400
> Chicago, IL 60606
> 312.986.0300 - Main
> 312.986.9192 - Fax
> www.franczek.com
> www.wagehourinsights.com
> Connect with me:
> [image: linkedin] <http://linkedin.com/in/douglashass>[image: twitter]
> <https://twitter.com/WageHourInsight>
> *Circular 230 Disclosure: Under requirements imposed by the Internal
> Revenue Service, we inform you that, unless specifically stated otherwise,
> any federal tax advice contained in this communication (including any
> attachments) is not intended or written to be used, and cannot be used, for
> the purposes of (i) avoiding penalties under the Internal Revenue Code or
> (ii) promoting, marketing or recommending to another party any transaction
> or tax-related matter herein. *
> ------------------------------
> For more information about Franczek Radelet P.C., please visit
> franczek.com. The information contained in this e-mail message or any
> attachment may be confidential and/or privileged, and is intended only for
> the use of the named recipient. If you are not the named recipient of this
> message, you are hereby notified that any dissemination, distribution, or
> copying of this message or any attachment thereto, is strictly prohibited.
> If you have received this message in error, please contact the sender and
> delete all copies.
> ------------------------------
> *Franczek Radelet is committed to sustainability - please consider the
> environment before printing this email*
>



-- 
If you only see yourself as part of the team but you don't see your team as
part of yourself you have already failed as part of the team.

Reply via email to