Quote:
Originally Posted by Matth
http://www.pcpro.co.uk/reviews/secur...tek-vigor-2955 - seems to be a fairly competent unit.
How CAN you forward a port to different IPs, how would it kow which one it was meant for.
To support a port forwarded service that may operate from different systems (but only one at a time), you need to use port triggering, where a certain condition that results from using the application (eg. outgoing on a known port), can be set to trigger forwarding of the required incoming port(s) while that condition is met
|
It's not forwarding a port TO different IP addresses, rather it's forwarding ports FROM different IP addresses. We have a small block of 15 IP's and it could just be me making a mistake, but it seems that when I forward a port from IP x.x.x.2, I can't then forward the same port from x.x.x.3. Or rather, I can and the interface doesn't give me any issues, but the port doesn't actually forward. Again, it could just be me, the Drayek interface isn't the clearest thing in the world (and it's not the worst, either).
Quote:
Originally Posted by qasdfdsaq
Historically for myself and where I've worked we've always had bespoke solutions because we've always had highly qualified dedicated network teams to look after them.
Given Openwrt is infinitely flexible and runs on literally hundreds of different devices it all boils down to your required specifications and needs.
How many ports? How many downstream devices? What sort of load, traffic, security, is required, etc. What level of resiliency or redundancy do you need?
|
"Highly Qualified" isn't a term I'd apply to my network skills. Give me a low level API or a programming task and I'm your guy, but networking? That's just the part time job :P
Anyway, it's not a massive deal, I was just putting the feelers out in case we could have been doing it better. Most people seem to think the Draytek should be good enough, so I'll persevere with it and see what happens.