Thom, as I already said I am sorry. I know if I do out of the box config install I am on my own. Please do not get mad, I am not mad . It looks that freymann was following instructions. My point is make decision about 1 or 2 nics before you start install, I did test install on single nic just to confirm that PlutoDHCP would work on other machine and it was easy, because I knew I was installing for single nic and it was install from scratch. Also, LinuxMCE install is intelligent to configure it self correctly, regardless 1 or 2 nics, but the trick is to do clean install knowing if you plan to use 1 or 2 nics. It seems to me that all these problems happen when user start to make changes after install.
Yes, but I followed the instructions given in "Single NIC & Existing DHCPd" which I can't locate the link for, because I guess, I hate this wiki system.
I'm no dummy, but after 4 days of struggling (and hey, I have made great progress to date) with LinuxMCE, my views about it are rather dim right now.
Yeah, I'm steamed, 'cause I spent 4 days friggin with the stuff. Believing the "demo video" I went out and spend $300-$400 on equipment to make media directors, get gyro mouses, video capture cards, IRD transceivers and remote, and gave up my ubuntu workstation to act as the core.
The point here is please don't start recommending modifications to the architecture until you have been here long enough to realise what this means. I recognise that you have technical competance, but that doesn't translate to experience. Andrew (Totallymaxed) is both highly experienced and a professional, and even he specifically does not recommend
single NIC installations, in fact specifically says 2 NICs is better and that is what they usually use. But moreover, he says nothing about disabling or rebuilding the DHCP system.
Saying "make decision about 1 or 2 nics before you start install" sets entirely the wrong tone for newbies. This is not
something that people just starting should even be thinking about unless an experienced LMCEer is prepared to support them through it. A quick search through the boards on this subject will reveal: 1) countless instances of agonising experiences of this and 2) enormous angst and irritation of experienced users trying to help others get this right when more fruitful activities could have been undertaken.
I'm not denying that there will be some instances where this is the more appropriate setup, however, that is rare - but setting this tone makes it seem like just a multi-choice option, that inevitably new users will lean towards, when the real point at issue was a <$20 NIC card... believe me, it is human nature, and is backed up by dozens of threads on the board. The recommendation should always be 2 NICs, no questions asked, until a user outlines a genuine roadblock to that approach. In such instances, I am more than happy to provide assistance as it is needed, but in practice I haven't needed to for a v long time. There are not 2 right ways, there is a right way, and an alternate way if the right way genuinely doesn't work .... genuinely not working does not include "I need to save $20 on a NIC!" You are spending at least $500 in the first place to set up a core (generally ... usually more).
Saving money on the point about wireless APs is a completely fatuous and specious argument for the same reasons! It is one thing to try to keep costs down by engineering smartly, it is another entirely to force an incompatible design/topology to achieve this end. APs are cheap, and naturally you don't need yet another NIC, Hari meant connect it to your internal switch. If you are setting up a hybrid/core, 1 MD, an orbiter or two, and perhaps even a NAS or big disks on a PC, you are already in for >$1000, saving ~$20 or so on an AP for the internal network, by trying to route a different broadcast domain across the firewall, transparently, is specious. By all means, save money by making smart decisions on hardware, but not by trying to force a square peg into a round hole.... after all, you could
use your neighbour's wifi AP, and route that traffic back into your network, and save money, too!