I shouldn't email after midnight.
So basically powercode is automatically monitoring that /24 so you want
the CPE radio, and the point to point radios to all be in that same
range. Is that the deal?
If you want that and also want a layer2 tunnel between the LAN ports on
the two routers, then I do believe you'll have to manually add that
tunnel each time rather than having a generic config.
Does powercode only ping monitored devices or does it automatically
discover services on certain ports? Maybe the router can be at the
midpoint like I was saying, but you always put the repeater AP on port
8001, and the repeater station is always on port 8002, etc.....could
powercode be configured to automatically discover and monitor services
on those ports and thus monitor the up/down state of the repeater bridge
thingy-ma-bobbers?
------ Original Message ------
From: "That One Guy /sarcasm" <[email protected]>
To: "[email protected]" <[email protected]>
Sent: 7/20/2016 12:22:14 AM
Subject: Re: [AFMUG] mikrotik repeater point router config
because the layer 2 is on a /24 off the site router that the AP resides
bruh
powercode requires any monored IP to be present in the BMU config
I can add subnets to customer accounts, but thats the only place theyre
listed (powercode is lacking lately)
so it would go back to maintaining a spreadsheet to keep track of small
subnets outside the primary ones since powercode offers no tool to keep
them centrally managed
off each site we keep a 10.2.x.x/24 for cpe radios, each AP gets 60ish
of them (10.2.x.2-10.2-60, 10.2.x.61-120, 10.2.x.12-180... then
10.2.1x.x when we need more for APs x=numeric site ID)
the NAT routers are 10.0.x.2-240 x=numeric site ID
and the publics are a subnetted distribution of our /22 ARIN allocation
DHCP is a requirement because I have to resize the public allocations
based on site demand
Static public are a whole other mess that we only give free to business
rates, residential have to pay 10/month for statics
If powercode actually handled documenting the subnets correctly, it
would probably be awesomer, but it is what it is, crummy since simon
left after killing the guy before him
1. Our AP to the house is all layer 2 (AP-CPE-Repeater AP-Repeater
CPE-remote router)
On Tue, Jul 19, 2016 at 11:01 PM, Adam Moffett <[email protected]>
wrote:
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.
--
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.
