Drop the out interface, that's you problem.

Josh Luthman
Office: 937-552-2340
Direct: 937-552-2343
1100 Wayne St
Suite 1337
Troy, OH 45373
On Mar 6, 2015 9:28 AM, "David" <[email protected]> wrote:

>  What about?
> /ip firewall nat
> add action-masquerade chain=srcnat out-interface=Public_ip_interface
>
> On 03/05/2015 09:25 PM, Josh Luthman wrote:
>
> No, just
>
>  /ip firewall nat
>
> add action=masquerade chain=srcnat src-address=192.168.2.0/24
>
>
>  Josh Luthman
> Office: 937-552-2340
> Direct: 937-552-2343
> 1100 Wayne St
> Suite 1337
> Troy, OH 45373
>
> On Thu, Mar 5, 2015 at 10:23 PM, Gabriel Pike <[email protected]>
> wrote:
>
>>  What Josh is saying is to create srcnat rules that equal your dstnat
>> rules eg.
>>
>>
>>
>> /ip firewall nat
>>
>> add action=masquerade chain=srcnat dst-port=CLIENT_DVR_PORT src-address=
>> 192.168.2.0/24
>>
>>
>>
>>
>>
>>
>>
>> Regards,
>>
>>
>>
>> Gabriel Pike
>>
>> Network Support and Engineering
>>
>> MTCNA
>>
>> DMCI Broadband, LLC <http://dmcibb.net/>
>>
>> [email protected]
>>
>>
>>
>> 877.936.2422
>>
>> Ext. 103
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *From:* Af [mailto:[email protected]] *On Behalf Of *Josh Luthman
>> *Sent:* Thursday, March 05, 2015 9:57 PM
>> *To:* [email protected]
>> *Subject:* Re: [AFMUG] Mikrotik Dst-nat question
>>
>>
>>
>> Ya I see what you're saying.  That's why I suggested that answer.  That
>> way you can still type in the public IP.
>>
>>
>>
>>
>> Josh Luthman
>> Office: 937-552-2340
>> Direct: 937-552-2343
>> 1100 Wayne St
>> Suite 1337
>> Troy, OH 45373
>>
>>
>>
>> On Thu, Mar 5, 2015 at 9:46 PM, Mark - Myakka Technologies <
>> [email protected]> wrote:
>>
>> Josh,
>>
>> Let me clarify
>>
>> When the customer is not home and is on a public network he will
>> access his DVR via the public IP address 199.47.xxx.yyy.  This works
>> fine.
>>
>> However, if he tries to access the public IP address while he is at
>> home, we have an issue.  It doesn't work.  He needs to access the DVR
>> via the local address 192.168.2.137.
>>
>> In most cases this is fine if the device lives in just one space such
>> as a desktop.  It gets annoying when the device moves from space to
>> space such as cell phone.  Yes, I can put two entries in the DVR APP.
>>  But that seems like rigging it to the normal user.
>>
>> I would like to a nat, netmap, etc.  When the user acesses
>> 199.47.xxx.yyy from his private 192.168.2.0/24 network, it actually
>> will access 192.168.2.137 on the private network.
>>
>> Ideas?
>>
>>
>> --
>> Best regards,
>>  Mark                            mailto:[email protected]
>>
>> Myakka Technologies, Inc.
>> www.MyakkaTech.com
>>
>> Proud Sponsor of the Myakka City Relay For Life
>> http://www.RelayForLife.org/MyakkaCityFL
>>
>> Please Donate at
>> http://main.acsevents.org/site/TR/RelayForLife/RFLFY12FL?team_id=1030009&pg=team&fr_id=37555
>> ------
>>
>> Thursday, March 5, 2015, 5:53:18 PM, you wrote:
>>
>> JL> Masquerade the local traffic.ᅵ Jobs done.
>>
>> JL> Josh Luthman
>> JL> Office: 937-552-2340
>> JL> Direct: 937-552-2343
>> JL> 1100 Wayne St
>> JL> Suite 1337
>> JL> Troy, OH 45373
>>
>> JL> On Mar 5, 2015 5:41 PM, "Mark - Myakka Technologies" <[email protected]>
>> wrote:
>> JL> I have a customer with a DVR, so we do the port forwarding thing in
>> JL> mikrotik and they can now access the DVR from the Internet all is
>> JL> good.
>>
>> JL> However, I want to do some type of re-direct on the internal network
>> JL> so they can use the public IP on the internal network to access the
>> JL> DVR.
>>
>> JL> This is what I tried?
>>
>> JL> 1ᅵ ᅵ ;;; DVR TCP External Access (works fine)
>> JL> ᅵ ᅵ ᅵ chain=dstnat action=dst-nat to-addresses=192.168.2.137
>> protocol=tcp
>> JL> ᅵ ᅵ ᅵ in-interface=ether1 dst-port=8080,554,8000 log=no
>> log-prefix=""
>>
>> JL> ᅵ2 Xᅵ ;;; DVR TCP Internal Access (Not Working)
>> JL> ᅵ ᅵ ᅵ chain=dstnat action=netmap to-addresses=192.168.2.137
>> protocol=tcp
>> JL> ᅵ ᅵ ᅵ dst-address=199.47.xxx.yyy in-interface=Local
>> dst-port=8080,554,8000
>> JL> ᅵ ᅵ ᅵ log=no log-prefix=""
>>
>> JL> Tried both netmap and dst-nat on line 2 with no luck
>>
>>
>>
>>
>>
>>
>> JL> --
>> JL> Thanks,
>> JL> ᅵMarkᅵ ᅵ ᅵ ᅵ ᅵ ᅵ ᅵ ᅵ ᅵ ᅵ ᅵ ᅵ ᅵ mailto:
>> [email protected]
>>
>> JL> Myakka Technologies, Inc.
>> JL> www.MyakkaTech.com
>>
>> JL> Proud Sponsor of the Myakka City Relay For Life
>> JL> http://www.RelayForLife.org/MyakkaCityFL
>>
>> JL> Please Donate at
>> JL> https://secure.acsevents.org/site/Donation2?df_id=1011305
>> JL> PROXY_ID=1645865 PROXY_TYPE=22 FR_ID=57644
>>
>>
>> JL> ---
>> JL> This email is free from viruses and malware because avast!
>> JL> Antivirus protection is active.
>> JL> http://www.avast.com
>>
>>
>>
>>
>>
>>
>>
>>
>> ---
>> This email is free from viruses and malware because avast! Antivirus
>> protection is active.
>> http://www.avast.com
>>
>>
>>
>
>
>

Reply via email to