rcplay / snake-os

Automatically exported from code.google.com/p/snake-os
1 stars 0 forks source link

Can't use services from WAN #103

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
Hi friends,

I upgraded my ns-k330 to snakeos latest version and everything seems to work 
fine when I access the services from my lan, but all becomes unaccessible when 
i try to access it through my ip address over the internet.

Let me make it clear: i use a router here, an d-link di-524, i defined on dhcp 
the nas as 192.168.0.166, i put this address in DMZ, i created also rules on 
the firewall to redirect from external port 9000 to internal 192.168.0.166:80, 
and external port 9001 to 192.168.0.166:21, but the services never respond. 
When i create rules on the router to any other device on the network it always 
works, they all respond, it's just the nas that fails, but inside the lan it 
works perfectly.

Is it possible that snakeos is refusing wan connections by some reason? Any 
idea of how to fix it?

Thanks folks.

Original issue reported on code.google.com by alexkarc...@gmail.com on 4 Dec 2010 at 5:31

GoogleCodeExporter commented 8 years ago
keep in mind u must use the dynamic dns service to access it over the internet.
Enable DDNS: selected
DDNS Provider: dyndns.org
DDNS Alias: xxx.dynalias.com
DDNS Username:  username
DDNS Password:  ********
DDNS status:    DDNS is running
that means u also have to signup an account at dyndns.org, using the manage 
domain and set it to ur ip, then u can access it at the subdomain u registered 
there. IP are dynamic (in major cases).

Original comment by ted.cho...@gmail.com on 4 Dec 2010 at 7:12

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
Thanks for the answer,

But in fact, i'm using an ddns service, provided by no-ip, and i've checked 
that the ip address has been updated correctly. As I said, i'm not getting 
access just when the router aims the nas, when i set the router to point to any 
other device inside the network it works fine, so the problem happens when 
accessing the nas from the wan, once from the lan it works fine. I've tested 
with online port checkers, if i open a port that aims my laptop on the lan it 
works and the port checker shows it's open, but when i do the same for the nas, 
it shows the door is closed, and yes, i'm sure the services are running well 
and i target to the right doors.
It's being very hard to understand this behavior, working fine on the lan, not 
working over internet access, but only the nas, the dhcp settings are ok, can 
it be related to the dns settings, once i set it to be done automatically my 
the router?

Original comment by alexkarc...@gmail.com on 4 Dec 2010 at 4:08

GoogleCodeExporter commented 8 years ago
You try to use DHCP server from your router. Select DHCP from the NAS nor fix 
ip. Then forward 9000 TCP and UDP to your NAS:80.
Also , you can check the Router LED is flashing or not when access the NAS from 
internet

Original comment by ray.ray...@gmail.com on 7 Dec 2010 at 5:51

GoogleCodeExporter commented 8 years ago
Try not to configure port forwarding and DMZ at the same time..
Try to configure either one or the other, and see what you get.

I had the same problem but because I have a phone adapter sitting before the 
router, and the ISP tech support couldn't configure it to run the router as 
DMZ. So I moved it to be part of the lan instead, so now my router is the 
access point and it's port forwarding works.

Original comment by mike.kol...@gmail.com on 3 Jan 2011 at 7:37