I was wondering if someone could shed some light on the subject of adding new device templates.  With the new involvement of pluto, does this mean that the bundled sqlcvs application within the admin site will now be useful for added new device templates. 

I am asking because I have finally finished my device template for LG LCD TVs and I am not sure the best method of getting it added to the list of device templates.  I also have a pnp script, but as many of you are aware it requires the device template id and currently this points only to my systems template number.

http://wiki.linuxmce.org/index.php/LG_42LB5D if any one is interested.

Hari, has been working on sqlcvs according to the forums, but it appeared to require some additional steps to sync with his database, and did not appear to be compatible with pluto's

Thanks for the hard work,
Rob

I have just finished posting instructions for adding LG LCD TV device template along with a pnp script if anyone is interested. 

http://wiki.linuxmce.org/index.php/LG_42LB5D

Thanks,
Rob

I really believe the reason no one has answered, is due to the fact that a simple google search will bring up the exact information that you are wanting.

http://en.wikipedia.org/wiki/Help:Starting_a_new_page

Here is a free one, but in the future try google first 9 out 10 times your answer is on the first page.

Rob

Here is the output requested, so it is getting loaded.

Code:

dcerouter_24050:~# iptables -t nat -xvnL
Chain PREROUTING (policy ACCEPT 40 packets, 2886 bytes)
    pkts      bytes target     prot opt in     out     source               destination
       0        0 DNAT       tcp  --  eth0   *       0.0.0.0/0            0.0.0.0/0           tcp dpt:80 to:192.168.80.1:8081

Chain POSTROUTING (policy ACCEPT 6 packets, 480 bytes)
    pkts      bytes target     prot opt in     out     source               destination
       0        0 MASQUERADE  0    --  *      eth0    192.168.80.0/24     !192.168.80.0/24

Chain OUTPUT (policy ACCEPT 6 packets, 480 bytes)
    pkts      bytes target     prot opt in     out     source               destination

My question is now, why did this same rule forward all outgoing browser requests to port 8081 in 704 and now it does not? 

Is there another way to handle outgoing connections.

I would like to figure this one out. 

right now the work around is to manually tell all browsers to us proxy 192.168.80.1:8081

Thanks,
Rob

that is exactly what my iptables -L looks like and I have three additional rules.  This worked in 704 but does not appear to be working in 710Beta3.

If someone else can confirm this I will file a Mantis report.

Thanks,
Rob

I have also been experiencing Firewall issues.  I asked the forum at this post. http://forum.linuxmce.org/index.php?topic=3890.0  but I have not gotten a response.  I had not tried Beta2, so  I do not know if my problem exists in Beta2, but I am not able to get any Firewall changes loaded via Admin in Beta3

try iptables -L and see what rules are loaded

Thanks,
Rob

I have upgraded to Beta3 without many problems with the exception of one I already posted about here.http://forum.linuxmce.org/index.php?topic=3890.0  and this one.

I followed the instruction on the Known issues page and ran the pre-upgrade.sh and post-upgrade.sh scripts for asterisk.  Everything appears to be correct due to the presence of my prior phone book, but I can not figure out how to log into check my voicemail via Telecom>My Voicemail on the Admin site.  In previous versions, this would automatically pop up to the user logged in, but since upgrading it asks for Login and password with instructions to use the same as you would use from a phone.

My Mailbox is 301
Password (PIN)

does not work.

I know this is correct, because I am able to change my user PIN without any issues.  I am not exactly sure what login and password it is asking for. 
Anyone else able to log in after upgrading.

Core: Version 710Beta3 amd64

Thanks,
Rob

I am trying to add a firewall rule to forward ports to 8081 as described in http://wiki.linuxmce.org/index.php/Installing_Dansguardian

I do not think the firewall rules are being updated as the page states.

here is the output of iptables -L before and after adding a new rule

Code:

dcerouter_24050:/etc/dansguardian# iptables -L
Chain INPUT (policy DROP)
target     prot opt source               destination
ACCEPT     0    --  anywhere             anywhere
ACCEPT     0    --  anywhere             anywhere            state RELATED,ESTABLISHED
ACCEPT     0    --  anywhere             anywhere            MARK match 0x1
ACCEPT     udp  --  anywhere             anywhere            udp dpt:bootps
ACCEPT     0    --  192.168.80.0/24      anywhere
ACCEPT     udp  --  anywhere             anywhere            udp dpt:iax
ACCEPT     udp  --  anywhere             anywhere            udp dpt:sip
ACCEPT     udp  --  anywhere             anywhere            udp dpt:2000
ACCEPT     tcp  --  anywhere             anywhere            tcp dpt:sieve
ACCEPT     tcp  --  anywhere             anywhere            tcp dpt:9001
ACCEPT     tcp  --  anywhere             anywhere            tcp dpt:9030
ACCEPT     tcp  --  anywhere             anywhere            tcp dpt:www

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination
TCPMSS     tcp  --  anywhere             anywhere            tcp flags:SYN,RST/SYN TCPMSS clamp to PMTU

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

If I manually tell Firefox to use port 8081 at 192.168.80.1 then it correctly blocks unwanted sites. 

Is any one else seeing this and if so is there a simple way to get these to update.  I even did a router reload and although the firewall page has the new rule listed, it is not listed on the iptables -L output.

Thanks,
Rob

Sorry,

I thought the PDF was included with that Download, but on closer look it was not.  I will look for it.  I have seen it I believe on this forum, but one of the links is down. 

Sorry,

Rob

http://wiki.linuxmce.org/index.php/Designer

I did a little more testing and it appears that you do not need to set the broadcast level this command works as well

Code:

/usr/pluto/bin/MessageSend dcerouter -targetType category 1 5 1 809 251 0 9 "TESTING DISPLAY ALERT" 182 15 70 "test"

I do not think this will make much difference, because I do not think you can pass -targetType category either, but at least we now know.

Out of curiosity how are you sending the command via ruby,  I tried to follow the instructions at http://wiki.linuxmce.org/index.php/GSD_Ruby_Interface , but all of the methods I tried were always sent as plain text to the wrong device.

Thanks for the section of source code, I added it to the wiki page.  I wanted to also put a word out for bulek who posted several messages which I tried to consolidate to a single page.

I see you are trying to get the little box in the corner, and not a full page to pop up.

Am I missing something here, why can you not send something like this.

/usr/pluto/bin/MessageSend dcerouter -targetType category -bl 5 1 5 1 809 251 0 9 "TESTING DISPLAY ALERT" 182 15 70 "test"
server= dcerouter
targetType= Category (device category found on template page)
-bl= 5 broadcast level 5 or whole house
Device from= 1 is the core
Device to = 5 (actually device category 5 orbiters)
command 809 with it parameters

I was able to send this to all of my orbiters.  I did not play with the parameters much, but it worked.

I hope this is what you are looking for.
Rob

Take a look at http://wiki.linuxmce.org/index.php/DCE_from_commandline

toward the bottom of the page.

As far as I can tell, the reason for '-1000' is to allow devices to broadcast events to the system as a whole rather than to a specific device, presumably for event-based devices that do not do a specific function. I shall look more into this... -AVJohn.

I put together the MessageSend page, and I have not really ever determined if this is indeed correct, but one can see the use of -1000 and -1001 for device to in MessageSend command through out the code.  It would be nice if we knew which was correct or if both are correct. 

I know this sends a message to every orbiter I have because it is annoying and happened on all my orbiters until I determined how much to tell MythTV to leave open.

Low Disc Space Message ( from DiskSpaceMonitor.sh)  This message is sent when the /home partition is over 95% full to fire event 64.

/usr/pluto/bin/MessageSend $DCERouter 0 -1001 2 64

if you set up the part
 Configuring Firewall to forward to port 8081
you will not need to do anything at the browser

I have mixed windows linux environment and all browsers automatically use dansguardian

thanks
rob

I was able to fix the problem.  It turns out I had a timeout value to high within the conn_.Recv command.  Lower the timeout fixes the problem.  Fires almost immediately.

I have a few loose ends to tie up and I will be posting the Ruby code and a PNP script for LG LCD TV's

Thanks ddamron for the link, it is what pointed me to the timeout value.

I have one question, I hope someone can answer.  the LG returns the following string:

Code:

kf 01 f\r\ne 00 OK0fx\r\n

but when I log the string it puts in the line breaks, I was able to fix the problem by using Regexp.escape, but this returns a string which I am able to log on one line, but the format is off slightly.

Code:

kf\ 01\ f\r\nf\ 00\ OK0fx\r\n

\ in front of spaces.  Obviously this is purely comestic, but I have been searching for a solution.  I hate not being able to figure something out. 

Thanks,
Rob