Live data from Hacker News

Why couldn't MAC addresses be used instead of IPv4|6 for networking?

serverfault.com

1–10 of 38 posts

Re: Why couldn't MAC addresses be used instead of IPv4|6 for networking?

#2
Typically, MAC is assigned by the hardware manufacturer (sometimes you can change/spoof it). IP is typically assigned either by the network administratior or DHCP. If all addresses were based on mac, you could easily intercept the messages from anyone. IP allows a layer of abstraction in which you can group multiple subnets into the same external IP or set up subnets within those subnets even.

Another problem is that numerous devices will share the same MAC address, it's just statistically unlikely to find them on the same network. It's an especially big problem with cheap/knockoff network equipment. See: http://www.linuxquestions.org/questions/linux-networking-3/m...

Re: Why couldn't MAC addresses be used instead of IPv4|6 for networking?

#4
post #3

No reason at all. Novell Netware did exactly this . The host portion of your address was your MAC. Networks were identified by their local netware servers.

That's pretty much exactly what IPv6 with stateless autoconfig does--network address in the upper 64 bits, MAC address (slightly modified) in the lower 64.

Re: Why couldn't MAC addresses be used instead of IPv4|6 for networking?

#5
post #2

Typically, MAC is assigned by the hardware manufacturer (sometimes you can change/spoof it). IP is typically assigned either by the network administratior or DHCP. If all addresses were based on mac, you could easily intercept the messages from anyone. IP allows a layer of abstraction in which you can group multiple subnets into the same external IP or set up subnets within those subnets even. Another problem is that…

Actually the main problem of MAC vs IP, as the response states, is the lack of hierarchy vs the presence of it.

Both IPs and MACs can be changed by the administrators and both can be set such that duplicates exist in the network. However the fact that MACs are set by manufacturer makes them impossible to route as the values are not related to the network locations but related to hardware origin.

Edit: As one of the replies stated, they are also used in Stateless autoconfig in IPV6 (see: https://en.wikipedia.org/wiki/IPv6_address#Modified_EUI-64)

Re: Why couldn't MAC addresses be used instead of IPv4|6 for networking?

#6
They already are. Part of the IPv6 address is derived from your MAC.

Despite not owning the network for which they are being allocated, IPv4 is a "paying job" to some people. And sometimes an ego boost too, i.e., people who get their kicks from creating "IP address policy". Needless to say this easy "work." Hello ARIN.

It's a lot like ICANN.

On CircleID someone recently pointed out that IPv6 will make this sort of "job" meaningless. There is so much IPv6 address space that playing favorites and charging hefty fees is unjustifiable.

Back to your point about MAC's: This is also why the "we're out of IP addresses" meme seems silly. Because we don't see the IEEE complaining they are "running out of MAC's". And IPv6 addresses use MAC's.

The thing to keep in mind is that just because something, e.g. a better addressing scheme, or true network-level peer-to-peer networking, is not "widely adopted" does not mean it isn't available, _right now_. It may have been available for years. There were people at universities still teaching the use of punch cards even after a well-known computer professional in Canada was already programming using a terminal display. And there were other Canadians sending emails before DARPA.

Do not assume that the crowd is always wise. And be wary of the "hype".

80/20 rules - another great internet meme - mean than we can have 80% of the people being stupid. And the 20% have to suffer.

When the "new" naming, "new" addressing and "new" peer-to-peer solutions are offered up the next time, keep an open mind. Try not to be so quick to dismiss any sort of change to the "status quo". Evaluate the approach carefully. It might have merit, and maybe it's not immediately obvious.

Many times (in fact almost all the time), the solutions are not new. We're just waiting for people to finally catch on and realize there is "a better way". We're waiting for people to "try something 'new'".

Re: Why couldn't MAC addresses be used instead of IPv4|6 for networking?

#7
Lots of reasons.

From a security perspective - IPv6 SLAAC (sort of like DHCP) does this - it uses the MAC as the last 48 bits of the 128 bit address. However, this is largely seen as a security problem things like RFC 4941 [1] have argued against this idea. If you think having your iPhone keep a track of which cell phone towers you've been to is bad, think about the consequences of being globally reachable by the same IP address at all times, which means you can be tracked to where that devices is and has been based on the routing rules.

As well, ethernet is not IP. They are different layers of the OSI model. Just because you're on ethernet (wired/wireless) doesn't mean you're using IP, and vice versa. Some devices don't have MAC addresses. Frame relay uses DLCI's for instance. Historically there were lots of other technologies using IP that weren't ethernet - FDDI, token ring, ATM, etc. Ethernet has replaced nearly all of those, but not all.

Routing scalability - another huge problem. But this will rear it's head in IPv6 with the exponentially large amount of possible routes. Right now the routing tables are around 350k-400k routes. Compare that to the billions of devices that connect to the internet simultaneously.

MAC addresses are locally assigned addresses. There would be no way to prevent duplicates. In most networks, your IP address will specify the way you are routed through the network and your security level. If that isn't centrally managed you have no security or IP addressing schemes.

[1] http://tools.ietf.org/html/rfc4941

Re: Why couldn't MAC addresses be used instead of IPv4|6 for networking?

#8
post #3

No reason at all. Novell Netware did exactly this . The host portion of your address was your MAC. Networks were identified by their local netware servers.

This is one of the reasons why IPX was a bad idea and never took off. Automagical discovery is always great until it doesn't work.

Re: Why couldn't MAC addresses be used instead of IPv4|6 for networking?

#9
post #3

No reason at all. Novell Netware did exactly this . The host portion of your address was your MAC. Networks were identified by their local netware servers.

This is one of the reasons why IPX was a bad idea and never took off. Automagical discovery is always great until it doesn't work.

and never took off.

IPX was everywhere NetWare was.

NetWare got into everything, like dust, in the 80s and part of the 90s.

Re: Why couldn't MAC addresses be used instead of IPv4|6 for networking?

#10
post #2

Typically, MAC is assigned by the hardware manufacturer (sometimes you can change/spoof it). IP is typically assigned either by the network administratior or DHCP. If all addresses were based on mac, you could easily intercept the messages from anyone. IP allows a layer of abstraction in which you can group multiple subnets into the same external IP or set up subnets within those subnets even. Another problem is that…

> If all addresses were based on mac, you could easily intercept the messages from anyone.

So you encrypt stuff you don't want anyone else to read. Security isn't the concern of the networking layers; it's all done, to the extent it is done, at the application layer.

That's the original design, anyway.

Edited to add: Well, the original original designs were by people who weren't thinking of security at all. That's why telnet and FTP are the way they are.

> Another problem is that numerous devices will share the same MAC address, it's just statistically unlikely to find them on the same network.

This, on the other hand, really is a perversion of the intended model. 48 bits was intended to be globally unique.

Post reply on HN