[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
IPv4 smaller than /24 leasing?
Yes, exactly right. You would probably have to tunnel the /27 back to where the >/24 lives. That's the only way I can see of it working "anywhere". That's a technically valid solution but maybe not so hot if you are looking for high redundancy/availability since you are dependent on the tunnel being up and working.
As always the reputation of the aggregate is going to be critical as to how well this works for you. It seems to me that increasingly these "portable" blocks have murky histories as spam and malware sources. I would rather have a block assigned by a reputable upstream provider than to do this.
> Le 2018-01-04 20:16, Job Snijders a Ã?Â©critÃ?Â :
>> On Thu, 4 Jan 2018 at 20:13, Filip Hruska <fhr at fhrnet.eu> wrote:
>>> I have stumbled upon this site  which seems to offer /27 IPv4
>>> They also claim "All of our IPv4 address space can be used on any
>>> network in any location."
>>> I thought that the smallest prefix size one could get routed
>>> globally is /24?
>> So how does this work?
>> Probably with GRE, IPIP or OpenVPN tunnels.
>> Kind regards,
> IPv4 /24 is commonly the minimal chunk advertised to (and accepted by)
> neighbors. If I run a global (or regional) network, I may advertise this
> /24 -- or rather an aggregate covering it -- over my diverse
> interconnection with neighbors, your /27 being part of the chunk and
> routed to you internally (if you're va customer)-- no need for
> encapsulation efforts. Similar scenario may be multi-upstream, subject
> to acceptance of "punching holes in aggregates"... Am I missing
> something? What's the trigger for doing tunneling here?
> Happy New Year '18, by the way !