14 ms·
Who is squatting IPv4 addresses?
- kevincox 5y agoOne minor philosophical question. If you are using AWS PrivateLink because your VPC is not connected to the internet are you really squatting anything? You are just aren't using the public internet. This means that you own the entire address space and can decide what you want to do with it. Of course it still may make sense to stick to ranges you own in case you need to peer your VPC with someone else, but I don't see much difference between using some random batch of IPs that you don't "own" on the public internet vs any block reserved for internal use. Either can conflict with someone that you want to merge with.
- quickthrower2 5y agoYes I didn’t understand this as squatting and made me question if I understood the post. As it is a topic I admit to not being too deeply knowledgeable about.
- kevincox 5y agoI think in general the author's definition of squatting is reasonable. I see it to mean "living on land you don't own" or more directly "using IP addresses that you don't own". My point is about fully private networks that aren't connected to the internet. I would argue that in this case you do own all of the addresses, even if someone else owns them on the public internet.
- quickthrower2 5y agoThanks. I have a question then. If you squat as per this definition, can you divert internet traffic designated foe the real IP address to your server? Or does it only divert it for computers on your network?
- kevincox 5y agoThe author is only talking about private networks. This does however occasionally happen on the public internet (or when a government turns their country into a private network and does this maliciously). The most common source is "BGP Leaks" which is a fun search.
- erik_seaberg 5y agoMy favorite example is when a Turkish ISP accidentally declared themselves to be the best route to anywhere, and the whole Internet simply took their word for it. https://web.archive.org/web/20080228131639/http://www.renesys.com/blog/2005/12/internetwide_nearcatastrophela.shtml https://web.archive.org/web/20080228131639/http://www.renesy...
- iqanq 5y agoThat's like saying if I create a 3D model of my neighbour's car and drive it around the streets of a videogame I am "squatting my neighbour's car" or "using a car I don't own".
- thedougd 5y agoThat's not really what the author was getting at. The VPC endpoints just provide a way (via TLS certificate authority logs) for the author to discover DNS addresses that they can then use to check for queries and determine what IP addresses are being used in private networks. They found a number of AWS users that are treating publicly routable IP space as their own private IP space. If someone were to ever offer a public service in that IP space, the company/network using it as private IPs would not be able to access the public service. The author is trying to understand how prevalent this is, and to what extent of trouble an owner of these IP spaces would have if they decided to host a public service.
- kevincox 5y agoI agree with you in general. If you do expect to be able to connect to the public internet and map an endpoint over a public address you are aiming a gun at your foot. However the point I was trying to make was about this quote: > This is useful since it can remove the need for some servers to have any outbound internet access at all. My point is that if you are not connected to the public internet at all I don't see why you should be expected to follow the rules of the public internet (who owns what). You can use whatever rules you want for your own private network.
- benjojo12 5y agoFor what it's worth, I've these endpoints in use for VPCs that still had internet access. Meaning that if you attempted to read the "real" internet address you put your VPC subnet on, they would be unreachable. It's hard/impossible to figure out if the VPC in question has been setup this way. But I agree that it would be likely that most of these VPC with the endpoints on don't have internet access. However if we assume (dangerously I suppose) that the VPC subnet distribution is similar to other VPCs without private link, we can imagine how many other VPCs are squatting on space that do have internet access! (Assuming any of this makes sense)
- kevincox 5y agoFor sure, I'd bet that most of the examples you found were still connected to the internet. I don't think the findings are any less valid I just thought it was an interesting observation that if you are in fact disconnected from the internet there isn't really any reason you should follow the public internet's rules.
- hotpotamus 5y agoI believe the networking term is "bogon". Basically you're using space in a way that isn't intended. Mostly I've seen it as people trying to use RFC1918 space on public networks probably because of misconfigurations and most routers/FWs will ignore these. This is sort of the inverse.
- Godel_unicode 5y agoNot really, bogon is generally used for either unallocated space or "Martian" packets (packets with a source in private space). This space is unannounced, but not unallocated, therefore it doesn't show up on the bogon list. Here's the team cymru bogon list, for instance: https://team-cymru.com/community-services/bogon-reference/bogon-dotted-decimal/ https://team-cymru.com/community-services/bogon-reference/bo...
- fullstop 5y agoThere are a lot of /24 in use strictly for BGP, even if they're not fully utilized. This is the public address space, though, and not really "squatting"
- _nickwhite 5y agoThis. I have a few /24s and only actually use maybe 25 active IP addresses. If I want to exist in global BGP tables, it's the smallest block I can use for my ASN (and not be filtered out). I think in 2022, the rise of SDWAN, CDNs, and, Zero-Trust reverse proxy services, it's not actually relevant to roll your own BGP, unless you're a big player, or if you just want to fly solo on the Internet.
- codechad 5y ago
- coretx 5y ago
- eatbitseveryday 5y ago> over 16% of all of the non-RFC1918 space is suspected squatted DoD space!
- mananaysiempre 5y agoWell, I’m entirely willing to believe the US DoD is one of the few entities that have more than 2^23 computers they want to be mutually addressable, so the RFC 1918 space is just too small for them if they are to run IPv4.
- JAlexoid 5y agoDoD has 8 million computers? It's not like it's all government branches combined. In fact - DoD should just have it's own internet - that is completely separate. I'd argue that DoD networks should not have any connectivity with broader internet, making their use of the whole 32 bit space completely independent from everyone else.
- maccolgan 5y agoThat'd essentially mean that any DoD computer can never communicate with anything on the standard internet.
- JAlexoid 5y agoThat means that no DoD computer can be connected to both at the same time. Which is a reasonable thing to have. Doesn't mean that DoD cannot use the global internet, just not use it and their own at the same time. I mean... They could even send traffic over global lines, without taking up IP addresses.
- IncRnd 5y agoThe entire address space was created for DoD use, so that is understandable.
- emilecantin 5y agoAbout 10 years ago, IBM used to use the 9.0.0.0/8 space in basically exactly the same way as one would use 10.0.0.0/8, for internal-only networking. Each workstation got its own 9.x.x.x IP, but it wasn't routable from outside. I hope they stopped doing that, but I doubt it.
- Milner08 5y agoAbout 5 years ago that was still a thing!
- jmreid 5y agoApple was the same when I was there for 17.0.0.0/8
- Aloha 5y agoI thought apple owned the 17.0.0.0/8 netblock?
- thetinguy 5y agoThey do.
- Aloha 5y agoThen how is it squatting? Even the article defined it as IP space not owned. From the parent article "I will define IP address squatting as “using IP addresses that are not RFC1918 defined and not your unicast space issued by a RIR”." Unless this is meant to construe all legacy assignments as "squatting" which is a pants on head definition.
- toast0 5y agoBy analogy, domain squatting isn't using a domain that isn't yours, it's underutilizing a limited resource that's assigned to you. Using IPs for internal networking doesn't necessarily mean under utilizing though; but might not be enough to justify such an assignment today.
- AshamedCaptain 5y agoArtificial scarcity is best scarcity. Certain popular western european ISP still gives IPv4s cheaper than IPv6s (still a high price, though).
- deleted 5y ago[deleted]
- tempnow987 5y agoIn the US it's hard for many home users to get static allocations of IPv6 but you can easily get an IPv4 block for $10/month or whatever. So same issue, if you need IPv6 static then you have to go to very expensive service tiers given the "shortage" of ipv6. Reality is I think IPv6 is just a pain up and down to deal with and they haven't sorted out all the tooling to deal with it for static IPs.
- dublin 5y agoThere is still plenty of IPv4 space available, it's just very badly distributed, for instance, due to early limits in Cisco's IOS, Chevron acquired an insane 26 Class B address blocks when connecting to the net back in the early 90s! With CIDR, we can easily reuse the many unused addrs like those, but the pain of readdressing has their owners sitting on them, raising prices and making them even more reluctant to turn loose of any for fear they won't be able to get them back... And, let's face it, IPv6 addressing is so fundamentally horked-up that it's practically only usable by propellerheads in the cloud backend: First, the addresses are too damn long and unwieldy to really be used; and second, even most people reading this, tech people in a tech forum, struggle to really grasp the inane IPv6 address shortening rules! Like X.400 mail addresses, they work technically, but are unusable in practice. (For those of you fortunate enough not to remember, the best way to get and transfer someone's X.400 address, even within the X.400 network, was to have them mail someone through an internet gateway and use whatever it said. Marshall Rose devoted an entire chapter to ranting about this in his Internet Mail book...)
- cameronh90 5y agoRemembering and hand manipulating IPv6 addresses is not something end users need to deal with. Like everyone else on my ISP, I have a publicly routeable v6 subnet at home and v6 addresses on my phones. I couldn't tell you what they are, but they work just fine.
- ospzfmbbzr 5y ago> Remembering and hand manipulating IPv6 addresses is not something end users need to deal with. Assuming it's configured correctly. Most devices are not. > Like everyone else on my ISP, I have a publicly routeable v6 subnet at home and v6 addresses on my phones. I couldn't tell you what they are, but they work just fine. Why would you ever want publicly routable addresses on devices inside your home? If Ipv6 was simply a 64-bit quad improvement on IPv4 it would be fine. However, the only valid use cases I can think of are mostly to the benefit of end users. What possible need could anyone have for more address space than the non-routable private address blocks already afforded by IPv4? Throw in the insecure-by-default and frequent misconfiguration out-of-the-box and you have the current flaming security dumpster fire that is IPv6.
- trimminghedges 5y agoBlackrock.
- mtmail 5y agoCan you elaborate or link to a source?
- hellow22 5y agoIPv4 address space is in short supply, so some people decide to use IP space ( allocated, but not advertised) that doesn't belong to them. The consequences are pretty well described in the article you quote.
- jeroenhd 5y agoBut this address space is non-routable, so it's effectively using address space that's equivalent to a 10/8 or 172/12 or 192.168/16 address. There's no need to grab random /8s when there is plenty of IPv4 address space that won't ever get routed to the internet (assuming nobody does something as dumb as actually changing the 127/8 semantics). If they somehow run out of those, 100.64/10 is also pretty much guaranteed not to be reachable from the internet.
- Swizec 5y agoI have an old static IP from the days of running a server from my bedroom. My mom kept it after I moved out. Stopped responding to pings 2 or 3 years ago when she upgraded her internet package and the ISP didn’t honor our ”Hey we have a static IP” agreement. Good old 193.77.212.100, may you rest in peace.
- zauguin 5y ago> [...] if you want to get a /24 block from RIPE NCC when you sign up as a member, then you are currently looking at a 2 month wait for a recycled IPv4 /24 block. That's a rather optimistic view of the situation. The next member who will get a block has already been waiting for 2 months and it's unclear when they will get one. It stands to reason that members applying now wold have to wait (potentially significantly) more than 2 months.
- svdr 5y agoI applied in October last year, and at that time the waiting list was zero days, so I received our /24 instantaneously. Some nice data on the prices of IPv4 addresses: https://auctions.ipv4.global/prior-sales https://auctions.ipv4.global/prior-sales
- z3t4 5y agoShould change to a montly fee. Then people would get rid of the ones not used.
- traceroute66 5y ago> Should change to a montly fee. Then people would get rid of the ones not used. There is a fee. Your EUR 1,400 annual fee. For that money you get one IPv4 and one IPv6 (IPv4 subject to availability, obvs!). Above that they charge per resource assignment, 50EUR per annum per resource assignment ( defined as: "IPv4 and IPv6 PI assignments; Anycast assignments; IPv4 and IPv6 IXP assignments; and Legacy IPv4 resource registrations through a sponsoring LIR. AS Numbers are excluded from this charge") And yes, I think the 50EUR should be put on a ladder scale so hoarders get charged exponentially more. ;-)
- Eikon 5y ago> And yes, I think the 50EUR should be put on a ladder scale so hoarders get charged exponentially more. ;-) They would just start to put IPV4 blocks behind shell companies.
- ajp11 5y agoA couple of years ago Amazon bought four million ip addresses for $108 million dollars. 44.192.0.0/10 AMPRnet sold them a quarter of the ip addresses that were allocated for amateur radio. They got a /8 back in the 1980s. A small number of addresses were used for ham radio networks but the AMPRnet addresses were generally not routed between the internet and the radio networks.
- aurizon 5y agoUse it or Lose it. Back in the day companies were allocated large blocs of IP space. They do not own it - what they do not use should be allocated to others who will use it with zero compensation to squatters - they own nothing. Sadly some have valued the IP blocs as assets = boosted bottom line - and there are some large boosts! These people will whine and scream - but screw them, they are just squatters and deserve nothing. Valid users can easily be identified by network data.
- taubek 5y agoAt University where I was working until few years ago we all have had static IP addresses for all of our desktops/laptops.
- angulardragon03 5y agoMy old uni holds two /16s which are used for clients. Firewalled, but if you use the Wi-Fi there then you are getting your own "personal" IPv4 address per device.
- jeroenhd 5y agoI know several universities that do the same. On certain LANs there isn't even a firewall, you just get a public IP. At my current university I think there's a limit of five or six static allocations per person, the rest is all dynamically allocated (and still a normal IP, no NAT here). And I honestly don't see why not. This is how the internet was designed to be used, and it works a lot better than most large managed networks in the 10/8 range I've seen. It'll only be a problem once there are more students and services than there is address space.
- briffle 5y agoYou mean they are using IP's as they were originally designed? Those people probably have NO conflicts or problems with things like video conferencing, VPN's, etc. NAT is a cludge, not a security feature.
- trollied 5y agoI can't recall the last time that NAT caused me any problems. Is it still an issue these days?
- thereddaikon 5y agoEven if its a mature cludge, its still a cludge.
- 5y ago
- api 5y agoInteresting work, but IMHO anything that extends the life of IPv4 does active harm. I'd prefer if these addresses stay out of the pool so scarcity increases and forces people to upgrade. IPv4 is fundamentally too small, period. There are already more people and computers on Earth than possible IPv4 addresses even if it were perfectly optimally used. It leads us further down a path in which everything is behind increasingly starved NATs, making point to point connectivity more and more difficult. Now we are seeing NATs in front of carrier-grade NAT and other madness. ... and no, NAT is not a security feature. You can and almost always do have a firewall in front of IPv6. If you really want NAT there is IPv6 NAT, but it allows you to have all mappings be 1:1 eliminating the need for port starvation madness and making P2P always work. All internal IPs get their own external IP, but those can be random and rotated if you want.
- paulnpace 5y agoThe total population I don't find to be a very strong argument, because all that matters is the population of people who desire to communicate with my service. If people not able to communicate with my service also don't want to communicate with my service and I don't see a need for them to communicate with my service, why do we both need the same protocols? Something I have observed is that sites that tend to attract DDoS attacks tend not to use IPv6 (note that reddit and HN do not have AAAA records, though I don't know the actual reason for this). I've even seen the heavily attacked sites that I know are using paid Cloudflare or Sucuri services to not have AAAA records, and I wonder if that's a decision or recommendation from the service providers. So, elimination of IPv4 may mean that sites can more easily and cheaply be knocked off the Internet.
- api 5y agoAs for point one: I'm not talking about client/server access to services. I'm talking about the capacity for endpoints to talk to each other. IPv4 would be fine if we want a fully centralized computing infrastructure where everything is only a thin client, but that's a future with zero privacy or personal freedom. I don't think there's anything special about IPv4 in terms of DDOS mitigation. What you're probably seeing is an artifact of focus and investment. IPv4 is still the lowest common denominator standard. Virtually everyone can talk to an IPv4 endpoint. As a result the DDOS protection services still mostly use IPv4 endpoints because it reduces the amount of attack surface they have to protect. If they were dual-stack they would have to deal with BGP black holing on what amounts to two BGP networks instead of just one. DDOS is something that desperately needs a more comprehensive solution, but it's a hard problem to solve. Right now the solution is for DDOS protection services to run bastions with enough bandwidth to absorb attacks, but that's a solution that constricts innovation tremendously. I feel like a permanent solution would require cryptography to be designed into the entire network so that you could do things like rate limit packets to your host for people who didn't present a certificate. That would require a deep redesign of the entire network though, and that's not going to happen.
- ck2 5y agoDOD needs to release those 175 million addresses back to the US public. That blog mentioned it but still, the timing of when it happened and who got control of them is odd af. https://arstechnica.com/information-technology/2021/04/pentagon-explains-odd-transfer-of-175-million-ip-addresses-to-obscure-company/ https://arstechnica.com/information-technology/2021/04/penta...
- zwieback 5y agoI work at hp and we have all of 15.x.x.x and use it for all our internal networking. At one time we also had all of 16.x.x.x because of DEC/Compaq. I suppose at some point this could be an asset for us since we could use some different scheme internally.
- tomc1985 5y agoAm I the only one alarmed that WD maintains a public registry (via DNS) of MyCloud device UUIDs, their public IP, and their private IP? How many of those are on networks with exploitable routers? Like, you have an external entrypoint and a target internal IP that you know will contain a trove of potentially interesting data.
- jedberg 5y agoI agree that's a ridiculous privacy issue. Definitely a case of poor security to provide a minor inconvenience (access your data from anywhere on the internet).
- AviationAtom 5y agoDidn't they actually recently recommend people disable direct Internet access and UPnP? I believe it was after a vulnerability was discovered in one of their legacy products.
- typh00n 5y agoI am curious: Could I in theory buy a IPv4 address, which I can use for the rest of my life? (given that I could convince my provider to route it)
- zamadatix 5y agoYou'd need to buy and have transferred a /24 (256) or more of "legacy" IPv4 that was allocated by IANA prior to the RIR system for your region. Then you could either convince your provider to route that block on your behalf or get an ASN and BGP peer at your local IX (or even over a tunnel to one). Getting it transferred to you may require setting up a business depending on your RIR. All in all you could make the above happen for about the price of a lower end new car in the best case. There are other ways to get non-legacy IPv4 assignments now but those are leased not owned.
- Chocoflan 5y agoI have some IPv4 addresses. What can I do with them?
- boomchinolo78 5y agoThe author of trilema.com at some point boasted of having bought a /16 and then renting it out. Something I don't quite understand is why IPV6 is better, if anything sticking to IPV4 will lead to more "selective" use. Actually useful things get an IP, the rest, well, better get more useful
- colinmhayes 5y agoArtificial scarcity is bad. IPv4 is bad because it’s expensive.
- prichino 5y agoThe author of trilema.com at some point boasted of having bought a /16 and then renting it out. Something I don't quite understand is why IPV6 is assumed to be better, if anything sticking to IPV4 will lead to more "selective" use. Actually useful things get an IP, the rest, well, better get more useful? Wishful thinking? Thank you,
- Plasmoid 5y ago> if anything sticking to IPV4 will lead to more "selective" use. That's a scarcity mindset and isn't useful in this case. Who cares if "low" value things use the internet? Imagine a network in rural Africa. It can't pay market rates for IP addresses but would be extremely valuable for its users. IP addresses aren't a negative externality like pollution or traffic, they're an artificial construct. So restricting them doesn't actually help people, and making them abundant is a huge benefit to literally everyone.
- tabtab 5y agoIpv4Coin, my latest sca....entrepreneurial project.
- geenew 5y agoRelevant bit of related humour: "How I Learned to Stop Worrying and Love IPv6" https://www.theregister.com/2012/08/21/verity_stob_ipv6/ https://www.theregister.com/2012/08/21/verity_stob_ipv6/ Choice quote: "'Do you NATter with your Neighbours? Don't squander the nation's resource!'"
- cute_boi 5y agoI think this is good. If these guys hoard ipv4, corporation will be forced to ipv6. Isn't that a good news?
- brippalcharrid 5y agoI know a number of IPv6 activists that are hoarding IPv4 address space with that in mind. Market forces will eventually provide compelling incentives once we have exhausted the easily accessible types of CGN magic.
- JAlexoid 5y agoWith the constricted supply of semiconductors - this may backfire spectacularly!
- atkbrah 5y agoUS Department of Defense has 14 /8 blocks. You'd have to wonder what they do with that large number of public IPs. Sure, some companies have large blocks but that's nothing compared to that.
- martin8412 5y agoLast I heard, that any project needing more than one IP got a /24
- lesuorac 5y agoAsk them [1] and report back. [1]: https://open.defense.gov/transparency/foia.aspx https://open.defense.gov/transparency/foia.aspx
- judge2020 5y agoThe actual page to request is foia.gov: https://www.foia.gov/request/agency-component/4fce7e7d-3b32-4da3-9922-5245dffde737/ https://www.foia.gov/request/agency-component/4fce7e7d-3b32-...
- kube-system 5y agoThe DoD is also larger than any company.
- bombcar 5y agoBy employees it’s the largest, though if Walmart bought McDonalds they’d have more employees (and perhaps as many chemical weapons).
- Wohlf 5y agoThey use them like private IPs, across several air gapped networks. When I was enlisted we were putting them on desktops.
- ipaddr 5y agoHow does this scale to other military globally. Does anyone else have an /8 block?
- futharkshill 5y agoI don't understand why was the next version of IP not just identical to IPv4 but with more bits in address space? Were they trying to do too many things at once in the 90's?
- aidenn0 5y agohttps://en.wikipedia.org/wiki/Second-system_effect https://en.wikipedia.org/wiki/Second-system_effect
- detaro 5y agoI don't think it not being that harms it as much as people think. It has to require updates for everything either way, people by and large don't care about "oh but it's only a small total breakage, going to jump on that then". On the other hand, yes, there certainly was some "we break everything anyways, so lets 'improve' things", combined with those improvements being designed at the wrong time, with assumptions that not always turned out to match reality. (E.g. a bunch of pieces that were added to IPv6 kind of assumed that routers would stay as they were, with routing done on CPUs, in software. Which they obviously didn't, and specialized hardware works on entirely different constraints)
- JAlexoid 5y agoIPv6 suffers the classic "we didn't think of thaaaaat" syndrome. We will probably use IPv4 for decades more. It's going to be even slower with constrained semiconductor pipeline. That's why we have squatters and expensive IPv4 blocks.
- detaro 5y ago> We will probably use IPv4 for decades more But I think we would also be in that situation if it were just IPv4-but-bigger. The main problem is incentives, and they wouldn't change through that.
- reincarnate0x14 5y agoIt was fixing (or trying to) issues with the v4 spec that were now very apparent. For example, ipv4 technically has a link-local address space but barely anything will use it and even less will successfully. Many other 80/90s protocols did much better at that (IPX being an example) as well as having distributed name and service locators and such. IPv6 local networks of IoT devices or whatever can pretty much automagically start communicating with zero configuration to anything else locally. No DHCP or whatever required. The world didn't stand still between v4 and v6, it'd be weird if the protocol did.
- tempnow987 5y agoI've said it before. Charge $10/year/ip. Would stop a lot of squatting on unused space and free it up.
- welterde 5y agoCould only be applied to more recently allocated networks and they are already paying some sum per network per year (not that much depending on the region but a non-zero number). However the worst offenders are legacy space that predate the modern RIR system and would be completely unaffected by this, since there is no mechanism to charge them.
- inopinatus 5y agoI had an ASSIGNED PORTABLE /24 in my name back in the 90s. I don’t have many regrets in life, but returning that to the registry remains a real big one.
- wdb 5y agoNeed to look into this. Vaguely remember my dad had a block of IPs. Not sure, if it’s lost since he passed away
- stjohnswarts 5y agoWe have a solution, so it doesn't really matter does it? Time to move on to IPV6 people.
- AviationAtom 5y agoDo you know if a good guide to IPv6?
- rhplus 5y ago> At the time of writing the market price for an IPv4 address is around 50 USD That's quite an outperforming asset class if true [0]. For a point of comparison, Microsoft paid $11 per address in 2011[1]. To get to $50 is about 15% appreciation/year, plus the added benefit of being able to rent them out by the minute. This article estimates that Amazon has paid about $25 per address in recent years [2]. [0] https://auctions.ipv4.global/ https://auctions.ipv4.global/ [1] https://www.marketwatch.com/story/microsoft-buys-nortels-vintage-web-addresses-2011-04-26 https://www.marketwatch.com/story/microsoft-buys-nortels-vin... [2] https://www.techradar.com/news/amazon-has-hoarded-billions-of-dollars-worth-of-ipv4-but-why https://www.techradar.com/news/amazon-has-hoarded-billions-o...
- DonHopkins 5y agoI know a naughty person who decades ago hijacked a /8 IPV4 network block when the company that owned it went out of business, by registering their expired domain name and sending in an email from that domain, transferring ownership of the block to himself. It was "hot" so he couldn't just squat on it or sell it in the open, but he laundered it by trading it to some shady company in exchange for free network services for life. If I were him, I would have printed out all the addresses on little slips of paper and taken an "IPV4 Address Bath" like Huell's scene in Breaking Bad: https://www.youtube.com/watch?v=7HrmD_vIMIk https://www.youtube.com/watch?v=7HrmD_vIMIk >(sexy lip bite) ... "I gotta do it, man!" ... "Mexico, all's I'm sayin'!"
- icedchai 5y agoWas it really an /8? I could believe a smaller block...
- DonHopkins 5y agoYep, it was a long time ago, and he was one of those "old net boys" who worked on the early ARPANET, but I won't say anything else that might identify him. I have another naughty friend (not the same person) who worked at SRI-NIC implementing and maintaining the ARPANET TACACS database, and as a personal favor, he created our mutual friend Devon his own ARPANET TAC card. So Devon's free vanity TACACS account was named "DEVON", while most other accounts like mine were something ugly like "DH32", using initials and numbers. One day his boss summoned him to his office and showed him a print-out of the TACACS accounts, with "DEVON" right at the top, and asked him who the hell that was. He sheepishly prevaricated that "DEVON" was actually a control code to turn the printer DEVice ON, which accidentally got printed at the beginning of the list because of a bug in his program missing an escape code, and he would fix it right away. And that's how Devon lost his TAC card. We still tease him about his name as a printer control code, and call him "DEVOFF" when he talks too much. I'm pretty sure his boss knew what was up, but just let it slide. Network security was a lot different in those days. TAC cards only happened later when they finally put passwords on the dialup TACs/TIPs -- you originally could dial up and connect to any host on the ARPANET without a password, then you could ask nicely for a free tourist account at places like the MIT-AI Lab. It didn't even require any social engineering, just being polite and curious, reading documentation, and following instructions. I asked BBN nicely about the TIP manual, and they helpfully mailed me a free hardcopy of the "Users Guide for the Terminal IMP", which documented how to take control of other people's sessions and even divert their output by prefixing @ commands by their terminal number! See "Section 5: Unusual uses of the TIP" page 5-7, "Setting Another Terminal's Parameters" and "The DIVERT OUTPUT Command": https://usermanual.wiki/Document/ADA014398UsersGuidetotheTerminalIMPAug75.1728500100/view https://usermanual.wiki/Document/ADA014398UsersGuidetotheTer... The guy who originally wrote that TIP manual in 1971 was none other than Will Crowther, who also developed Colossal Cave Adventure with Don Woods! You're in a twisty little maze of IMPs, all different. https://en.wikipedia.org/wiki/William_Crowther_(programmer) https://en.wikipedia.org/wiki/William_Crowther_(programmer) https://en.wikipedia.org/wiki/Colossal_Cave_Adventure https://en.wikipedia.org/wiki/Colossal_Cave_Adventure ARPANET Psiber SPACE (circa 1986): This is the network of IMPs (Interface Message Processors) that comprised the ARPANET in 1986. The ARPANET is history now, but thanks to the magic of Pseudo-Scientific Visualization and the ScriptX language and class library from Kaleida Labs, you can now experience what it was like to be free ranging packet hopping around the ARPANET in 1986! https://www.donhopkins.com/home/catalog/arpanet/index-large.html https://www.donhopkins.com/home/catalog/arpanet/index-large.... MIT AI Lab Tourist Policy https://medium.com/@donhopkins/mit-ai-lab-tourist-policy-f73b77075631 https://medium.com/@donhopkins/mit-ai-lab-tourist-policy-f73... “The MIT machines were a nerd magnet for kids who had access to the ARPANET,” https://news.ycombinator.com/item?id=15080221 https://news.ycombinator.com/item?id=15080221 Keith F. Lynch wrote up a fascinatingly detailed and accurate history of the ARPANET from his perspective: http://keithlynch.net/history.net.html http://keithlynch.net/history.net.html Keith mentions that ARPANET TACACS passwords were installed in 1986, and even mentions how Jerry Pournelle got himself kicked off the ARPANET for being obnoxious in 1985, which I can conform with the email messages he mentioned. The first message is about TACACS, and explains how MILNET TACACS was implemented in 1984, before ARPANET TACACS (in 1986). It was addressed to the same DEVON, and HN's own GUMBY chimed in with some salty remarks: https://www.donhopkins.com/home/catalog/text/pourne-smut.html https://www.donhopkins.com/home/catalog/text/pourne-smut.htm...
- deleted 5y ago[deleted]
- vaxman 5y agoBenJojo sings “I’ve got too much…time on my hands” The whole migration to IPv6 reminds me of DECnet migration to OSI…which basically never truly happened (because XNS/ITP grew up and became TCP/IP which was then extended to the edge with PPP/RAS, ending the era of store-and-forward email/usenet and destroying X.25/X.PC with its distance-based pricing, heralding the new era of free SPAM and Script Kiddies From Overseas). Same thing will happen to TCP/IP..something else will succeed it before IPv4 is obsolete, probably after somethingBad(TM) happens to create the market imperative for network operators to invest in the alternative.