Sounds like you've now worked this out, but for clarity and future reference - all your equipment related to LMCE should be on the internal LMCE network as that is the whole point of that network. Trying to hook it in from the external network will work with appropriate firewall rules, etc, but you need to be conscious that this is not how it was designed to work, so you can expect unexpected behaviour
well I know, in the current situation I cannot let the dcerouter be The router (it's in our bedroom and network need to be up 24/7) but when we move to the house
Also the problem actually did not seem to be related to the routing but something else. As I found the user was not set. (otherwise I would not have posted actually)
Thanks. I opened these ports as well but there must be something else missing as well since startup takes along time(click start orbiter,black screen with pointer,wait 10-20s, now the progress bar shows up)
Will do some more tcpdump:s to see what packages get's lost.
I don't expect you to troubleshoot this(since I am not connected the way supposed to), hence the non-informative info that it dies sometimes. The main problem is solved with the user config. I beleive the "dying" is due to routing issues, not with the orbiter sw.
If you however would still like to know what happens for future reference maybe. I can do as much logging as you want me to.
Since it does actually work _pretty_ well outside of the FW.
For other people who may want to do the same(knowing what you're doing is off course very good)
I also opened these ports(only my orbiter should be able to access these ports from outside):
3451(configured to be the default listening port of the orbiter)
With these ports it works but as I said there are some other ports missing since it seem to loose connection while looking at a movie for example and shuts down(like the dcerouter stops talking due to high proc load) But I find that not so likely.(haven't hade the time to loook into that more)
also when starting the orbiter, it sometimes gets stuck in the pink "prompt_user_window" and then dies..
I assume this is because the orbiter is still beleived to be active(?) by the Core..Orbiter on the Inside Lan(the way it should be):
I had a few minutes alone in the network today and changed the netw topology abit. The dce router became The router connected directly to my isp and on the internal Lan I had the wlan router routing the traffic for all the other computers(wired and wireless)
Hmm.. need to dig into dns config since dns lookup took very long time and the dns config sent out to th computers where the dcerouter itself and that seemed to have small issues resolving the names with the help from the isp dns:s..
But Wow! the Orbiter became much faster(menu loading) and I actually saw these _sometimes_ annoing popups about added bluetooth yada yada
Had some issues with the startup still, but there where a too short testperiod to say anything.
Really missing tschak909's exit button though.. will try to do what he did but that can wait since compiling sounds difficult
Also sometimes wish I had some equipment from work at home since then the FW config would be a piece of cake (Checkpoint NGX on ipso) don't like leaving the dcerouter directly conn. to the "big evil" internet
You guys Rock!