Messages

Changed the script as instructed, seems to have solved my issue.  Using "iptables -t nat -xvnL" without the change, I reading the source as 0.0.0.0/0 when I applied the firewall rule in web admin.  After the change, the source correctly shows the ip I specified under "Limit to IP" when I reapplied the rule.

Thanks for the help!

to clarify my few posts just in case they needed it.

My problem:
Opening ports with an ip specified in Limit to IP failed on beta2 and beta3.  The port would be opened, but it would not be limited to the ip.

My temporary solution:
Keep the port open through the web admin, and limit IP in the ip tables of the pc that receives the forwarding.

Late reply, but to permanently add the type, I think these instructions work:
http://forum.linuxmce.org/index.php?topic=3307.msg17474#msg17474

So I'm on beta3 32bit now, and it still seems to not "limit to ip" on the ip i specify.  I think I'm going to opt to stop forwarding ports for now.  For the record, it should be possible to block all traffic on an open port except for an ip I specify correct?  I'd rather not leave threat filtering up to my novice ability at administering a private svn server with apache if I have a choice to do it through the firewall menu.

iptables -L output (with ports forwarded):

Code Select Expand

Chain INPUT (policy DROP)
target     prot opt source               destination         
ACCEPT     0    --  anywhere             anywhere           
ACCEPT     0    --  anywhere             anywhere   
ACCEPT     0    --  anywhere             anywhere   
ACCEPT     udp  --  anywhere             anywhere   
ACCEPT     0    --  192.168.80.0/24      anywhere           
ACCEPT     udp  --  anywhere             anywhere   
ACCEPT     udp  --  anywhere             anywhere   
ACCEPT     udp  --  anywhere             anywhere   
ACCEPT     tcp  --  anywhere             anywhere   

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination         
TCPMSS     tcp  --  anywhere             anywhere

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

I'm on beta2 right now (going to 3 in short order).  But I was curious as to what this option does.  The wiki says : You can limit rules to specific ip addresses.

My goal is to forward one port as securely as possible - I'd like to limit access to one specific IP address if possible.  I figured that the "Limit to IP" was the way to do that, so I specified it as the target ip.  With it set I was still able to see the port as open from IPs that weren't specified. ( www.grc.com ). 

Am I misunderstanding that option's purpose or do I have something misconfigured?

I'm still working on it, just want to report that my issue most likely had nothing to do with my MD being 64bit and that the mce_usb2 should 'just work'.

Somewhere in the rebuilding image process, it configured my mce_usb2 reciever before it went for my bluetooth dongle.  The result was a working mce_usb2 remote+receiver and a bluetooth dongle giving me nearly the same error as I was getting previously, with the black screen of "some devices didn't startup correctly".  Now I'm looking into trying to clear out whatever conflict these two devices have with eachother that only let's one get through the setup process with the other failing.

Now either just do a reload router or if that does not get the remote working then reboot the MD and it will be!

Sorry, tried to imply that I had gotten to that through the forum search so you didn't have to repost.  Tried and failed following those steps more than a few times.  This doesn't bode well for my system... Where does one go after the tried and true method fails?  Anyway, I see that niz23 says he had this issue with beta1.  If I remember correctly, the short period that beta-1 was available, it was only in 64 bit form.  Could the fact that my MD configured under Architecture: amd64 be a problem?  How would I force it to go 32 bit instead?

Screenshot of web admin: http://www.easyscreens.info/?v=1992 .

totallymaxed.

Just installed beta2 and I can confirm that Windows MCE Remote now work.

How did you get the your mce remote working?  I'm having a hard time getting mine going.  Have an mce_usb2 receiver with the xp media center RC-6 remote.  Upon plugging the reciever into the MD, I get the "detected" message.  It then attempts to configure/install the device, but fails with a message along the lines of "Failed to get dce lirc wrapper" "Install failed".  Log in the manager says: "Not starting device 68 mce_usb2 - binary is not found, probably it is in the middle of installing..." (not sure which log to look at to get the full message).

How would I go about setting it up in the beta?  I've taken a long series of steps across various tutorials and forum posts here and there, and have failed for the most part.   Tried all variations of totallymaxed's steps in: http://forum.linuxmce.org/index.php?topic=3539.0 and I end up with the same result.  I've gotten irw registering button presses etc... just can't seem to get LMCE to configure it properly.