Messages

1

Installation issues / Re: Diskless Media Directors on a 1 NIC Core, is that possible?

« on: April 14, 2009, 05:43:23 am »

WAN side of your Core connected to a Switch and then all MD's and other devices controlled by core are connected to ports of this Switch (or additional switches connected to it)...
...
Andrew

Andrew,
Did you mean "Internal side of your Core..."?

2

Installation issues / Re: New diskless MD does not install properly. Why?

« on: March 25, 2009, 06:25:30 pm »

Hi Boris,
I did not change the IP (that was already assigned as 80.18 by the core), but I entered the NIC in the web admin. As I wrote above, that got me one step ahead.

The modification of /etc/network/interfaces was another step.

But now the MD makes its eth0 available after the initrd.img is loaded, and that obviously confuses the heck out of the whole booting procedure. It first boots with eth1, and then there is all of a sudden an additional eth0!

Making eth0 a hotpluggable interface does not help. The screen output while booting shows the message about the newly found interface, with new MAC address, and then everythings hangs again. What is needed, I think, is a way to tell the MD to ignore eth0 and eth2. That probably requires a new initrd.img... 

Best regards
Mark

Mark,
I, was hopping you did not change IP.

Can you post your /usr/pluto/diskless/[MD#]/etc/network/interfaces?

I still say try this - disable NICs in your bios (that is really bad that you can not disable just one NIC at the time), delete your MD with IP 80.18 from webpage, reboot core, and PXE boot from your PIC NIC card.

3

Installation issues / Re: New diskless MD does not install properly. Why?

« on: March 25, 2009, 08:11:37 am »

boris - please do not use the "setup diskless md" button. This is legacy. The correct way to set up an MD is just to turn it on with PXE enabled in the BIOS. The core does everything else.

Fair enough Andrew , just kidding Colin. It looks that if you use MD wizard to add your device then "setup diskless md" is useless because it seems that "add device" already does all the work.

But as Colin and Tim said, PEX booted MD will configure it self. So delete your MD from MD wizard web page, then reload or reboot your core and boot your MD from PEX and it should just work.
If you once again see that your MD gets address 192.168.80.248 before you see "Announce MD to Core.." (or something like that) message that is normal. You will get IP in range of pluto devices after "Announce MD to Core.." message.

Domodude, you said "That worked, as far as changing the IP." what did you change that IP to?

4

Installation issues / Re: New diskless MD does not install properly. Why?

« on: March 24, 2009, 11:43:32 pm »

after you do all configs and run "setup bootless md" from MD set up web page, can you show what your /etc/dhcp3/dhcpd.conf looks like?

5

Installation issues / Re: New diskless MD does not install properly. Why?

« on: March 24, 2009, 08:25:48 pm »

add MAC address of your new NIC in configuration for your MD in admin web interface. The same place where you set IP address for MD.

6

Installation issues / Re: Diskless Media Directors on a 1 NIC Core, is that possible?

« on: March 24, 2009, 05:33:05 pm »

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.

 Impressed? Not.

7

Developers / Re: LMCE Launch Manager - name change suggestions please

« on: March 24, 2009, 05:05:19 pm »

I agree with others, if it is not broken do not fix it.

After reading the question again I change my mind .
I think - lmced, LMCE-client (LinuxMCE Dashboard).  Lower case for LMCE-client, I do not know how to prevent substitution to lmce when I type LMCE in lower case.

8

Installation issues / Re: Diskless Media Directors on a 1 NIC Core, is that possible?

« on: March 24, 2009, 04:51:31 pm »

thats called an access point.

So, in my opinion, if you plan to use wireless orbiters then it is better to use only one NIC

please don't suggest that to users..

you just need to connect a $15 access point to the internal nic.. done.

br, Hari

Hi Hari,
You call it access point, I call it wireless router (that would be used as access point), but at the end it does not matter because they both serve the same purpose .  I can not find access point for $15.00, the least expensive access point that I can find is about $40.00 (http://www.newegg.ca/Product/ProductList.aspx?Submit=ENE&Description=access%20point&bop=And&Order=PRICE). So extra nic $10 then $15-40 for access point, I thought one of the goals was to use equipment user already have and keep the cost down. I have read a few posts where users were pretty upset because they had to spend money on new equipment (regardless of cost $1 or $100).

I think, I understand the design concepts, goals and intended use/configurations of LinuxMCE, only because I do not agree with some of them, it does not make me a bad person, right? I do like, the capabilities and futures of LinuxMCE, if I did not like it I would not use it . 

I did not meant for my comment to be interpreted as suggestion or advice, I only stated my opinion, and I am sorry if it was misinterpreted as suggestion.

9

Installation issues / Re: Diskless Media Directors on a 1 NIC Core, is that possible?

« on: March 24, 2009, 08:33:21 am »

...
pool { allow unknown-clients; range 0.0.0.0 0.0.0.0;}
...

After recompiling and replacing PlutoDHCP in usr/pluto/bin, without any code changes, this problem went away. I no longer need to check "Provide IP addresses for anonymous...". I wanted core/hybrid to work this way, so I have control of PCs booting from network. Also, all other devices on network get address from DHCP server on Dlink router. DHCP ranges on core/hybrid router and Dlink router do not overlap, but are on the same subnet.

The reason I want it to work this way so I can use my iPAQ as orbiter via wireless network.

So, in my opinion, if you plan to use wireless orbiters then it is better to use only one NIC. As far as I understand if you use wireless orbiter, I my case iPAQ, then it has to connect to internal NIC. So if two NICs are used and one is external connected to router(most of them are wireless these days), then one would need to have second wireless router connected to internal NIC, right or I am missing something? The second wireless router has to be on internal network so your wireless device gets configured via DHCP (I am assuming we trying to say away from manual network confutation as much as possible) and load orbiter from the core.

10

Developers / Re: Developer FAQ

« on: March 24, 2009, 12:32:57 am »

you want bluez-devel

Thanks, that did the trick.

ok where do these instructions need to go?  Sorry this is first time I am doing this, so if I make any mistakes I am sorry.
 Run this to install libs

Code: [Select]

sudo apt-get install libbluetooth-dev


11

Feature requests & roadmap / Re: feature request - Skype integration

« on: March 23, 2009, 10:54:21 pm »

What about using Skype APIs https://developer.skype.com/Docs?
I did not read all legal info (http://www.skype.com/intl/en/legal/terms/api/), but there are may be a limitations of how it could be used.

As end user I like idea of Skype, or equivalent, be integrated with LinuxMCE.

12

Developers / Re: Developer FAQ

« on: March 23, 2009, 09:32:31 pm »

Where can I find  bluetooth sources referenced in /PlutoDHCP/PlutoDHCP.ccp -> /BD/PhoneDevice.h see error below.

I followed all steps outlined at http://wiki.linuxmce.org/index.php/Building_From_Source. And was able to build UpdateMedia.  But I also see "/!\ WARNING: at the moment the sources are moving, so there are some bugs related to sources versions. you may not be able to compile" at http://wiki.linuxmce.org/index.php/Setting_Up_A_Development_Environment.
Is this warning the reason I am not able to locate bluetooth sources?

Code: [Select]

/src/PlutoDHCP$ make
g++ -I. -I.. -I.. -I../DCE -I/usr/include/mysql -W -Wall -pipe -ggdb3  -c -o PlutoDHCP.o PlutoDHCP.cpp
In file included from PlutoDHCP.cpp:53:
../BD/PhoneDevice.h:24:33: error: bluetooth/bluetooth.h: No such file or directory
../BD/PhoneDevice.h:25:30: error: bluetooth/rfcomm.h: No such file or directory
../BD/PhoneDevice.h:26:27: error: bluetooth/hci.h: No such file or directory
../BD/PhoneDevice.h:27:31: error: bluetooth/hci_lib.h: No such file or directory
../pluto_main/Table_Device.h:262: warning: unused parameter ‘iSC_Version’
../pluto_main/Table_Device_DeviceData.h:164: warning: unused parameter ‘iSC_Version’
../pluto_main/Table_DeviceData.h:169: warning: unused parameter ‘iSC_Version’
../pluto_main/Table_DeviceCategory.h:184: warning: unused parameter ‘iSC_Version’
../pluto_main/Table_DeviceTemplate.h:315: warning: unused parameter ‘iSC_Version’
../pluto_main/Table_Installation.h:255: warning: unused parameter ‘iSC_Version’
../BD/PhoneDevice.h:53: error: ‘bdaddr_t’ does not name a type
../BD/PhoneDevice.h: In copy constructor ‘PhoneDevice::PhoneDevice(const PhoneDevice&)’:
../BD/PhoneDevice.h:120: error: ‘m_bdaddrDongle’ was not declared in this scope
../BD/PhoneDevice.h:120: error: ‘const class PhoneDevice’ has no member named ‘m_bdaddrDongle’
PlutoDHCP.cpp: In member function ‘std::string PlutoDHCP::GetDHCPConfig()’:
PlutoDHCP.cpp:298: warning: comparison between signed and unsigned integer expressions
PlutoDHCP.cpp:308: warning: comparison between signed and unsigned integer expressions
PlutoDHCP.cpp:244: warning: unused variable ‘iMoonNumber’
make: *** [PlutoDHCP.o] Error 1


13

Installation issues / Re: Diskless Media Directors on a 1 NIC Core, is that possible?

« on: March 22, 2009, 08:51:51 am »

Sorry all, this post is more suitable for this http://forum.linuxmce.org/index.php?topic=6042.0 , sorry I got them mixed up .

Yes it is possible.
I just upgraded to 710 adm64 from 704 with keep settings, well that did not really work well. In retrospect I should have just done clean install.

If you planing to have only one NIC then the best thing to do, in my opinion is to disable the the second NIC on hardware level before installation. Most of motherboard have option to disable NIC in BIOS.  Also, in order to have NetBoot working you must check "Provide IP addresses for anonymous..." in network setup and provide range of for addresses for anonymous devices. If you do not, then DHCP server configuration file (/etc/dhcp3/dhcpd.con) is not generated correctly by /usr/pluto/bin/PlutoDHCP, and as result DHCP server does not re/start due to error in configuration file. If there is no rage specified for anonymous devices PlutoDHCP writes incorrect range to dhcp.conf file and sets it to 0.0.0.0-0.0.0.0.
Here what it looks like in file :
...
pool { allow unknown-clients; range 0.0.0.0 0.0.0.0;}
...

You need DHCP server in order to do netboot, aka diskless media director.

If you do not feel like reinstalling then keep reading.
1. In Advance->Configuration->Devices->CORE change "Network Interfaces" and remove everything after "|" and including  "|" (without "s), and Save changes. This will force network reconfig on reboot". Only do this step if you had previously 2 NICs and removed/disabled second NIC and the first thing after "|" is "eth1".
2. Remove everything in /etc/network/interfaces that has to do with configuring eth1 (ex.
auto eth1
iface eth1 inet static
        address 192.168.1.101
        netmask 255.255.255.0
).

3. If you disabled second NIC then check /etc/udev/rules.d/70-persistent-net.rules and remove or comment out (with #) all the lines that are not for your existing interface. To match you interface use MAC address, also make MAC address be assigned to eth0 interface in this file (ex. SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:1d:60:54:35:56", NAME="eth0").
4. Set up your network, check "Enable DHCP server" and "Provide IP addresses for anonymous devices....". And provide not over lapping ranges (ex. 192.168.1.100-192.168.1.150 and 192.168.1.151-192.168.1.170). Set static IP address for external interface, and remove IP address and Sub Net mask from second NIC.

Once you click Update your Core should reboot. After reboot you internal network card should be eth0:0, set the address and sub net mask for this interface (I used the same address for internal and external interfaces). Your Core should reboot one more time. Then go to Wizard->Devices->Media Directors and click Setup Diskless MD, pay attention to any errors after (and make user that dhcp server re/starts), it may make a while for Setup Diskless to complete. If you get no errors  and dhcp server started then your Diskless boot should work. To check if your dhcp server running run this "/etc/init.d/dhcp3-server status" without "s from command prompt.

I did all of my changes vi ssh/command prompt and directly in database using mysql so, above is the best interpretation of how to do same steps via admin web interface and ssh/command prompt. To get to command prompt press Crl+Alt+F2 and login as linuxmce user.

Here are my setting that work for me (make sure to replace MAC addresses if you try to use them):
-----/etc/default/dhcp3-server---
INTERFACES="eth0"
-------------------------------------
----/etc/dhcp3/dhcpd.conf----------
# option definitions common to all supported networks...
#option domain-name "fugue.com";
#option domain-name-servers toccata.fugue.com;
option domain-name-servers 192.168.1.101;
authoritative;

option routers 192.168.1.101;
option subnet-mask 255.255.255.0;

# lease IPs for 1 day, maximum 1 week
default-lease-time 86400;
max-lease-time 604800;

allow booting;
allow bootp;

option space pxelinux;
option pxelinux.magic code 208 = string;
option pxelinux.configfile code 209 = text;
option pxelinux.pathprefix code 210 = text;
option pxelinux.reboottime code 211 = unsigned integer 32;

subnet 192.168.1.0 netmask 255.255.255.0 {
        next-server 192.168.1.101;
        filename "/tftpboot/pxelinux.0";
        option pxelinux.reboottime = 30;

        default-lease-time 86400;
        max-lease-time 604800;
        pool {
                 allow unknown-clients;
                 range 192.168.1.231 192.168.1.250;
        }
}

# PXE booting machines
group {
        next-server 192.168.1.101;
        filename "/tftpboot/pxelinux.0";
        option pxelinux.reboottime = 30;

        # Generic PC as MD (75)
        host moon75 { hardware ethernet 00:E0:18:A7:BD:4B; fixed-address 192.168.1.200; }
        # Generic PC as MD (98)
        host moon98 { hardware ethernet 00:1D:7D:D6:F5:F7; fixed-address 192.168.1.201; }
}

# regular machines
group {
        # CORE (1)
        host pc1 { hardware ethernet 00:1D:60:54:35:56; fixed-address 192.168.1.101; }
        # DCEROUTER - DCEROUTER (120)
        host pc2 { hardware ethernet 00:00:00:00:00:00; fixed-address 192.168.1.203; }
}
-----------------------------------

Out put from Network Config on admin site:

EXTERNAL_IFACE     eth0
EXTERNAL_MAC    00:1D:60:54:35:56
EXTERNAL_IP    192.168.1.101
EXTERNAL_NETMASK    255.255.255.0
EXTERNAL_DHCP    0
INTERNAL_IFACE    eth0:0
INTERNAL_MAC    00:1D:60:54:35:56
INTERNAL_IP    192.168.1.101
INTERNAL_NETMASK    255.255.255.0
GATEWAY    192.168.1.2
DNS1    64.59.176.13
DNS2    64.59.176.15