--- In firstname.lastname@example.org
, Rod Whitby <rod@...> wrote:
> Patrick Sansoucy wrote:
> > Well,
> > Wow, I did not think I would have started such a thread ...
> > Anyway, the goal I wanted to achieve with the slug was this:
> > My router only does simple port fowarding (no port changing) and I
> > wanted to use my slug a dispatcher behind my router in order to avoid
> > changing ports on my devices on my internal network.
> > I went with OpenWRT since it provided a nice web interface.
> > So just asking to clarify my 'need' would have been simpler than all
> > of this 'flaming' of sort. English is not my native tongue, so Im
> > doing my best in order to make myself as clear as possible.
> I don't think anyone was flaming you. I'm very sure your English is
> infinitely better than me trying to speak your native tongue :-)
> What you are trying to do is an advanced feature of openwrt, and you may
> need to understand iptables to do it. So your original question did not
> have a simple answer, and it wasn't until you gave more information (or
> make some guesses at the required scenario) that we could start to help.
> My comment about the quality of the question was a reminder to everyone
> to give as much contextual information as possible when asking questions
> - this will help to ensure you get the best quality responses.
> BTW, there should be nothing that is NSLU2-specific about how you
> achieve this result. Just think of it as a single-interface Linux
> 184.108.40.206 desktop server with iptables support, and any information you
> find about how to port forwarding on a single-interface desktop linux
> box will apply equally to the NSLU2.
> -- Rod
Maybe it's the lack of sleep of the last few days that's kicking in a
Well, since the firmware provided a means to do this, I was wondering
what was wrong. Also I read some contradictory info on if it was
possible or not (with a single port). As I can see, it is possible,
but the ui is useless AFAIK. Guess I'll go the manual way ...
Thanks for the help