- NANOG - lists.nanog.org

Re: IPv6 prefix from T-Mobile USA used but not announced in BGP (2607:7700::/32)
by Baptiste Jonglez 27 Apr '16

27 Apr '16

On Wed, Apr 27, 2016 at 02:38:41PM -0700, Ca By wrote: > What behavior do you expect when an ipv6only node connects to an ipv4only > node , which is the tmobile case? How is that address of the address > report? As far as I know, IPv4-only DHT nodes do not directly communicate with IPv6-only DHT nodes, I don't see how this would be possible in general. The code of the DHT client is here: https://github.com/savoirfairelinux/opendht > On Wednesday, April 27, 2016, Baptiste Jonglez <baptiste(a)bitsofnetworks.org> > wrote: > > > On Wed, Apr 27, 2016 at 01:16:28PM -0700, Aaron Hopkins wrote: > > > On Wed, 27 Apr 2016, Baptiste Jonglez wrote: > > > > > > >While doing statistics on the participants of a public DHT, I was > > > >surprised to see some IP addresses that are not present in the DFZ: > > > > > > I believe those are used by T-mobile's 464XLAT (RFC 6877) implementation. > > > > > > Recent Android on T-mobile is IPv6-only and has no ability to connect to > > > raw IPv4 addresses. T-mobile's DNS servers are only asked by these > > devices > > > to translate hostnames to IPv6 addresses. If they can't find an IPv6 > > > address, they will look up the IPv4 address for a hostname, and pack it > > into > > > the bottom 32 bits of an IPv6 address that routes to a IPv6-to-IPv4 NAT > > > device. > > > > Thanks, I had forgotten that DNS64 is possible without using the > > well-known prefix. The encoded IPv4 addresses seem to belong to other > > peers of the DHT. > > > > So, if this is basically DNS64/NAT64, these IP addresses should not be > > seen as source or destination address outside of T-Mobile's network, and > > are not attached to the interface of any device. > > > > I can see two possible explanations: > > > > 1/ packets with src or dest IP in 2607:7700::/32 somehow escaped > > T-Mobile's network, without being translated back to IPv4. They caused > > other DHT nodes to believe they have incoming peers in 2607:7700::/32. > > > > 2/ there is an interesting bug in the DHT software when run behind 464XLAT > > (btw, the DHT is dual-stack and supports IPv6 just fine) > > > > I still wonder how this can happen, because the DHT does not use DNS at > > all... > > > > Baptiste > >

1 0

GeoIP database issues and the real world consequences
by Chris Boyd 27 Apr '16

27 Apr '16

Interesting article. http://fusion.net/story/287592/internet-mapping-glitch-kansas-farm/ An hour’s drive from Wichita, Kansas, in a little town called Potwin, there is a 360-acre piece of land with a very big problem. The plot has been owned by the Vogelman family for more than a hundred years, though the current owner, Joyce Taylor née Vogelman, 82, now rents it out. The acreage is quiet and remote: a farm, a pasture, an old orchard, two barns, some hog shacks and a two-story house. It’s the kind of place you move to if you want to get away from it all. The nearest neighbor is a mile away, and the closest big town has just 13,000 people. It is real, rural America; in fact, it’s a two-hour drive from the exact geographical center of the United States. But instead of being a place of respite, the people who live on Joyce Taylor’s land find themselves in a technological horror story. For the last decade, Taylor and her renters have been visited by all kinds of mysterious trouble. They’ve been accused of being identity thieves, spammers, scammers and fraudsters. They’ve gotten visited by FBI agents, federal marshals, IRS collectors, ambulances searching for suicidal veterans, and police officers searching for runaway children. They’ve found people scrounging around in their barn. The renters have been doxxed, their names and addresses posted on the internet by vigilantes. Once, someone left a broken toilet in the driveway as a strange, indefinite threat. --Chris

52 115

trout views
by Randy Bush 27 Apr '16

27 Apr '16

nfs0.dfw.rg.net:/root# ping 128.223.51.20 PING 128.223.51.20 (128.223.51.20) 56(84) bytes of data. From 4.69.145.11 icmp_seq=1 Time to live exceeded From 4.69.145.11 icmp_seq=2 Time to live exceeded ^C --- 128.223.51.20 ping statistics --- 2 packets transmitted, 0 received, +2 errors, 100% packet loss, time 1001ms nfs0.dfw.rg.net:/root# traceroute 128.223.51.20 traceroute to 128.223.51.20 (128.223.51.20), 30 hops max, 60 byte packets 1 r0.dfw.rg.net (198.180.152.3) 1.571 ms 1.559 ms 1.597 ms 2 r1.dfw.rg.net (198.180.152.2) 0.558 ms 0.551 ms 0.640 ms 3 ge-102-0-0-29-53.r08.dllstx09.us.bb.gin.ntt.net (157.238.224.205) 1.562 ms 1.598 ms 1.716 ms 4 ae-12.r07.dllstx09.us.bb.gin.ntt.net (129.250.3.107) 0.488 ms 0.538 ms 0.582 ms 5 * * * 6 * * * 7 ae-65-65.csw1.Dallas1.Level3.net (4.69.206.133) 0.514 ms 0.555 ms ae-95-95.csw4.Dallas1.Level3.net (4.69.206.145) 0.525 ms 8 ae-3-80.edge2.Dallas1.Level3.net (4.69.145.139) 0.627 ms 0.769 ms ae-1-60.edge2.Dallas1.Level3.net (4.69.145.11) 0.633 ms 9 vlan90.csw4.Dallas1.Level3.net (4.69.145.254) 0.517 ms vlan80.csw3.Dallas1.Level3.net (4.69.145.190) 0.589 ms 0.676 ms 10 ae-1-60.edge2.Dallas1.Level3.net (4.69.145.11) 0.519 ms ae-3-80.edge2.Dallas1.Level3.net (4.69.145.139) 0.632 ms ae-4-90.edge2.Dallas1.Level3.net (4.69.145.203) 13.412 ms 11 vlan60.csw1.Dallas1.Level3.net (4.69.145.62) 13.264 ms 0.604 ms vlan80.csw3.Dallas1.Level3.net (4.69.145.190) 0.530 ms 12 ae-1-60.edge2.Dallas1.Level3.net (4.69.145.11) 0.633 ms 0.519 ms 0.513 ms 13 vlan80.csw3.Dallas1.Level3.net (4.69.145.190) 0.540 ms vlan60.csw1.Dallas1.Level3.net (4.69.145.62) 13.318 ms vlan90.csw4.Dallas1.Level3.net (4.69.145.254) 0.554 ms 14 ae-3-80.edge2.Dallas1.Level3.net (4.69.145.139) 0.723 ms ae-4-90.edge2.Dallas1.Level3.net (4.69.145.203) 12.793 ms ae-1-60.edge2.Dallas1.Level3.net (4.69.145.11) 0.494 ms 15 vlan80.csw3.Dallas1.Level3.net (4.69.145.190) 0.554 ms vlan90.csw4.Dallas1.Level3.net (4.69.145.254) 0.541 ms vlan80.csw3.Dallas1.Level3.net (4.69.145.190) 2.040 ms 16 ae-4-90.edge2.Dallas1.Level3.net (4.69.145.203) 12.294 ms ae-3-80.edge2.Dallas1.Level3.net (4.69.145.139) 0.896 ms 0.790 ms 17 vlan80.csw3.Dallas1.Level3.net (4.69.145.190) 0.590 ms vlan60.csw1.Dallas1.Level3.net (4.69.145.62) 0.610 ms vlan80.csw3.Dallas1.Level3.net (4.69.145.190) 0.932 ms 18 ae-1-60.edge2.Dallas1.Level3.net (4.69.145.11) 0.522 ms ae-4-90.edge2.Dallas1.Level3.net (4.69.145.203) 11.423 ms ae-3-80.edge2.Dallas1.Level3.net (4.69.145.139) 0.747 ms 19 vlan90.csw4.Dallas1.Level3.net (4.69.145.254) 0.673 ms vlan80.csw3.Dallas1.Level3.net (4.69.145.190) 0.803 ms vlan60.csw1.Dallas1.Level3.net (4.69.145.62) 0.638 ms 20 ae-1-60.edge2.Dallas1.Level3.net (4.69.145.11) 0.525 ms ae-3-80.edge2.Dallas1.Level3.net (4.69.145.139) 0.826 ms 0.876 ms 21 vlan60.csw1.Dallas1.Level3.net (4.69.145.62) 0.635 ms 9.840 ms 9.404 ms 22 ae-1-60.edge2.Dallas1.Level3.net (4.69.145.11) 0.622 ms 0.604 ms ae-4-90.edge2.Dallas1.Level3.net (4.69.145.203) 8.751 ms 23 vlan80.csw3.Dallas1.Level3.net (4.69.145.190) 0.671 ms 0.817 ms 0.687 ms 24 ae-3-80.edge2.Dallas1.Level3.net (4.69.145.139) 0.785 ms 0.754 ms ae-4-90.edge2.Dallas1.Level3.net (4.69.145.203) 4.774 ms 25 vlan90.csw4.Dallas1.Level3.net (4.69.145.254) 0.633 ms 0.683 ms 0.795 ms 26 ae-1-60.edge2.Dallas1.Level3.net (4.69.145.11) 0.659 ms ae-3-80.edge2.Dallas1.Level3.net (4.69.145.139) 0.758 ms 0.907 ms 27 vlan60.csw1.Dallas1.Level3.net (4.69.145.62) 0.776 ms vlan90.csw4.Dallas1.Level3.net (4.69.145.254) 0.721 ms vlan60.csw1.Dallas1.Level3.net (4.69.145.62) 0.705 ms 28 ae-4-90.edge2.Dallas1.Level3.net (4.69.145.203) 15.057 ms 14.660 ms ae-3-80.edge2.Dallas1.Level3.net (4.69.145.139) 0.871 ms 29 vlan80.csw3.Dallas1.Level3.net (4.69.145.190) 0.864 ms vlan60.csw1.Dallas1.Level3.net (4.69.145.62) 0.752 ms 0.747 ms 30 ae-3-80.edge2.Dallas1.Level3.net (4.69.145.139) 0.877 ms ae-1-60.edge2.Dallas1.Level3.net (4.69.145.11) 0.721 ms ae-4-90.edge2.Dallas1.Level3.net (4.69.145.203) 14.302 ms and, of course, email does not work

3 4

NCS5K?
by Chris Welti 27 Apr '16

27 Apr '16

According to some slides from a russian cisco connect event, the upcoming small-size NCS 5501 and NCS 5502 will support 1M+ FIB and 50ms per port buffers. Seem to be killer boxes. 48x100GE in 2RU with large FIB & buffers? Loving it already. I wonder what prices will look like for those. With Google Translate: NCS 5501 • 800 Gbps @ 430 watts • 40 x SFP + 1G / 10G + 4 x QSFP28 100G • 1RU • Intel Broadwell CPU 8Core @ 1.6GHz • Dimensions WxDxH 444mm x551mm x 44mm • External TCAM for more FIB, large buffers (~ 50 ms) • 1-2M IPv4 FIB • The same set of features as a modular • FCS in IOS XR 6.1.1 NCS 5502 • 4.8 Tbps 100G @ ~ 2200 W • 48 x QSFP 28 or QSFP + optics • 2RU • Intel Broadwell CPU 12Core @ 1.6GHz • 8 ASIC packet processing • Integrated FIA • External FIB TCAM for more • Large buffers (~ 50 ms) • 1-2M IPv4 FIB • The same set of features as a modular • FCS in IOS XR 6.1.1 On Mon Jan 25 18:01:41 EST 2016, Phil Bedard <philxor at gmail.com> wrote: > My guess is you will see something from Cisco similar to the PTX1K in the > NCS 55XX series but it will be more expensive than the 500X series. These > boxes I believe use the Broadcom Tomahawk chipset and the NCS55XX uses the > Jericho. The Jericho can support an external TCAM with more routes but > with some speed limitations since the bus to the off-chip TCAM memory is > slower. Those boxes will also have more packet buffering than what you'll > find on the 500X. > > Either way the cost of 100G is rapidly dropping, crazy to think what we > paid for just a CFP transceiver a few years ago.

4 6

Firewall list recommendations (config conversion options)
by b f 25 Apr '16

25 Apr '16

Hi list, Could any one recommend any firewall related mailing lists? Looking for options on converting a large amount of Fortinet rules to Checkpoint. Ultimately converting the entire configuration to Checkpoint would be nice. Thank you for any advice you can provide. Respectfully, Ed

4 3

As a SP, what is your standard CoS configuration on JunOS?
by Sean Kennedy 25 Apr '16

25 Apr '16

NANOG, I realize that every SP handles marking and queueing/scheduling differently, but I am curious to see other provider's 'standard' config for QoS that is deployed on the JunOS platform. What config do apply to all your ingress interfaces for classification? How are your core link schedulers configured? What kind of remarking do you do (specifically on packets arriving on internet-facing interfaces)? If you have a converged network carrying both internet and carrier-eth/transport traffic, how do you handle guaranteeing bandwidth to the carrier eth services? Thank you, Sean

2 1

google and amazon wierdness via HE right now
by Ken Chase 22 Apr '16

22 Apr '16

>From toronto - something odd - mtr to google.com (google.com (172.217.3.142)) 5. v638.core1.tor1.he.net 6. 100ge7-2.core1.nyc4.he.net 7. 100ge11-1.core1.par2.he.net 8. 10ge3-2.core1.zrh1.he.net 9. ??? par is paris, zrh is zurich? same base path for hitting my EC2 nodes... Cant imagine this is just affecting Toronto HE customers. EC2 node is in 107.20/14 /kc

6 6

Weekly Routing Table Report
by Routing Analysis Role Account 22 Apr '16

22 Apr '16

This is an automated weekly mailing describing the state of the Internet Routing Table as seen from APNIC's router in Japan. The posting is sent to APOPS, NANOG, AfNOG, AusNOG, SANOG, PacNOG, SAFNOG, PaNOG, SdNOG, BJNOG, CaribNOG and the RIPE Routing WG. Daily listings are sent to bgp-stats(a)lists.apnic.net For historical data, please see http://thyme.rand.apnic.net. If you have any comments please contact Philip Smith <pfsinoz(a)gmail.com>. Routing Table Report 04:00 +10GMT Sat 23 Apr, 2016 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 592244 Prefixes after maximum aggregation (per Origin AS): 217479 Deaggregation factor: 2.72 Unique aggregates announced (without unneeded subnets): 289716 Total ASes present in the Internet Routing Table: 53506 Prefixes per ASN: 11.07 Origin-only ASes present in the Internet Routing Table: 36591 Origin ASes announcing only one prefix: 15706 Transit ASes present in the Internet Routing Table: 6431 Transit-only ASes present in the Internet Routing Table: 167 Average AS path length visible in the Internet Routing Table: 4.3 Max AS path length visible: 39 Max AS path prepend of ASN ( 40285) 34 Prefixes from unregistered ASNs in the Routing Table: 1000 Unregistered ASNs in the Routing Table: 361 Number of 32-bit ASNs allocated by the RIRs: 13578 Number of 32-bit ASNs visible in the Routing Table: 10484 Prefixes from 32-bit ASNs in the Routing Table: 41067 Number of bogon 32-bit ASNs visible in the Routing Table: 18 Special use prefixes present in the Routing Table: 0 Prefixes being announced from unallocated address space: 387 Number of addresses announced to Internet: 2809388612 Equivalent to 167 /8s, 115 /16s and 222 /24s Percentage of available address space announced: 75.9 Percentage of allocated address space announced: 75.9 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 98.1 Total number of prefixes smaller than registry allocations: 193331 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 151863 Total APNIC prefixes after maximum aggregation: 42146 APNIC Deaggregation factor: 3.60 Prefixes being announced from the APNIC address blocks: 162423 Unique aggregates announced from the APNIC address blocks: 66131 APNIC Region origin ASes present in the Internet Routing Table: 5170 APNIC Prefixes per ASN: 31.42 APNIC Region origin ASes announcing only one prefix: 1185 APNIC Region transit ASes present in the Internet Routing Table: 914 Average APNIC Region AS path length visible: 4.4 Max APNIC Region AS path length visible: 39 Number of APNIC region 32-bit ASNs visible in the Routing Table: 2018 Number of APNIC addresses announced to Internet: 754038596 Equivalent to 44 /8s, 241 /16s and 183 /24s Percentage of available APNIC address space announced: 88.1 APNIC AS Blocks 4608-4864, 7467-7722, 9216-10239, 17408-18431 (pre-ERX allocations) 23552-24575, 37888-38911, 45056-46079, 55296-56319, 58368-59391, 63488-64098, 131072-135580 APNIC Address Blocks 1/8, 14/8, 27/8, 36/8, 39/8, 42/8, 43/8, 49/8, 58/8, 59/8, 60/8, 61/8, 101/8, 103/8, 106/8, 110/8, 111/8, 112/8, 113/8, 114/8, 115/8, 116/8, 117/8, 118/8, 119/8, 120/8, 121/8, 122/8, 123/8, 124/8, 125/8, 126/8, 133/8, 150/8, 153/8, 163/8, 171/8, 175/8, 180/8, 182/8, 183/8, 202/8, 203/8, 210/8, 211/8, 218/8, 219/8, 220/8, 221/8, 222/8, 223/8, ARIN Region Analysis Summary ---------------------------- Prefixes being announced by ARIN Region ASes: 180914 Total ARIN prefixes after maximum aggregation: 89696 ARIN Deaggregation factor: 2.02 Prefixes being announced from the ARIN address blocks: 185979 Unique aggregates announced from the ARIN address blocks: 88323 ARIN Region origin ASes present in the Internet Routing Table: 16385 ARIN Prefixes per ASN: 11.35 ARIN Region origin ASes announcing only one prefix: 5859 ARIN Region transit ASes present in the Internet Routing Table: 1711 Average ARIN Region AS path length visible: 3.8 Max ARIN Region AS path length visible: 37 Number of ARIN region 32-bit ASNs visible in the Routing Table: 1148 Number of ARIN addresses announced to Internet: 1101398848 Equivalent to 65 /8s, 166 /16s and 3 /24s Percentage of available ARIN address space announced: 58.3 ARIN AS Blocks 1-1876, 1902-2042, 2044-2046, 2048-2106 (pre-ERX allocations) 2138-2584, 2615-2772, 2823-2829, 2880-3153 3354-4607, 4865-5119, 5632-6655, 6912-7466 7723-8191, 10240-12287, 13312-15359, 16384-17407 18432-20479, 21504-23551, 25600-26591, 26624-27647, 29696-30719, 31744-33791 35840-36863, 39936-40959, 46080-47103 53248-55295, 62464-63487, 64198-64296, 393216-395164 ARIN Address Blocks 3/8, 4/8, 6/8, 7/8, 8/8, 9/8, 11/8, 12/8, 13/8, 15/8, 16/8, 17/8, 18/8, 19/8, 20/8, 21/8, 22/8, 23/8, 24/8, 26/8, 28/8, 29/8, 30/8, 32/8, 33/8, 34/8, 35/8, 38/8, 40/8, 44/8, 45/8, 47/8, 48/8, 50/8, 52/8, 53/8, 54/8, 55/8, 56/8, 57/8, 63/8, 64/8, 65/8, 66/8, 67/8, 68/8, 69/8, 70/8, 71/8, 72/8, 73/8, 74/8, 75/8, 76/8, 96/8, 97/8, 98/8, 99/8, 100/8, 104/8, 107/8, 108/8, 128/8, 129/8, 130/8, 131/8, 132/8, 134/8, 135/8, 136/8, 137/8, 138/8, 139/8, 140/8, 142/8, 143/8, 144/8, 146/8, 147/8, 148/8, 149/8, 152/8, 155/8, 156/8, 157/8, 158/8, 159/8, 160/8, 161/8, 162/8, 164/8, 165/8, 166/8, 167/8, 168/8, 169/8, 170/8, 172/8, 173/8, 174/8, 184/8, 192/8, 198/8, 199/8, 204/8, 205/8, 206/8, 207/8, 208/8, 209/8, 214/8, 215/8, 216/8, RIPE Region Analysis Summary ---------------------------- Prefixes being announced by RIPE Region ASes: 142056 Total RIPE prefixes after maximum aggregation: 70126 RIPE Deaggregation factor: 2.03 Prefixes being announced from the RIPE address blocks: 151030 Unique aggregates announced from the RIPE address blocks: 92997 RIPE Region origin ASes present in the Internet Routing Table: 18067 RIPE Prefixes per ASN: 8.36 RIPE Region origin ASes announcing only one prefix: 7906 RIPE Region transit ASes present in the Internet Routing Table: 3001 Average RIPE Region AS path length visible: 4.3 Max RIPE Region AS path length visible: 29 Number of RIPE region 32-bit ASNs visible in the Routing Table: 4676 Number of RIPE addresses announced to Internet: 704622720 Equivalent to 41 /8s, 255 /16s and 176 /24s Percentage of available RIPE address space announced: 102.4 RIPE AS Blocks 1877-1901, 2043, 2047, 2107-2136, 2585-2614 (pre-ERX allocations) 2773-2822, 2830-2879, 3154-3353, 5377-5631 6656-6911, 8192-9215, 12288-13311, 15360-16383 20480-21503, 24576-25599, 28672-29695 30720-31743, 33792-35839, 38912-39935 40960-45055, 47104-52223, 56320-58367 59392-61439, 61952-62463, 196608-204287 RIPE Address Blocks 2/8, 5/8, 25/8, 31/8, 37/8, 46/8, 51/8, 62/8, 77/8, 78/8, 79/8, 80/8, 81/8, 82/8, 83/8, 84/8, 85/8, 86/8, 87/8, 88/8, 89/8, 90/8, 91/8, 92/8, 93/8, 94/8, 95/8, 109/8, 141/8, 145/8, 151/8, 176/8, 178/8, 185/8, 188/8, 193/8, 194/8, 195/8, 212/8, 213/8, 217/8, LACNIC Region Analysis Summary ------------------------------ Prefixes being announced by LACNIC Region ASes: 61961 Total LACNIC prefixes after maximum aggregation: 12274 LACNIC Deaggregation factor: 5.05 Prefixes being announced from the LACNIC address blocks: 76230 Unique aggregates announced from the LACNIC address blocks: 36035 LACNIC Region origin ASes present in the Internet Routing Table: 2470 LACNIC Prefixes per ASN: 30.86 LACNIC Region origin ASes announcing only one prefix: 575 LACNIC Region transit ASes present in the Internet Routing Table: 566 Average LACNIC Region AS path length visible: 4.7 Max LACNIC Region AS path length visible: 24 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 2433 Number of LACNIC addresses announced to Internet: 170984768 Equivalent to 10 /8s, 49 /16s and 5 /24s Percentage of available LACNIC address space announced: 101.9 LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-265628 + ERX transfers LACNIC Address Blocks 177/8, 179/8, 181/8, 186/8, 187/8, 189/8, 190/8, 191/8, 200/8, 201/8, AfriNIC Region Analysis Summary ------------------------------- Prefixes being announced by AfriNIC Region ASes: 14273 Total AfriNIC prefixes after maximum aggregation: 3196 AfriNIC Deaggregation factor: 4.47 Prefixes being announced from the AfriNIC address blocks: 16195 Unique aggregates announced from the AfriNIC address blocks: 5879 AfriNIC Region origin ASes present in the Internet Routing Table: 737 AfriNIC Prefixes per ASN: 21.97 AfriNIC Region origin ASes announcing only one prefix: 181 AfriNIC Region transit ASes present in the Internet Routing Table: 171 Average AfriNIC Region AS path length visible: 4.6 Max AfriNIC Region AS path length visible: 21 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 209 Number of AfriNIC addresses announced to Internet: 77973504 Equivalent to 4 /8s, 165 /16s and 200 /24s Percentage of available AfriNIC address space announced: 77.5 AfriNIC AS Blocks 36864-37887, 327680-328703 & ERX transfers AfriNIC Address Blocks 41/8, 102/8, 105/8, 154/8, 196/8, 197/8, APNIC Region per AS prefix count summary ---------------------------------------- ASN No of nets /20 equiv MaxAgg Description 4538 5555 4192 76 China Education and Research 7545 3286 353 208 TPG Telecom Limited 4766 3164 11145 1121 Korea Telecom 17974 2921 914 96 PT Telekomunikasi Indonesia 9829 2494 1466 462 National Internet Backbone 4755 2090 432 241 TATA Communications formerly 9808 1883 8717 30 Guangdong Mobile Communicatio 4808 1659 2301 539 CNCGROUP IP network China169 9583 1508 121 564 Sify Limited 38197 1492 92 212 Sun Network (Hong Kong) Limit Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-APNIC ARIN Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 22773 3321 2948 145 Cox Communications Inc. 6389 2318 3671 41 BellSouth.net Inc. 18566 2207 394 277 MegaPath Corporation 20115 1923 1937 404 Charter Communications 30036 1728 340 317 Mediacom Communications Corp 6983 1694 849 232 EarthLink, Inc. 209 1567 4666 1236 Qwest Communications Company, 4323 1567 1004 386 tw telecom holdings, inc. 701 1296 10702 704 MCI Communications Services, 7018 1279 19906 975 AT&T Services, Inc. Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-ARIN RIPE Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 39891 2708 143 10 SaudiNet, Saudi Telecom Compa 20940 2442 924 1780 Akamai International B.V. 34984 1964 323 414 TELLCOM ILETISIM HIZMETLERI A 8551 1628 376 55 Bezeq International-Ltd 12479 1159 981 86 France Telecom Espana SA 13188 1079 98 69 TOV "Bank-Inform" 8402 1056 544 15 OJSC "Vimpelcom" 31148 1030 47 41 Freenet Ltd. 9198 938 352 25 JSC Kazakhtelecom 6830 893 2719 463 Liberty Global Operations B.V Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-RIPE LACNIC Region per AS prefix count summary ----------------------------------------- ASN No of nets /20 equiv MaxAgg Description 10620 3460 540 170 Telmex Colombia S.A. 8151 2220 3320 539 Uninet S.A. de C.V. 7303 1509 940 238 Telecom Argentina S.A. 11830 1484 368 53 Instituto Costarricense de El 6503 1435 437 56 Axtel, S.A.B. de C.V. 6147 1046 377 27 Telefonica del Peru S.A.A. 26615 1003 2325 34 Tim Celular S.A. 3816 996 478 186 COLOMBIA TELECOMUNICACIONES S 7738 987 1882 40 Telemar Norte Leste S.A. 11172 869 125 76 Alestra, S. de R.L. de C.V. Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-LACNIC AfriNIC Region per AS prefix count summary ------------------------------------------ ASN No of nets /20 equiv MaxAgg Description 24863 1223 402 40 Link Egypt (Link.NET) 37611 647 48 2 Afrihost-Brevis Computer Serv 36903 617 310 105 Office National des Postes et 8452 542 1472 15 TE-AS 36992 510 1357 26 ETISALAT MISR 37492 394 234 67 Orange Tunisie 24835 326 210 13 Vodafone Data 29571 301 37 13 Cote d'Ivoire Telecom 2018 256 327 74 TENET (The UNINET Project) 36947 238 807 13 Telecom Algeria Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-AFRINIC Global Per AS prefix count summary ---------------------------------- ASN No of nets /20 equiv MaxAgg Description 4538 5555 4192 76 China Education and Research 10620 3460 540 170 Telmex Colombia S.A. 22773 3321 2948 145 Cox Communications Inc. 7545 3286 353 208 TPG Telecom Limited 4766 3164 11145 1121 Korea Telecom 17974 2921 914 96 PT Telekomunikasi Indonesia 39891 2708 143 10 SaudiNet, Saudi Telecom Compa 9829 2494 1466 462 National Internet Backbone 20940 2442 924 1780 Akamai International B.V. 6389 2318 3671 41 BellSouth.net Inc. Complete listing at http://thyme.rand.apnic.net/current/data-ASnet Global Per AS Maximum Aggr summary ---------------------------------- ASN No of nets Net Savings Description 10620 3460 3290 Telmex Colombia S.A. 22773 3321 3176 Cox Communications Inc. 7545 3286 3078 TPG Telecom Limited 17974 2921 2825 PT Telekomunikasi Indonesia 39891 2708 2698 SaudiNet, Saudi Telecom Compa 6389 2318 2277 BellSouth.net Inc. 4766 3164 2043 Korea Telecom 9829 2494 2032 National Internet Backbone 18566 2207 1930 MegaPath Corporation 9808 1883 1853 Guangdong Mobile Communicatio Complete listing at http://thyme.rand.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Network Transit AS Description 65001 PRIVATE 5.143.176.0/20 15468 OJSC Rostelecom 30662 UNALLOCATED 8.2.129.0/24 3356 Level 3 Communicatio 53506 UNALLOCATED 8.17.102.0/23 3356 Level 3 Communicatio 46467 UNALLOCATED 8.19.192.0/24 46887 Lightower Fiber Netw 16589 UNALLOCATED 8.20.247.0/24 35838 CCANET Limited 16589 UNALLOCATED 8.26.56.0/24 35838 CCANET Limited 46473 UNALLOCATED 8.27.122.0/24 3356 Level 3 Communicatio 46473 UNALLOCATED 8.27.124.0/24 3356 Level 3 Communicatio 27205 UNALLOCATED 8.38.16.0/21 3356 Level 3 Communicatio 27205 UNALLOCATED 8.38.20.0/24 32787 Prolexic Technologie Complete listing at http://thyme.rand.apnic.net/current/data-badAS Advertised Unallocated Addresses -------------------------------- Network Origin AS Description 23.226.112.0/20 62788 >>UNKNOWN<< 23.249.144.0/20 40430 colo4jax, LLC 27.100.7.0/24 56096 >>UNKNOWN<< 41.73.1.0/24 37004 >>UNKNOWN<< 41.73.2.0/24 37004 >>UNKNOWN<< 41.73.3.0/24 37004 >>UNKNOWN<< 41.73.4.0/24 37004 >>UNKNOWN<< 41.73.5.0/24 37004 >>UNKNOWN<< 41.73.6.0/24 37004 >>UNKNOWN<< 41.73.7.0/24 37004 >>UNKNOWN<< Complete listing at http://thyme.rand.apnic.net/current/data-add-IANA Number of prefixes announced per prefix length (Global) ------------------------------------------------------- /1:0 /2:0 /3:0 /4:0 /5:0 /6:0 /7:0 /8:16 /9:13 /10:36 /11:101 /12:267 /13:512 /14:1034 /15:1762 /16:12979 /17:7590 /18:12773 /19:25883 /20:38229 /21:39950 /22:65462 /23:56907 /24:327039 /25:556 /26:593 /27:420 /28:43 /29:32 /30:14 /31:1 /32:32 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 39891 2664 2708 SaudiNet, Saudi Telecom Compa 22773 2505 3321 Cox Communications Inc. 18566 2109 2207 MegaPath Corporation 30036 1544 1728 Mediacom Communications Corp 6389 1485 2318 BellSouth.net Inc. 10620 1358 3460 Telmex Colombia S.A. 6983 1342 1694 EarthLink, Inc. 34984 1249 1964 TELLCOM ILETISIM HIZMETLERI A 11492 1171 1265 CABLE ONE, INC. 8551 1124 1628 Bezeq International-Ltd Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1591 2:748 4:21 5:2065 6:28 8:949 12:1775 13:39 14:1674 15:45 16:2 17:80 18:89 20:48 23:1477 24:1768 27:2273 31:1750 32:57 33:2 34:2 35:5 36:286 37:2253 38:1212 39:27 40:89 41:2746 42:395 43:1728 44:42 45:1810 46:2512 47:75 49:1140 50:875 51:19 52:167 54:329 55:5 56:6 57:45 58:1551 59:861 60:347 61:1811 62:1497 63:1923 64:4469 65:2146 66:4246 67:2142 68:1088 69:3248 70:1071 71:468 72:1986 74:2544 75:343 76:424 77:1370 78:1259 79:1049 80:1322 81:1351 82:924 83:693 84:819 85:1573 86:466 87:1034 88:561 89:1970 90:170 91:6055 92:875 93:2331 94:2343 95:2295 96:478 97:357 98:945 99:45 100:72 101:1051 103:10462 104:2375 105:151 106:398 107:1100 108:672 109:2325 110:1244 111:1652 112:965 113:1161 114:1047 115:1566 116:1586 117:1444 118:2050 119:1598 120:924 121:1168 122:2226 123:2010 124:1568 125:1756 128:708 129:381 130:406 131:1336 132:626 133:174 134:448 135:125 136:374 137:344 138:1729 139:254 140:385 141:468 142:657 143:891 144:646 145:157 146:865 147:679 148:1466 149:500 150:652 151:755 152:607 153:270 154:614 155:958 156:493 157:480 158:341 159:1113 160:474 161:780 162:2291 163:535 164:752 165:1052 166:312 167:1131 168:1762 169:645 170:1571 171:267 172:532 173:1705 174:733 175:724 176:1710 177:3983 178:2192 179:1170 180:2065 181:1746 182:1899 183:926 184:802 185:6280 186:3130 187:2135 188:2109 189:1726 190:7722 191:1237 192:8923 193:5732 194:4365 195:3748 196:1714 197:1107 198:5528 199:5701 200:6926 201:3727 202:10126 203:9644 204:4653 205:2712 206:2984 207:3101 208:4059 209:3795 210:3922 211:2051 212:2663 213:2206 214:851 215:72 216:5786 217:1926 218:786 219:561 220:1672 221:874 222:661 223:1193 End of report

1 0

Major IX bandwidth sharing
by Piotr Iwanejko 22 Apr '16

22 Apr '16

Hello Nanog-ers, We are looking for a company that has >=100G connectivity to major IX-es (AMS-IX, DE-CIX preferred) with traffic asymmetry/heavy outgoing traffic, willing to resell incoming fraction n*10G/1*100G IX-only IP transit. Our company develops custom Anti-DDoS solution on PC platform (http://www.slideshare.net/atendesoftware/100-mpps-on-pc) and we want to collocate 1U scrubbing node. Please contact me off list for more details. Thank you. -- Piotr Iwanejko

6 9

LDP flaps specifically present on ACX Juniper routers (ACX4000 and ACX1100)
by joel ahumuza 22 Apr '16

22 Apr '16

Hi All, We are experiencing an issue with ACX routers running on 12.3X54-D20.7 where the LDP sessions are continuously flapping, the logs indicate the following; Apr 21 03:36:31 hostname rpd[2299]: RPD_LDP_SESSIONDOWN: LDP session x.x.x.x is down, reason: hold time expired Apr 21 03:36:34 hostname rpd[2299]: RPD_LDP_NBRDOWN: LDP neighbor x.x.x.x (lo0.0) is down Apr 21 03:36:38 hostname rpd[2299]: RPD_LDP_NBRDOWN: LDP neighbor x.x.x.x (lo0.0) is down Apr 21 03:36:38 hostname rpd[2299]: RPD_LDP_SESSIONDOWN: LDP session x.x.x.x is down, reason: all adjacencies down Apr 21 03:55:34 hostname rpd[2299]: RPD_LDP_SESSIONDOWN: LDP session x.x.x.x is down, reason: received notification from peer Apr 21 03:55:34 hostname rpd[2299]: RPD_LDP_SESSIONDOWN: LDP session x.x.x.x is down, reason: received notification from peer Apr 21 03:55:35 hostname rpd[2299]: RPD_LDP_SESSIONDOWN: LDP session x.x.x.x is down, reason: received notification from peer Apr 21 03:55:35 hostname rpd[2299]: RPD_LDP_SESSIONDOWN: LDP session x.x.x.x is down, reason: received notification from peer Actions taken from our team was; - Increase the hold time setting on the ldp enabled interfaces. - Increase the time interval on the same ldp enabled interfaces. - setting the ldp session protection setting on the ldp enabled loopback interface. Unfortunately the actions did not yield much since the flaps have been ongoing. Anyone have any Idea on what the problem / solution might be? -- Blessings, Joel Ahumuza SkypeID - jl.hmz + 256-75-1040411 | + 256-78-2040411

1 0