September 2016 - Test - lists.nanog.org

Status of IPv6 on Charter Communications
by Stephen Satchell 25 Sep '16

25 Sep '16

Would someone at Charter Communications who is on this list indicate the roll-out schedule for IPv6 to business customers using cable modems as opposed to fiber links?

3 2

Weekly Routing Table Report
by cscora＠apnic.net 23 Sep '16

23 Sep '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, 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 24 Sep, 2016 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 611401 Prefixes after maximum aggregation (per Origin AS): 220201 Deaggregation factor: 2.78 Unique aggregates announced (without unneeded subnets): 298301 Total ASes present in the Internet Routing Table: 54892 Prefixes per ASN: 11.14 Origin-only ASes present in the Internet Routing Table: 36377 Origin ASes announcing only one prefix: 15380 Transit ASes present in the Internet Routing Table: 6523 Transit-only ASes present in the Internet Routing Table: 171 Average AS path length visible in the Internet Routing Table: 4.3 Max AS path length visible: 54 Max AS path prepend of ASN ( 55644) 51 Prefixes from unregistered ASNs in the Routing Table: 65 Unregistered ASNs in the Routing Table: 20 Number of 32-bit ASNs allocated by the RIRs: 15526 Number of 32-bit ASNs visible in the Routing Table: 11992 Prefixes from 32-bit ASNs in the Routing Table: 47864 Number of bogon 32-bit ASNs visible in the Routing Table: 102 Special use prefixes present in the Routing Table: 0 Prefixes being announced from unallocated address space: 342 Number of addresses announced to Internet: 2828439524 Equivalent to 168 /8s, 150 /16s and 143 /24s Percentage of available address space announced: 76.4 Percentage of allocated address space announced: 76.4 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 98.2 Total number of prefixes smaller than registry allocations: 198636 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 156403 Total APNIC prefixes after maximum aggregation: 42921 APNIC Deaggregation factor: 3.64 Prefixes being announced from the APNIC address blocks: 170011 Unique aggregates announced from the APNIC address blocks: 69184 APNIC Region origin ASes present in the Internet Routing Table: 5191 APNIC Prefixes per ASN: 32.75 APNIC Region origin ASes announcing only one prefix: 1148 APNIC Region transit ASes present in the Internet Routing Table: 947 Average APNIC Region AS path length visible: 4.5 Max APNIC Region AS path length visible: 54 Number of APNIC region 32-bit ASNs visible in the Routing Table: 2389 Number of APNIC addresses announced to Internet: 759948228 Equivalent to 45 /8s, 75 /16s and 227 /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-137529 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: 184481 Total ARIN prefixes after maximum aggregation: 89596 ARIN Deaggregation factor: 2.06 Prefixes being announced from the ARIN address blocks: 190286 Unique aggregates announced from the ARIN address blocks: 88489 ARIN Region origin ASes present in the Internet Routing Table: 16188 ARIN Prefixes per ASN: 11.75 ARIN Region origin ASes announcing only one prefix: 5689 ARIN Region transit ASes present in the Internet Routing Table: 1705 Average ARIN Region AS path length visible: 3.8 Max ARIN Region AS path length visible: 23 Number of ARIN region 32-bit ASNs visible in the Routing Table: 1477 Number of ARIN addresses announced to Internet: 1107456736 Equivalent to 66 /8s, 2 /16s and 114 /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-397212 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: 146000 Total RIPE prefixes after maximum aggregation: 71898 RIPE Deaggregation factor: 2.03 Prefixes being announced from the RIPE address blocks: 156352 Unique aggregates announced from the RIPE address blocks: 96559 RIPE Region origin ASes present in the Internet Routing Table: 18136 RIPE Prefixes per ASN: 8.62 RIPE Region origin ASes announcing only one prefix: 7827 RIPE Region transit ASes present in the Internet Routing Table: 3039 Average RIPE Region AS path length visible: 4.4 Max RIPE Region AS path length visible: 27 Number of RIPE region 32-bit ASNs visible in the Routing Table: 5056 Number of RIPE addresses announced to Internet: 708744960 Equivalent to 42 /8s, 62 /16s and 151 /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-207259 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: 61851 Total LACNIC prefixes after maximum aggregation: 12484 LACNIC Deaggregation factor: 4.95 Prefixes being announced from the LACNIC address blocks: 77626 Unique aggregates announced from the LACNIC address blocks: 37425 LACNIC Region origin ASes present in the Internet Routing Table: 2474 LACNIC Prefixes per ASN: 31.38 LACNIC Region origin ASes announcing only one prefix: 544 LACNIC Region transit ASes present in the Internet Routing Table: 579 Average LACNIC Region AS path length visible: 4.8 Max LACNIC Region AS path length visible: 26 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 2807 Number of LACNIC addresses announced to Internet: 170771520 Equivalent to 10 /8s, 45 /16s and 196 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-266652 + 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: 14736 Total AfriNIC prefixes after maximum aggregation: 3292 AfriNIC Deaggregation factor: 4.48 Prefixes being announced from the AfriNIC address blocks: 16784 Unique aggregates announced from the AfriNIC address blocks: 6330 AfriNIC Region origin ASes present in the Internet Routing Table: 733 AfriNIC Prefixes per ASN: 22.90 AfriNIC Region origin ASes announcing only one prefix: 172 AfriNIC Region transit ASes present in the Internet Routing Table: 182 Average AfriNIC Region AS path length visible: 4.6 Max AfriNIC Region AS path length visible: 18 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 263 Number of AfriNIC addresses announced to Internet: 81179648 Equivalent to 4 /8s, 214 /16s and 180 /24s 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 5558 4190 74 ERX-CERNET-BKB China Education and Rese 7545 3525 382 250 TPG-INTERNET-AP TPG Telecom Limited, AU 4766 3014 11138 984 KIXS-AS-KR Korea Telecom, KR 17974 2943 904 78 TELKOMNET-AS2-AP PT Telekomunikasi Indo 9829 2694 1497 532 BSNL-NIB National Internet Backbone, IN 9808 2246 8781 42 CMNET-GD Guangdong Mobile Communication 4755 2053 429 222 TATACOMM-AS TATA Communications formerl 4808 1757 2289 524 CHINA169-BJ China Unicom Beijing Provin 45899 1601 1235 89 VNPT-AS-VN VNPT Corp, VN 24560 1548 515 223 AIRTELBROADBAND-AS-AP Bharti Airtel Ltd 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 3515 2964 145 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 6389 2221 3671 41 BELLSOUTH-NET-BLK - BellSouth.net Inc., 18566 2194 405 110 MEGAPATH5-US - MegaPath Corporation, US 20115 1940 1982 405 CHARTER-NET-HKY-NC - Charter Communicat 30036 1752 339 291 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom 209 1730 5071 664 CENTURYLINK-US-LEGACY-QWEST - Qwest Com 6983 1676 848 227 ITCDELTA - Earthlink, Inc., US 701 1625 10693 678 UUNET - MCI Communications Services, In 16509 1403 2534 472 AMAZON-02 - Amazon.com, Inc., US 7018 1365 20092 1005 ATT-INTERNET4 - AT&T Services, Inc., US 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 3329 169 15 ALJAWWALSTC-AS , SA 20940 2816 1069 1999 AKAMAI-ASN1 , US 34984 1968 325 361 TELLCOM-AS , TR 12479 1343 1018 46 UNI2-AS , ES 13188 1236 99 57 BANKINFORM-AS , UA 8551 1206 377 46 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 6849 1144 355 21 UKRTELNET , UA 8402 1089 544 15 CORBINA-AS Russia, RU 9198 934 352 25 KAZTELECOM-AS , KZ 12389 925 1113 401 ROSTELECOM-AS , RU 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 3484 540 184 Telmex Colombia S.A., CO 8151 2284 3396 558 Uninet S.A. de C.V., MX 7303 1543 955 245 Telecom Argentina S.A., AR 6503 1404 437 55 Axtel, S.A.B. de C.V., MX 11830 1326 367 57 Instituto Costarricense de Electricidad 6147 1078 377 27 Telefonica del Peru S.A.A., PE 7738 994 1882 40 Telemar Norte Leste S.A., BR 3816 965 468 202 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 28573 934 2203 176 CLARO S.A., BR 11172 907 125 76 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 1179 402 50 LINKdotNET-AS, EG 36903 684 344 115 MT-MPLS, MA 37611 666 51 5 Afrihost, ZA 36992 547 1373 25 ETISALAT-MISR, EG 8452 539 1472 15 TE-AS TE-AS, EG 37492 384 250 69 ORANGE-TN, TN 24835 349 611 17 RAYA-AS, EG 29571 318 37 12 CITelecom-AS, CI 15399 298 35 7 WANANCHI-KE, KE 2018 269 327 74 TENET-1, ZA 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 5558 4190 74 ERX-CERNET-BKB China Education and Rese 7545 3525 382 250 TPG-INTERNET-AP TPG Telecom Limited, AU 22773 3515 2964 145 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 10620 3484 540 184 Telmex Colombia S.A., CO 39891 3329 169 15 ALJAWWALSTC-AS , SA 4766 3014 11138 984 KIXS-AS-KR Korea Telecom, KR 17974 2943 904 78 TELKOMNET-AS2-AP PT Telekomunikasi Indo 20940 2816 1069 1999 AKAMAI-ASN1 , US 9829 2694 1497 532 BSNL-NIB National Internet Backbone, IN 8151 2284 3396 558 Uninet S.A. de C.V., MX Complete listing at http://thyme.rand.apnic.net/current/data-ASnet Global Per AS Maximum Aggr summary ---------------------------------- ASN No of nets Net Savings Description 22773 3515 3370 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 39891 3329 3314 ALJAWWALSTC-AS , SA 10620 3484 3300 Telmex Colombia S.A., CO 7545 3525 3275 TPG-INTERNET-AP TPG Telecom Limited, AU 17974 2943 2865 TELKOMNET-AS2-AP PT Telekomunikasi Indo 9808 2246 2204 CMNET-GD Guangdong Mobile Communication 6389 2221 2180 BELLSOUTH-NET-BLK - BellSouth.net Inc., 9829 2694 2162 BSNL-NIB National Internet Backbone, IN 18566 2194 2084 MEGAPATH5-US - MegaPath Corporation, US 4766 3014 2030 KIXS-AS-KR Korea Telecom, KR 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 KLGELECS-AS 38, Teatralnaya st 65001 PRIVATE 31.172.192.0/20 15468 KLGELECS-AS 38, Teatralnaya st 65001 PRIVATE 31.172.192.0/21 15468 KLGELECS-AS 38, Teatralnaya st 65001 PRIVATE 31.172.200.0/21 15468 KLGELECS-AS 38, Teatralnaya st 65001 PRIVATE 31.172.208.0/21 15468 KLGELECS-AS 38, Teatralnaya st 65001 PRIVATE 31.172.216.0/21 15468 KLGELECS-AS 38, Teatralnaya st 65000 PRIVATE 31.219.177.0/25 8966 ETISALAT-AS P.O. Box 1150, Dub 65000 PRIVATE 31.219.177.128/25 8966 ETISALAT-AS P.O. Box 1150, Dub 65412 PRIVATE 41.89.7.0/24 36866 JTL, KE 65512 PRIVATE 45.252.244.0/24 45899 VNPT-AS-VN VNPT Corp, VN Complete listing at http://thyme.rand.apnic.net/current/data-badAS Advertised Unallocated Addresses -------------------------------- Network Origin AS Description 23.249.144.0/20 40430 COLO4JAX-AS - colo4jax, LLC, US 24.49.144.0/20 30164 USACOMMUNICATIONS-1 - USA COMPANIES, LP 27.100.7.0/24 56096 UNKNOWN 41.73.1.0/24 37004 -Reserved AS-, ZZ 41.73.2.0/24 37004 -Reserved AS-, ZZ 41.73.3.0/24 37004 -Reserved AS-, ZZ 41.73.4.0/24 37004 -Reserved AS-, ZZ 41.73.5.0/24 37004 -Reserved AS-, ZZ 41.73.6.0/24 37004 -Reserved AS-, ZZ 41.73.7.0/24 37004 -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:16 /9:13 /10:36 /11:103 /12:273 /13:523 /14:1052 /15:1773 /16:13150 /17:7833 /18:13012 /19:25408 /20:38759 /21:40323 /22:68143 /23:59710 /24:339823 /25:504 /26:475 /27:338 /28:55 /29:32 /30:13 /31:1 /32:33 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 39891 2896 3329 ALJAWWALSTC-AS , SA 22773 2739 3515 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 18566 2086 2194 MEGAPATH5-US - MegaPath Corporation, US 30036 1568 1752 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom 6389 1418 2221 BELLSOUTH-NET-BLK - BellSouth.net Inc., 10620 1408 3484 Telmex Colombia S.A., CO 6983 1325 1676 ITCDELTA - Earthlink, Inc., US 34984 1253 1968 TELLCOM-AS , TR 11492 1206 1304 CABLEONE - CABLE ONE, INC., US 13188 1011 1236 BANKINFORM-AS , UA Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1644 2:780 4:23 5:2174 6:31 8:991 12:1805 13:43 14:1742 15:46 16:2 17:97 18:126 20:50 22:1 23:1817 24:1803 27:2339 31:1783 32:84 33:4 35:5 36:328 37:2316 38:1247 39:36 40:101 41:2952 42:454 43:1836 44:47 45:2141 46:2545 47:98 49:1213 50:907 51:13 52:551 53:2 54:346 55:7 56:7 57:41 58:1570 59:1009 60:378 61:1823 62:1511 63:1927 64:4556 65:2174 66:4277 67:2209 68:1120 69:3263 70:1283 71:556 72:2058 74:2590 75:400 76:413 77:1380 78:1214 79:911 80:1298 81:1397 82:982 83:705 84:858 85:1566 86:483 87:1128 88:543 89:2098 90:231 91:6087 92:955 93:2373 94:2438 95:2487 96:558 97:341 98:959 99:89 100:148 101:1153 103:12333 104:2482 105:108 106:434 107:1428 108:786 109:2257 110:1271 111:1635 112:1054 113:1151 114:1084 115:1684 116:1675 117:1562 118:2038 119:1576 120:933 121:1121 122:2267 123:2039 124:1569 125:1824 128:666 129:439 130:417 131:1369 132:612 133:175 134:490 135:196 136:376 137:405 138:1885 139:430 140:579 141:462 142:664 143:955 144:729 145:164 146:945 147:659 148:1381 149:536 150:657 151:879 152:664 153:297 154:695 155:950 156:525 157:514 158:386 159:1239 160:510 161:735 162:2403 163:555 164:770 165:1135 166:335 167:1188 168:2187 169:667 170:1955 171:251 172:708 173:1741 174:760 175:674 176:1723 177:3940 178:2240 179:1179 180:2149 181:1869 182:2057 183:1001 184:824 185:7474 186:3129 187:2118 188:2204 189:1757 190:7673 191:1272 192:9020 193:5736 194:4450 195:3844 196:1773 197:1150 198:5581 199:5758 200:7159 201:3654 202:10113 203:9836 204:4514 205:2746 206:2980 207:3075 208:4046 209:3861 210:3886 211:2039 212:2723 213:2345 214:865 215:70 216:5775 217:1973 218:810 219:607 220:1635 221:883 222:699 223:1306 End of report

1 0

Manage Outage Notifications?
by Shawn L 23 Sep '16

23 Sep '16

What are people using to manage / send their outage notifications? We're currently using a mostly manual process to identify customers that need to be aware of an outage and send out e-mail at $dayjob. Looking for a way to automate it more. I'd prefer something open source, but that's not a requirement. Thanks

2 1

Re: PlayStationNetwork blocking of CGNAT public addresses
by Alexander Maassen 23 Sep '16

23 Sep '16

Maybe its time then for a global accepted, unified way to send/report abuse? That should solve most of the issues and end points would be able to deal with it in a common way and only would need to think about how to integrate it in their crm's etc. We are all using the same medium, but attempt to communicate issues using several methods. Perhaps iana can use those (m/b)illions they got from selling tld's and cook something up. Kind regards, Alexander Maassen - Technical Maintenance Engineer Parkstad Support BV- Maintainer DroneBL- Peplink Certified Engineer -------- Oorspronkelijk bericht --------Van: Baldur Norddahl <baldur.norddahl(a)gmail.com> Datum: 22-09-16 14:10 (GMT+01:00) Aan: nanog(a)nanog.org Onderwerp: Re: PlayStationNetwork blocking of CGNAT public addresses On 22 September 2016 at 10:42, Alexander Maassen <outsider(a)scarynet.org> wrote: > So you ignore/don't deal with the abuse coz it's shipped in a format you > refuse to handle? > > And you don't even bother telling the reporter you would like it in a per > ip format? Or make attempts to make it work the way they report it (split > out the ip's and modify the to be forwarded mail to only contain the ip's > belonging to that customer)???? > You will have to remember that these are automated mails from the reporter. If I write them back it goes into their bit bucket, because they do not really care enough to bother replying. I am betting they are sending out thousands mails each day and they can not handle manually replying to all of that. In the same way we receive a large amount of automated mail so we have to be able to handle it automatically. Send me something sane and I will make a script that forwards it. Send me something unusable and I wont - but I will not do manual handling of your automated mail. All I am trying to do here is tell people that send abuse mails not to combine multiple abuse complaints in one mail, because that makes it harder for everybody and makes it more likely that your mail will be dropped as too much work. Double so if your abuse mails is from an automated system, because I will try to match your automated system with my own. However it is much harder to make a system that can edit your complaint and duplicate it to several recipients, than it is to run a simple filter that just forwards the mail as is. As to PSN they will usually send multiple mails if the abuse is ongoing. At some point they will send a mail with just one IP and that one gets forwarded. So we are dropping some of the mails, but the users eventually get notified anyway. It is not ideal but it works. Regards, Baldur

4 3

PlayStationNetwork blocking of CGNAT public addresses
by Simon Lockhart 23 Sep '16

23 Sep '16

All, We operate an access network with several hundred thousand users. Increasingly we're putting the users behind CGNAT in order to continue to give them an IPv4 service (we're all dual-stack, so they all get public IPv6 too). Due to the demographic of our users, many of them are gamers. We're hitting a problem with PlayStationNetwork 'randomly' blocking some of our CGNAT outside addresses, because they claim to have received anomalous, or 'attack' traffic from that IP. This obviously causes problems for the other legitimate users who end up behind the same public IPv4 address. Despite numerous attempts to engage with PSN, they are unwilling to give us any additional information which would allow us to identify the 'rogue' users on our network, or to identify the 'unwanted' traffic so that we could either block it, or use it to identify the rogue users ourselves. Has anyone else come up against the problem, and/or have any suggestions on how best to resolve it? Many thanks in advance, Simon

18 34

Re: PlayStationNetwork blocking of CGNAT public addresses
by Alexander Maassen 22 Sep '16

22 Sep '16

So you ignore/don't deal with the abuse coz it's shipped in a format you refuse to handle? And you don't even bother telling the reporter you would like it in a per ip format? Or make attempts to make it work the way they report it (split out the ip's and modify the to be forwarded mail to only contain the ip's belonging to that customer)???? Kind regards, Alexander Maassen - Technical Maintenance Engineer Parkstad Support BV- Maintainer DroneBL- Peplink Certified Engineer -------- Oorspronkelijk bericht --------Van: Baldur Norddahl <baldur.norddahl(a)gmail.com> Datum: 21-09-16 10:37 (GMT+01:00) Aan: nanog(a)nanog.org Onderwerp: Re: PlayStationNetwork blocking of CGNAT public addresses Hi We have the opposite problem with PSN: Sometimes they will send abuse reports with several of our IP addresses listed. The problem with that is that we can not give data about one customer to another customer. By listing multiple IP addresses we are prevented from forwarding the email to the customer. Which means we may ignore it instead. Regards, Baldur

5 6

Livestream of NYNOG Meetup #2 today
by Joly MacFie 22 Sep '16

22 Sep '16

10:45am EDT https://livestream.com/internetsociety/nynog2 -- --------------------------------------------------------------- Joly MacFie 218 565 9365 Skype:punkcast -------------------------------------------------------------- -

1 0

Re: PlayStationNetwork blocking of CGNAT public addresses
by Alexander Maassen 22 Sep '16

22 Sep '16

Both gamers and content providers do not care. The gamers as they only care about the game itself and don't care about the technical mumbo jumbo. And the makers coz they only care about making money by producing content the gamers want. And you service providers are left with the headache of attempts to please both sides. If this wasn't the case, then why after 20 years, ipv6 ain't rolled out. Hence again I'd be voting for an ipv6 only day, but that will never happen..... Kind regards, Alexander Maassen - Technical Maintenance Engineer Parkstad Support BV- Maintainer DroneBL- Peplink Certified Engineer -------- Oorspronkelijk bericht --------Van: Mark Andrews <marka(a)isc.org> Datum: 21-09-16 03:29 (GMT+01:00) Aan: Justin Wilson <lists(a)mtin.net> Cc: NANOG <nanog(a)nanog.org> Onderwerp: Re: PlayStationNetwork blocking of CGNAT public addresses In message <09342130-874F-4FA4-B410-B7B66A75FA4D(a)mtin.net>, Justin Wilson write s: > PSN is one reason I am not a fan of CGNAT. All they see are tons of > connections from the same IP. This results in them banning folks. Due > to them being hacked so many times getting them to actually communicate > is almost impossible. My .02 is just get the gamers a true public if at > all possible. > > Justin Wilson > j2sw(a)mtin.net What we need is business tech reporters to continually report on these failures of content providers to deliver their services over IPv6. 20 years lead time should be enough for any service. Mark -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: marka(a)isc.org

3 2

Re: PlayStationNetwork blocking of CGNAT public addresses
by Alexander Maassen 22 Sep '16

22 Sep '16

Ipv6 is there for 20+ years, cgnat is needed coz the net grows kinda exponentially due to stuff like IoT/mobiles/m2m, and isp's need to provide users with the ability to talk ipv4 simply because the other side refuses to deploy v6 abilities. Do the math if they really care. Also the servers itself hosting the gameserver probably already are dual stacked. But the gamecode itself misses the support. Then there is the issue of you as isp not being able or daring to show a fist and simply saying: screw you. Because you are risking to loose customers. And as long as the company's earn plenty of money using outdated code, they won't change it, coz that would imply spending money that won't flow into fancy buildings, fast cars and all that other useless luxury. Kind regards, Alexander Maassen - Technical Maintenance Engineer Parkstad Support BV- Maintainer DroneBL- Peplink Certified Engineer -------- Oorspronkelijk bericht --------Van: Mike Hammett <nanog(a)ics-il.net> Datum: 22-09-16 13:23 (GMT+01:00) Aan: Alexander Maassen <outsider(a)scarynet.org> Cc: NANOG <nanog(a)nanog.org> Onderwerp: Re: PlayStationNetwork blocking of CGNAT public addresses If you told them they would have fewer NAT issues if they supported IPv6, they'd start to care. ;-) They know enough to hate NAT. ----- Mike Hammett Intelligent Computing Solutions Midwest Internet Exchange The Brothers WISP From: "Alexander Maassen" <outsider(a)scarynet.org> Cc: "NANOG" <nanog(a)nanog.org> Sent: Thursday, September 22, 2016 3:35:01 AM Subject: Re: PlayStationNetwork blocking of CGNAT public addresses Both gamers and content providers do not care. The gamers as they only care about the game itself and don't care about the technical mumbo jumbo. And the makers coz they only care about making money by producing content the gamers want. And you service providers are left with the headache of attempts to please both sides. If this wasn't the case, then why after 20 years, ipv6 ain't rolled out. Hence again I'd be voting for an ipv6 only day, but that will never happen..... Kind regards, Alexander Maassen - Technical Maintenance Engineer Parkstad Support BV- Maintainer DroneBL- Peplink Certified Engineer -------- Oorspronkelijk bericht --------Van: Mark Andrews <marka(a)isc.org> Datum: 21-09-16 03:29 (GMT+01:00) Aan: Justin Wilson <lists(a)mtin.net> Cc: NANOG <nanog(a)nanog.org> Onderwerp: Re: PlayStationNetwork blocking of CGNAT public addresses In message <09342130-874F-4FA4-B410-B7B66A75FA4D(a)mtin.net>, Justin Wilson write s: > PSN is one reason I am not a fan of CGNAT. All they see are tons of > connections from the same IP. This results in them banning folks. Due > to them being hacked so many times getting them to actually communicate > is almost impossible. My .02 is just get the gamers a true public if at > all possible. > > Justin Wilson > j2sw(a)mtin.net What we need is business tech reporters to continually report on these failures of content providers to deliver their services over IPv6. 20 years lead time should be enough for any service. Mark -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: marka(a)isc.org

1 0

Re: PlayStationNetwork blocking of CGNAT public addresses
by Alexander Maassen 22 Sep '16

22 Sep '16

As long as their is no international accepted standard as to how to report abuse and everyone cooking up his/her own methods.. I think you have either the choice of adapting and thus be able to deal with the abuse. Or be lazy and stubborn, ignore it, wait for the bad reputation to say hi to your company and face the effects it might cause. Kind regards, Alexander Maassen - Technical Maintenance Engineer Parkstad Support BV- Maintainer DroneBL- Peplink Certified Engineer -------- Oorspronkelijk bericht --------Van: Tom Beecher <beecher(a)beecher.cc> Datum: 21-09-16 17:13 (GMT+01:00) Aan: Justin Wilson <lists(a)mtin.net> Cc: NANOG <nanog(a)nanog.org> Onderwerp: Re: PlayStationNetwork blocking of CGNAT public addresses I have a hard time accepting that service providers should re-engineer their networks because other companies cannot properly engineer their abuse tooling. On Tue, Sep 20, 2016 at 11:33 AM, Justin Wilson <lists(a)mtin.net> wrote: > PSN is one reason I am not a fan of CGNAT. All they see are tons of > connections from the same IP. This results in them banning folks. Due to > them being hacked so many times getting them to actually communicate is > almost impossible. My .02 is just get the gamers a true public if at all > possible. > > Justin Wilson > j2sw(a)mtin.net > > --- > http://www.mtin.net Owner/CEO > xISP Solutions- Consulting – Data Centers - Bandwidth > > http://www.midwest-ix.com COO/Chairman > Internet Exchange - Peering - Distributed Fabric > > > On Sep 20, 2016, at 8:24 AM, Danijel Starman <theghost101(a)gmail.com> > wrote: > > > > Something similar happened to a local FantasyConon I was helping set up, > we > > had only two PS4 machines there and accounts provided by Blizzard for > > Overwatch. Outside IP of the LAN (as it was NATed) was banned by PSN in > > about 8h. There was no other traffic other then those two accounts > playing > > Overwatch so my guess is that they have some too aggressive checks. I've > > managed to convince our ISP there to change the outside IP of the link so > > we got them working the next day but it happened again in 8h. > > > > -- > > *blap* > > > > On Fri, Sep 16, 2016 at 3:12 PM, Simon Lockhart <simon(a)slimey.org> > wrote: > > > >> All, > >> > >> We operate an access network with several hundred thousand users. > >> Increasingly > >> we're putting the users behind CGNAT in order to continue to give them > an > >> IPv4 > >> service (we're all dual-stack, so they all get public IPv6 too). Due to > the > >> demographic of our users, many of them are gamers. > >> > >> We're hitting a problem with PlayStationNetwork 'randomly' blocking some > >> of our > >> CGNAT outside addresses, because they claim to have received anomalous, > or > >> 'attack' traffic from that IP. This obviously causes problems for the > other > >> legitimate users who end up behind the same public IPv4 address. > >> > >> Despite numerous attempts to engage with PSN, they are unwilling to > give us > >> any additional information which would allow us to identify the 'rogue' > >> users > >> on our network, or to identify the 'unwanted' traffic so that we could > >> either > >> block it, or use it to identify the rogue users ourselves. > >> > >> Has anyone else come up against the problem, and/or have any > suggestions on > >> how best to resolve it? > >> > >> Many thanks in advance, > >> > >> Simon > >> > >> > > > >

1 0