Earlier quoted context omitted.
Honestly that sounds like a better alternative, than hosting on bare metal.
By default the service max out at 512 MB of RAM (yes, the service was invented in a different decade, way before AWS was cool). So if I want anything more than that, I'm better off running my own server. Also ironically, I can't reach any of the newly NAT'd networks from my XVM instance. I bet the XVM maintainers haven't been warned about the NAT.
By installing NAT, MIT stifles innovation
181–188 of 188 posts
Re: By installing NAT, MIT stifles innovation
#182Earlier quoted context omitted.
That isn't what Aloha was getting at, why is a layer 2 device (in this case a WiFi AP) even interacting with IP addressing? You should be able to run whatever you want, whether that be IPv4, IPv6, or your own custom protocol using raw ethernet frames (of which there are quite a few). Also, what is this whole "Comcast did not play nice with them" trope? I've dealt with Comcast many times, and used Asus, TP-Link, Cisco…
So at home my Comcast connection works fine with most modems and routers without any problems. At my startup's house: - Using the Comcast default combined modem+router works. - Using the Google Wifi AP with a DPC3010 resulted in the DPC3010 being bricked upon connecting to the cable line. This is after the DPC3010 was working fine at my home. That DPC3010 no longer works, even at home, and only gets a power light upo…
Re: By installing NAT, MIT stifles innovation
#183Earlier quoted context omitted.
except NAT does neither network segmentation or lock down the network. Those things are done by a router and firewall. Implementing proper security of IoT devices can be solved by A) writing more secure software for IoT devices and B) having a proper firewall solution with sane defaults. Using NAT as a tool to masquerade your IP addres is not secure. see NAT hole punching for example [1] NAT is terrible from a networ…
> NAT is terrible from a network engineering perspective, it was mostly a patchwork to deal with the rapid expansion of the internet and the shortage of IPv4 space NAT is very useful to the network engineer. NAT lets you turn one network into a different one on a simple one-to-one translations basis. However NAP got mixed up with masquerading to the point where when someone says NAT they assume you also mean masquera…
One to One NAT translation is fine although it still breaks a lot of things, especially on the IPV6 side of things. (like MTU path discovery).
Re: By installing NAT, MIT stifles innovation
#184Earlier quoted context omitted.
So at home my Comcast connection works fine with most modems and routers without any problems. At my startup's house: - Using the Comcast default combined modem+router works. - Using the Google Wifi AP with a DPC3010 resulted in the DPC3010 being bricked upon connecting to the cable line. This is after the DPC3010 was working fine at my home. That DPC3010 no longer works, even at home, and only gets a power light upo…
I still think the combined router/modem is the issue. I've worked with one of the combined router/modems with a Comcast business connection before. Very buggy, and Getting the static IPv6 and IPv4 is a herculean task. The Cisco DPC3010 has its own oddities. I would suggest looking at some of the newer cable modems that Comcast supports. If you need static IPv4 though, you have to use Comcast's equipment.
Re: By installing NAT, MIT stifles innovation
#185Earlier quoted context omitted.
Forcing people to use anything is never a good way to promote innovation. Two words: seat belts. The auto industry fought this tooth and nail, as did parts of the general public. But once this painful transition was accomplished, it resulted in a big improvement in automotive safety. Other examples include EPA regulations that forced out the use of hazardous chemicals and processes. This, in turn, also produced a not…
Creating seat belts is innovation. Creating regulation requiring cars to have them and passing laws that people have to use them is not innovative.
You're arguing against a straw man. This is about the promotion of innovation. Yes, seat belts were innovative, and left to their own course were going nowhere. Some innovations face adoption challenges that go beyond the mere "meh" of "non-consumption". They are major social battles, requiring large and multi-faceted campaigns to succeed and overcome social inertia. E.g. for seat belts: regulations on manufacturing, laws and law enforcement campaigns, public education and marketing, etc.
Re: By installing NAT, MIT stifles innovation
#186Earlier quoted context omitted.
Creating seat belts is innovation. Creating regulation requiring cars to have them and passing laws that people have to use them is not innovative.
Quoth the parent to my post (emphasis mine): > Forcing people to use anything is never a good way to promote innovation. You're arguing against a straw man. This is about the promotion of innovation. Yes, seat belts were innovative, and left to their own course were going nowhere. Some innovations face adoption challenges that go beyond the mere "meh" of "non-consumption". They are major social battles, requiring lar…
Re: By installing NAT, MIT stifles innovation
#187Earlier quoted context omitted.
I'm not switching my private network. This has nothing to do with wider adoption, nor do I have issues with IPv6 as a protocol. What's blocking me is router firmware. It can do IPv6, but only as an afterthought. Sadly, no level of adoption is going to fix that, until I buy a new router.
Time for a new router, then, and by "new" I mean any produced in the last ten years. I have several old routers in a junk drawer that only do 10/100 and even they support it.
A router that fixes all this is at least 120. That is too much for me. I tried dd-wrt, but that doesn't fix the first router on the chain.
Re: By installing NAT, MIT stifles innovation
#188MIT had a very non-authoritarian, egalitarian culture, as Richard Stallman described it:
"I went to a school [Harvard] with a computer science department that was probably like most of them. There were some professors that were in charge of what was supposed to be done, and there were people who decided who could use what. There was a shortage of terminals for most people, but a lot of the professors had terminals of their own in their offices, which was wasteful, but typical of their attitude. When I visited the Artificial Intelligence lab at MIT I found a spirit that was refreshingly different from that. For example: there, the terminals was thought of as belonging to everyone, and professors locked them up in their offices on pain of finding their doors broken down. I was actually shown a cart with a big block of iron on it, that had been used to break down the door of one professors office, when he had the gall to lock up a terminal." (https://www.gnu.org/philosophy/stallman-kth.html)
In 2004, the MIT AI Lab was "upgraded" to the new Stata Center building, an unwieldy, Frank Gehry-designed monument to a recent MIT president's ego, and the antithesis of what it replaced, Building 20. Building 20 was a utilitarian construction from WW2 with no pretenses of becoming a prized or permanent spot on campus. Instead, its residents helped it organically acquired a character of its own as Wikipedia describes well:
'Due to Building 20's origins as a temporary structure, researchers and other occupants felt free to modify their environment at will. As described by MIT professor Paul Penfield, "Its 'temporary nature' permitted its occupants to abuse it in ways that would not be tolerated in a permanent building. If you wanted to run a wire from one lab to another, you didn't ask anybody's permission — you just got out a screwdriver and poked a hole through the wall." [...] MIT professor Jerome Y. Lettvin once quipped, "You might regard it as the womb of the Institute. It is kind of messy, but by God it is procreative!" [...] Because of its various inconveniences, Building 20 was never considered to be prime space, in spite of its location in the central campus. As a result, Building 20 served as an "incubator" for all sorts of start-up or experimental research, teaching, or student groups. [...] Building 20 was the home of the Tech Model Railroad Club, where many aspects of what later became the hacker culture developed [not to mention pranksters and lock pickers, as well].'
Sadly, the TMRC's elaborate railroad, which exhibited interesting pre-miniaturization computation, didn't survive the dismantling of Building 20 and was eventually replaced with modern components. I also hear the Stata Center has two spires, one maddeningly named after Bill Gates, separating the two fiefdoms of computer science at MIT in glass-paneled offices meant to flatter status-conscious administrative types. Since Frank Gehry's architecture is proprietary and depends on strict tolerances, there's scant building modification going on.
That's why I think you can see these network changes as a tragic continuation of a destruction of the historical character of MIT, even though they may also be necessary.
More info about Building 20:
http://web.archive.org/web/20011215020413/http://rleweb.mit....
http://web.archive.org/web/20060912140051/http://www.eecs.mi...