Community discussions

MikroTik App
 
Spartacus
Member Candidate
Member Candidate
Topic Author
Posts: 132
Joined: Thu Apr 19, 2018 6:38 pm

Issue with NAT and internal Subnets

Thu Aug 09, 2018 3:39 pm

Hi,
I have several internal subnets with WAN Access and the following NAT-Rule:
add action=masquerade chain=srcnat comment="masquerade LAN->WAN" out-interface-list=WAN
Internet works for all VLAN Subnets, but I have an issue with Multicast Routing within my subnets. If I disable the NAT Rule (only for test purposes), everything works! So I think, I have to exclude all internal Subnes from SrcNat. But I am struggling with the configuration. All attempts failed! I have a dynamic WAN IP from ISP.

Can someone help me to change my NAT rule?
Thanks,
Christian
 
User avatar
Anumrak
Forum Guru
Forum Guru
Posts: 1180
Joined: Fri Jul 28, 2017 2:53 pm

Re: Issue with NAT and internal Subnets

Thu Aug 09, 2018 3:50 pm

Does interface list "WAN" contains only your ISPs interfaces?
 
Spartacus
Member Candidate
Member Candidate
Topic Author
Posts: 132
Joined: Thu Apr 19, 2018 6:38 pm

Re: Issue with NAT and internal Subnets

Thu Aug 09, 2018 3:53 pm

Hi,
yes, it is ether1 (WAN)
Christian
 
User avatar
Anumrak
Forum Guru
Forum Guru
Posts: 1180
Joined: Fri Jul 28, 2017 2:53 pm

Re: Issue with NAT and internal Subnets

Thu Aug 09, 2018 4:00 pm

What ROS and firmware version do you use?
 
Spartacus
Member Candidate
Member Candidate
Topic Author
Posts: 132
Joined: Thu Apr 19, 2018 6:38 pm

Re: Issue with NAT and internal Subnets

Thu Aug 09, 2018 4:38 pm

Hi,
I use 6.42.6 and FW3.41 on RB3011
Christian
 
proximus
Member Candidate
Member Candidate
Posts: 114
Joined: Tue Oct 04, 2011 1:46 pm

Re: Issue with NAT and internal Subnets

Thu Aug 09, 2018 6:15 pm

Given the issue as you describe it, give this a try ....
add action=masquerade chain=srcnat comment="masquerade LAN->WAN" out-interface-list=WAN src-address-type=!multicast 
 
Spartacus
Member Candidate
Member Candidate
Topic Author
Posts: 132
Joined: Thu Apr 19, 2018 6:38 pm

Re: Issue with NAT and internal Subnets

Thu Aug 09, 2018 6:47 pm

Hi,
thanks for the modification of the NAT-Rule, but it is not working!

Let me try to explain the whole story. Maybe some has an idea:
I have Sonos palyers on vlan30 and controller on vlan10 and vlan60 (interface-list "Sonos Control"). PIM is working and I implemented the following FW-rules:
add action=accept chain=forward comment="SONOS: forward Multicast traffic" \
    dst-address=239.255.255.250
add action=accept chain=forward comment=\
    "SONOS: forward  Controller events to Players" dst-port=1400,4444,4070 \
    in-interface-list="Sonos Control" out-interface=vlan30 protocol=tcp
add action=accept chain=forward comment=\
    "SONOS: Forward Contoller events  from Players" dst-port=\
    3400,3401,3500,4070 in-interface=vlan30 out-interface-list=\
    "Sonos Control" protocol=tcp
add action=accept chain=forward comment=\
    "SONOS. Forward UPnP Device Discovery events from Players" dst-port=\
    1900,1901,5353,6969 in-interface=vlan30 out-interface-list=\
    "Sonos Control" protocol=udp
Sonos works across different subnets as long as player and controller were initially setup in the same subnet.

This means:
My issue is only present for initial player/controller setup, although all relevant ports are free (checked with Sonos support). I cannot connect new players/controllers to the Sonos system if player and controller are in different subnets.

Workaround:
bring new player/controller to vlan30 (Sonos SubNet), temporary!

But:
If I disable the NAT Rule (see above) I can connect new devices accross the subnets and I do not understand why this is the case!
This must have something to do with the NAT-Rule

Christian

Who is online

Users browsing this forum: mistyrhythm and 54 guests