Benches macOS

9

DHCP classless static routing support

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

I'm attempting to supply a network with link-local routes for multiple disjoint subnets via DHCP, by using the DHCP classless static routing option as specified in RFC 3442 (code 121 and/or 249).

This works fine with both windows and linux clients, but OS X appears to ignore the option entirely. There is very little information about OS X support for RFC3442 on google, but what I've seen suggests that it should be working - what am I doing wrong?

The routing table isn't affected at all. route monitor shows no indications that the client notices the option. I did notice that the Leopard DHCP client supplies an explicit list of option requests, CSR not being among them, so I had to force dhcpd to return it; by inspection, the returned option is exactly the same as for OSs for which it does work.

9 replies

Sign in or join Beachball Help to reply.

  1. 0

    Dogcow-Moof

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    DHCP on Mac OS X does not request option code 121 or 249, but I don't know whether Mac OS X will do anything with the information if the server provides it.

  2. 0

    Baughn

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    It doesn't; that's rather the point.

    This is a six-year-old standard, supported and used on many other systems - I would have expected better from Apple, which is why I was wondering whether there might be some way to turn it on. Meanwhile, I'm writing a daemon to handle it.

  3. 0

    guydavies

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Hi Baughn,

    I was just trying to achieve the very same thing and came to the same conclusions as you did. Irrespective of whether you use code 121 or 249, Mac OSX appears to ignore the option. It seems strange that Apple haven't got round to fixing that yet.

    Time for a 'report' to Apple, I think.

    Rgds,

    Guy

  4. 0

    Dogcow-Moof

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Note at this point it's a feature request rather than a bug.

    Let Apple know what you'd like to see here:

    http://www.apple.com/feedback/macosx.html

  5. 0

    Baughn

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Nah, not much point; we only had one macintosh computer to begin with, and we've decided it's easier to get rid of it. If Apple can't be bothered to implement the entire standard, that's now their problem.

    Whether it's a feature request or a bug is more of a philosophical discussion, really; yes, it's an optional feature, but it's one that every other OS we use supports.

  6. 0

    direwolf8

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    The ENTIRE standard? Then I suppose you threw your Windows machines away too.

  7. 0

    Baughn

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Alright, alright.

    The parts of the standard that we care about, ie, RFC3442

  8. 0

    guydavies

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Unlike Baughn I do care enough to create the feature request. However, I consider this to be a significant deficiency that is bordering on a bug, particularly if Apple wishes the Mac to be taken seriously as an enterprise machine.

    I also have to say that Apple's feature request mechanism is horrendously opaque with absolutely zero feedback (and it's not even obvious that the "feedback" link is the appropriate mechanism to make feature requests).

    Rgds,

    Guy

  9. 0

    Dogcow-Moof

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    The feedback link is literally the only way to ask for a feature.

    There is no response, just the "thank you" page after you click submit.

    In all fairness, I'm not aware of any interactive mechanism by which one would ask for a feature in Windows, either.