Couple of thoughts I had while reading this thread...
0) Just to be clear.. Having multiple DHCP servers on a network is just asking for trouble.. Don't do it!
1) If the scripts are just reading the syslog entries, you can set up the core as your syslog server, and set up your linux and some hardware routers to log to your core. That would allow the auto scripts to work. It doesn't do anything for the fixed IP addresses that get automatically assigned/saved for MD's though.
2) I had at one point in my quest for a media server, ran a single NIC install of LinuxMCE, heck I even tried Pluto@Home before LinuxMCE.. I ran into an issue with the database entries, and auto generated dhcpd.conf file not storing the default router entry, which I did post I believe in these forums not Pluto's. I had modified the dhcpd.conf generation script to put in the correct default router for my network, but it was a pain. I had turned off the DHCP on my hardware router, but if I didn't have the correct default route things didn't work correctly.
3) What about the Asterisk problems being NATted? Are there any? Also, does the core do any kind of traffic shaping for VOIP when it's acting as the router?
4) Is LinuxMCE using shorewall, or anything like that, or is it using homebrew rulesets?
5) I too have problems putting all my eggs (so to speak) in one basket, and would prefer being able to split up the servers a bit. ie.. LRP/Leaf Router, Asterisk Server, Myth Backend being distributed among different machines.
6) There is no reason for people to jump all over people for wanting more flexibility in the networking choices when installing the core. There is also no reason not to tell them to implement it and submit a patch, but if they do go to the trouble to submit a patch I would hope that it wouldn't be dismissed out of hand.
7) There is no need for the level of rudeness that has been exhibited by some of the authors of this thread. I do realize however that most of the requests and comments on this subject have been made many times before. Since this is one place where the lack of flexibility to easily put a LinuxMCE core into an existing network can get frustrating. I also realize that the original system that this was based on was designed to be the starting point or replacement, not to integrate in, after all, you have to draw the line somewhere.
Yes, I too rambled a bit...