Port Forwarding - Belkin Router

[Andeh13]

I am trying to open a port as per link below, for my new Buffalo NAS> I have entered everything as they say but when I hit ''apply changes'' I get the below error message:

''The XXX you entered in invalid.
where xxx is the ''port number'' or ''address'' depending on the context''

I need Port 9000 open for remote access to the NAS. Can anyone advice?

cheers

edit: I get the error message even when I try to apply one of Belkin's pre-setup port forwarding options.

[watercooled]

Could you post a screenshot of the page with the information entered?

[Splash]

..and also details of the model?

[Andeh13]

Sorry guys, realised I posted little information in use! It is a Belkin F5D8235-4 for future reference.

I managed to sort the problem through entering 0 into the end of the IP address range they offered me. Weird none of their default inputs had this, but it seems to have worked. Can anyone explain why this IP address is relevant, and whether putting the IP address fully as 192.168.2.*0* is relevant?

Screenshot:
http://foscam.us/blog/wp-content/upl...3.22.56-AM.png

Instructions/Port forwarding I require:
http://portforward.com/english/route...XE4.0TL-R5.htm

Cheers

[watercooled]

You mean the port range? If that's the case, if you only want to forward one port, type the same number in both boxes if it won't accept a blank box.

Edit: If you mean, why is the IP address necessary - it's where you're forwarding the port *to* i.e. the IP address of your NAS, which will need to be set static.

[b0redom]

As an aside, port forwarding to a NAS (or anything else really) direct from the Internet is a really bad idea. You'd be better off using something like SSH/VPN or whatever to encrypt and secure incoming traffic.

[peterb]

The last number in the IP address should be the IP address of the NAS, port forwarding to a range doesn't really make sense.

As an aside, port forwarding to a NAS (or anything else really) direct from the Internet is a really bad idea. You'd be better off using something like SSH/VPN or whatever to encrypt and secure incoming traffic.

Very true! I use SSH with public/private key authentication. So I forward port 22 to my server, but only machines with my private key can connect (you need to configure SSH accordingly) and well worth doing - port 22 (and others) are probed pretty much constantly. I also use fail2ban to lock out IP addresses that attack port22 (and other ports I have open for various reasons) for a lengthy period.

[b0redom]

You mean port 22 right? 21 is ftp? I personally do that too, but run SSH on a non-standard port. Sure it's not infallible, but it probably means they'll target someone else. Someone with non-encrypted standard ports open their NAS for example

[watercooled]

OpenVPN's tls-auth option is an interesting security feature too. Packets which don't authenticate correctly (which needs a shared key) don't even get acknowledged.

Off on a bit of a tangent to the OP there, sorry.

[peterb]

You mean port 22 right? 21 is ftp? I personally do that too, but run SSH on a non-standard port. Sure it's not infallible, but it probably means they'll target someone else. Someone with non-encrypted standard ports open their NAS for example

FTFY! (Yes, meant 22 )