En zo zou die rubriek met technische gegevens ook kunnen aangevuld worden naar mate en aan de hand van vragen die op dit forum gesteld worden. If you own a BT Home Hub, you may need to configure Port Forwarding to allow external services to make a connection through your forewall. On this page, we explain. Hi all, I have the Home Hub 2000 over fiber (Bell Fibe). I am trying to configure the modem with my DynDNS to remotely access my NAS and PC. The range thing is for some applications which require more than one port. Most DVRs have a web interface for viewing the video streams, normally on port 80. Features The BT Home Hub interface is refreshingly clean and simple, as the router doesn't have that many advanced options. You get the basic options, such as port. Any experiences with Draytek 2820Vn and BT infinity? and is there a PDF config manual for the HH5 anywhere?
PODCAST FEATURE: The 'Unofficial Guide to the Home Hub' is a free downloadable audio file, helping with many setup and config issues. Listen to the show online, or. INTRODUCTION. What is NAT Loopback and why is it needed to host a public Opensimulator Region? Currently (as at August 2010), a hosted region on a home connection.
Port Forwarding for CCTV - WTF - Page 1 - Computers, Gadgets & Stuff. The range thing is for some applications which require more than one port. Most DVRs have a web interface for viewing the video streams, normally on port 8. So you need to forward port 8.
- View and Download D-Link DES-1228/ME user manual online. Managed 10/100Mbps Metro Ethernet Switch. DES-1228/ME Switch pdf manual download.
- View and Download Synology DS411slim manual online. DiskStation DS411slim. NAS, DLNA, RAID. DS411slim pdf manual download.
IP address of your DVR. Then when you go to http: //your. DVR. If you need to find your external IP: http: //www. From a quick google for forwarding port 8. Go to Settings - > Advanced Settings - > Port Forwarding - > Supported Applications. Add a new game or application" (don't copy anything from the past) and in my example let's call it Synology although the name really does not matter. To keep things really clean, for ports which need to be open, just use either TCP or UDP.
Don't use the "Any" option. For example, if you want to forward port 8. TCP, select the following: Protocol = TCPPort Range = 8. Translate = 8. 0 to 8. Continue to follow this step until you have put in place all the firewall rules you require. For Synology, this is likely to be quite a number of ports running across both TCP and UDP protocols.
Remember the golden rule not to open more ports than you need as each opening represents a theoretical security risk. When finished hit "Apply". Go to Settings - > Advanced Settings - > Port Forwarding - > Configuration. Select the 'Application' you created in the step before from the Application drop down list and then under device select the bottom option of 'User Defined IP Address'.
Select this and enter the IP address of the device you setup in Step 2/3, where X = the number between 1 and 6.
Bell Home Hub 2. 00. Dyn. DNS. I don't know your equipment, but in general terms it's a matter of design ethos. Think of the firewall in your router as having two "interfaces" one internal and one external. In normal operation there's no reason why traffic addressed to the external interface should arrive at the internal interface. So many firewall designs regard this as suspect and drop it. In big corporate type environments we "fix" this problem by arranging for DNS to resolve names differently for internal devices and external ones. Let's use an example and say I've built something called widget.
IP address 1. 72. IP address 1. 2. 3. Externally we arrange for DNS to resolve widget.
Dyn. DNS.) But for devices connected to the internal network, I use a different DNS server (my own internal one) and arrange for that to resolve widget. Thence our internal traffic never reaches the router and trips up at the firewall. SOHO LAN's one often doesn't have an internal DNS server, so one can't use this trick. If you are lucky your router might include a DNS proxy that will let you override the DNS resolutions for certain names or even do it for you automatically. I've seen some SOHO routers that offer this, but many don't. Have a look in it's manual and see if it lets you do anything with DNS.
If not, then there's not much you can do about it unless you want to create your own DNS (which is a bit of a waste for this one issue.) You could create some local overides on the client devices (if they will let you - I suspect a lot of modern kit such as phones and tablets won't.) However, that would then "go wrong" and not work when you are outside your local network (which presumably is the point of doing this.)The simplest workaround is to just not use the Dyn. DNS name when you are working locally and use the internal IP addresses instead. So in my example above, I'll use 1. I'm elsewhere. In terms of securing your NAS, then it's basically about only opening (port forwarding) the ports you need to and ensuring that access requires a credentials exchange.
So whenever anyone connects they are required to provide a logonid and password before access is granted. It's normally in the gift of the NAS as to whether it avails such, not something you "add on" somewhere else. If you're uber paranoid you could use protocols that encrypt the data in flight. So, https instead of http and SFTP instead of FTP. A lot of network admins have a bit of a downer on FTP and only allow it if it's web browser based. Again, you'd need to look to your NAS to see what it offers. Personally I would never expose any file sharing protocols (CIFS/SMB, NFS, etc.) and want everything browser based and protected by credentials.
And of course, one ensures we have backups of the data in case the worst happens. But then I get paid to be paranoid about such things and others are more relaxed about it.