Thanks for the very good points, it didn't occur to me that having an extra, hardwired dd-wrt device behind the adsl router would be more than beneficial but obviously it does and it will be a lifesaver for sure.
I did run for some time a test setup with a gateway behind an adsl router with port forwarding etc and I must say that the OM1P never died on me requiring a hard reboot, but that was a test setup without any real traffic/clients.
Sadly I can't really do much on the adsl router with incoming internet connection because that device belongs to someone else who is willing to share the connection as they hardly use it, but if I can convince the owner "he won't feel a thing" I will swap it with a dd-wrt adsl device as that makes much, much more sense
This mesh isn't going to be a big production, but mainly a setup that will be used for +- 2 months by some people, but it's a long way from where I am and on-site there's no-one there who can do much more than just power cycle a node.
Do you advise to put the gateway/mesh network behind the dd-wrt, or put the dd-wrt & the gateway/mesh on the 192.* network directly behind the adsl router?
I'm using what came installed on the OM1P's which is r2694-26/nO 0.5.6-r8.
If I want to open/close the ssh port on the adsl router would that mean I have to expose the admin/config page for that router on the wan side to make the open/close change each time I have to ssh to a node or is there another option?
I don't have much say in what type of internet connection is provided, it'll be "as-is" and I'm expecting it won't be much (telefonica/spain).
But, for a next project I'm asked to do in a few months I'll be setting up a real 24/7 production network in a small hostel, and there I'm able to exactly specify what type of adsl & subscription options are required, a static IP and an entry point adsl router running dd-wrt with openVPN seems to be the very basic of what a remote mesh needs.