Timeline for Can I announce prefix 161.117.25.0/24 even though I don't have all of /24 IPs?
Current License: CC BY-SA 4.0
8 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
May 12, 2019 at 15:16 | history | edited | jonathanjo | CC BY-SA 4.0 |
punctuation
|
Feb 27, 2019 at 21:09 | comment | added | jonathanjo | My understanding of the question is that the upstream ISP is cutting out the two /32s, not the owner of the nearly-/24. | |
Feb 27, 2019 at 18:07 | comment | added | Ricky | He announces the /24 and the others announce their /32. Of course, one can't globally route a /32, so he who has the /24 has to rig up a way to deliver the two /32's. (just like how the ISP announces a /16 to the world, and internally figures out how to divide it up) | |
Feb 27, 2019 at 14:55 | comment | added | jonathanjo | @RickyBeam ... from the point of view of routes, certainly. As for advertising blocks across organisations, surely you only say what you actually have, per the other answers. | |
Feb 27, 2019 at 0:21 | comment | added | Ricky | If 161.117.25.0/24 is assigned to a LAN, some trickery would be necessary to put 100 and 200 somewhere else. (I've done this very thing.) From a route table perspective, 161.117.25.0/24, 161.117.25.100/32, 161.117.25.200/32 do not create a conflict. | |
Feb 26, 2019 at 21:46 | history | edited | jonathanjo | CC BY-SA 4.0 |
note re short prefixes
|
Feb 26, 2019 at 21:44 | vote | accept | Jack | ||
Feb 26, 2019 at 21:44 | |||||
Feb 26, 2019 at 21:40 | history | answered | jonathanjo | CC BY-SA 4.0 |