Oh wait, you wanted monitoing and mangement access. Make an exception
in the NAT rule.
/ip firewall nat add chain=srcnat src-address=192.168.1.0/24
dst-address-list !=monitoring action=masquerade
/ip firewall address-list add list=monitoring address=<powercode>
/ip firewall address-list add list=monitoring address=<your office>
/ip firewall address-list add list=monitoring address=<your house>
/ip firewall address-list add list=monitoring address=<my house>
/ip firewall address-list add list=monitoring address=<your mom's house>
------ Original Message ------
From: "Adam Moffett" <[email protected]>
To: [email protected]
Sent: 7/19/2016 11:50:36 PM
Subject: Re: [AFMUG] mikrotik repeater point router config
IDK bruh
Why not make the barn mikrotik an ordinary NAT router and make the one
at the house just an AP/Bridge? No fancy stuff required.
A. What problems am I creating?
B. if a customer wants to add their own device at the midpoint and get
a public IP from our public pool, is there a way to leave a universal
config but allow them to attach that (had considered leaving port 2 in
the WAN so their device could pull DHCP, but then they would plug a
computer in)
C. assuming both routers are mikrotiks, and theyre both DHCP what
would it take to bridge the two LANS (like EOIP) without VLANS since
the repeater radios are vendor agnostic and might not pass it?
D. how do I get the "WAN" bridge to bridge the CPE and the repeater AP
but only pass the MAC of the bridge and not also the physical port?
This is a value add (revenue) and will be a 5-10 dollar charge on top
of a repeater fee so if the absolute only option is some client
specific configuration I wouldnt be completely opposed, but would
prefer at the end of the day to have a default config that will just
work once we get the MACs for DHCP.
--
If you only see yourself as part of the team but you don't see your
team as part of yourself you have already failed as part of the team.
