Community discussions

MikroTik App
 
pomah
Frequent Visitor
Frequent Visitor
Topic Author
Posts: 61
Joined: Fri Aug 15, 2014 5:00 pm

portforwarding WAN

Sun Aug 24, 2014 1:20 pm

Hi guys, I'm trying to open up my ports so that I can access my server from outside. I have dynamic IP from my ISP. Any comments on these rules?

The problem atm is that I can not access them from inside or outside.

EDIT: Used this service, http://www.yougetsignal.com/tools/open-ports/, to check if the ports are open, it says they are. But I'm not reaching what I should...
You do not have the required permissions to view the files attached to this post.
Last edited by pomah on Sun Aug 24, 2014 1:22 pm, edited 1 time in total.
 
plisken
Forum Guru
Forum Guru
Posts: 2509
Joined: Sun May 15, 2011 12:24 am
Location: Belgium
Contact:

Re: portforwarding WAN

Sun Aug 24, 2014 1:21 pm

 
pomah
Frequent Visitor
Frequent Visitor
Topic Author
Posts: 61
Joined: Fri Aug 15, 2014 5:00 pm

Re: portforwarding WAN

Sun Aug 24, 2014 8:03 pm

I can access everything from outside now, must have been my dns script that failed, but internal access does not work. I followed the stops in the wiki you sent for hairpin, but it still seems not to work, anything I can upload for you you guys to look at?
 
MikeDavis
just joined
Posts: 8
Joined: Thu May 08, 2014 7:41 am

Re: portforwarding WAN

Thu Aug 28, 2014 3:06 am

Remove in-interface=ether1-gateway from both of yours dst-nat rules:

add action=masquerade chain=srcnat comment="default configuration" out-interface=ether1-gateway
add action=dst-nat chain=dstnat comment=shh dst-address-type=local dst-port=22 protocol=tcp to-addresses=192.168.1.10
add action=dst-nat chain=dstnat comment=Transmission dst-address-type="" dst-port=9091 protocol=tcp to-addresses=192.168.1.11


Then add: (assuming your LAN is 192.168.1.0/24)

add action=masquerade chain=srcnat dst-address=192.168.1.10 dst-port=22 out-interface=bridge-local protocol=tcp src-address=192.168.1.0/24
add action=masquerade chain=srcnat dst-address=192.168.1.11 dst-port=9091 out-interface=bridge-local protocol=tcp src-address=192.168.1.0/24
 
DBob
Frequent Visitor
Frequent Visitor
Posts: 81
Joined: Fri Jun 10, 2011 4:13 pm

Re: portforwarding WAN

Fri Aug 29, 2014 2:23 am

Why is it better to use IP addresses instead of the given interface?
(Assuming that the functionality seems to be the same in the end).
 
ryandenis
newbie
Posts: 31
Joined: Fri Aug 29, 2014 7:40 am

Re: portforwarding WAN

Fri Aug 29, 2014 7:51 am

I have the same exact issue here. the tool listed above http://www.yougetsignal.com/tools/open-ports/ says that my port is open (Port 32400 is open on 68.186.58.237)

But for whatever reason I cannot get the plex cloud to talk to my server. Is there an outbound firewall rule or something else I'm missing?

/ip firewall nat
add action=dst-nat chain=dstnat comment="Thecus Plex" dst-port=32400 in-interface=ether1-gateway protocol=tcp to-addresses=192.168.88.251 \
to-ports=32400
add action=masquerade chain=srcnat comment="default configuration" out-interface=ether1-gateway to-addresses=0.0.0.0
 
ryandenis
newbie
Posts: 31
Joined: Fri Aug 29, 2014 7:40 am

Re: portforwarding WAN

Fri Aug 29, 2014 8:43 am

I'm having the same issue. I used the same website as the person above and verified that the port was open, I can get my plex server to start to load from the outside world however it just hangs once the gui loads up. I think it has something to do with a firewall rule or outbound rule or something? its connecting inbound but like its not talking outbound.... thoughts?



/ip firewall nat
add action=dst-nat chain=dstnat comment="Thecus Plex" dst-port=32400 in-interface=ether1-gateway protocol=tcp to-addresses=192.168.88.251 \
to-ports=32400
add action=masquerade chain=srcnat comment="default configuration" out-interface=ether1-gateway to-addresses=0.0.0.0
 
nerden
just joined
Posts: 2
Joined: Sat Dec 27, 2014 6:51 pm

Re: portforwarding WAN

Sat Dec 27, 2014 7:11 pm

I have been fighting with this for the last two days, and think I have read all the posts on this forum relating to Plex and UPnP,
After a lot of tinkering there I found two fixes;

1)Use UPnP, several other poeple have not had issues when using UPnP, it just worked for them, i had to manually specify the information for my external interface:
/ip upnp
set enabled=yes
/ip upnp interfaces
add interface=bridge type=internal
add forced-external-ip=85.96.108.209 interface=ether1-gateway type=external

2) Rather than using UPNP, manually create a DNAT tranlation, it looks a bit different from the other translations i have used but seems to work.
(Basically this was in the list of NAT translations when I had it setup with UPnP, so I removed the automatic config and the UPnp settings and created it manually, you will need to specify the port number from the Plex config page (Server>Connect>Port)
/ip firewall nat
add action=dst-nat chain=dstnat comment=PLEX dst-address=\
86.27.67.17 dst-port=32400 protocol=tcp to-addresses=192.168.100.10
to-ports=32400

Hopefully that will save someone two days of frustration in future
-Aids

Who is online

Users browsing this forum: Google [Bot], Maajed, MarkusT and 48 guests