remote access to router and nas - Page 1
Forum section: electronics / general

author: Simon
author_rank: Unknown
timestamp: April 13, 2013, 12:56:28 pm
content: I am finding it impossible to firstly setup my NAS for external use.I'm now trying to setup a USB drive attached to my router as if that will work the nas probably will and I'm only trouble shooting 1 peice of equipment.The router manual tells me to put in my router IP address to access it from the net. Surely it is not that simple ? I'm on shared IP's from my ISP and it's dynamic. To set it static i need to set a DNS server. What am i missing ? do i need to put my router under a domain name etc. or something like that ?

author: ecat
author_rank: Frequent Contributor
timestamp: April 13, 2013, 01:11:52 pm
content: Generally you want to use Port forwarding...http://en.wikipedia.org/wiki/Port_forwardingHow To:http://www.wikihow.com/Set-Up-Port-Forwarding-on-a-RouterThe links explain things better than I can.The big issue is security. As soon as you open a port to the public internet you WILL have hundreds of random folk and bots probing and possibly trying to hack into your link.I'm not saying don't do it, I'm just saying think about your data and ALL of the the rest of the network local to your public device.

author: Simon
author_rank: Unknown
timestamp: April 13, 2013, 01:24:52 pm
content: I've setup port forwarding but it won't work, how do I find my router on all of the internet (particularly if it keeps changing IP) surely the xxx.xxx.xxx.xxx number format is not capable of listing every router and server on the net (basically my router now has server status ?)

author: ecat
author_rank: Frequent Contributor
timestamp: April 13, 2013, 01:43:00 pm
content: http://www.whatismyip.com/should show your current external IP address.Many times 'dynamic' addresses don't actually change all that often, still you want to check outhttp://www.noip.com/,http://dyn.com/dns/and probably a host of other similar services. It is possibly your router has a setting allowing you to link directly to one of these services.Important:For testing you do of course need some sort of external connection. A mobile smart phone is a good place to start. Trying to access your own external ports from within your own local network does not always work and certainly may not test the actual external connection... this may depend upon the router.

author: F4CPY
author_rank: Contributor
timestamp: April 13, 2013, 03:33:54 pm
content: @simon: missed something, is your router is also your ISP modem? because you'll have to open/forward ports also on it.Is your configuration is:Modem--->Router+switch-->Nas ; PC... ?Didier

author: Simon
author_rank: Unknown
timestamp: April 13, 2013, 03:40:30 pm
content: No my router and modem are seperate, yes i see your point, if I visit my nas URL from inside I hit the modem, if I try to visit from the outside I hit a blank wall.

author: temet
author_rank: Newbie
timestamp: April 13, 2013, 03:43:36 pm
content: To easily access a NAS over the internet you would need a static IP address which you have to buy from your ISP, then use whatever software to access it.

author: ecat
author_rank: Frequent Contributor
timestamp: April 13, 2013, 04:12:23 pm
content: Quote from: Simon on April 13, 2013, 03:40:30 pmStrictly speaking, you do not have a modem. The box that connects to the telephone line/ cable is a router. Theexternalconnection (telephone/cable) is part of your ISP's network, it should have an IP address and this should be the address you see usinghttp://www.whatismyip.com/. Theinternalconnection of this box is part of your local network.Starting with the box that has the external connection, is it configured to allow external access?Edit:Perhaps you could draw a picture of your configuration... Make and model numbers could help too

author: nerdyHippy
author_rank: Contributor
timestamp: April 13, 2013, 04:28:43 pm
content: Quote from: temet on April 13, 2013, 03:43:36 pmThat's not really true. There are dynamic DNS services that will give you a proper URL that can be continually updated to point to your non-static IP address. I'd recommendafraid.org. If you have port forwarding set up properly you should then be able to connect to your NAS via the URL given to you by afraid or whomever.

author: temet
author_rank: Newbie
timestamp: April 13, 2013, 04:36:25 pm
content: cool, but how does the service know what your IP address is going to change to?Do you have you update it manually? That would be fine for some small applications I guess.Quote from: nerdyHippy on April 13, 2013, 04:28:43 pm

author: madires
author_rank: Super Contributor
timestamp: April 13, 2013, 04:51:08 pm
content: Quote from: Simon on April 13, 2013, 12:56:28 pmYou need a DynDNS service, e.g. dyndns.org. If you're lucky your router or NAS supports DynDNS directly. But it's not very reliable, but better than nothing :-)

author: 4to20Milliamps
author_rank: Regular Contributor
timestamp: April 13, 2013, 04:56:52 pm
content: Have you considered setting up a vpn?http://lifehacker.com/5487500/five-best-vpn-toolshttp://lifehacker.com/201786/geek-to-live--create-your-own-virtual-private-network-with-hamachihttp://openvpn.net/index.php/access-server/docs/videos.html

author: AlfBaz
author_rank: Super Contributor
timestamp: April 13, 2013, 05:04:45 pm
content: Don't you have to find out the IP address of your NAS on your local network then ad that to the routers DMZ, thereby exposing it to external internet traffic?

author: kxenos
author_rank: Frequent Contributor
timestamp: April 13, 2013, 05:40:09 pm
content: As others said, go to the DDNS tab in your router's web interface. Check the supported services. Select a service provider, i.e. no-ip and create an account by them. Create a new host and set the current IP address. Then in your router's configuration, provide the no-ip or dyndns user/pass. This will solve the IP issue. Then port forward your server port like Outside port:8080, inside port:8080, inside ip:Your device's IP, save, reboot, done

author: temet
author_rank: Newbie
timestamp: April 13, 2013, 05:50:44 pm
content: Routers have installed routing protocols that know where all network nodes are and then traffic any external traffic filtered through port forwarding to them quite easily. so that is not a problem.Quote from: AlfBaz on April 13, 2013, 05:04:45 pm

author: Simon
author_rank: Unknown
timestamp: April 13, 2013, 09:33:06 pm
content: Quote from: AlfBaz on April 13, 2013, 05:04:45 pmdone that, port forwarding is setup, the problem is that the modem needs opening.My setup is phone line into modem, modem to so called cable router and the nas is plugged into the router and my pc is on wireless.

author: Simon
author_rank: Unknown
timestamp: April 13, 2013, 09:35:07 pm
content: Quote from: temet on April 13, 2013, 05:50:44 pmyes the nas comes with software that essentially is doing what you do with sites like no-ip you create an account with LG and they handle it for the NAS

author: TerraHertz
author_rank: Super Contributor
timestamp: April 13, 2013, 11:24:17 pm
content: The root of the problem is that ISPs do not 'advertise' individual IP addresses from their pool, to the global DNS root servers. So no backbone router in the global net (including ones in your own city) know how to reach that IP address.Also often the WAN port IP address your cable modem or whatever is saying it shows to your ISP, won't be the IP address that external machines (outside your ISP) see as your accessible IP address.When you start a session of some kind from your PC (eg web browsing) your request packets contain your 'contact address' (in layers), and the reply packets find you that way. But if some outside machine wants to initiate an exchange with your home machine, it can't - doesn't know your IP address, and neither does whatever DNS server it's asking.So as people have suggested, the only ways to achieve what you want are to either subscribe to an independent service that uses some special communication with your machine to maintain knowledge of your current IP in the ISP's dynamic pool, OR, to pay your ISP for a static IP address. Which they also then add to the IP lists that they advertise to the global DNS servers.There's an economic factor here - ISPs don't really like people being able to run Internet servers of any kind, since they tend to increase the ISPs overall 'outflow' traffic (which increases their backbone usage costs) and also more heavily loads shared bandwidth infrastructure such as the street cables in the case of cable internet. In the case of cable, I'm pretty sure the infrastructure just flatly cannot bear the upgoing bandwidth that would result from many subscribers running servers.That's why you don't have free fixed (and advertised) IP addresses as part of the typical account with an ISP.

author: Simon
author_rank: Unknown
timestamp: April 14, 2013, 08:04:01 am
content: well my modem definitly has an option to "Assign the public IP address of a connection to a LAN device" to allow incoming connections. As I said above the software and service provided by LG is basically a free DNS service that keeps track of the NAS, this seems to be working because if i type "myname".lgnas.com I end up in my modem as that is as far as I can come as the modem is bocking access.Most ISP's limit uploading traffic anyway, I know mine will be pityfully slow (something like 700KB/s or Kb can't remember) but I'd be able to access stuff at least

author: Simon
author_rank: Unknown
timestamp: April 14, 2013, 08:12:47 am
content: what I need to establish now is what sort of security I need to setup and do i need to put any extra in. Like I think on routers you have a default local user and password that are week as you can only use them locally but you can also access them remotely but need more secure logins but that might be only for getting into the router settings and no just for going through it onto the network.I'll open the modem up this afternoon, see what happens

author: amspire
author_rank: Super Contributor
timestamp: April 14, 2013, 08:26:43 am
content: You usually don't want to share your drives to the whole internet. Never forward the drive ports to the internet via the router. Anyone connecting could have full read/write/delete access and your drive will be discovered by hackers.+I would recommend OpenVPN or one of the alternative VPN's if you are connecting from your notebook, tablet or phone. This gives you a direct access to your files, but no-one else can connect. You will still need to forward the VPN port to the router, and once you are connected via VPN, you will basically be a local PC on your home network. OpenVPN is a bit of a pain to get started, but it is great once it is working.The advice about the IP's is correct. If your are connecting to your host with a fix IP address, then you can find out what is it and use the IP number directly, or use one of the dynamic DNS services that will track the currently assigned IP address of your home router. This works as long as your host is assigning a public IP. Some hosts may connect users by a private network, and that makes life a lot harder.If the NAS supports OpenVPN, I may be able to give you some settings that will work. What is the type of NAS?Probably a simpler solution is that your NAS probably supports SSH access and perhaps SCP. If it does, you can run WinSCP from a remote PC can connect to your NAS drives. You will have to forward port 22 from the NAS to the Internet. If you do make sure you pick a good password (absolute minimum of 10 characters and if you use names or dictionary words, the password probably needs to be more like 20 characters).Richard.

author: Psi
author_rank: Super Contributor
timestamp: April 14, 2013, 08:37:58 am
content: A while back i was using this configuration.- A standard linux box on the home LAN with SSH setup (don't use root, create a proper account).- The home router setup to give a static IP to my linux box. (based on it's MAC address)- The home router setup to port forwarded the SSH port (22) to my linux box.- A free dynamic dns address setup usingwww.noip.comand the linux app installed so it automatically updates the IP if it changes. (if you want to do this google "ubuntu How to install No-IP Linux Dynamic Update Client")With those things done I can do quite a bit of remote access tasks.I can;- Get any directory on the linux box to appear as a drive letter on a remote PC using the windows sshfs program. (it allows you to mount a drive letter over a typical ssh shell)- Use "Putty" to tunnel any LAN ip/port to my remote PC. (So i can access the routers webgui setup page or VNC running on other PCs etc..All of that is pretty straightforward and doesn't take much linux knowledge.

author: babysitter
author_rank: Frequent Contributor
timestamp: April 14, 2013, 09:47:29 am
content: Unfortunately you didn`t share the model and the software you are using, right ?You better look in the right user manuals and google for your router model, together with the keywords "port forwarding", "exposed host" or the wrongly named "DMZ" by yourself. All will ask for the internal IP adress of the host which shall be available from the outside, e.g. your NAS. The first one will selectively expose certain services and asks for either services or protocols. Cheat sheet: Expose 80 for a webserver or 21 for a ftp server.The other two will summon the full force of evil internet users on all ports of the host.Get a appropriate server running on the host, like filezilla for ftp, or what is shipped with the host (A NAS will already contain several servers to select from.)Intermediate test: Use a "what is my ip" service (hint: internet forum software often shows which IP it will log!) and ask a friendly guy to try to access the server(s) at your public IP address.This already means your NAS is available to the internet.Then, set up a dynamic dns account and use the adequate integrated software on the NAS or a client program on another PC to publish the IP to the dynamic dns service.The friendly guy can check if the IP is accurate, by accessing your exposed server using the name provided by the dynamic dns, like myexposednas.dynamicdnsservice.org.Safety: Make your NAS use login credentials and dont let an anonymous user in.Pro safety: Google for openvpn, your router and your NAS model, and use prot forwarding only providing the openvpn port (1194 i think) to the internet. OpenVPN is another server which only accepts people with login data and "mirrors" their computer into your internal network. To enter this internal network, a virtual networking device will be created on the clients PC.Further help you would immediately get in internet forums which are directly related to your router/NAS.Good luck

author: madires
author_rank: Super Contributor
timestamp: April 14, 2013, 11:42:23 am
content: This might become a little bit off topic but some professional touch is required here :-)Quote from: TerraHertz on April 13, 2013, 11:24:17 pmISPs don't advertise IP addresses or subnets to root name servers. They advertise subnets (i.e. their allocations and maybe PI space of customers) via dynamic routing protocols like BGP to other ISPs or networks. DNS is just like a telephone book, has nothing to do with routing. Every router needs to know how to reach the users IP address, otherwise the Internet would not be able to work. That might be just a default route for a dump router or a full BGP routing table for a backbone router.QuoteWhen the ISP uses private IP addresses with NAT or CGN internally to save public address space then the user got bad luck. In that case one should consider a server somewhere in the cloud (=fixed IP address). Store data directly on that server or setup something like ssh port forwarding back home.

author: Simon
author_rank: Unknown
timestamp: April 14, 2013, 12:29:36 pm
content: My router is a WNDR3400 the nas is an LG N1T3

author: ecat
author_rank: Frequent Contributor
timestamp: April 14, 2013, 01:31:17 pm
content: WNDR3400 Which version, V1 or V2 or V3? May not matter but we may as well know.So, it looks like this?http://www.broadbandbuyer.co.uk/Shop/ShopDetail.asp?ProductID=10543Half way down that page is a picture of the back of the device. How do you have it connected to your modem (1) ?If your modem is connected to the Yellow port, looking at page 1-7 of the WNDR3400v1 Setup Manual, what values do have in the Basic Setting screen (Figure 1-6) ?(1) Looks like the entire world uses the name modem, oh well.

author: Simon
author_rank: Unknown
timestamp: April 14, 2013, 01:45:07 pm
content: Yes it's that one.My basic settings are that I don't need an ISP login (well my modem is probably doing that) and it is on dynamic IP addresses which are automatically set.

author: ecat
author_rank: Frequent Contributor
timestamp: April 14, 2013, 02:04:00 pm
content: Quote from: Simon on April 14, 2013, 08:04:01 amSo, if you enable the Assign option in the modem the IP address of the Yellow port (the external side of your router) should be the same as your public IP address.

author: madires
author_rank: Super Contributor
timestamp: April 14, 2013, 02:05:30 pm
content: Quote from: Simon on April 14, 2013, 01:45:07 pmDHCP is a common setup for cable providers. Please check if the WAN IP address your router got is a private or public one. If it's a private one port forwarding wouldn't work (assuming the cable provider doesn't run 1:1 SNAT).

author: Simon
author_rank: Unknown
timestamp: April 14, 2013, 02:18:44 pm
content: there is no WAN address given, there is a defaultg DMZ address of 10.0.0.0 that is not enabled. Everything on the inside has a 10.0.0.x address

author: Simon
author_rank: Unknown
timestamp: April 14, 2013, 02:21:18 pm
content: I'm starting to think the firewall in the modem is blocking connections but i can't see any way of disabling it, I'm guessing that the router will have a firewall that will deal with it.

author: madires
author_rank: Super Contributor
timestamp: April 14, 2013, 02:28:44 pm
content: Quote from: Simon on April 14, 2013, 02:18:44 pmDoes the status page tell you anything about the WAN status? Most SOHO routers display the WAN details like IP adddress, gateway and nameserver (obtained via PPPoE or DHCP in your case).

author: ecat
author_rank: Frequent Contributor
timestamp: April 14, 2013, 02:31:04 pm
content: Also,What make/model is the modem?

author: Simon
author_rank: Unknown
timestamp: April 14, 2013, 02:34:59 pm
content: Quote from: madires on April 14, 2013, 02:28:44 pmI just activated the DMZ address and after the modem updated tried to outside url for my nas, I go a page up that didn't tell me much but that I'm sure is drom the NAS so I go through. I'll retry the setup for the nas see if that fixes it

author: Simon
author_rank: Unknown
timestamp: April 14, 2013, 02:51:04 pm
content: I think i might have figured what I'm doing wrong. I've setup all of the port forwards but used the NAS IP address do i need to use the router (DMZ) address ?

author: madires
author_rank: Super Contributor
timestamp: April 14, 2013, 03:06:54 pm
content: Quote from: Simon on April 14, 2013, 02:34:59 pmPlease select "Advanced", "Administration" and then "Router Status". At the top right you should see "Internet Port" with the details. Netgear managed to hide the good stuff :-)

author: madires
author_rank: Super Contributor
timestamp: April 14, 2013, 03:13:41 pm
content: Quote from: Simon on April 14, 2013, 02:51:04 pmDo you mean the "Default DMZ Server"? If you enable that all incoming traffic (not linked to any established outgoing connection) will be forwarded to that server, security-wise a really bad idea.

author: Simon
author_rank: Unknown
timestamp: April 14, 2013, 03:15:16 pm
content: It got me into my NAS, seems to be what actually allows the router to handle ins/outs

author: Simon
author_rank: Unknown
timestamp: April 14, 2013, 03:24:54 pm
content: Quote from: madires on April 14, 2013, 03:06:54 pmCan't find that menu. But if you want the internet port number I'll take a look. It seems my router is rejecting requests from my modem, I have looked at the router log and there are a load of so called DoS attacks, putting in the IP address the attack came from gets me into my modem, so I'm guessing my modem is not being allowed in which is kind of a deal breaker

author: madires
author_rank: Super Contributor
timestamp: April 14, 2013, 03:30:09 pm
content: Quote from: Simon on April 14, 2013, 03:24:54 pmJust like to know the WAN IP address. I downloaded the manual for N600 Wireless Dual Band Router WNDR3400v2, maybe you got v1.

author: mrflibble
author_rank: Super Contributor
timestamp: April 14, 2013, 03:35:53 pm
content: Quote from: TerraHertz on April 13, 2013, 11:24:17 pmEhr, wut? O_oDNS entries have nothing to do with being able to do routing your packets. Sure, you (the client) have to know the ip address, and if you want to that using a hostname a dns lookup would indeed be handy.But if you happen to know the ip address then who the hell cares about DNS. Those backbone routers on the global net will reach that IP address just fine.Maybe you meant to say this, but it's not what you actually said...In any event you can use dyndns or whatever is hip these days if you want to have an actual hostname. Or the cheapo trick used way back before there was such a thing as dyndns is to have a little script running server side. Your server checks if it's internet facing IP address has changed since last check. If yes, send an email to your favorite mailbox. And yes, put a rate limiter on it.That also works just fine since update rate will be on the order of 1/day max anyways.But some randomly chosen free dynamic dns service will probably do the trick just fine.

author: mrflibble
author_rank: Super Contributor
timestamp: April 14, 2013, 03:37:37 pm
content: Quote from: madires on April 14, 2013, 11:42:23 amRight, I see you already responded to that one. Sorry for the duplication. That'll teach me to read the entire thread first.

author: ecat
author_rank: Frequent Contributor
timestamp: April 14, 2013, 03:55:40 pm
content: Quote from: Simon on April 14, 2013, 03:24:54 pmA quick read of the internet suggests the DoS attack messages can be mostly ignored.

author: madires
author_rank: Super Contributor
timestamp: April 14, 2013, 03:56:39 pm
content: Quote from: Simon on April 14, 2013, 03:24:54 pmOk, for v1 it's "Maintenance", "Router Status" and then see section "Internet Port".

author: Simon
author_rank: Unknown
timestamp: April 14, 2013, 04:05:44 pm
content: Great now my computer and nas box have swapped IP addresses as i rebooted the lot to see if that help !!!! I'm getting sick of this !

author: ecat
author_rank: Frequent Contributor
timestamp: April 14, 2013, 04:18:40 pm
content: lolDHCP is a brilliant idea, except when it works against you. Look at the current IP address of your NAS (or pick some other address if you must) then go the NAS configuration, disable DHCP and use a fixed IP address and whatever it is you use for the subnet mask.Edit:If the subnet mask is not obvious in the NAS or router config pages you can get it from windows "Network and Sharing Centre"->"Local Area Connection"->Details.

author: madires
author_rank: Super Contributor
timestamp: April 14, 2013, 04:30:22 pm
content: Quote from: Simon on April 14, 2013, 04:05:44 pmDHCP client enabled on the NAS? oops :-) Set a fixed IP address outside the local DHCP range. If required make the DHCP pool on the router smaller.

author: mrflibble
author_rank: Super Contributor
timestamp: April 14, 2013, 04:38:06 pm
content: *grin* Multiple dhcp servers is always fun! That's always step 1 when I get some new goodie ... disable DHCP. And step 2 is disable wifi.

author: madires
author_rank: Super Contributor
timestamp: April 14, 2013, 04:45:32 pm
content: Quote from: mrflibble on April 14, 2013, 04:38:06 pmIn this case we're hunting down the NAS :-) But multiple DHCP servers would be also quite entertaining. ;-)

author: nerdyHippy
author_rank: Contributor
timestamp: April 14, 2013, 05:03:31 pm
content: You can change it manually, but generally it's easier to run a daemon to do it automatically. Many routers have such functionality built in, or you can run a small application on computer to do the same.Quote from: temet on April 13, 2013, 04:36:25 pm

author: mrflibble
author_rank: Super Contributor
timestamp: April 14, 2013, 05:20:49 pm
content: Quote from: madires on April 14, 2013, 04:45:32 pmI noticed that. Buuuuut, if he gets conflicting IPs then there is more than 1 dhcp server handing out leases. Or maybe he just means his clients (nas box being one of them) got new IPs handed to them and he was assuming things about what the ip would be.Hunting down the nas should be trivial. rarping the MAC.Or if you don't have that, then broadcast ping and then do a regular arping for all the responding ip. Or arping the entire dhcp range (probably 128 or so anyways). Or ... *gasp* use the admin interface or something. But that could potentially mean physically walking to the box. WAY too much effort.Anyways, the answer has already been given. Put your nas on a static IP. Which is what you want anyways if you want to config port forwarding on your adsl router.And seeing all the confuzlement here... Put NAS on static IP. Put ADSL router on whatever (you probably don't have an option from your ISP anyways to choose between dynamic internet facing IP or static). On the adsl router setup portforwarding for your favorite external port on adsl router to your nice and static internal NAS ip:port. Then setup one of many free dynamic dns services. Done.

author: mrflibble
author_rank: Super Contributor
timestamp: April 14, 2013, 05:24:09 pm
content: Forgot to add .. if you really really want to export your NAS over the big bad internet I suggest you use SSL if your NAS supports it. If not, do something like an openssl tunnel or ssh tunnel to some intermediate on your network. The ssh tunnel being easier to config. Or if you don't care about your nas content, just spam it over the internet in the clear. XD

author: Simon
author_rank: Unknown
timestamp: April 14, 2013, 05:26:49 pm
content: I fixed the NAS IP from the nas menu so that is the end of that one.

author: Simon
author_rank: Unknown
timestamp: April 14, 2013, 06:11:08 pm
content: I'm trying to work out how to use no-ip, it looks like most commercial scumbags they just advertise a free baseline service and then make it impossible to find.I guess i should set my router up as DNS so that I can to it from the outside, at the moment that is the stumbling block.

author: ecat
author_rank: Frequent Contributor
timestamp: April 14, 2013, 06:14:53 pm
content: Quote from: Simon on April 13, 2013, 09:35:07 pm

author: Simon
author_rank: Unknown
timestamp: April 14, 2013, 06:20:24 pm
content: and said software is piss poor which is why I'm here now

author: mrflibble
author_rank: Super Contributor
timestamp: April 14, 2013, 08:12:44 pm
content: Quote from: Simon on April 14, 2013, 06:11:08 pmO_oAnd how is that going to help you from finding out your dynamic IP? As in you are at work, don't have your home ip written down somewhere and/or your isp just assigned you a different IP. You have "your router set up as DNS" (which usually just means your router is a forwarder for dns requests from your LAN), and then what?I guess you should just try a little harder to find a free dynamic dns provider. There are still bound to be a few, but can't be bothered to filter through the list. That's your job.Or as I mentioned earlier on ... if you have a server somewhere in the network, you can send yourself an e-mail whenever you detect an IP change. Or the ever popular way of trying to make sure your isp doesn't change IPs on you ... make a permanent connection to some box somewhere. For example ssh/vpn/whatever to your work, and then ping or some other keepalive every once in a while. That usually works.Or just get dynamic dns to work.

author: casper.bang
author_rank: Frequent Contributor
timestamp: April 14, 2013, 08:28:00 pm
content: Quote from: madires on April 14, 2013, 04:30:22 pmRather than limiting the range of the DHCP, it's often beneficial to go DHCP over the full 254 spectrum and simply assign a static lease via MAC address of the client devices (NAS) NIC. This makes the physical infrastructure mapping strictly a job for the router, rather than splitting the responsibility between the router and client (I.e. hooking the NAS up to another network or with a crossed cable is handy in a debugging scenario without you having to mess with the static IP you might not even be able to get to due to the NAS being on a different subnet etc.).

author: Simon
author_rank: Unknown
timestamp: April 14, 2013, 08:31:44 pm
content: I've set the IP of the nas from the nas's own web interface and disabled DCHP so I won't have that problem again. The problem is that the software provided by LG is shit and has virtually no instructions so I'm haing to play networking expert to make everything talk manually.

author: nerdyHippy
author_rank: Contributor
timestamp: April 15, 2013, 08:32:15 am
content: Quote from: mrflibble on April 14, 2013, 08:12:44 pmI can't discern what Simon's issue is at this point, but I'll reiterate my fondness forafraid.org. It's free, stable, community-run, and a zillion other positive adjectives.

author: RickieSalad
author_rank: Regular Contributor
timestamp: April 15, 2013, 09:32:25 am
content: I assume you're trying to connect to the routers built in webpage from the outside world? If that's the case your router's internal webserver that serves that page is either serving it on port 80(http) or port 443 (https),probably 80. Well unless you're paying for some sort of business class of internet service, every ISP I've ever heard of blocks common server ports like port 80, so you can't host a web server from your bedroom and gobble up bandwidth. So unless you changed the port forward so that you're hitting a different port from the outside then the most likely reason you aren't getting anything is that you're trying to make an http(80) connection from the ouside which is blocked by the ISP.Setup your port forward so that the "external port" is something else that isn't a common server port, like 80, 443, 21, 23, etc. Pick something off the wall like 1000. Set your "external port" to 1000, your "internal port" to 80, and the "internal IP address" to the router you're trying to hit. Save all that, reboot the router if you have to. Find out your external IP(whatismyip.com). Say your IP is 1.2.3.4 Then from a webbrowser,or smartphone or whatever, put in 1.2.3.4:1000. by putting in the :1000 you're telling the browser not to default to port 80 but to specifically connect via port 1000 in this case.So when you put that in your webbrowser, your webbrowser hits your external IP, the modem, at port 1000(or whatever you choose) which the ISP doesn't block. Then your port forward sends that request over to the internal IP at port 80.Once you get that to work, then you can move on to thinking about DDNS type settings to keep your dynamically assigned ISP IP up to date. All the DDNS stuff is moot though if you can't connect via an IP address first.

author: madires
author_rank: Super Contributor
timestamp: April 15, 2013, 12:40:59 pm
content: Quote from: casper.bang on April 14, 2013, 08:28:00 pmYou can do that too but it will create new problems. If the router fails DHCP also fails. Maybe the network is larger and there's an additional switch or you would connect the laptop back to back to the NAS to get the important data you need. In the first case you could increase the lease timeout to mitigate the situation as long as the NAS or the PCs aren't rebooted. In the latter case the lease would be dropped by the DHCP client because the ethernet link is lost (router's dead). In both cases it's easy to set a fixed IP address on a PC/laptop to access the NAS, but not so easy to set a fixed IP address on the NAS. Another problem is a firmware update. A lot of SOHO routers reset their configuration while updating the firmware to prevent any trouble with mismatching configurations (poor design). So you would have to re-enter the static leases.

author: madires
author_rank: Super Contributor
timestamp: April 15, 2013, 12:49:27 pm
content: Quote from: RickieSalad on April 15, 2013, 09:32:25 amFirst we should find out if he has got a dedicated public IP address, since he's a customer of a cable company. Some are using private IP address space inside their network and just dNATting at the edges. And with CGN there will be even more fun (we need IPv6 very badly!!!).

author: RickieSalad
author_rank: Regular Contributor
timestamp: April 15, 2013, 01:06:36 pm
content: Quote from: madires on April 15, 2013, 12:49:27 pmHe's just got to goto whatismyip.com. If it's not one of the following then he's good.10.0.0.0 to 10.255.255.255172.16.0.0 to 172.31.255.255192.168.0.0 to 192.168.255.255

author: madires
author_rank: Super Contributor
timestamp: April 15, 2013, 01:18:52 pm
content: Quote from: RickieSalad on April 15, 2013, 01:06:36 pmI think I should place ahere :-) whatismyip.com will show the public IP address. Maybe it's a dedicated one, maybe it's one from a NAT pool. Only your local router can tell you that.

author: RickieSalad
author_rank: Regular Contributor
timestamp: April 15, 2013, 11:48:05 pm
content: Quote from: madires on April 15, 2013, 01:18:52 pmYeah, yeah you're right. I guess I've always had public IP's from all my ISP's so I wasn't thinking of that clearly. I don't think I've ever known anyone who got a NAT'ed IP from their ISP. And of course if I've never seen it then it doesn't exist. Hahaha

author: SeanB
author_rank: Super Contributor
timestamp: April 16, 2013, 04:15:51 pm
content: Use mobile data and you will have NAT.

author: madires
author_rank: Super Contributor
timestamp: April 16, 2013, 05:25:59 pm
content: Quote from: RickieSalad on April 15, 2013, 11:48:05 pmI've seen (also done :-) tons of strange and weird stuff, like public IP addresses NATed to other public IP addresses. Might seem to be braindead at first sight but if you know the network design it makes perfectly sense.

author: mrflibble
author_rank: Super Contributor
timestamp: April 16, 2013, 06:53:08 pm
content: Quote from: madires on April 16, 2013, 05:25:59 pmI know of a few large & expensive companies who shall remain nameless that did precisely that.And the way they implemented it actually was braindead at 2nd sight as well. XD But I agree that it can be useful if used to solve the correct class of problem. The instances I am thinking of caused more problems than it solved... I suspect that it started out as a good design, and then historical growth happened (typically after the original architect has left the company for years).