1
Rule #1 - Be Patient - Rule #2 - Don't ask when, if you don't contribute - Rule #3 - You have coding skills - LinuxMCE's small brother is available: http://www.agocontrol.com
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
[quote author=dbs link=topic=4574.msg49621#msg49621 date=1237831014
Thanks Andrew and, also, collinjones
Some of your constraints apply and I was also hoping to be able to bring the core up on my existing lan for testing without having to recable or reconfigure to keep my legacy units online. Additionally, in another thread a member indicated a preference for his existing firewall and didn't want to put the overhead on the core. I tend to lean that way myself.
Your configuration looks pretty straightforward.
Turn off DHCP on the firewall/router and assign a fixed IP to LinuxMCE 192.168.1.xx (my gateway)
Allwo LinuxMCE to assign 192.168.80.xx logins
The crux of my question is can I assign a static IP to my existing PCs in the 192.168.1.xx domain without breakiing or confusing LinuxMCE? If not, I'll take collins kind advice.
Thanks
Leave them on the external network for now, so they are not dependant on the core being up. Patch one over to the internal network whilst you are testing and back again, when done. The only other sane option is to dual home one of the PCs on both internal and external networks, but even that is not very sane!
man is your friend try man grep