Got meself a brand new Orcon connection and went to configure port-forwarding on the NF4V as the connection goes live tomorrow.

Hmm. Can not port-forward (virtual servers the nF4v calls 'em) to a subnet that is different to the modem lan subnet, despite adding previously in a static route in the NF4V for that internal range. Modem just states there was an error adding the entry.

Despite most of our calls being to the handheld head warmers, the real power in the household has decreed we need a real phone line so I can't ditch the NF4V.

Port forwarding is also rather useful for me and my internal network has a few VLANs in order to keep the fandamnily away from my work gear, etc.

I'd REALLY prefer not to have to collapse internal vlans and the associated ip readdressing.

It MAY be that because the wan connection is not yet live that port-forwarding can not be configured. (Hoping this is the case but if not I'll be internet-less tomorrow and the afore-mentioned fandamnily will start to get ornery and I really don't want that)!

Anyone done this before or have any ideas?