- Test - lists.nanog.org

Spectre/Meltdown impact on network devices
by Jean | ddostest.me 08 Jan '18

08 Jan '18

Hello, I'm curious to hear the impact on network devices of this new hardware flaws that everybody talk about. Yes, the Meltdown/Spectre flaws. I know that some Arista devices seem to use AMD chips and some say that they might be immune to one of these vulnerability. Still, it's possible to spawn a bash shell in these and one with limited privileges could maybe find some BGP/Ospf/SNMP passwords. Maybe it's also possible to leak a full config. I understand that one need access but still it could be possible for one to social engineer a NOC user, hijack the account with limited access and maybe run the "exploit". I know it's a lot of "if" and "maybe", but still I'm curious what is the status of big networking systems? Are they vulnerable? Thanks Jean

8 9

Customer woes and ps3 network
by Michael Crapse 08 Jan '18

08 Jan '18

I have a customer on a ps3, and he can't seem to connect to the psn. Keeps getting the 80710016 error. If there is anyone that can help me troubleshoot this issue, that would be great.

3 4

Re: Spectre/Meltdown impact on network devices
by Masataka Ohta 08 Jan '18

08 Jan '18

Jason Gmail wrote: > The only business I've been looking at is AWS > > https://aws.amazon.com/security/security-bulletins/AWS-2018-013/ It merely says: All instances across the Amazon EC2 fleet are protected from all known threat vectors from the CVEs previously listed. not spectre in general. But, as mentioned in: https://access.redhat.com/security/cve/cve-2017-5715 It relies on the presence of a precisely-defined instruction sequence in the privileged code and https://access.redhat.com/security/cve/cve-2017-5753 It relies on the presence of a precisely-defined instruction sequence in the privileged code CVEs previously listed are spectre attacks between privileged and unprivileged codes, which means spectre attack between unprivileged codes is still possible with AWS, which is why we should avoid cloud servers, until CPU hardware is fixed. Masataka Ohta

1 0

Re: Blockchain and Networking
by Denys Fedoryshchenko 08 Jan '18

08 Jan '18

Each offsite copy of git repository will give alert then, as all hashes in chain changed at some moment. Same principle as blockchain. On 2018-01-08 09:54, tglassey(a)earthlink.net wrote: > Uh since MITM Bill perk of custody is key. > > //tsg > > Sent from my HTC > ----- Reply message ----- > From: "Denys Fedoryshchenko" <denys(a)visp.net.lb> > To: <nanog(a)nanog.org> > Subject: Blockchain and Networking > Date: Mon, Jan 8, 2018 10:03 > > On 2018-01-08 08:59, Peter Kristolaitis wrote: >> On 2018-01-08 12:52 AM, William Herrin wrote: >>> I'm having trouble envisioning a scenario where blockchain does > that >> any >>> better than plain old PKI. >>> >> Blockchain is great at proving chain of custody, but when do you > need >> to do >>> that in computer networking? >>> >> Regards, >>> Bill Herrin >> > There's probably some potential in using a blockchain for things > like >> configuration management. You can authenticate who made what change >> and when (granted, we can kinda-sorta do this already with the > various >> authentication and logging mechanisms, but the blockchain is an >> immutable, permanent record inherently required for the system to > work >> at all). >> > That immutable, sequenced chain of events would let you do things > like >> "make my test environment look like production did last Thursday at >> 9AM" trivially by reading the blockchain up until that timestamp, > then >> running a fork of the chain for the new test environment to track > its >> own changes during testing. >> > Or when you know you did something 2 months ago for client A, and > you >> need your new NOC guy to now do it for client B -- the blockchain >> becomes the documentation of what was done. >> > We can build all of the above in other ways today, of course. But >> there's certainly something to be said for a vendor-supported > solution >> that is inherent in the platform and requires no additional >> infrastructure. Whether or not that's worth the complexities of >> managing a blockchain on networking devices is, perhaps, a whole > other >> discussion. :) >> > - Peter > Why to reinvent git? :) > Lot of tools available also, to see diff on git commits, to see who > did commit, and what exactly he changed. > (it is possible to cryptographically sign commits, as well, and yes, > they are chain signed, as "blockchain")

1 0

Re: Attacks from poneytelecom.eu
by Dovid Bender 06 Jan '18

06 Jan '18

Mcikael, 1) As others have mentioned your AS seemingly has a history of tolerating abuse. I know some of the other VPS players such as DO have automated scripts that look for attacks and lock them out. I see you peer with them perhaps they can share some scripts ;) 2) I went to the abuse URL you have posted and it just lands at your main page. The offending IP was 195.154.182.242. I checked two different boxes (one our own range and another a hosted box elsewhere) and both have entries in the last 3 days from that IP. Scans have been going on for at least the last 48+ hours. On Wed, Jan 3, 2018 at 2:47 AM, Mickael Marchand <mmarchand(a)corp.free.fr> wrote: > Hi Dovid, > > Just fill in our abuse form at https://abuse. <https://abuse.scaleway> > online.net > > I know people feel these are not processed but they actually are (and > human reviewed) > we are improving our automated tracking of bad guys > more reports come in, easier it is in the end. > > note that most IPs you report are rented per minute and it’s usually not > the same account (but often the same IP as they are reused quickly I agree), > we are working on killing these accounts as fast as we can > > we have a long awaited overall of our abuse system coming in the next > months and additional global scale network security in the pipe (automated > SIP scan detection and blocking is among them for example) > > regards > Mik > > > Le 3 janv. 2018 à 04:11, Ahad Aboss <ahad(a)swiftelnetworks.com> a écrit : > > Have you emailed their abuse or NOC teams with the attack logs from their > IPs? > > Sometimes ISP servers or their customer CPEs are compromised without their > knowledge. > > On Wed, 3 Jan 2018 at 1:56 pm, Dovid Bender <dovid(a)telecurve.com> wrote: > > Hi All, > > Lately we have seen a lot of attacks from IPs where the PTR record ends in > poneytelecom.eu to PBX systems. A quick search on twitter ( > https://twitter.com/hashtag/poneytelecom) shows multiple people > complaining > that they reported the IP's yet nothing happens. Has anyone had the > pleasure of dealing with them and have you gotten anywhere? I wonder if the > only option is public shaming. > > I would rather not ban their AS as it may hurt legit traffic but I am out > of ideas at this point.... > > TIA. > > Dovid > > > -- > Mickael Marchand, > VP Network Scaleway - Online.net > Looking for an amazing job? Join us NOW ! https://careers.scaleway.com/ > > > >

10 18

Weekly Routing Table Report
by cscora＠apnic.net 05 Jan '18

05 Jan '18

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, CaribNOG TZNOG, MENOG, BJNOG, SDNOG, CMNOG, LACNOG, IRNOG 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 Jan, 2018 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 677605 Prefixes after maximum aggregation (per Origin AS): 263671 Deaggregation factor: 2.57 Unique aggregates announced (without unneeded subnets): 327932 Total ASes present in the Internet Routing Table: 59484 Prefixes per ASN: 11.39 Origin-only ASes present in the Internet Routing Table: 51353 Origin ASes announcing only one prefix: 22635 Transit ASes present in the Internet Routing Table: 8131 Transit-only ASes present in the Internet Routing Table: 244 Average AS path length visible in the Internet Routing Table: 4.4 Max AS path length visible: 30 Max AS path prepend of ASN ( 29046) 25 Prefixes from unregistered ASNs in the Routing Table: 88 Number of instances of unregistered ASNs: 89 Number of 32-bit ASNs allocated by the RIRs: 21091 Number of 32-bit ASNs visible in the Routing Table: 16887 Prefixes from 32-bit ASNs in the Routing Table: 69434 Number of bogon 32-bit ASNs visible in the Routing Table: 14 Special use prefixes present in the Routing Table: 0 Prefixes being announced from unallocated address space: 334 Number of addresses announced to Internet: 2860024994 Equivalent to 170 /8s, 120 /16s and 132 /24s Percentage of available address space announced: 77.3 Percentage of allocated address space announced: 77.3 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 98.8 Total number of prefixes smaller than registry allocations: 224483 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 186127 Total APNIC prefixes after maximum aggregation: 53465 APNIC Deaggregation factor: 3.48 Prefixes being announced from the APNIC address blocks: 185206 Unique aggregates announced from the APNIC address blocks: 77299 APNIC Region origin ASes present in the Internet Routing Table: 8570 APNIC Prefixes per ASN: 21.61 APNIC Region origin ASes announcing only one prefix: 2430 APNIC Region transit ASes present in the Internet Routing Table: 1243 Average APNIC Region AS path length visible: 4.4 Max APNIC Region AS path length visible: 29 Number of APNIC region 32-bit ASNs visible in the Routing Table: 3452 Number of APNIC addresses announced to Internet: 770308898 Equivalent to 45 /8s, 233 /16s and 251 /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: 202522 Total ARIN prefixes after maximum aggregation: 97512 ARIN Deaggregation factor: 2.08 Prefixes being announced from the ARIN address blocks: 203785 Unique aggregates announced from the ARIN address blocks: 95631 ARIN Region origin ASes present in the Internet Routing Table: 18045 ARIN Prefixes per ASN: 11.29 ARIN Region origin ASes announcing only one prefix: 6679 ARIN Region transit ASes present in the Internet Routing Table: 1784 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: 2289 Number of ARIN addresses announced to Internet: 1107523104 Equivalent to 66 /8s, 3 /16s and 118 /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: 183210 Total RIPE prefixes after maximum aggregation: 89257 RIPE Deaggregation factor: 2.05 Prefixes being announced from the RIPE address blocks: 179162 Unique aggregates announced from the RIPE address blocks: 107873 RIPE Region origin ASes present in the Internet Routing Table: 24791 RIPE Prefixes per ASN: 7.23 RIPE Region origin ASes announcing only one prefix: 11325 RIPE Region transit ASes present in the Internet Routing Table: 3514 Average RIPE Region AS path length visible: 4.5 Max RIPE Region AS path length visible: 30 Number of RIPE region 32-bit ASNs visible in the Routing Table: 6535 Number of RIPE addresses announced to Internet: 714008704 Equivalent to 42 /8s, 142 /16s and 232 /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: 87728 Total LACNIC prefixes after maximum aggregation: 19441 LACNIC Deaggregation factor: 4.51 Prefixes being announced from the LACNIC address blocks: 89021 Unique aggregates announced from the LACNIC address blocks: 39646 LACNIC Region origin ASes present in the Internet Routing Table: 6689 LACNIC Prefixes per ASN: 13.31 LACNIC Region origin ASes announcing only one prefix: 1835 LACNIC Region transit ASes present in the Internet Routing Table: 1246 Average LACNIC Region AS path length visible: 5.2 Max LACNIC Region AS path length visible: 29 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 4222 Number of LACNIC addresses announced to Internet: 172507104 Equivalent to 10 /8s, 72 /16s and 63 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-268700 + 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: 17928 Total AfriNIC prefixes after maximum aggregation: 3932 AfriNIC Deaggregation factor: 4.56 Prefixes being announced from the AfriNIC address blocks: 20097 Unique aggregates announced from the AfriNIC address blocks: 7210 AfriNIC Region origin ASes present in the Internet Routing Table: 1114 AfriNIC Prefixes per ASN: 18.04 AfriNIC Region origin ASes announcing only one prefix: 365 AfriNIC Region transit ASes present in the Internet Routing Table: 225 Average AfriNIC Region AS path length visible: 4.7 Max AfriNIC Region AS path length visible: 21 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 389 Number of AfriNIC addresses announced to Internet: 95278336 Equivalent to 5 /8s, 173 /16s and 213 /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 5411 4192 74 ERX-CERNET-BKB China Education and Rese 7545 3271 403 389 TPG-INTERNET-AP TPG Telecom Limited, AU 4766 2884 11132 772 KIXS-AS-KR Korea Telecom, KR 17974 2783 918 77 TELKOMNET-AS2-AP PT Telekomunikasi Indo 9829 2769 1499 540 BSNL-NIB National Internet Backbone, IN 7552 2509 1159 49 VIETEL-AS-AP Viettel Group, VN 45899 2253 1524 119 VNPT-AS-VN VNPT Corp, VN 9394 2168 4923 26 CTTNET China TieTong Telecommunications 9808 2097 8699 32 CMNET-GD Guangdong Mobile Communication 4755 2082 417 209 TATACOMM-AS TATA Communications formerl 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 6327 3333 1323 86 SHAW - Shaw Communications Inc., CA 22773 3280 2951 146 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 18566 2169 405 108 MEGAPATH5-US - MegaPath Corporation, US 20115 2066 2328 465 CHARTER-NET-HKY-NC - Charter Communicat 16509 1988 4145 586 AMAZON-02 - Amazon.com, Inc., US 6389 1959 3671 39 BELLSOUTH-NET-BLK - BellSouth.net Inc., 209 1916 5061 623 CENTURYLINK-US-LEGACY-QWEST - Qwest Com 30036 1871 332 246 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom 11492 1723 233 571 CABLEONE - CABLE ONE, INC., US 7018 1675 20197 1247 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 3520 187 21 ALJAWWALSTC-AS, SA 20940 2856 846 2059 AKAMAI-ASN1, US 8551 2282 378 42 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 12389 2091 1830 688 ROSTELECOM-AS, RU 12479 1991 1068 127 UNI2-AS, ES 9121 1981 1691 17 TTNET, TR 34984 1979 330 477 TELLCOM-AS, TR 13188 1605 100 46 TRIOLAN, UA 6849 1228 355 21 UKRTELNET, UA 8402 1225 544 14 CORBINA-AS OJSC "Vimpelcom", 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 8151 3752 3433 602 Uninet S.A. de C.V., MX 10620 3577 539 262 Telmex Colombia S.A., CO 11830 2632 370 66 Instituto Costarricense de Electricidad 6503 1617 437 53 Axtel, S.A.B. de C.V., MX 7303 1498 1023 192 Telecom Argentina S.A., AR 6147 1195 377 27 Telefonica del Peru S.A.A., PE 28573 1022 2246 194 CLARO S.A., BR 3816 1015 509 114 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 11172 919 126 85 Alestra, S. de R.L. de C.V., MX 18881 904 1065 27 TELEFÔNICA BRASIL S.A, BR 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 1190 398 50 LINKdotNET-AS, EG 37611 781 91 8 Afrihost, ZA 36903 741 372 137 MT-MPLS, MA 36992 688 1383 31 ETISALAT-MISR, EG 8452 520 1730 18 TE-AS TE-AS, EG 24835 487 786 17 RAYA-AS, EG 29571 444 36 13 ORANGE-COTE-IVOIRE, CI 37492 440 367 77 ORANGE-, TN 37342 356 32 1 MOVITEL, MZ 15399 349 35 7 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 4538 5411 4192 74 ERX-CERNET-BKB China Education and Rese 8151 3752 3433 602 Uninet S.A. de C.V., MX 10620 3577 539 262 Telmex Colombia S.A., CO 39891 3520 187 21 ALJAWWALSTC-AS, SA 6327 3333 1323 86 SHAW - Shaw Communications Inc., CA 22773 3280 2951 146 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 7545 3271 403 389 TPG-INTERNET-AP TPG Telecom Limited, AU 4766 2884 11132 772 KIXS-AS-KR Korea Telecom, KR 20940 2856 846 2059 AKAMAI-ASN1, US 17974 2783 918 77 TELKOMNET-AS2-AP PT Telekomunikasi Indo Complete listing at http://thyme.rand.apnic.net/current/data-ASnet Global Per AS Maximum Aggr summary ---------------------------------- ASN No of nets Net Savings Description 39891 3520 3499 ALJAWWALSTC-AS, SA 10620 3577 3315 Telmex Colombia S.A., CO 6327 3333 3247 SHAW - Shaw Communications Inc., CA 8151 3752 3150 Uninet S.A. de C.V., MX 22773 3280 3134 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 7545 3271 2882 TPG-INTERNET-AP TPG Telecom Limited, AU 17974 2783 2706 TELKOMNET-AS2-AP PT Telekomunikasi Indonesia, I 11830 2632 2566 Instituto Costarricense de Electricidad y Telec 7552 2509 2460 VIETEL-AS-AP Viettel Group, VN 8551 2282 2240 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo Complete listing at http://thyme.rand.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Network Transit AS Description 65456 PRIVATE 31.171.126.0/23 199311 AZRT-LX Local Internet Exchang 64525 PRIVATE 45.119.143.0/24 133275 GIGANTIC-AS Gigantic Infotel P 64525 PRIVATE 45.125.62.0/24 133275 GIGANTIC-AS Gigantic Infotel P 65001 PRIVATE 46.237.40.0/21 13118 ASN-YARTELECOM PJSC Rostelecom 65534 PRIVATE 58.68.109.0/24 10201 DWL-AS-IN Dishnet Wireless Lim 64513 PRIVATE 62.150.101.0/24 9155 QNET Kuwait, KW 419333 UNALLOCATED 84.17.91.0/24 41933 IPRAGAZ-AS Istanbul/ TURKEY, T 64609 PRIVATE 94.245.126.0/24 6584 MICROSOFT-GP-AS - Microsoft Co 65000 PRIVATE 95.179.2.0/24 65001 -Private Use AS-, ZZ 65000 PRIVATE 95.179.3.0/24 65001 -Private Use AS-, ZZ Complete listing at http://thyme.rand.apnic.net/current/data-badAS Advertised Unallocated Addresses -------------------------------- Network Origin AS Description 14.128.14.0/23 10247 NETLINE, ZA 14.192.50.0/23 10247 NETLINE, ZA 14.192.58.0/23 10247 NETLINE, ZA 27.100.7.0/24 56096 UNKNOWN 36.255.250.0/23 10247 NETLINE, ZA 41.78.180.0/23 37265 -Reserved AS-, ZZ 43.228.144.0/22 9829 BSNL-NIB National Internet Backbone, IN 43.251.20.0/22 9381 WTT-AS-AP WTT HK Limited, HK 43.251.84.0/22 133676 PNPL-AS Precious netcom pvt ltd, IN 43.251.84.0/23 133676 PNPL-AS Precious netcom pvt ltd, IN 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:15 /9:12 /10:37 /11:99 /12:279 /13:558 /14:1088 /15:1896 /16:13416 /17:7769 /18:13670 /19:25260 /20:38892 /21:44620 /22:82804 /23:66621 /24:378323 /25:844 /26:608 /27:657 /28:36 /29:20 /30:17 /31:4 /32:60 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 6327 3125 3333 SHAW - Shaw Communications Inc., CA 39891 2946 3520 ALJAWWALSTC-AS, SA 22773 2526 3280 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 18566 2063 2169 MEGAPATH5-US - MegaPath Corporation, US 11830 1978 2632 Instituto Costarricense de Electricidad y Telec 8551 1746 2282 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 30036 1635 1871 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom Communi 10620 1577 3577 Telmex Colombia S.A., CO 11492 1520 1723 CABLEONE - CABLE ONE, INC., US 9121 1457 1981 TTNET, TR Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1573 2:819 4:18 5:2636 6:39 8:1094 9:1 12:1854 13:198 14:1749 15:29 16:3 17:185 18:76 20:53 21:1 23:2502 24:1927 25:2 27:2340 31:1951 32:87 35:22 36:458 37:2464 38:1430 39:224 40:101 41:3027 42:549 43:1929 44:93 45:3491 46:2986 47:193 49:1371 50:1051 51:47 52:916 54:355 55:5 56:7 57:42 58:1569 59:1010 60:372 61:1997 62:1778 63:1825 64:4638 65:2239 66:4486 67:2311 68:1194 69:3165 70:1132 71:588 72:2115 74:2693 75:392 76:423 77:1553 78:1617 79:1960 80:1480 81:1406 82:1070 83:792 84:1005 85:1989 86:565 87:1210 88:917 89:2318 90:177 91:6255 92:1085 93:2345 94:2370 95:2738 96:667 97:356 98:909 99:107 100:152 101:1535 102:14 103:16628 104:3213 105:212 106:521 107:1800 108:816 109:2727 110:1549 111:1722 112:1283 113:1380 114:1115 115:1603 116:1621 117:1669 118:2241 119:1660 120:913 121:1050 122:2419 123:1760 124:1479 125:1840 128:963 129:580 130:440 131:1627 132:588 133:194 134:1000 135:220 136:447 137:465 138:1983 139:549 140:388 141:677 142:768 143:942 144:799 145:195 146:1142 147:687 148:1471 149:711 150:712 151:982 152:749 153:309 154:959 155:744 156:742 157:743 158:599 159:1621 160:849 161:733 162:2531 163:522 164:981 165:1490 166:398 167:1377 168:3111 169:789 170:3641 171:403 172:1027 173:1909 174:862 175:772 176:1858 177:3939 178:2442 179:1155 180:2226 181:2133 182:2418 183:1059 184:895 185:11955 186:3475 187:2369 188:2624 189:1970 190:8220 191:1364 192:9756 193:5873 194:4779 195:3985 196:2321 197:1440 198:5525 199:5882 200:7280 201:4918 202:10378 203:9917 204:4560 205:2871 206:3043 207:3112 208:3994 209:3938 210:4002 211:2151 212:2938 213:2618 214:858 215:63 216:5748 217:2111 218:900 219:626 220:1728 221:956 222:696 223:1225 End of report

1 0

Anyone else blacklisted this morning by rbl.iprange.net?
by Mel Beckman 05 Jan '18

05 Jan '18

I woke up this morning to a barrage of complaints from users that our mail servers' outbound emails are bouncing due to a blacklisting. Sure enough, mxtoolbox.com<http://mxtoolbox.com> reports that rbl.iprange.net<http://rbl.iprange.net> has blacklisted us for more than a day. However, looking up our address on the rbl.iprange.net<http://rbl.iprange.net> lookup webpage shows we're NOT listed. But a check of the RBL's DNS shows that we are. Then I found this on the rbl.iprange.net<http://rbl.iprange.net> owner's website (): "rbl.iprange.net<http://rbl.iprange.net> (is offline since 01-01-2018) please replace it with rbl.realtimeblacklist.com<http://rbl.realtimeblacklist.com> rbl.iprange.net<http://rbl.iprange.net> will mark every ip address as listed to force removal of this server." What the heck? I've tried contacting realtimeblacklisk.com<http://realtimeblacklisk.com>, but they're in the Netherlands and apparently fast asleep (in more ways than one, it seems). -mel beckman

8 12

Re: IPv4 smaller than /24 leasing?
by Filip Hruska 04 Jan '18

04 Jan '18

Thanks for all the responses! Seems like I was right about doubting this. Regards -- Filip Hruska Linux System Administrator Dne 1/4/18 v 20:20 Matt Harris napsal(a): > They're probably using GRE or other sorts of tunnels, I'd imagine? It > would likely involve increased latency, as any packets coming to those > addresses would hit them first, and then be tunneled - either over the > public internet using gre or some kind of vpn, or perhaps via a > private connection or even an IX, to you? As far as outgoing traffic > from those addresses, you'd probably need to make sure that any > upstreams you're sending packets to from those addresses are not > running urpf which would cause them to be discarded, or otherwise get > around such a configuration. > > Take care, > Matt > > > On Thu, Jan 4, 2018 at 1:13 PM, Filip Hruska <fhr(a)fhrnet.eu > <mailto:fhr@fhrnet.eu>> wrote: > > Hi, > > I have stumbled upon this site [1] which seems to offer /27 IPv4 > leasing. > They also claim "All of our IPv4 address space can be used on any > network in any location." > > I thought that the smallest prefix size one could get routed > globally is /24? > So how does this work? > > [1] http://www.forked.net/ip-address-leasing/ > <http://www.forked.net/ip-address-leasing/> > > > Thanks > > -- > Filip Hruska > Linux System Administrator > > > > > -- > Matt Harris - Chief Security Officer > Main: +1 855.696.3834 ext 103 > Mobile: +1 908.590.9472 > Email:matt@netfire.net <mailto:matt@netfire.net>

1 0

Level 3 Voice
by Mike Hammett 04 Jan '18

04 Jan '18

I'm looking for a contact at Level 3's voice operations, preferably someone that knows about LNP. My client didn't get a port request to approve for their customer, yet operationally their customer's number has been ported to Level 3. Their customer wasn't aware of it going elsewhere as they called my client for support on the lack of inbound calling. Thank you. ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest-IX http://www.midwest-ix.com

1 0

Re: Threads that never end (was: Waste will kill ipv6 too)
by sizone!math 03 Jan '18

03 Jan '18

On Sat, Dec 30, 2017 at 06:42:46AM -0800, Stephen Satchell said: > On 12/29/2017 09:05 PM, Randy Bush wrote: > >the good thing about these long threads, which have ZERO new > >information, is having a KillThread command in one's mail user agent. > >get a life! > >I no longer use KillThread. Instead, I sort my inbox by subject, and use >the Delete key liberally. NANOG is by no means my first mailing list where >religious wars have broken out. (*cough* Linux kernel list) :) I used to gate mailing lists into cnews, and then just use tin with well-developed killfiles. Been a while though since I've touched a news system at all. (long live sizone.uucp! :) Unfortunately I haven't gotten mutt to the tin level (though collapsing threads makes reading the index easier..). (Ctrl-D to kill an entire thread in mutt btw.) Congrats on the record breaking thread! If anyone wants to TL;DR Im mildly interested in the results of this 'wisdom of the cloud' brainstorm. Certainly ipv6 is well solved by now. Happy Brave New ipv6 Year! /kc -- Ken Chase - uunet.ca!{ryelect,zeibmef,pci,jaywon,robohack}!sizone!math

8 8