February 2022 - NANOG - lists.nanog.org

Weekly Global IPv4 Routing Table Report
by Routing Table Analysis Role Account 11 Feb '22

11 Feb '22

This is an automated weekly mailing describing the state of the Global IPv4 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 https://thyme.apnic.net. If you have any comments please contact Philip Smith <pfsinoz(a)gmail.com>. IPv4 Routing Table Report 04:00 +10GMT Sat 12 Feb, 2022 BGP Table (Global) as seen in Japan. Report Website: https://thyme.apnic.net Detailed Analysis: https://thyme.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 888216 Prefixes after maximum aggregation (per Origin AS): 334710 Deaggregation factor: 2.65 Unique aggregates announced (without unneeded subnets): 427455 Total ASes present in the Internet Routing Table: 72833 Prefixes per ASN: 12.20 Origin-only ASes present in the Internet Routing Table: 62489 Origin ASes announcing only one prefix: 25802 Transit ASes present in the Internet Routing Table: 10344 Transit-only ASes present in the Internet Routing Table: 368 Average AS path length visible in the Internet Routing Table: 4.3 Max AS path length visible: 53 Max AS path prepend of ASN (265020) 50 Prefixes from unregistered ASNs in the Routing Table: 962 Number of instances of unregistered ASNs: 965 Number of 32-bit ASNs allocated by the RIRs: 38545 Number of 32-bit ASNs visible in the Routing Table: 32109 Prefixes from 32-bit ASNs in the Routing Table: 149645 Number of bogon 32-bit ASNs visible in the Routing Table: 22 Special use prefixes present in the Routing Table: 1 Prefixes being announced from unallocated address space: 562 Number of addresses announced to Internet: 3068928512 Equivalent to 182 /8s, 236 /16s and 34 /24s Percentage of available address space announced: 82.9 Percentage of allocated address space announced: 82.9 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 99.5 Total number of prefixes smaller than registry allocations: 300423 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 233450 Total APNIC prefixes after maximum aggregation: 65864 APNIC Deaggregation factor: 3.54 Prefixes being announced from the APNIC address blocks: 228289 Unique aggregates announced from the APNIC address blocks: 94179 APNIC Region origin ASes present in the Internet Routing Table: 12370 APNIC Prefixes per ASN: 18.46 APNIC Region origin ASes announcing only one prefix: 3541 APNIC Region transit ASes present in the Internet Routing Table: 1714 Average APNIC Region AS path length visible: 4.6 Max APNIC Region AS path length visible: 29 Number of APNIC region 32-bit ASNs visible in the Routing Table: 7566 Number of APNIC addresses announced to Internet: 774475904 Equivalent to 46 /8s, 41 /16s and 144 /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-151865 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: 258538 Total ARIN prefixes after maximum aggregation: 119014 ARIN Deaggregation factor: 2.17 Prefixes being announced from the ARIN address blocks: 258644 Unique aggregates announced from the ARIN address blocks: 123403 ARIN Region origin ASes present in the Internet Routing Table: 18983 ARIN Prefixes per ASN: 13.63 ARIN Region origin ASes announcing only one prefix: 6899 ARIN Region transit ASes present in the Internet Routing Table: 1960 Average ARIN Region AS path length visible: 3.8 Max ARIN Region AS path length visible: 35 Number of ARIN region 32-bit ASNs visible in the Routing Table: 4342 Number of ARIN addresses announced to Internet: 1295964160 Equivalent to 77 /8s, 62 /16s and 216 /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-401308 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: 253719 Total RIPE prefixes after maximum aggregation: 116382 RIPE Deaggregation factor: 2.18 Prefixes being announced from the RIPE address blocks: 250101 Unique aggregates announced from the RIPE address blocks: 148984 RIPE Region origin ASes present in the Internet Routing Table: 28185 RIPE Prefixes per ASN: 8.87 RIPE Region origin ASes announcing only one prefix: 12134 RIPE Region transit ASes present in the Internet Routing Table: 3977 Average RIPE Region AS path length visible: 4.3 Max RIPE Region AS path length visible: 32 Number of RIPE region 32-bit ASNs visible in the Routing Table: 10644 Number of RIPE addresses announced to Internet: 713448576 Equivalent to 42 /8s, 134 /16s and 92 /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-213403 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: 113955 Total LACNIC prefixes after maximum aggregation: 27367 LACNIC Deaggregation factor: 4.16 Prefixes being announced from the LACNIC address blocks: 114689 Unique aggregates announced from the LACNIC address blocks: 48536 LACNIC Region origin ASes present in the Internet Routing Table: 10944 LACNIC Prefixes per ASN: 10.48 LACNIC Region origin ASes announcing only one prefix: 2676 LACNIC Region transit ASes present in the Internet Routing Table: 2210 Average LACNIC Region AS path length visible: 4.9 Max LACNIC Region AS path length visible: 53 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 8630 Number of LACNIC addresses announced to Internet: 176510208 Equivalent to 10 /8s, 133 /16s and 85 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-273820 + 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: 27592 Total AfriNIC prefixes after maximum aggregation: 5367 AfriNIC Deaggregation factor: 5.14 Prefixes being announced from the AfriNIC address blocks: 35931 Unique aggregates announced from the AfriNIC address blocks: 11875 AfriNIC Region origin ASes present in the Internet Routing Table: 1593 AfriNIC Prefixes per ASN: 22.56 AfriNIC Region origin ASes announcing only one prefix: 552 AfriNIC Region transit ASes present in the Internet Routing Table: 312 Average AfriNIC Region AS path length visible: 5.1 Max AfriNIC Region AS path length visible: 34 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 927 Number of AfriNIC addresses announced to Internet: 108164608 Equivalent to 6 /8s, 114 /16s and 118 /24s AfriNIC AS Blocks 36864-37887, 327680-329727 & 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 9808 9059 8886 46 CHINAMOBILE-CN China Mobile Communicati 7545 5867 788 691 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4681 4192 74 ERX-CERNET-BKB China Education and Rese 7552 3596 1330 20 VIETEL-AS-AP Viettel Group, VN 7713 3484 1038 51 TELKOMNET-AS-AP PT Telekomunikasi Indon 45899 3435 1880 57 VNPT-AS-VN VNPT Corp, VN 4766 2557 11123 631 KIXS-AS-KR Korea Telecom, KR 9498 2317 475 235 BBIL-AP BHARTI Airtel Ltd., IN 45090 2170 1438 79 TENCENT-NET-AP Shenzhen Tencent Compute 4755 2114 429 198 TATACOMM-AS TATA Communications formerl Complete listing at https://thyme.apnic.net/current/data-ASnet-APNIC ARIN Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 16509 6241 10151 2680 AMAZON-02, US 11492 4514 299 785 CABLEONE, US 22773 3963 3028 367 ASN-CXA-ALL-CCI-22773-RDC, US 7155 3902 264 30 VIASAT-SP-BACKBONE, US 16625 3650 1883 2564 AKAMAI-AS, US 6327 3376 1318 63 SHAW, CA 749 2887 50780 2143 DNIC-AS-00749, US 30036 2608 374 150 MEDIACOM-ENTERPRISE-BUSINESS, US 209 2519 4962 428 CENTURYLINK-US-LEGACY-QWEST, US 20115 2253 3036 500 CHARTER-20115, US Complete listing at https://thyme.apnic.net/current/data-ASnet-ARIN RIPE Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 12479 6801 1715 152 UNI2-AS, ES 9121 6745 1692 17 TTNET, TR 8551 4004 378 39 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 20940 3887 3347 207 AKAMAI-ASN1, NL 39891 3274 188 25 ALJAWWALSTC-AS, SA 12389 2961 2274 910 ROSTELECOM-AS, RU 9009 2469 250 1285 M247, GB 34984 2225 358 604 TELLCOM-AS, TR 47331 1953 312 1490 TTNET, TR 58224 1792 929 580 TCI, IR Complete listing at https://thyme.apnic.net/current/data-ASnet-RIPE LACNIC Region per AS prefix count summary ----------------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 10268 3415 566 Uninet S.A. de C.V., MX 10620 3458 519 719 Telmex Colombia S.A., CO 11830 2456 369 62 Instituto Costarricense de Electricidad 13999 1666 284 474 Mega Cable, S.A. de C.V., MX 6503 1441 354 524 Axtel, S.A.B. de C.V., MX 28573 1400 2330 246 CLARO S.A., BR 3816 1246 651 148 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 26615 1149 2351 140 TIM SA, BR 6147 1096 369 21 Telefonica del Peru S.A.A., PE 11664 1001 191 447 Techtel LMDS Comunicaciones Interactiva Complete listing at https://thyme.apnic.net/current/data-ASnet-LACNIC AfriNIC Region per AS prefix count summary ------------------------------------------ ASN No of nets /20 equiv MaxAgg Description 24863 1607 393 21 LINKdotNET-AS, EG 24835 1546 515 32 RAYA-AS, EG 36992 1299 1518 262 ETISALAT-MISR, EG 36903 1195 543 114 MT-MPLS, MA 29571 895 63 57 ORANGE-COTE-IVOIRE, CI 36935 735 521 39 Vodafone-, EG 6713 612 1863 34 IAM-AS, MA 15399 519 50 33 WANANCHI-, KE 37342 468 32 1 MOVITEL, MZ 23889 422 232 16 MauritiusTelecom, MU Complete listing at https://thyme.apnic.net/current/data-ASnet-AFRINIC Global Per AS prefix count summary ---------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 10268 3415 566 Uninet S.A. de C.V., MX 9808 9059 8886 46 CHINAMOBILE-CN China Mobile Communicati 12479 6801 1715 152 UNI2-AS, ES 9121 6745 1692 17 TTNET, TR 16509 6241 10151 2680 AMAZON-02, US 7545 5867 788 691 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4681 4192 74 ERX-CERNET-BKB China Education and Rese 11492 4514 299 785 CABLEONE, US 8551 4004 378 39 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 22773 3963 3028 367 ASN-CXA-ALL-CCI-22773-RDC, US Complete listing at https://thyme.apnic.net/current/data-ASnet Global Per AS Maximum Aggregation summary ----------------------------------------- ASN No of nets Net Savings Description 9808 9059 9013 CHINAMOBILE-CN China Mobile Communications Grou 9121 6745 6728 TTNET, TR 12479 6801 6649 UNI2-AS, ES 7545 5867 5176 TPG-INTERNET-AP TPG Telecom Limited, AU 4538 4681 4607 ERX-CERNET-BKB China Education and Research Net 8551 4004 3965 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 7155 3902 3872 VIASAT-SP-BACKBONE, US 11492 4514 3729 CABLEONE, US 20940 3887 3680 AKAMAI-ASN1, NL 22773 3963 3596 ASN-CXA-ALL-CCI-22773-RDC, US Complete listing at https://thyme.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Net Originated Transit AS Transit AS Name 46990 UNALLOCATED 8.5.242.0/23 3356 LEVEL3, US 62828 UNALLOCATED 8.21.130.0/24 3356 LEVEL3, US 393266 UNALLOCATED 8.23.52.0/24 46887 LIGHTOWER, US 18604 UNALLOCATED 8.25.204.0/24 3356 LEVEL3, US 394936 UNALLOCATED 8.33.224.0/24 22442 HOU-PHONOSCOPE, US 54338 UNALLOCATED 8.33.241.0/24 6461 ZAYO-6461, US 395438 UNALLOCATED 8.42.206.0/24 3356 LEVEL3, US 395056 UNALLOCATED 8.45.133.0/24 3356 LEVEL3, US 32306 UNALLOCATED 8.46.80.0/24 33652 CMCS, US 17033 UNALLOCATED 8.48.225.0/24 3356 LEVEL3, US Complete listing at https://thyme.apnic.net/current/data-badAS Prefixes from the Special Purpose Address Registry (Global) ----------------------------------------------------------- Prefix Origin AS Description 192.88.99.0/24 6939 HURRICANE, US Complete listing at https://thyme.apnic.net/current/data-spar Advertised Unallocated Addresses -------------------------------- Unassigned Network ASN Information AS Name 23.141.0.0/24 Origin: 395350 UNASSIGNED 23.141.0.0/24 Transit: 11426 TWC-11426-CAROLINAS, US 23.252.160.0/24 Origin: 398968 GROUP-IID-01, US 23.252.160.0/24 Transit: 174 COGENT-174, US 23.252.161.0/24 Origin: 398968 GROUP-IID-01, US 23.252.161.0/24 Transit: 174 COGENT-174, US 23.252.163.0/24 Origin: 398968 GROUP-IID-01, US 23.252.163.0/24 Transit: 174 COGENT-174, US 23.252.164.0/24 Origin: 398968 GROUP-IID-01, US 23.252.164.0/24 Transit: 174 COGENT-174, US Complete listing at https://thyme.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:40 /11:102 /12:305 /13:590 /14:1204 /15:2034 /16:13577 /17:8355 /18:13897 /19:25165 /20:43382 /21:52167 /22:108288 /23:95228 /24:523062 /25:791 /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 9121 5908 6745 TTNET, TR 12479 5765 6801 UNI2-AS, ES 8151 3943 10268 Uninet S.A. de C.V., MX 8551 3469 4004 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 11492 3436 4514 CABLEONE, US 6327 3187 3376 SHAW, CA 7155 2992 3902 VIASAT-SP-BACKBONE, US 22773 2956 3963 ASN-CXA-ALL-CCI-22773-RDC, US 39891 2810 3274 ALJAWWALSTC-AS, SA 30036 2263 2608 MEDIACOM-ENTERPRISE-BUSINESS, US Complete listing at https://thyme.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1924 2:996 3:153 4:7 5:3744 6:103 7:5 8:1559 9:1 11:172 12:1720 13:415 14:2386 15:160 16:39 17:368 18:137 20:167 21:4 22:188 23:5486 24:2337 25:6 27:2585 29:19 31:2414 32:98 34:1 35:58 36:1734 37:3947 38:2518 39:681 40:149 41:3924 42:1058 43:2091 44:288 45:15960 46:3885 47:303 49:1639 50:1913 51:107 52:1361 53:1 54:293 55:755 56:8 57:55 58:1764 59:1165 60:959 61:2266 62:2442 63:1938 64:5499 65:2307 66:4901 67:2932 68:1177 69:4165 70:1347 71:672 72:3056 74:2630 75:1515 76:717 77:2120 78:3810 79:3099 80:1951 81:1663 82:1457 83:1194 84:1336 85:3625 86:714 87:1952 88:2621 89:3190 90:506 91:7533 92:1886 93:2595 94:3262 95:4488 96:1309 97:345 98:988 99:862 100:75 101:1032 102:1960 103:28252 104:4137 105:463 106:812 107:2459 108:768 109:4182 110:2058 111:3258 112:1965 113:1531 114:1535 115:1955 116:1896 117:2496 118:2328 119:1827 120:1667 121:1031 122:2543 123:2110 124:1611 125:2090 128:1348 129:1201 130:926 131:2084 132:760 133:370 134:1925 135:287 136:860 137:861 138:2436 139:1221 140:883 141:1354 142:1255 143:1443 144:1230 145:344 146:1770 147:1471 148:2218 149:1686 150:857 151:1078 152:1825 153:448 154:3591 155:1340 156:1878 157:1221 158:1012 159:2044 160:2402 161:1301 162:3447 163:1217 164:1662 165:1573 166:633 167:1692 168:3703 169:682 170:4335 171:824 172:3002 173:3061 174:1024 175:1128 176:3519 177:4603 178:3031 179:1994 180:2286 181:2928 182:3243 183:1920 184:2391 185:19285 186:4293 187:3573 188:3809 189:3020 190:8841 191:1316 192:11033 193:8516 194:6917 195:4983 196:2923 197:2359 198:5997 199:6008 200:7507 201:5660 202:10402 203:9993 204:4541 205:3357 206:3852 207:3403 208:4009 209:4631 210:4235 211:2454 212:3942 213:3378 214:1158 215:64 216:6382 217:2652 218:1247 219:600 220:1955 221:988 222:857 223:2173 End of report

1 0

Cryptocurrency attack due to BGP hijacking
by Andrew Wesie 11 Feb '22

11 Feb '22

Recently, there was an attack on Klayswap [1] believed to be due to BGP hijacking [2]. From the public data on routeviews, we can see that there were announcements for the hijacked IP ranges, for example: U|A|1643854199.000000|routeviews|route-views.wide|||2497|202.249.2.169|211.249.221.0/24|202.249.2.169|2497 6461 9457|9457||| The weird part is that the path from AS6461 to AS9457 does not show up in any other routes. As far as I can tell from public information, there is no transit nor peering relationship between AS6461 and AS9457. As such, it seems likely a peer or customer of AS6461 was impersonating AS9457. I sent an email to Zayo's abuse email asking if they could provide any additional information but did not receive a response. If anyone has additional information, please reach out. Especially information about where the announcement may have originated. -- Andrew Wesie Theori, Inc. [1] https://medium.com/klayswap/klayswap-compensation-plan-99ec4db6742f [2] https://economist.co.kr/2022/02/07/column/expertColumn/20220207070013230.ht…

1 0

Re: VPN recommendations?
by William Herrin 10 Feb '22

10 Feb '22

On Thu, Feb 10, 2022 at 10:47 AM Juri Grabowski <nanog(a)jugra.de> wrote: > Or buy official supported hardware from https://shop.opnsense.com/ Howdy, Opnsense looks like it might work. I dug through some of the documentation but didn't find something entirely on point for my use case. Are you aware of any documentation which describes: LAN - OPNSense Appliance - (rfc1918) NAT Appliance (dynamic IP) - Internet - (static IP) OPNSense appliance - LAN Where the left-side OPNSense is responsible for establishing and keeping the NAT translations alive without any special configuration on the NAT? Thanks, Bill -- William Herrin bill(a)herrin.us https://bill.herrin.us/

2 1

Re: VPN recommendations?
by William Herrin 10 Feb '22

10 Feb '22

On Thu, Feb 10, 2022 at 10:06 AM Guillaume Tournat <guillaume(a)ironie.org> wrote: > Fortinet firewalls (FortiGate) are a great deal Thanks Guillaume, I found this https://community.fortinet.com/t5/FortiGate/Technical-Tip-IPsec-VPN-between… but it suggests that the dynamic IP fortigate expects to have a public dynamic IP directly on the Fortigate, not be stuck behind a NAT. Are you aware of any documentation that describes: LAN - Fortigate - NAT (dynaimic IP) - Internet - (static IP) Fortigate - LAN Where the Meraki is responsible for keeping the NAT translations alive without any programming on the NAT? Regards, Bill -- William Herrin bill(a)herrin.us https://bill.herrin.us/

1 0

Lumen/Century Link Clue Contact
by Mark Tinka 10 Feb '22

10 Feb '22

Hi all. Grateful if anyone from Lumen with some clue can reach out. They appear to be dropping traffic to our name servers (ns3.seacomnet.com + ns4.seacomnet.com) at our interconnect transit edge with them in MRS. Naturally, this is causing whoever is on their network to fail DNS queries to zones hosted on those name servers, which is causing all kinds of breakage, e-mail included. We can't e-mail them because, obviously, they can't verify our source domain names; and what should be our AM's appear to be on some kind of holiday. If someone from there can reach out to me (ideally from a non-Lumen/CenturyLink/Level(3) e-mail address), I'd be terribly obliged. Thanks. Mark.

1 0

Fwd: 2022 MANRS Ambassadors
by Arturo Servin 10 Feb '22

10 Feb '22

I think that this message hasn't been shared here. Regards as ---------- Forwarded message --------- From: Israel Rosas <rosas(a)isoc.org> Date: Mon, 7 Feb 2022 at 16:12 Subject: [lacnog] 2022 MANRS Ambassadors To: LACNOG <lacnog(a)lacnic.net> Dear all, Happy Monday! I’m reaching out to you to announce that today we are opening the call for applications for the 2022 MANRS Ambassadors program. *Ambassadors are required to be part of a MANRS participant organization*. They'll be responsible for guiding and mentoring a group of Fellows, as well as work together with the MANRS team. The call will remain open from 7-18 February. Selected Ambassadors will be announced on March 4. All the details and the link to participate can be found at https://www.manrs.org/ambassadors-program/ At the end of this month we will start the selection process for MANRS Fellows. In that case, the call for applications will be open to any interested person, not only to MANRS participants. Cheers, *Israel Rosas*, Senior Regional Development Manager rosas(a)isoc.org | Mobile: +52 55 3550 2363 | Pronouns: he/him/his internetsociety.org | @internetsociety My work hours may not be your work hours. Please respond in your own time. _______________________________________________ LACNOG mailing list LACNOG(a)lacnic.net https://mail.lacnic.net/mailman/listinfo/lacnog Cancelar suscripcion: https://mail.lacnic.net/mailman/options/lacnog

1 0

HULU
by Shon Elliott 10 Feb '22

10 Feb '22

Anyone from HULU on the list that can contact me regarding a network issue? Kind Regards, Shon Elliott Level 3 IP/Routing/Security Network Engineer unWired Broadband, LLC. selliott(a)getunwired.com<mailto:selliott@getunwired.com> [uw-logo] www.getunwired.com<http://www.getunwired.com/> The Valleys #1 Rural High-Speed Fixed Wireless Internet Service Provider

1 0

NANOG 84 Networking Events - N84 Kicks-Off Monday!
by Nanog News 09 Feb '22

09 Feb '22

*NANOG 84 Networking Opportunities * Networking is essential to the health of your career! Take advantage of the opportunity to meet + greet with industry leaders + professionals at next week's networking events at NANOG 84. *Day 1: Newcomers Breakfast Orientation* Monday, Feb. 14 | 9:00am - 9:45am CST Location: Waterloo Ballroom 5-6, Level 5 New to NANOG? Don’t miss our Newcomers Breakfast Orientation happening Monday, Feb 14 at 9:00am at our upcoming meeting, NANOG 84. Have an opportunity to network with fellow newcomers! *REGISTER NOW <https://nanog.org/events/nanog-84/>* *Day 1: NANOG Networking Luncheon * Monday, Feb. 14 | 12:00pm - 1:30pm CST Location: MoonTower Hall, Level 2 Some of the tables at lunch will have "Table Topics" for you to use to chat with others & network around the same topic. - Network Management - Automation - BGP Security - Routing - Traffic Management and Policy - Job Hunting - Peering - Newcomers Networking Follow-up - War Stories - The Time I Thought I'd Get Fired Sponsors: Kentik <https://nanog.us20.list-manage.com/track/click?u=4d708401d0e69d9dc73d1c204&…> , Sparkle <https://nanog.us20.list-manage.com/track/click?u=4d708401d0e69d9dc73d1c204&…> ,Telescent <https://nanog.us20.list-manage.com/track/click?u=4d708401d0e69d9dc73d1c204&…> *SEE AGENDA * <https://www.nanog.org/events/nanog-84/nanog-84-agenda/> *Day 2: Women in Tech * Tuesday, Feb. 15 | 12:00pm - 1:15pm CST Location: Waterloo Ballroom 5-6, Level 5 "What makes NANOG an incredible community, also makes it intimidating - 'courageous women' helping you not feel small" - Jezzibell Gilmore Co-founder of Packetfabric This is a no-pressure space to empower your fellow (wo)man! Join us for an opportunity to meet, network + potentially find your next mentee or mentor in the Women in Tech community. *Sponsor:* AWS <https://nanog.us20.list-manage.com/track/click?u=4d708401d0e69d9dc73d1c204&…> *SEE AGENDA <https://www.nanog.org/events/nanog-84/nanog-84-agenda/>* *Peering Forum Applications Still Available * NANOG 84 Peering Coordination Forum tables are still available. The forum provides time for attendees to meet + network with others in the peering community present at NANOG. Sign up for your table today! *SIGN UP * <https://www.nanog.org/events/nanog-84/peering-forum/>

1 0

PeeringDB Hackathon - looking for feature requests
by Steve McManus 09 Feb '22

09 Feb '22

PeeringDB is looking at participating at an upcoming NANOG Hackathon. One of the ideas for a theme is to improve the API. Specifically by adding API calls for common use cases that people need to handle outside of the API. Typically, by dumping the entire database to SQL For example - given two IXes, which networks are present at both? We'd like to make a list of such useful queries such that people don't have to dump the database just to run them. A stretch goal would be to expose into the website instead of requiring API calls. This issue has some more detail, including a few existing ideas: https://github.com/peeringdb/peeringdb/issues/1020 Comments there or in email to me would be super helpful. As always, if there are other feature requests for PeeringDB, feel free to create an issue in github ( https://github.com/peeringdb/peeringdb/issues/new/choose ) or in email, even if they're not strictly Hackathon ideas. They are always appreciated! Thanks! -Steve PeeringDB Product Committee chair

4 4

Re: Authoritative Resources for Public DNS Pinging
by J. Hellenthal 09 Feb '22

09 Feb '22

Not to mention. It is viable traffic to monitor, if I know that I get X number of icmp traffic through a point in tranfer consistently and that starts to drop off considerably that it may be a failing connection due to some circumstance I should start checking that equipment. And if im that connection in the middle... that is money ! On Wed, Feb 09, 2022 at 03:02:19PM +0000, J. Hellenthal wrote: > > Just think of all the smokeping probes that are out there plus services > like UptimeRobot and similiar. > > you can't just put something up as a provider of a service and say ... > ya know im not going to plan for this... traffic for them of any kind is > money... not only to them but to their IX's as well. > > ya just don't willy nilly cut that shit down and not expect a huge > blowup to happen. > > On Wed, Feb 09, 2022 at 03:53:15PM +0100, Łukasz Bromirski wrote: > > > > Yup. And Google folks accounted for the world pinging them all day long. > > > > I wouldn't call using DNS resolvers as best "am I connected to internet over this interface" tool though. A day, year or 5 years from now the same team may decide to drop/filter and then thousands of hardcoded "handmade automation solutions" will break. And I believe that's closer to what Masataka was trying to convey. > > > > — > > Łukasz Bromirski > > > > > On 9 Feb 2022, at 14:23, Mark Tinka <mark(a)tinka.africa> wrote: > > > > > >> On 2/9/22 15:00, Masataka Ohta wrote: > > >> > > >> > > >> Wrong. It is not bad, at least not so bad, pinging properly > > >> anycast DNS servers. > > >> > > >> The point of anycast is resistance to DDoS. > > >> > > >> But, relying on hard coded 8.8.8.8 is not a good idea because > > >> DNS service of the address may be terminated. > > >> > > >> Instead, properly anycast root name servers are authoritative > > >> resources provided for public DNS queries which can be used for > > >> pinging, though pinging so with ICMP should be less painful > > >> for the servers. > > > > > > That's like saying you won't have an egg for dinner because it's typically had for breakfast. > > > > > > Users don't care what infrastructure has been designated for. If they can find another use for it other than designed, which serves their interests, they will use it. > > > > > > We need to allow, and account, for that. > > > > > > Mark. > > -- > The fact that there's a Highway to Hell but only a Stairway to Heaven says a lot about anticipated traffic volume. -- The fact that there's a Highway to Hell but only a Stairway to Heaven says a lot about anticipated traffic volume.

1 0