Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror
×

Comment Re:IPV6 is the problem. (Score 1) 309

They deliberately chose to make ipv4 and ipv6 incompatible. Again, emphasized. They could have increased the address space and allowed vendors to tweak the ip stack to recognize both types of addressses. Routers could have an interface running ipv6 and an interface running ipv4 and pad the ipv4 destination with zeros to allow transit on ipv6 networks.

Instead they fixed a lot of problems that weren't problems. And because it was seen as a solution we pissed away 10 years where we could have slowly migrated.

Comment Re:IPV6 is the problem. (Score 1) 309

AMEN. The fucking forum is the the bastards who caused this mess. Yes CAUSED. People assume that ipv6 was a valid solution to the problem and went about their business. Anyone charged with implementing it outside of a lab or their basement quickly realized what a clusterfuck it was. The requirement , yes the REQUIREMENT of running dual stacks has made safe deployment of ipv6 impossible.

IPv4 was a test protocol that progressed organically until vendors were forced to adopt it or lose customers. Problems were fixed by smart working engineers suggesting drafts and working with vendors.

IPv6 was created by a bunch of jackasses. Someone should have produced an internet draft where a modified ipv4 with larger IP space and ipv4 devices could communicate with each other. An ipv4 device getting a new style address in answer to a dns request would be able to route to it using ipv4.

The ipv6 spec stated that NAT between ipv6 and ipv4 was PROHIBITED. So we are going to need dualstack proxies until every last ipv4 only device is gone.

ipv4 v6 DNS is a joke. So every content provider will need dual implementations of thier servers. DNS errors will cause mystery outages that customers blame on the content providers. GRRR.

Comment The IPv6 Working Group is the real root cause. (Score 2, Interesting) 270

Stupid fuckers could have made the protocols interactive, but no, they had to try to be clever and redesign the whole thing, so we will need to run dual stack for 5-10 years. No bugs gonna be there. They were just pissy because no one liked OSI CLNS . Which would be just as easy to switch over to, by the way. How many addressable addresses does IPX/SPX have? Lets Dual stack that instead, just to fuck them.

My only bitter pleasure will be watching microsoft networking melt down. Dynamic DNS? No way bitch, ip6 addresses handed out by the router. Of course they will just continue to cheat and use NetBui with a local global catolauge server, like they do now.

Comment Re:Wasteful allocation is nearly as bad. (Score 1) 270

Well, some devices have support for a /31 subnet, that helps a bit. But the problem is usually that the way the cable head end infrasructure works, you are on a shared network, and they roll out a subnet for static ip addresses keyed to mac addresses. So if you are the only static subnet user in the neightborhood, then some addresses are wasted.

Canada

Ontario School Bans Wi-Fi 287

St. Vincent Euphrasia elementary school in Meaford, Ont. is the latest Canadian school to decide to save its students from the harmful effects of Wi-Fi by banning it. Schools from universities on down have a history of banning Wi-Fi in Ontario. As usual, health officials and know-it-all scientists have called the move ridiculous. Health Canada has released a statement saying, "Wi-Fi is the second most prevalent form of wireless technology next to cell phones. It is widely used across Canada in schools, offices, coffee shops, personal dwellings, as well as countless other locations. Health Canada continues to reassure Canadians that the radiofrequency energy emitted from Wi-Fi equipment is extremely low and is not associated with any health problems."

Comment Re:NOOOOOOO (Score 1) 583

The first set of idiots wrong out of the tech sector will be IPv6 early adopters. When the core routers start rebooting because of IPv6 ospf bugs, and layer 2 switches turn out to use silicon shortcuts that depend on ipv4 ethertypes and shit does not work, have fun troubleshooting dynamic address assignment and dns via hostnames.

The IPv6 adoption is still 2 years off, and Fusion power is 30 years off.

What is the needless hardware and Software involved with NAT? Firewalls and load balances are still in place. Firewalls usually need static statements even if you don't NAT.

Having merged many an organization with overlapping private space, I sure do wish that they had just rolled out IPv6 by doing nothing other than doubling the address space and making ipv4 and ipv6 connections seamless. But they got clever, and we need to wait untill a bunch of suckers roll out ipv6 and hit all the career ending outages and bugs.

Slashdot Top Deals

It seems that more and more mathematicians are using a new, high level language named "research student".

Working...