Switched from Vuma to Openserve - need assistance with port forwarding etc

[rinners]

I have a Mikrotik with SFP port. With Vuma I ditched the CPE media converter and put the fibre straight into the router. No issues, happy days, I think I always had the same IP as well which was nice and no PPPoE.

So in prep for switching to Open serve, I got a patch cable to go from their termination box to the SFP module, connected it all up and no dice, could only get the PPPoE to work with their CPE. Ok whatever, I just left it, but now I am trying to get the port forwarding working, so updated the NAT rules to the PPPoE interface and... 1 52 B packet is all I see. Then I found this:

Issues accessing webpage even with Port Forwarding enabled on PPPoE WAN

I have gone through a bunch of similar questions here and other forums but none of them exactly fit my scenario. I have checked on http://www.whatsmyip.org/ and it reports 103.XXX.YY.ZZ as my IP a...

superuser.com

To the help I would appreciate:

Has anyone done port forwarding on IPv4 through Open Serve? Or IPv6 for that matter?

Is there anyway I can get rid of this stupid CPE? It's a waste of power... or an I stuck with it? Is this something to do with how GPON networks are structured?

 

[Oops!!!]

Has anyone done port forwarding on IPv4 through Open Serve? Or IPv6 for that matter?

I'm running a few forwards on a Openserve/Telkom setup, with Telkom passing through the public IP.

Mikrotik Cloud Enabled>>>services point to the DDNS name>>>DST-NAT rule for each service

i'm assuming with the PPPOE you not double NAT'd and getting a private subnet from the CPE??

 

[rinners]

i'm assuming with the PPPOE you not double NAT'd and getting a private subnet from the CPE??

The router shows IP address (same as when I google 'my IP' 102.x.x.x) and also a Gateway IP address. Not sure where the gateway sits now, that one is a 45.x.x.x

Do you use DDNS because Open serve dishes you a new IP often?

 

[Oops!!!]

The router shows IP address (same as when I google 'my IP' 102.x.x.x) and also a Gateway IP address. Not sure where the gateway sits now, that one is a 45.x.x.x

Are you referring to the local and remote address under PPPoE status?

Do you use DDNS because Open serve dishes you a new IP often?

Not as often as some of the other carriers but enough to be a pain.

Have you logged your NAT activity and seen anything from that DST public IP?

 

[rinners]

Are you referring to the local and remote address under PPPoE status?

Yes, but under the quick set they refer to it as gateway

Have you logged your NAT activity and seen anything from that DST public IP?

Not entirely sure how to do that, but logged the main NAT masquerade rule since you mentioned it. Ticked box in the rule.

 

[Tanka]

Works fine on Openserve with WebAfrica/Afrihost:

Here is my firewall NAT config with two ports being forwarded

/ip firewall nat
add action=masquerade chain=srcnat ipsec-policy=out,none out-interface-list=WAN
add action=dst-nat chain=dstnat dst-port=3478 in-interface-list=WAN protocol=udp to-addresses=192.168.1.111 to-ports=3478
add action=dst-nat chain=dstnat dst-port=8080 in-interface-list=WAN protocol=tcp to-addresses=192.168.1.111 to-ports=8080

 

[Oops!!!]

Yes, but under the quick set they refer to it as gateway

You didn't use quickset to set the router up? Quickset has issue's where it applies rules you can only see if you dump the router configs but cant see in winbox.

Not entirely sure how to do that, but logged the main NAT masquerade rule since you mentioned it. Ticked box in the rule.

This will only log the masq rules.

There is CLI command to log all DST-NAT rules, let me see if i can find it.

 

[rinners]

Works fine on Openserve with WebAfrica/Afrihost:

Here is my firewall NAT config with two ports being forwarded

/ip firewall nat
add action=masquerade chain=srcnat ipsec-policy=out,none out-interface-list=WAN
add action=dst-nat chain=dstnat dst-port=3478 in-interface-list=WAN protocol=udp to-addresses=192.168.1.111 to-ports=3478
add action=dst-nat chain=dstnat dst-port=8080 in-interface-list=WAN protocol=tcp to-addresses=192.168.1.111 to-ports=8080

Thanks. So that's basically what I had with one difference, I used the in-interface not the in-interface-list. It worked fine on VUMA, but now I get 0 traffic. When I set the in-interface to the PPPoE connection I get 52 B or 1 packet (as I do when I set the in-interface-list to WAN), so it's like it's trying, but something is blocking it.

 

[rinners]

You didn't use quickset to set the router up? Quickset has issue's where it applies rules you can only see if you dump the router configs but cant see in winbox.

Oh, ok, that's annoying, I don't recall how I set it up, but I had the same settings from when I was on Vuma. I know I did enter the PPPoE settings into the Quickset though. Maybe it's time for a wipe and a do over just to be sure?