I have a meshlium lan connected to a wifi base with a USB modem that gives me access to the network. Because the modem is DHCP I use noip to achieve a fixed IP.
Noip communicates with servers using TCP port 8245, so I've redirected all ports on the modem / wifi base to the local ip I've assigned to meshlium (192.168.0.150), but now I feel I must also allow access to meshlium .
I guess I'll have to use iptables to get it, but I would not want to interfere with the current iptables configuration. The configuration is as follows:

Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination
ath0-INBOUND all -- anywhere 10.10.10.0/24
ath0-FORWARD all -- 10.10.10.0/24 anywhere

Chain OUTPUT (policy ACCEPT)
target prot opt source destination

Chain ath0-FORWARD (1 references)
target prot opt source destination
ACCEPT all -- 10.10.10.0/24 anywhere

Chain ath0-INBOUND (1 references)
target prot opt source destination
ACCEPT all -- anywhere 10.10.10.0/24


Could this affect the normal operation of the connection? I commented it because there are times that the USB modem is disconnected from the network completely.

Would it be necessary to modify iptables?

What ports would use meshlium? FTP (20 and 21), SFTP (22), HTTP (80), HTTP ALT (8080), MYSQL (3306), DNS (53) and NOIP (8245)?

You don't have to modify iptables. The only thing you need is to enable port forwarding from your router to meshlium in port 22, if you want to access through ssh.

I have already redirected port 22 to meshlium and I can connect remotely via ssh. But in the syslog I get this :
Can't get our visible IP address from ip1.dynupdate.no-ip.com

Using nmap localhost I achieve a relationship of the PORTS/SERVICES.



I have to open this ports in the router too?

Sorry, the image is too small and I can't see any text. Can you post it larger or the text output?

PORT STATE SERVICE
22/tcp open ssh
53/tcp open domain
80/tcp open http
111/tcp open rpcbind
443/tcp open https
1723/tcp open pptp
2006/tcp open invokator
8080/tcp open http-proxy

It seems that the noip daemon cannot contact with the ip1.dynupdate.no-ip.com address to obtain the actual external ip. Check that you can ping an internet address from meshlium or resolve the name:

hello,

I installed noip2 and it`s worked.

But when I run remount I get this:



What is the function of commands remountw and remount?

what happens if you do not use remounto?

regards

Hi,

This 2 functions make reference to the working mode of the storage system of Meshlium:
- remountrw --> mount in Read and Write mode (to enable writing)
- remountro --> mount in Read Only mode (to disable writing)

It is REALLY important to respect the Meshlium Donnot's:
viewtopic.php?f=4&t=7712

You can read there in point 4 what you must do. If you would switch off Meshlium in R&W mode (or unplug the power wire), the storage system could be damaged. This mistake is not covered by the warranty.

Best regards

ok, I understand the importance of leaving the system in read-only mode.

But then my question is how?.

Because apparently no-ip has something that keeps the system busy and not let me mount it, in read only mode.

Dear otrab, as you understand we can not know exactly the functioning of other software on Meshlium, it's possible that the no-ip daemon keep open some file that does not allow to remount the system read-only mode.

Try restarting Meshlium with the command restart-secure, so the meshlium restart in read only mode and if the daemon and test if no-ip daemon works properly.