MDXi / Lagos

Hi Guys, Sorry for the off-topic post. I would appreciate it if someone that has rack space in MDXi can please ping me off list. I just have a few (two or three) random questions that I would appreciate some general feedback on. Many thanks, -- Regards, Chris Knipe

Re: AFRINIC: The Saga Continues

elcome input on this as I look into the history a little more. > > Cheers! > > James > > On 1/29/20 7:27 AM, Chris Knipe wrote: > > Hi All, > > > > http://ftp.afrinic.net/stats/afrinic/delegated-afrinic-extended-20200129 > > > > Another thing that stuc

Re: AFRINIC: The Saga Continues

not at this > moment clear to me that Afrinic is even in possession of such historical > backups, and the fact that they have, as yet, made no apparent efforts to > remediate the fradulently fiddled person: records suggests to me that they > likely do not possess such backups. > > Many of the legacy blocks and many parts of the blocks that were stolen > from the Afrinic free pool, both those that have been reclaimed and those > that haven't yet been reclaimed, continue to be routed by various parties > on behalf of the thieves and black market buyers of these blocks even as > we speak. I hope to be able to post a fully list of those routes and the > relevant ASNs that are providing the ongoing routing for various parts of > this mass of stolen booty in the very near future. > > > Regards, > rfg > -- Regards, Chris Knipe

Re: DoD IP Space

in the absolute last situation where I wanted to be in. Regards, Chris. On Mon, Nov 4, 2019 at 4:44 PM Joe Provo wrote: > On Mon, Nov 04, 2019 at 10:55:47AM +0200, Chris Knipe wrote: > > Hi Guys, > > > > Except for the email on ARIN's details, does anyone else have a cont

Re: DoD IP Space

On Mon, Nov 4, 2019 at 3:13 PM Jason Biel wrote: > 22/8 is actively used by DoD, just not publicly. It would be in your best > interest to not accept routes for it. > > if you need something more official, contact the DoD NIC directly at the > email address specified in WHOIS. > > Precisely what

Re: DoD IP Space

use by anyone else. -- Regards, Chris Knipe

DoD IP Space

is the 22.0.0.0/8 network, which according to ARIN is actively assigned to the DoD (US). -- Regards, Chris Knipe

Re: [nanog] BGP routes by country

On Thu, Sep 26, 2019 at 9:53 PM Christopher Morrow wrote: > Maybe asking from the get-go: > "What are you trying to do?" > > because the question asked is fraught with peril and disaster... > Why? When you have a serious problem with a specific ASN, it's not unreasonable to drop traffic to

Re: Protecting 1Gb Ethernet From Lightning Strikes

n > > Software Tool & Die| b...@theworld.com | > http://www.TheWorld.com > Purveyors to the Trade | Voice: +1 617-STD-WRLD | 800-THE-WRLD > The World: Since 1989 | A Public Information Utility | *oo* > -- Regards, Chris Knipe

Re: really amazon?

Try j...@amazon.com > > -- > S.C. > Then update your ARIN records to reflect that. Fully agree with Dan on this one. -- Regards, Chris Knipe

Re: Colo in Africa

On Tue, Jul 16, 2019 at 4:57 PM Akshay Kumar via NANOG wrote: > The 2nd requirement seems artificial. The new hypervisors have come a long > way and the overhead is minimal. Also you can run bare metal instances in > AWS if you really need them with 100Gbps. > > Just just use the South Africa

VPN / IPSEC Management

, or are there something out there to manage this with? -- Regards, Chris Knipe

Re: WIndows Updates Fail Via IPv6

r I enabled IPv6 in the TCP/IP stack. > > Disabling it immediately solves the issue. > > > > Quite odd that this is happening in 2018... > > > > Mark. > > I’ve had IPv6 enabled for a while and I don’t have the same issue. We > also > peer directly with Microsoft. Are you sure it’s an IPv6 issue and not a > general reachability issue? > > -Daniel > > > -- Regards, Chris Knipe

Re: Purchased IPv4 Woes

hat other > than not using their service. > > Also, no reason why a UDP (or DNS based even) query can't be implemented to facilitate reputation lookups for ASNs, or even ownership. -- Regards, Chris Knipe

Re: Purchased IPv4 Woes

On Sun, Mar 12, 2017 at 6:17 PM, <valdis.kletni...@vt.edu> wrote: > On Sun, 12 Mar 2017 17:59:59 +0200, Chris Knipe said: > > > Sure, that will work. (And no, the problem isn't the number of http hits > on the registries. 35,840,000,000 hits per day is the easy part...)

Re: Purchased IPv4 Woes

On Sun, Mar 12, 2017 at 5:59 PM, Baldur Norddahl wrote: > They could watch the routing table and notice which ASN is actually using > the address space. In fact ASN reputation might work better than IP space > reputation. > +1 And not only the originating ASN, but

Re: Purchased IPv4 Woes

On Sun, Mar 12, 2017 at 5:40 PM, wrote: > > How does Spamhaus find out the block has been resold? > > How do other DNS-based blacklist operators find out? > > >From the REGISTRY as the ultimate custodian of the IP block. > How do all the AS's that have their own

Re: Port 2323/tcp

;> 115.76.127.118 > >> 116.73.65.248 > >> 116.100.170.92 > >> 117.0.7.77 > >> 117.1.26.234 > >> 117.195.254.3 > >> 118.32.44.99 > >> 118.42.15.21 > >> 118.43.112.120 > >> 118.100.64.159 > >> 118.163.191.208 > >> 119.199.160.207 > >> 119.202.78.47 > >> 120.71.215.81 > >> 121.129.203.22 > >> 121.178.104.129 > >> 121.180.53.143 > >> 122.117.245.28 > >> 123.9.72.86 > >> 123.16.78.77 > >> 123.23.49.149 > >> 123.24.108.10 > >> 123.24.250.187 > >> 123.25.74.209 > >> 123.27.159.13 > >> 123.240.245.72 > >> 124.66.99.251 > >> 124.131.28.38 > >> 125.166.193.206 > >> 125.227.138.132 > >> 138.204.203.66 > >> 171.97.245.221 > >> 171.224.7.147 > >> 171.226.20.220 > >> 171.232.118.93 > >> 171.248.210.120 > >> 171.249.223.213 > >> 171.250.26.209 > >> 173.56.21.67 > >> 175.138.81.130 > >> 175.203.202.232 > >> 175.207.137.139 > >> 175.211.251.156 > >> 177.207.49.108 > >> 177.207.67.170 > >> 177.223.52.193 > >> 178.222.246.96 > >> 179.4.140.63 > >> 179.235.55.39 > >> 179.253.163.107 > >> 180.73.117.62 > >> 180.254.224.10 > >> 182.37.156.98 > >> 182.180.80.75 > >> 182.180.123.43 > >> 183.46.49.216 > >> 183.144.245.235 > >> 186.19.48.158 > >> 186.69.170.130 > >> 186.219.1.156 > >> 187.104.248.17 > >> 187.211.63.51 > >> 188.209.153.15 > >> 189.101.220.244 > >> 189.234.9.147 > >> 191.103.35.250 > >> 191.180.198.31 > >> 191.249.21.41 > >> 196.207.83.23 > >> 197.224.37.108 > >> 201.243.225.103 > >> 210.178.250.121 > >> 211.7.146.51 > >> 211.216.202.191 > >> 213.5.216.213 > >> 213.14.195.100 > >> 213.170.76.149 > >> 217.129.243.48 > >> 218.161.121.178 > >> 218.186.43.224 > >> 220.85.169.133 > >> 220.132.111.124 > >> 220.133.24.142 > >> 220.133.198.71 > >> 220.133.234.229 > >> 220.134.132.200 > >> 220.134.193.133 > >> 220.135.64.43 > >> 221.145.147.78 > >> 221.159.105.17 > >> 221.167.64.53 > >> 222.254.238.188 > >> 223.154.223.159 > > > > -- Regards, Chris Knipe

NetRouting NOC

Hi, Anyone from NetRouting NOC (AS47869) that can contact me off list please. Not getting anywhere resolving a routing issue with your support personnel. -- Regards, Chris Knipe

Re: Zayo Extortion

ally* fast... > Although a company that can't manage their book keeping properly, is IMHO enough reason to not use them... :-) -- Regards, Chris Knipe

Re: Netflix banning HE tunnels

Exactly. So what precisely are the metrics they use to block? I'm not using a proxy at all, its my own ASN... On Wed, Jun 8, 2016 at 11:06 PM, Andy Ringsmuth <a...@newslink.com> wrote: > > > On Jun 8, 2016, at 3:52 PM, Chris Knipe <sav...@savage.za.org> wrote: >

Re: Netflix banning HE tunnels

them a bill. > > > > > > > > > > They're doing the same thing with IPv4 (banning people based on the > > > apparent IP address). Your IPv4 numbers may not be on their blacklist > > > at the moment, and disabling IPv6 might work for you, but the > > > underlying problem is the practice of GeoIP/VPN blocking, and the > > > HE.net tunnels are just one example of the collateral damage. > > > > > > I don't know why Netflix and other GeoIP users can't just ask > > > customers where they are located, instead of telling them. It is > > > possible that some user might lie, but what about "assume good faith"? > > > It shows how much they value you as a customer if they would rather > > > dump you than trust you to tell them where you are located. > > > > > > -Laszlo > > > > > > -- Regards, Chris Knipe

Re: 10G-capable customer router recommendations?

On Sat, Apr 16, 2016 at 12:04 AM, Josh Reynolds wrote: > Can't do more than 1Gbps per flow. Not suitable for this application. > On Apr 15, 2016 5:03 PM, wrote: > > > Check out the Mikrotik Cloud Core routers, they make them with SFP+ > > support now.

Re: Netflix NOC? VPN Mismarked?

On Thu, Jan 28, 2016 at 7:40 PM, Mike Hammett wrote: > There's little reason to buy a newer TV more than every 5 - 10 years, so > many TVs will be stranded until (if) they have some unifying firmware. > > Well the TV is also meaningless if the CPE, and (at the very least)

Re: Netflix NOC? VPN Mismarked?

On Thu, Jan 28, 2016 at 11:07 AM, Owen DeLong wrote: > > Fortunately Netflix is running IPv6 for most things already. If you’re an > ISP and you’re not > allowing them to reach Netflix via IPv6, then you’re part of the problem > rather than the solution. > > Sure. Easy to say

Re: Netflix NOC? VPN Mismarked?

Highly unlikely... On Thu, Jan 28, 2016 at 3:46 PM, Bacon Zombie <baconzom...@gmail.com> wrote: > Do all "smart" TVs and Game consoles fully support IPv6 out of the box? > On 28 Jan 2016 10:17, "Chris Knipe" <sav...@savage.za.org> wrote: > >> O

Re: *tap tap* is this thing on?

ONE message on AFNOG, and that was the end of it, and I think two, or three on the Freeradius lists, and that was the end of that... Hundreds, and hundreds on NANOG however. -- Regards, Chris Knipe

Re: Fw: new message

esnacres.ca/were.php?zha> > > > > Salima Ait Meziane > > -- Regards, Chris Knipe

Re: Current IPv4 Options

s as well. That being said, they still need > the IPv4 space in the near-term. > Sitting in exactly the same position. IPv6 is great and all, but running my business natively on IPv6 means nothing to me if my customers can't reach me. -- Regards, Chris Knipe

Re: internet visualization

> > If you love it, send Job your accolades. If you hate it, > > see above disclaimer. If in a country with a holiday on monday, > > enjoy it safely. > > > > - Jared > > > > -- Regards, Chris Knipe

Re: Recommended wireless AP for 400 users office

me Ruckus Wireless, it would be great if you can share your experience with Ruckus or with a similar vendor. My experience with ubiquity for this type of requirement was not that good. Thank you and have a great day -- Eduardo Schoedler -- Regards, Chris

Re: Experience with Third-Party memory (Cisco)?

attachments. 9284f6a0-bf16-11e3-b1b6-0800200c9a66 -- Regards, Chris Knipe

Re: misunderstanding scale (was: Ipv4 end, its fake.)

independant) cannot obtain address space. And it is continueing to this very day. I'm definately all for proper audits, stricter audits, and more importantly the releasing of unused address space back to the respective registries. -- Regards, Chris Knipe

Re: google mail problems?

to the GApps status page: http://www.google.com/appsstatus#hl=env=statusts=1372272841152 -- Blair Trosper Weather Data / Updraft Networks blair.tros...@updraftnetworks.com blair.tros...@updraft.us NOC: 512-666-0536 -- Regards, Chris Knipe