How to setup a os x router as a ODM?

[macmattias]

I have a OS X 10.5 server setup as a router/firewall at home and now I want to add a OD.
But when I promote the server to ODM it goes on the info that it gets from en0 and that is the WAN-info. Therefore Kerberos fails.

How do I get the promotion to look for its info on en1 that is the LAN.
There I have DHCP, DNS and all that setup and working.

Feels like it should be a simple cli-command or something but so far I havn’t been able to track it down.

So does anyone know what I should do?

[macmattias]

This thought struck me as I was about to fall alseep, could it be so easy that I just need to change the order of the ethernet prefes in the Network pane?

[macmattias]

[QUOTE][u]Quote by: macmattias[/u][p]This thought struck me as I was about to fall alseep, could it be so easy that I just need to change the order of the ethernet prefes in the Network pane?[/p][/QUOTE]

I know that was just a stupid idea, I know better than that…
Ah well… hoping for answer from someone who knows. 🙂

[McDeth]

As long as you’re not doing NAT you should be able to switch the connections, otherwise the outside interface needs to the first interface listed on the Network Prefs pane in order for NAT to function properly. Unfortunately, if you are using NAT, then I don’t believe that this is where your problem lies.

In order for Kerberos to work properly on a machine set up with an external and internal interface, you need to have DNS functioning properly on both the internal and external sides of your network. Internally, it shouldn’t be an issue, since you can set up your own DNS server in Mac OS X. Externally, the problem lies with your ISP and any outside DNS servers. First of all, you need to have a static IP if you’re going to assign that address a domain name. Second, you need to have access to your own DNS server or subscribe to a service where you can edit dns records. Once these two things are done, you must make sure that your server has the same exact domain name on both sides of the network. For example, if your internal domain name is xserver.myhome.com, then the external dns needs to point to a WAN IP address that is also assigned to xserver.myhome.com Additionally, the reverse lookup for the external domain name needs to point back at your external IP address, otherwise Kerberos will refuse to bind.

Of course, this is how I got an OD master working with both an external and internal interface, but I could be completely off base.

[Author]

Posts