- Test - lists.nanog.org

Re: Uhaul not routing IPs
by Michael Crapse 06 Jul '19

06 Jul '19

Forgot to attach our main subnet, 196.53.96.0/22 On Fri, Jul 5, 2019, 6:59 PM Neil Hanlon <neil(a)neilhanlon.com> wrote: > Hi Michael, > > > Wondering if you might be able to clarify a few points... I'm not from > uhaul but am a casual observer and have a couple questions. What does "not > routing ips" mean? Where is traffic stopping? > > > Can you clarify "unable to load the page"? Have any example traceroutes? > Error messages? > > > I'm also a a bit unsure what geolocolation or routing has to do with this > at all. Your message seems to go back and forth between being application > level and network level, so I think clearing up exactly the symptoms of > your issues would be helpful. > > > -Neil > > > > > On Jul 5, 2019, at 20:32, Michael Crapse <michael(a)wi-fiber.io> wrote: >> >> Our customers are trying to access uhauldealer.com and are unable to >> load the page. Classic case of incorrect geolocation and/or up filtering. >> Our emails to their webmaster/wan team have gone unanswered or bounced >> If anyone knows how to contact them please contact me off list >> >

1 0

Re: Uhaul not routing IPs
by Michael Crapse 06 Jul '19

06 Jul '19

The server does not respond to our clients when they originate from a certain subnet, but they do with a different subnet On Fri, Jul 5, 2019, 6:57 PM Neil Hanlon <neil(a)neilhanlon.com> wrote: > Hi Michael, > > Wondering if you might be able to clarify a few points... I'm not from > uhaul but am a casual observer and have a couple questions. What does "not > routing ips" mean? Where is traffic stopping? > > Can you clarify "unable to load the page"? Have any example traceroutes? > Error messages? > > I'm also a a bit unsure what geolocolation or routing has to do with this > at all. Your message seems to go back and forth between being application > level and network level, so I think clearing up exactly the symptoms of > your issues would be helpful. > > -Neil > On Jul 5, 2019, at 20:32, Michael Crapse <michael(a)wi-fiber.io> wrote: >> >> Our customers are trying to access uhauldealer.com and are unable to >> load the page. Classic case of incorrect geolocation and/or up filtering. >> Our emails to their webmaster/wan team have gone unanswered or bounced >> If anyone knows how to contact them please contact me off list >> >

1 0

Uhaul not routing IPs
by Michael Crapse 06 Jul '19

06 Jul '19

Our customers are trying to access uhauldealer.com and are unable to load the page. Classic case of incorrect geolocation and/or up filtering. Our emails to their webmaster/wan team have gone unanswered or bounced If anyone knows how to contact them please contact me off list

1 0

Weekly Routing Table Report
by cscora＠apnic.net 05 Jul '19

05 Jul '19

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, SANOG, PacNOG, SAFNOG TZNOG, MENOG, BJNOG, SDNOG, CMNOG, LACNOG 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 06 Jul, 2019 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 760370 Prefixes after maximum aggregation (per Origin AS): 293074 Deaggregation factor: 2.59 Unique aggregates announced (without unneeded subnets): 366150 Total ASes present in the Internet Routing Table: 64764 Prefixes per ASN: 11.74 Origin-only ASes present in the Internet Routing Table: 55696 Origin ASes announcing only one prefix: 23947 Transit ASes present in the Internet Routing Table: 9068 Transit-only ASes present in the Internet Routing Table: 284 Average AS path length visible in the Internet Routing Table: 4.5 Max AS path length visible: 42 Max AS path prepend of ASN ( 27978) 31 Prefixes from unregistered ASNs in the Routing Table: 22 Number of instances of unregistered ASNs: 24 Number of 32-bit ASNs allocated by the RIRs: 27720 Number of 32-bit ASNs visible in the Routing Table: 22620 Prefixes from 32-bit ASNs in the Routing Table: 102165 Number of bogon 32-bit ASNs visible in the Routing Table: 17 Special use prefixes present in the Routing Table: 0 Prefixes being announced from unallocated address space: 217 Number of addresses announced to Internet: 2838933888 Equivalent to 169 /8s, 54 /16s and 177 /24s Percentage of available address space announced: 76.7 Percentage of allocated address space announced: 76.7 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 99.3 Total number of prefixes smaller than registry allocations: 252618 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 205898 Total APNIC prefixes after maximum aggregation: 61349 APNIC Deaggregation factor: 3.36 Prefixes being announced from the APNIC address blocks: 201560 Unique aggregates announced from the APNIC address blocks: 84128 APNIC Region origin ASes present in the Internet Routing Table: 9868 APNIC Prefixes per ASN: 20.43 APNIC Region origin ASes announcing only one prefix: 2749 APNIC Region transit ASes present in the Internet Routing Table: 1476 Average APNIC Region AS path length visible: 4.5 Max APNIC Region AS path length visible: 26 Number of APNIC region 32-bit ASNs visible in the Routing Table: 4868 Number of APNIC addresses announced to Internet: 770901888 Equivalent to 45 /8s, 243 /16s and 7 /24s 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, 64297-64395, 131072-141625 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: 225924 Total ARIN prefixes after maximum aggregation: 105561 ARIN Deaggregation factor: 2.14 Prefixes being announced from the ARIN address blocks: 225090 Unique aggregates announced from the ARIN address blocks: 106979 ARIN Region origin ASes present in the Internet Routing Table: 18511 ARIN Prefixes per ASN: 12.16 ARIN Region origin ASes announcing only one prefix: 6867 ARIN Region transit ASes present in the Internet Routing Table: 1905 Average ARIN Region AS path length visible: 3.9 Max ARIN Region AS path length visible: 42 Number of ARIN region 32-bit ASNs visible in the Routing Table: 2786 Number of ARIN addresses announced to Internet: 1067927168 Equivalent to 63 /8s, 167 /16s and 70 /24s 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-399260 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, 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: 209782 Total RIPE prefixes after maximum aggregation: 99531 RIPE Deaggregation factor: 2.11 Prefixes being announced from the RIPE address blocks: 205861 Unique aggregates announced from the RIPE address blocks: 122658 RIPE Region origin ASes present in the Internet Routing Table: 26193 RIPE Prefixes per ASN: 7.86 RIPE Region origin ASes announcing only one prefix: 11584 RIPE Region transit ASes present in the Internet Routing Table: 3732 Average RIPE Region AS path length visible: 4.6 Max RIPE Region AS path length visible: 35 Number of RIPE region 32-bit ASNs visible in the Routing Table: 8244 Number of RIPE addresses announced to Internet: 720259712 Equivalent to 42 /8s, 238 /16s and 74 /24s 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, 64396-64495 196608-210331 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: 97349 Total LACNIC prefixes after maximum aggregation: 22262 LACNIC Deaggregation factor: 4.37 Prefixes being announced from the LACNIC address blocks: 98646 Unique aggregates announced from the LACNIC address blocks: 42909 LACNIC Region origin ASes present in the Internet Routing Table: 8592 LACNIC Prefixes per ASN: 11.48 LACNIC Region origin ASes announcing only one prefix: 2289 LACNIC Region transit ASes present in the Internet Routing Table: 1575 Average LACNIC Region AS path length visible: 5.2 Max LACNIC Region AS path length visible: 39 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 6143 Number of LACNIC addresses announced to Internet: 173820928 Equivalent to 10 /8s, 92 /16s and 76 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-270748 + 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: 21394 Total AfriNIC prefixes after maximum aggregation: 4353 AfriNIC Deaggregation factor: 4.91 Prefixes being announced from the AfriNIC address blocks: 28996 Unique aggregates announced from the AfriNIC address blocks: 9283 AfriNIC Region origin ASes present in the Internet Routing Table: 1301 AfriNIC Prefixes per ASN: 22.29 AfriNIC Region origin ASes announcing only one prefix: 458 AfriNIC Region transit ASes present in the Internet Routing Table: 255 Average AfriNIC Region AS path length visible: 4.9 Max AfriNIC Region AS path length visible: 27 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 579 Number of AfriNIC addresses announced to Internet: 105794560 Equivalent to 6 /8s, 78 /16s and 76 /24s AfriNIC AS Blocks 36864-37887, 327680-328703 & ERX transfers AfriNIC Address Blocks 41/8, 45/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 7545 4808 564 544 TPG-INTERNET-AP TPG Telecom Limited, AU 7552 3221 1459 31 VIETEL-AS-AP Viettel Group, VN 45899 3013 1738 121 VNPT-AS-VN VNPT Corp, VN 9808 2773 9043 63 CMNET-GD Guangdong Mobile Communication 9829 2696 1489 562 BSNL-NIB National Internet Backbone, IN 4766 2515 11119 760 KIXS-AS-KR Korea Telecom, KR 4755 2142 428 183 TATACOMM-AS TATA Communications formerl 9394 2094 4882 26 CTTNET China TieTong Telecommunications 9498 2082 427 172 BBIL-AP BHARTI Airtel Ltd., IN 7713 2058 608 612 TELKOMNET-AS-AP PT Telekomunikasi Indon 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 7155 4064 280 25 VIASAT-SP-BACKBONE - ViaSat,Inc., US 11492 3679 240 616 CABLEONE - CABLE ONE, INC., US 6327 3577 1324 90 SHAW - Shaw Communications Inc., CA 22773 3431 2974 157 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 16509 2984 6377 1368 AMAZON-02 - Amazon.com, Inc., US 16625 2621 1378 1900 AKAMAI-AS - Akamai Technologies, Inc., 30036 2157 347 246 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom 20115 2152 2762 524 CHARTER-20115 - Charter Communications, 18566 2098 405 107 MEGAPATH5-US - MegaPath Corporation, US 5650 2083 3074 1459 FRONTIER-FRTR - Frontier Communications 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 12479 5435 1629 141 UNI2-AS, ES 39891 3778 203 20 ALJAWWALSTC-AS, SA 8551 3232 379 46 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 20940 2705 512 1934 AKAMAI-ASN1, US 12389 2350 2230 662 ROSTELECOM-AS, RU 34984 2095 344 546 TELLCOM-AS, TR 9121 1641 1692 19 TTNET, TR 9009 1631 177 876 M247, GB 13188 1604 100 47 TRIOLAN, UA 61317 1468 151 496 ASDETUK http://www.heficed.com, GB 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 8151 6220 3355 592 Uninet S.A. de C.V., MX 10620 3409 534 440 Telmex Colombia S.A., CO 11830 2696 370 54 Instituto Costarricense de Electricidad 7303 1474 1022 274 Telecom Argentina S.A., AR 6503 1219 425 53 Axtel, S.A.B. de C.V., MX 28573 1166 2243 206 CLARO S.A., BR 6147 1095 377 31 Telefonica del Peru S.A.A., PE 3816 1040 524 114 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 13999 975 468 241 Mega Cable, S.A. de C.V., MX 11172 937 112 61 Alestra, S. de R.L. de C.V., MX 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 1171 393 22 LINKdotNET-AS, EG 37611 970 107 9 Afrihost, ZA 24835 885 634 22 RAYA-AS, EG 36992 838 1535 77 ETISALAT-MISR, EG 36903 831 418 129 MT-MPLS, MA 8452 676 1859 20 TE-AS TE-AS, EG 29571 518 68 11 ORANGE-COTE-IVOIRE, CI 37492 483 470 56 ORANGE-, TN 37342 408 32 1 MOVITEL, MZ 15399 386 45 11 WANANCHI-, KE 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 8151 6220 3355 592 Uninet S.A. de C.V., MX 12479 5435 1629 141 UNI2-AS, ES 7545 4808 564 544 TPG-INTERNET-AP TPG Telecom Limited, AU 7155 4064 280 25 VIASAT-SP-BACKBONE - ViaSat,Inc., US 39891 3778 203 20 ALJAWWALSTC-AS, SA 11492 3679 240 616 CABLEONE - CABLE ONE, INC., US 6327 3577 1324 90 SHAW - Shaw Communications Inc., CA 22773 3431 2974 157 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 10620 3409 534 440 Telmex Colombia S.A., CO 8551 3232 379 46 BEZEQ-INTERNATIONAL-AS Bezeqint Interne Complete listing at http://thyme.rand.apnic.net/current/data-ASnet Global Per AS Maximum Aggr summary ---------------------------------- ASN No of nets Net Savings Description 12479 5435 5294 UNI2-AS, ES 7545 4808 4264 TPG-INTERNET-AP TPG Telecom Limited, AU 7155 4064 4039 VIASAT-SP-BACKBONE - ViaSat,Inc., US 39891 3778 3758 ALJAWWALSTC-AS, SA 6327 3577 3487 SHAW - Shaw Communications Inc., CA 22773 3431 3274 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 7552 3221 3190 VIETEL-AS-AP Viettel Group, VN 8551 3232 3186 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 11492 3679 3063 CABLEONE - CABLE ONE, INC., US 10620 3409 2969 Telmex Colombia S.A., CO Complete listing at http://thyme.rand.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Network Transit AS Description 230105 UNALLOCATED 38.110.79.0/24 23015 CMC180-TOR-AS - Cambridge Merc 266842 UNALLOCATED 45.238.156.0/22 265680 HNTELCO S.A, HN 65550 DOCUMENT 81.8.34.0/24 15924 BORUSANTELEKOM-AS, TR 65550 DOCUMENT 81.8.35.0/24 15924 BORUSANTELEKOM-AS, TR 65549 DOCUMENT 117.239.163.0/24 65544 UNKNOWN 64339 UNALLOCATED 143.0.108.0/22 18747 IFX18747 - IFX Corporation, US 64355 UNALLOCATED 156.40.196.0/24 30387 NIH-NET-NCCS - National Instit 64011 UNALLOCATED 166.133.128.0/18 20057 ATT-MOBILITY-LLC-AS20057 - AT& 64011 UNALLOCATED 166.133.192.0/18 20057 ATT-MOBILITY-LLC-AS20057 - AT& 64011 UNALLOCATED 166.184.9.0/24 20057 ATT-MOBILITY-LLC-AS20057 - AT& Complete listing at http://thyme.rand.apnic.net/current/data-badAS Advertised Unallocated Addresses -------------------------------- Network Origin AS Description 27.100.7.0/24 56096 UNKNOWN 27.126.156.0/22 55827 UNKNOWN 27.126.156.0/23 55827 UNKNOWN 27.126.158.0/23 55827 UNKNOWN 41.76.136.0/22 37500 -Reserved AS-, ZZ 41.76.140.0/22 37500 -Reserved AS-, ZZ 41.78.180.0/23 37265 -Reserved AS-, ZZ 41.220.48.0/20 36900 -Reserved AS-, ZZ 41.242.92.0/24 37643 -Reserved AS-, ZZ 41.242.93.0/24 37643 -Reserved AS-, ZZ 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:10 /9:11 /10:37 /11:100 /12:294 /13:569 /14:1135 /15:1911 /16:13256 /17:8002 /18:13939 /19:25814 /20:40323 /21:47471 /22:95060 /23:76939 /24:434610 /25:889 /26:0 /27:0 /28:0 /29:0 /30:0 /31:0 /32:0 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 12479 4389 5435 UNI2-AS, ES 6327 3366 3577 SHAW - Shaw Communications Inc., CA 7155 3156 4064 VIASAT-SP-BACKBONE - ViaSat,Inc., US 39891 2946 3778 ALJAWWALSTC-AS, SA 11492 2883 3679 CABLEONE - CABLE ONE, INC., US 8551 2685 3232 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 22773 2664 3431 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 11830 2044 2696 Instituto Costarricense de Electricidad y Telec 18566 1993 2098 MEGAPATH5-US - MegaPath Corporation, US 30036 1908 2157 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom Communi Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1704 2:1054 3:6 4:19 5:3062 6:45 7:1 8:1342 9:1 11:1 12:1808 13:367 14:2065 15:38 16:6 17:258 18:79 20:57 23:2808 24:2574 25:4 27:2451 31:2018 32:99 35:37 36:877 37:3065 38:1770 39:289 40:120 41:3202 42:826 43:2096 44:151 45:8681 46:3343 47:261 49:1354 50:1109 51:337 52:1010 54:279 55:698 56:6 57:46 58:1768 59:1091 60:537 61:2198 62:1956 63:1856 64:4984 65:2210 66:4842 67:2775 68:1174 69:3553 70:1389 71:658 72:2633 74:2711 75:1295 76:569 77:1803 78:1836 79:2273 80:1851 81:1493 82:1132 83:944 84:1131 85:2299 86:557 87:1544 88:1051 89:2557 90:208 91:6601 92:1434 93:2473 94:2475 95:3320 96:945 97:339 98:961 99:789 100:87 101:1195 102:640 103:21667 104:3636 105:266 106:786 107:1758 108:697 109:3778 110:1728 111:2019 112:1526 113:1386 114:1240 115:1735 116:1760 117:1925 118:2175 119:1652 120:1056 121:1054 122:2248 123:1795 124:1497 125:2020 128:1358 129:840 130:550 131:1824 132:770 133:222 134:1097 135:250 136:598 137:780 138:2061 139:904 140:606 141:895 142:793 143:1056 144:883 145:275 146:1299 147:842 148:1719 149:984 150:788 151:1016 152:1091 153:337 154:4274 155:908 156:1649 157:1027 158:663 159:1949 160:1608 161:931 162:2958 163:829 164:1269 165:1496 166:478 167:1415 168:3441 169:897 170:4195 171:611 172:1663 173:2209 174:1040 175:990 176:2373 177:4013 178:2559 179:1375 180:2153 181:2354 182:2727 183:1103 184:2277 185:15360 186:3656 187:2479 188:2942 189:1989 190:8228 191:1453 192:10063 193:6747 194:5503 195:4150 196:2968 197:1614 198:5938 199:5977 200:7103 201:5109 202:10412 203:10193 204:4550 205:3073 206:3262 207:3239 208:3938 209:4271 210:3934 211:2045 212:3122 213:2975 214:1117 215:54 216:5895 217:2235 218:895 219:608 220:1907 221:976 222:979 223:1414 End of report

1 0

Re: CloudFlare issues?
by Francois Lecavalier 04 Jul '19

04 Jul '19

Hi Mark, Following that Verizon debacle I got onboard with ROV, after a couple research I stopped my choice on the ....drum roll.... CloudFlare GoRTR (https://github.com/cloudflare/gortr) If you trust them enough they provide an updated JSON every 15 minutes of the global RIR aggregate. I'll see down the road if we'll fetch them ourselves but at least it got us up and running in less than an hour. It was also easy for us to deploy as the routers and the servers are on the same PoP directly connected, so we don't need the whole encryption recipe they provide for mass distribution. But I also have a question for all the ROA folks out there. So far we are not taking any action other than lowering the local-pref - we want to make sure this is stable before we start denying prefixes. So the question, is it safe as of this date to : 1.Accept valid, 2. Accept unknown, 3. Reject invalid? Have any large network who implemented it dealt with unreachable destinations? I'm wondering as I haven't found any blog mentioning anything in this regard and ClouFlare docs only shows example for valid and invalid, but nothing for unknown. My assumption is that 1.Accept valid, 2. Accept unknown, 3. Reject invalid shouldn't break anything. Thanks, -Francois This e-mail may be privileged and/or confidential, and the sender does not waive any related rights and obligations. Any distribution, use or copying of this e-mail or the information it contains by other than an intended recipient is unauthorized. If you received this e-mail in error, please advise me (by return e-mail or otherwise) immediately. Ce courrier ?lectronique est confidentiel et prot?g?. L'exp?diteur ne renonce pas aux droits et obligations qui s'y rapportent. Toute diffusion, utilisation ou copie de ce message ou des renseignements qu'il contient par une personne autre que le (les) destinataire(s) d?sign?(s) est interdite. Si vous recevez ce courrier ?lectronique par erreur, veuillez m'en aviser imm?diatement, par retour de courrier ?lectronique ou par un autre moyen.

5 12

Real-world MPLS P/LSR experience on BCM T3 (X5/X7) vs T2+
by Jason Lixfeld 04 Jul '19

04 Jul '19

Hey all, In the role of an MPLS P/LSR, I’m curious if there have been any gotchas (or fixes) revealed with BCM T3 vs. T2+. I remember reading somewhere some years ago that there were oddities on the T2+ that I’d like to believe have been addressed on T3, but does anyone have any real-world experience with T3 in an MPLS core? (IS-IS, LDP, rLFA, 2-3 labels wide, likely SR/Seamless/BGP-LU/whatever down the road) I’m sure J, C, A, etc. all have their own challenges wrapping their code around the APIs, so would be curious to hear anything anyone has to share along those lines as well. Thanks in advance.

1 0

Any contact at VERIZON who manages @VTEXT.COM?
by Curtis Generous 04 Jul '19

04 Jul '19

We started seeing emails to @VTEXT.COM being periodically rejected earlier in the week, and now most/all our getting soft-bounced. Anyone here on the list have contact info at VERIZON who can assist in troubleshooting this? All normal channels to get hold of their support have failed Thanks --curtis

1 0

Microsoft SNDS contact
by Brian Rak 03 Jul '19

03 Jul '19

We've been trying to get SNDS access for our IP space, and we keep running into issues where the SNDS site is unable to determine what emails it should use to authorize access. SNDS support has so far been very unhelpful, they keep trying to tell us to submit the space as individual /24's, which is less then helpful when we have multiple /18s we're trying to set up. Does anyone have a contact at Microsoft that can help?

3 7

Re: few big monolithic PEs vs many small PEs
by James Bensley 03 Jul '19

03 Jul '19

On Wed, 19 Jun 2019 at 21:23, <adamv0025(a)netconsultings.com> wrote: > > Hi folks, > > Recently I ran into a peculiar situation where we had to cap couple of PE > even though merely a half of the rather big chassis was populated with > cards, reason being that the central RE/RP was not able to cope with the > combined number of routes/vrfs/bgp sessions/etc.. > > So this made me think about the best strategy in building out SP-Edge > nowadays (yes I'm aware of the centralize/decentralize pendulum swinging > every couple of years). > The conclusion I came to was that *currently the best approach would be to > use several medium to small(fixed) PEs to replace a big monolithic chasses > based system. > So what I was thinking is, > Yes it will cost a bit more (router is more expensive than a LC) > Will end up with more prefixes in IGP, more BGP sessions etc.. -don't care. > But the benefits are less eggs in one basket, simplified and hence faster > testing in case of specialized PEs and obviously better RP CPU/MEM to port > ratio. > Am I missing anything please? > > *currently, > Yes some old chassis systems or even multi-chassis systems used to support > additional RPs and offloading some of the processes (e.g. BGP onto those) > -problem is these are custom hacks and still a single OS which needs > rebooting LC/ASICs when being upgraded -so the problem of too many eggs in > one basket still exists (yes cisco NCS6k and recent ASR9k lightspeed LCs are > an exception) > And yes there is the "node-slicing" approach from Juniper where one can > offload CP onto multiple x86 servers and assign LCs to each server (virtual > node) - which would solve my chassis full problem -but honestly how many of > you are running such setup? Exactly. And that's why I'd be hesitant to > deploy this solution in production just yet. I don't know of any other > vendor solution like this one, but who knows maybe in 5 years this is going > to be the new standard. Anyways I need a solution/strategy for the next 3-5 > years. > > > Would like to hear what are your thoughts on this conundrum. > > adam > > netconsultings.com > ::carrier-class solutions for the telecommunications industry:: Hi Adam, Over the years I have been bitten multiple times by having fewer big routers with either far too many services/customers connected to them or too much traffic going through them. These days I always go for more smaller/more routers than fewer/larger routers. One experience I have made is that when there is an outage on a large PE, even when it still has spare capacity, is that the business impact can be too much to handle (the support desk is overwhelmed, customers become irate if you can't quickly tell them what all the impacted services are, when service will be restored, the NMS has so many alarms it’s not clear what the problem is or where it's coming from etc.). I’ve seen networks place change freeze on devices, with the exception of changes that migrate customers or services off of the PE, because any outage would create too great an impact to the business, or risk the customers terminating their contract. I’ve also seen changes freeze be placed upon large PEs because the complexity was too great, trying to work out the impact of a change on one of the original PEs from when the network was first built, which is somehow linked to virtually every service on the network in some obscure and unforeseeable way. This doesn’t mean there isn’t a place for large routers. For example, in a typical network, by the time we get to the P nodes layer in the core we tend to have high levels of redundancy, i.e. any PE is dual-homed to two or more P nodes and will have 100% redundant capacity. Down at the access layer customers may be connected to a single access layer device or the access layer device might have a single backhaul link. So technically we have lots of customers, services and traffic passing through larger P node devices, but these devices have a low rate of changes / low touch, perform a low number of functions, they are operationally simple, and are highly redundant. Adversely at the service edge, which I guess is your main concern here, I’m all about more smaller devices with single service dedicated devices. I’ve tried to write some of my experiences here (https://null.53bits.co.uk/index.php?page=few-larger-routers-vs.-many-smalle…) The tl;dr version though is that there’s rarely a technical restriction to having fewer large routers and it’s an operational/business impact problem. I'd like to hear from anyone who has had great success with fewer larger PEs. Cheers, James.

2 3

Intermittent "bad gateway"
by Stephen Satchell 02 Jul '19

02 Jul '19

Are we having another BGP problem this morning?

13 12