Re: [AFMUG] powercode and mikrotik BMUs

[Steve Jones]

These guys worked through the shitshow, identified the root issue, we were
able to replicate the issue, patched it, verified the patch resolved it. It
did all root in v18, should probably eol it. This weekends issue i suspect
revolved around having a mikrotik present in a v18 to v19 migration. Proper
documentation would have eliminated the bulk of the complaints. I don't
need as much documentation though, cause packetcaptures pull the entire
process out to a readable form (benefit of the plain text).  Will probably
go away when encryption gets turned on. Whoever it was that said that is
right, you ha e to do something in the mikrotik then they can enable it.

On Mon, Dec 16, 2019, 12:42 PM Steve Jones 
wrote:

> BMU rebuild caused massive phantom usage and kicked non overage customers
> into slow when triggered state. Its happened before enough times that
> customers are testy. Got the usage cleared before billing ran, thank
> jeebus, but the slow when triggered states were still present. Boils down
> to poor planning on my part at the end of the day, with it being a specific
> risk I inquired about, I should have known to disable the notification. As
> a side, if we were a dishonest company, this could have been a great
> revenue generator, customers are still calling in wanting to upgrade
> because their usage went up according to the notification email.
> We are getting it all squared away here in a few minutes though, Ill be
> back to fanboy status when I get my site mikrotiks turned into BMUs as long
> as im still employed through the whole project. This all originated from a
> need to move where NAT took place on the network and save 20 grand on
> buying more IP space, this is my penance for being cheap.
>
> On Mon, Dec 16, 2019 at 12:19 PM Matt Hoppes <
> mattli...@rivervalleyinternet.net> wrote:
>
>> What broke so bad in V19?
>>
>> On Dec 16, 2019, at 1:02 PM, Steve Jones 
>> wrote:
>>
>> Weve had one in play because they dont have any powercode BMUs anymore,
>> we outran the smaller ones capacity. It only did the queues and the
>> redirect. It was the testing on moving them out to sites that pushed this
>> whole issue. We are on V19 now, so the world should be gravy. The migration
>> was pretty much a disaster, more than pretty much, we will probably shed a
>> few customers over it, but thats partially on me. The last major migration,
>> I built up a demo server imported the DB did process testing on a lab
>> network, all that, over the course of like a month. This I pushed out about
>> 16 hours after the decision to migrate was made, bug tested on the fly and
>> got bit. I was pretty confident I was fired when I got in this morning, but
>> I wasnt so we are working through the few remaining bugs and letting
>> bygones be bygones, maybe the boss just doesnt have the heart to can me
>> right before christmas, who knows.
>>
>> Out of curiosity, Josh, what are you doing with your tiks, are they site
>> routers? We currently have pretty vanilla setup on our mikrotiks with two
>> headend BMUs and NAT handled at each of our upstream edge routers. Each POP
>> has a LAN bridge defined for customer traffic with a DHCP relay to old BMUs
>> that handle the DHCP and the monitoring.  OSPF for site to site routing. A
>> default deny input policy with exceptions for certain things and an ACL.
>> some do have multiple LAN bridges if we have a stub site that doesnt have a
>> router at it backhauled in.
>>
>> The only thing aside from moving Queues and whatnot that we want to add
>> at the sites is the NAT to eliminate the BGP limitations it presents when
>> doing it on the border routers. We dont even think we will do the DHCP on
>> these, will just stick to the relay.
>>
>> On Mon, Dec 16, 2019 at 9:29 AM Josh Luthman 
>> wrote:
>>
>>> I didn't even think you could use v18 with Mikrotik.  Definitely not
>>> recommended.  I've been on the latest latest with Mikrotik and it works
>>> well.
>>>
>>> Josh Luthman
>>> Office: 937-552-2340
>>> Direct: 937-552-2343
>>> 1100 Wayne St
>>> Suite 1337
>>> Troy, OH 45373
>>>
>>>
>>> On Sat, Dec 14, 2019 at 10:22 PM Steve Jones 
>>> wrote:
>>>
 When I was a very young man, my uncle's power went out. This, of course
 caused his sump pump to fail. As I was helping him lug out his destroyed
 furniture and carpet from his beautiful finished basement, he would just
 repeat, "if you have a guy down, you might as well kick him" ...ha. I
 understand what uncle Moe meant. He was right.
 Anyhow, turns out v18 did have some fatal issues with mikrotik. Went to
 v19 last night, good times. I would venture a guess that new customers
 could onboard gracefully, lots of better goodness in 19 new customers.

 On Fri, Dec 13, 2019, 10:43 AM Josh Luthman <
 j...@imaginenetworksllc.com> wrote:

> Same as Kurt.  Probes work wonderfully.  Customer radios, tower APs,
> power monitors, all of it.
>
> I talked to Ubnt about that at 

Re: [AFMUG] powercode and mikrotik BMUs

[Steve Jones]

BMU rebuild caused massive phantom usage and kicked non overage customers
into slow when triggered state. Its happened before enough times that
customers are testy. Got the usage cleared before billing ran, thank
jeebus, but the slow when triggered states were still present. Boils down
to poor planning on my part at the end of the day, with it being a specific
risk I inquired about, I should have known to disable the notification. As
a side, if we were a dishonest company, this could have been a great
revenue generator, customers are still calling in wanting to upgrade
because their usage went up according to the notification email.
We are getting it all squared away here in a few minutes though, Ill be
back to fanboy status when I get my site mikrotiks turned into BMUs as long
as im still employed through the whole project. This all originated from a
need to move where NAT took place on the network and save 20 grand on
buying more IP space, this is my penance for being cheap.

On Mon, Dec 16, 2019 at 12:19 PM Matt Hoppes <
mattli...@rivervalleyinternet.net> wrote:

> What broke so bad in V19?
>
> On Dec 16, 2019, at 1:02 PM, Steve Jones 
> wrote:
>
> Weve had one in play because they dont have any powercode BMUs anymore, we
> outran the smaller ones capacity. It only did the queues and the redirect.
> It was the testing on moving them out to sites that pushed this whole
> issue. We are on V19 now, so the world should be gravy. The migration was
> pretty much a disaster, more than pretty much, we will probably shed a few
> customers over it, but thats partially on me. The last major migration, I
> built up a demo server imported the DB did process testing on a lab
> network, all that, over the course of like a month. This I pushed out about
> 16 hours after the decision to migrate was made, bug tested on the fly and
> got bit. I was pretty confident I was fired when I got in this morning, but
> I wasnt so we are working through the few remaining bugs and letting
> bygones be bygones, maybe the boss just doesnt have the heart to can me
> right before christmas, who knows.
>
> Out of curiosity, Josh, what are you doing with your tiks, are they site
> routers? We currently have pretty vanilla setup on our mikrotiks with two
> headend BMUs and NAT handled at each of our upstream edge routers. Each POP
> has a LAN bridge defined for customer traffic with a DHCP relay to old BMUs
> that handle the DHCP and the monitoring.  OSPF for site to site routing. A
> default deny input policy with exceptions for certain things and an ACL.
> some do have multiple LAN bridges if we have a stub site that doesnt have a
> router at it backhauled in.
>
> The only thing aside from moving Queues and whatnot that we want to add at
> the sites is the NAT to eliminate the BGP limitations it presents when
> doing it on the border routers. We dont even think we will do the DHCP on
> these, will just stick to the relay.
>
> On Mon, Dec 16, 2019 at 9:29 AM Josh Luthman 
> wrote:
>
>> I didn't even think you could use v18 with Mikrotik.  Definitely not
>> recommended.  I've been on the latest latest with Mikrotik and it works
>> well.
>>
>> Josh Luthman
>> Office: 937-552-2340
>> Direct: 937-552-2343
>> 1100 Wayne St
>> Suite 1337
>> Troy, OH 45373
>>
>>
>> On Sat, Dec 14, 2019 at 10:22 PM Steve Jones 
>> wrote:
>>
>>> When I was a very young man, my uncle's power went out. This, of course
>>> caused his sump pump to fail. As I was helping him lug out his destroyed
>>> furniture and carpet from his beautiful finished basement, he would just
>>> repeat, "if you have a guy down, you might as well kick him" ...ha. I
>>> understand what uncle Moe meant. He was right.
>>> Anyhow, turns out v18 did have some fatal issues with mikrotik. Went to
>>> v19 last night, good times. I would venture a guess that new customers
>>> could onboard gracefully, lots of better goodness in 19 new customers.
>>>
>>> On Fri, Dec 13, 2019, 10:43 AM Josh Luthman 
>>> wrote:
>>>
 Same as Kurt.  Probes work wonderfully.  Customer radios, tower APs,
 power monitors, all of it.

 I talked to Ubnt about that at Vegas and a couple times since then.
 Tony responds to me and I feel like the devs ignore him just as much as us.

 Josh Luthman
 Office: 937-552-2340
 Direct: 937-552-2343
 1100 Wayne St
 Suite 1337
 Troy, OH 45373


 On Fri, Dec 13, 2019 at 9:51 AM Kurt Fankhauser <
 lists.wavel...@gmail.com> wrote:

> probes been working fine for us in Powercode, the only probe problem i
> have is AF5XHD's oid's are screwed up right now, but thats not a Powercode
> problem.
>
> On Fri, Dec 13, 2019 at 7:38 AM Mike Hammett  wrote:
>
>> I wish billing\oss systems would stop trying to be everything to
>> everybody.
>>
>>
>>
>> -
>> Mike Hammett
>> Intelligent Computing Solutions 
>> 

Re: [AFMUG] powercode and mikrotik BMUs

[Matt Hoppes]

What broke so bad in V19?

> On Dec 16, 2019, at 1:02 PM, Steve Jones  wrote:
> 
> Weve had one in play because they dont have any powercode BMUs anymore, we 
> outran the smaller ones capacity. It only did the queues and the redirect. It 
> was the testing on moving them out to sites that pushed this whole issue. We 
> are on V19 now, so the world should be gravy. The migration was pretty much a 
> disaster, more than pretty much, we will probably shed a few customers over 
> it, but thats partially on me. The last major migration, I built up a demo 
> server imported the DB did process testing on a lab network, all that, over 
> the course of like a month. This I pushed out about 16 hours after the 
> decision to migrate was made, bug tested on the fly and got bit. I was pretty 
> confident I was fired when I got in this morning, but I wasnt so we are 
> working through the few remaining bugs and letting bygones be bygones, maybe 
> the boss just doesnt have the heart to can me right before christmas, who 
> knows.
> 
> Out of curiosity, Josh, what are you doing with your tiks, are they site 
> routers? We currently have pretty vanilla setup on our mikrotiks with two 
> headend BMUs and NAT handled at each of our upstream edge routers. Each POP 
> has a LAN bridge defined for customer traffic with a DHCP relay to old BMUs 
> that handle the DHCP and the monitoring.  OSPF for site to site routing. A 
> default deny input policy with exceptions for certain things and an ACL. some 
> do have multiple LAN bridges if we have a stub site that doesnt have a router 
> at it backhauled in.
> 
> The only thing aside from moving Queues and whatnot that we want to add at 
> the sites is the NAT to eliminate the BGP limitations it presents when doing 
> it on the border routers. We dont even think we will do the DHCP on these, 
> will just stick to the relay.
> 
>> On Mon, Dec 16, 2019 at 9:29 AM Josh Luthman  
>> wrote:
>> I didn't even think you could use v18 with Mikrotik.  Definitely not 
>> recommended.  I've been on the latest latest with Mikrotik and it works well.
>> 
>> Josh Luthman
>> Office: 937-552-2340
>> Direct: 937-552-2343
>> 1100 Wayne St
>> Suite 1337
>> Troy, OH 45373
>> 
>> 
>>> On Sat, Dec 14, 2019 at 10:22 PM Steve Jones  
>>> wrote:
>>> When I was a very young man, my uncle's power went out. This, of course 
>>> caused his sump pump to fail. As I was helping him lug out his destroyed 
>>> furniture and carpet from his beautiful finished basement, he would just 
>>> repeat, "if you have a guy down, you might as well kick him" ...ha. I 
>>> understand what uncle Moe meant. He was right.
>>> Anyhow, turns out v18 did have some fatal issues with mikrotik. Went to v19 
>>> last night, good times. I would venture a guess that new customers could 
>>> onboard gracefully, lots of better goodness in 19 new customers.
>>> 
 On Fri, Dec 13, 2019, 10:43 AM Josh Luthman  
 wrote:
 Same as Kurt.  Probes work wonderfully.  Customer radios, tower APs, power 
 monitors, all of it.
 
 I talked to Ubnt about that at Vegas and a couple times since then.  Tony 
 responds to me and I feel like the devs ignore him just as much as us.
 
 Josh Luthman
 Office: 937-552-2340
 Direct: 937-552-2343
 1100 Wayne St
 Suite 1337
 Troy, OH 45373
 
 
> On Fri, Dec 13, 2019 at 9:51 AM Kurt Fankhauser 
>  wrote:
> probes been working fine for us in Powercode, the only probe problem i 
> have is AF5XHD's oid's are screwed up right now, but thats not a 
> Powercode problem.
> 
>> On Fri, Dec 13, 2019 at 7:38 AM Mike Hammett  wrote:
>> I wish billing\oss systems would stop trying to be everything to 
>> everybody.
>> 
>> 
>> 
>> -
>> Mike Hammett
>> Intelligent Computing Solutions
>> 
>> Midwest Internet Exchange
>> 
>> The Brothers WISP
>> 
>> 
>> 
>> 
>> From: "Steve Jones" 
>> To: "AnimalFarm Microwave Users Group" 
>> Sent: Thursday, December 12, 2019 3:34:13 PM
>> Subject: [AFMUG] powercode and mikrotik BMUs
>> 
>> Powercode has become quite a joke. Half our probes havent worked for 
>> months and they dont even respond to the ticket. We had to spin up 
>> Librenms just to get monitoring data
>> 
>> Trying to integrate mikrotik BMUs and having issues, they have zero 
>> legitimate documentation and when you ask whats supposed to be happening 
>> they tell you to seek out a consultant and that the info may be 
>> proprietary.
>> 
>> Thats all bad enough, but i figure ill do some packet sniffing to find 
>> out what the communication is between the billing server and the 
>> mikrotik, maybe find out I misconfigured something, come to find out the 
>> nitwits are sending out the authentication in PLAIN TEXT. They dont even 
>> have a disclaimer when you add one of these. but christ, if youre 

Re: [AFMUG] powercode and mikrotik BMUs

[Steve Jones]

Weve had one in play because they dont have any powercode BMUs anymore, we
outran the smaller ones capacity. It only did the queues and the redirect.
It was the testing on moving them out to sites that pushed this whole
issue. We are on V19 now, so the world should be gravy. The migration was
pretty much a disaster, more than pretty much, we will probably shed a few
customers over it, but thats partially on me. The last major migration, I
built up a demo server imported the DB did process testing on a lab
network, all that, over the course of like a month. This I pushed out about
16 hours after the decision to migrate was made, bug tested on the fly and
got bit. I was pretty confident I was fired when I got in this morning, but
I wasnt so we are working through the few remaining bugs and letting
bygones be bygones, maybe the boss just doesnt have the heart to can me
right before christmas, who knows.

Out of curiosity, Josh, what are you doing with your tiks, are they site
routers? We currently have pretty vanilla setup on our mikrotiks with two
headend BMUs and NAT handled at each of our upstream edge routers. Each POP
has a LAN bridge defined for customer traffic with a DHCP relay to old BMUs
that handle the DHCP and the monitoring.  OSPF for site to site routing. A
default deny input policy with exceptions for certain things and an ACL.
some do have multiple LAN bridges if we have a stub site that doesnt have a
router at it backhauled in.

The only thing aside from moving Queues and whatnot that we want to add at
the sites is the NAT to eliminate the BGP limitations it presents when
doing it on the border routers. We dont even think we will do the DHCP on
these, will just stick to the relay.

On Mon, Dec 16, 2019 at 9:29 AM Josh Luthman 
wrote:

> I didn't even think you could use v18 with Mikrotik.  Definitely not
> recommended.  I've been on the latest latest with Mikrotik and it works
> well.
>
> Josh Luthman
> Office: 937-552-2340
> Direct: 937-552-2343
> 1100 Wayne St
> Suite 1337
> Troy, OH 45373
>
>
> On Sat, Dec 14, 2019 at 10:22 PM Steve Jones 
> wrote:
>
>> When I was a very young man, my uncle's power went out. This, of course
>> caused his sump pump to fail. As I was helping him lug out his destroyed
>> furniture and carpet from his beautiful finished basement, he would just
>> repeat, "if you have a guy down, you might as well kick him" ...ha. I
>> understand what uncle Moe meant. He was right.
>> Anyhow, turns out v18 did have some fatal issues with mikrotik. Went to
>> v19 last night, good times. I would venture a guess that new customers
>> could onboard gracefully, lots of better goodness in 19 new customers.
>>
>> On Fri, Dec 13, 2019, 10:43 AM Josh Luthman 
>> wrote:
>>
>>> Same as Kurt.  Probes work wonderfully.  Customer radios, tower APs,
>>> power monitors, all of it.
>>>
>>> I talked to Ubnt about that at Vegas and a couple times since then.
>>> Tony responds to me and I feel like the devs ignore him just as much as us.
>>>
>>> Josh Luthman
>>> Office: 937-552-2340
>>> Direct: 937-552-2343
>>> 1100 Wayne St
>>> Suite 1337
>>> Troy, OH 45373
>>>
>>>
>>> On Fri, Dec 13, 2019 at 9:51 AM Kurt Fankhauser <
>>> lists.wavel...@gmail.com> wrote:
>>>
 probes been working fine for us in Powercode, the only probe problem i
 have is AF5XHD's oid's are screwed up right now, but thats not a Powercode
 problem.

 On Fri, Dec 13, 2019 at 7:38 AM Mike Hammett  wrote:

> I wish billing\oss systems would stop trying to be everything to
> everybody.
>
>
>
> -
> Mike Hammett
> Intelligent Computing Solutions 
> 
> 
> 
> 
> Midwest Internet Exchange 
> 
> 
> 
> The Brothers WISP 
> 
>
>
> 
> --
> *From: *"Steve Jones" 
> *To: *"AnimalFarm Microwave Users Group" 
> *Sent: *Thursday, December 12, 2019 3:34:13 PM
> *Subject: *[AFMUG] powercode and mikrotik BMUs
>
> Powercode has become quite a joke. Half our probes havent worked for
> months and they dont even respond to the ticket. We had to spin up 
> Librenms
> just to get monitoring data
>
> Trying to integrate mikrotik BMUs and having issues, they have zero
> legitimate documentation and when you ask whats supposed to be
> happening they tell you to seek out a consultant and that the info may be
> proprietary.
>
> Thats all bad enough, but i figure ill 

Re: [AFMUG] powercode and mikrotik BMUs

[Josh Luthman]

I didn't even think you could use v18 with Mikrotik.  Definitely not
recommended.  I've been on the latest latest with Mikrotik and it works
well.

Josh Luthman
Office: 937-552-2340
Direct: 937-552-2343
1100 Wayne St
Suite 1337
Troy, OH 45373


On Sat, Dec 14, 2019 at 10:22 PM Steve Jones 
wrote:

> When I was a very young man, my uncle's power went out. This, of course
> caused his sump pump to fail. As I was helping him lug out his destroyed
> furniture and carpet from his beautiful finished basement, he would just
> repeat, "if you have a guy down, you might as well kick him" ...ha. I
> understand what uncle Moe meant. He was right.
> Anyhow, turns out v18 did have some fatal issues with mikrotik. Went to
> v19 last night, good times. I would venture a guess that new customers
> could onboard gracefully, lots of better goodness in 19 new customers.
>
> On Fri, Dec 13, 2019, 10:43 AM Josh Luthman 
> wrote:
>
>> Same as Kurt.  Probes work wonderfully.  Customer radios, tower APs,
>> power monitors, all of it.
>>
>> I talked to Ubnt about that at Vegas and a couple times since then.  Tony
>> responds to me and I feel like the devs ignore him just as much as us.
>>
>> Josh Luthman
>> Office: 937-552-2340
>> Direct: 937-552-2343
>> 1100 Wayne St
>> Suite 1337
>> Troy, OH 45373
>>
>>
>> On Fri, Dec 13, 2019 at 9:51 AM Kurt Fankhauser 
>> wrote:
>>
>>> probes been working fine for us in Powercode, the only probe problem i
>>> have is AF5XHD's oid's are screwed up right now, but thats not a Powercode
>>> problem.
>>>
>>> On Fri, Dec 13, 2019 at 7:38 AM Mike Hammett  wrote:
>>>
 I wish billing\oss systems would stop trying to be everything to
 everybody.



 -
 Mike Hammett
 Intelligent Computing Solutions 
 
 
 
 
 Midwest Internet Exchange 
 
 
 
 The Brothers WISP 
 


 
 --
 *From: *"Steve Jones" 
 *To: *"AnimalFarm Microwave Users Group" 
 *Sent: *Thursday, December 12, 2019 3:34:13 PM
 *Subject: *[AFMUG] powercode and mikrotik BMUs

 Powercode has become quite a joke. Half our probes havent worked for
 months and they dont even respond to the ticket. We had to spin up Librenms
 just to get monitoring data

 Trying to integrate mikrotik BMUs and having issues, they have zero
 legitimate documentation and when you ask whats supposed to be
 happening they tell you to seek out a consultant and that the info may be
 proprietary.

 Thats all bad enough, but i figure ill do some packet sniffing to find
 out what the communication is between the billing server and the mikrotik,
 maybe find out I misconfigured something, come to find out the nitwits are
 sending out the authentication in PLAIN TEXT. They dont even have a
 disclaimer when you add one of these. but christ, if youre operating an off
 network BMU, your infrastructure credentials are getting tossed into the
 ether like its nothing.

 I wish simon hadnt left

 --
 AF mailing list
 AF@af.afmug.com
 http://af.afmug.com/mailman/listinfo/af_af.afmug.com

 --
 AF mailing list
 AF@af.afmug.com
 http://af.afmug.com/mailman/listinfo/af_af.afmug.com

>>> --
>>> AF mailing list
>>> AF@af.afmug.com
>>> http://af.afmug.com/mailman/listinfo/af_af.afmug.com
>>>
>> --
>> AF mailing list
>> AF@af.afmug.com
>> http://af.afmug.com/mailman/listinfo/af_af.afmug.com
>>
> --
> AF mailing list
> AF@af.afmug.com
> http://af.afmug.com/mailman/listinfo/af_af.afmug.com
>
-- 
AF mailing list
AF@af.afmug.com
http://af.afmug.com/mailman/listinfo/af_af.afmug.com

Re: [AFMUG] powercode and mikrotik BMUs

[Steve Jones]

When I was a very young man, my uncle's power went out. This, of course
caused his sump pump to fail. As I was helping him lug out his destroyed
furniture and carpet from his beautiful finished basement, he would just
repeat, "if you have a guy down, you might as well kick him" ...ha. I
understand what uncle Moe meant. He was right.
Anyhow, turns out v18 did have some fatal issues with mikrotik. Went to v19
last night, good times. I would venture a guess that new customers could
onboard gracefully, lots of better goodness in 19 new customers.

On Fri, Dec 13, 2019, 10:43 AM Josh Luthman 
wrote:

> Same as Kurt.  Probes work wonderfully.  Customer radios, tower APs, power
> monitors, all of it.
>
> I talked to Ubnt about that at Vegas and a couple times since then.  Tony
> responds to me and I feel like the devs ignore him just as much as us.
>
> Josh Luthman
> Office: 937-552-2340
> Direct: 937-552-2343
> 1100 Wayne St
> Suite 1337
> Troy, OH 45373
>
>
> On Fri, Dec 13, 2019 at 9:51 AM Kurt Fankhauser 
> wrote:
>
>> probes been working fine for us in Powercode, the only probe problem i
>> have is AF5XHD's oid's are screwed up right now, but thats not a Powercode
>> problem.
>>
>> On Fri, Dec 13, 2019 at 7:38 AM Mike Hammett  wrote:
>>
>>> I wish billing\oss systems would stop trying to be everything to
>>> everybody.
>>>
>>>
>>>
>>> -
>>> Mike Hammett
>>> Intelligent Computing Solutions 
>>> 
>>> 
>>> 
>>> 
>>> Midwest Internet Exchange 
>>> 
>>> 
>>> 
>>> The Brothers WISP 
>>> 
>>>
>>>
>>> 
>>> --
>>> *From: *"Steve Jones" 
>>> *To: *"AnimalFarm Microwave Users Group" 
>>> *Sent: *Thursday, December 12, 2019 3:34:13 PM
>>> *Subject: *[AFMUG] powercode and mikrotik BMUs
>>>
>>> Powercode has become quite a joke. Half our probes havent worked for
>>> months and they dont even respond to the ticket. We had to spin up Librenms
>>> just to get monitoring data
>>>
>>> Trying to integrate mikrotik BMUs and having issues, they have zero
>>> legitimate documentation and when you ask whats supposed to be
>>> happening they tell you to seek out a consultant and that the info may be
>>> proprietary.
>>>
>>> Thats all bad enough, but i figure ill do some packet sniffing to find
>>> out what the communication is between the billing server and the mikrotik,
>>> maybe find out I misconfigured something, come to find out the nitwits are
>>> sending out the authentication in PLAIN TEXT. They dont even have a
>>> disclaimer when you add one of these. but christ, if youre operating an off
>>> network BMU, your infrastructure credentials are getting tossed into the
>>> ether like its nothing.
>>>
>>> I wish simon hadnt left
>>>
>>> --
>>> AF mailing list
>>> AF@af.afmug.com
>>> http://af.afmug.com/mailman/listinfo/af_af.afmug.com
>>>
>>> --
>>> AF mailing list
>>> AF@af.afmug.com
>>> http://af.afmug.com/mailman/listinfo/af_af.afmug.com
>>>
>> --
>> AF mailing list
>> AF@af.afmug.com
>> http://af.afmug.com/mailman/listinfo/af_af.afmug.com
>>
> --
> AF mailing list
> AF@af.afmug.com
> http://af.afmug.com/mailman/listinfo/af_af.afmug.com
>
-- 
AF mailing list
AF@af.afmug.com
http://af.afmug.com/mailman/listinfo/af_af.afmug.com

Re: [AFMUG] powercode and mikrotik BMUs

[Josh Luthman]

Same as Kurt.  Probes work wonderfully.  Customer radios, tower APs, power
monitors, all of it.

I talked to Ubnt about that at Vegas and a couple times since then.  Tony
responds to me and I feel like the devs ignore him just as much as us.

Josh Luthman
Office: 937-552-2340
Direct: 937-552-2343
1100 Wayne St
Suite 1337
Troy, OH 45373


On Fri, Dec 13, 2019 at 9:51 AM Kurt Fankhauser 
wrote:

> probes been working fine for us in Powercode, the only probe problem i
> have is AF5XHD's oid's are screwed up right now, but thats not a Powercode
> problem.
>
> On Fri, Dec 13, 2019 at 7:38 AM Mike Hammett  wrote:
>
>> I wish billing\oss systems would stop trying to be everything to
>> everybody.
>>
>>
>>
>> -
>> Mike Hammett
>> Intelligent Computing Solutions 
>> 
>> 
>> 
>> 
>> Midwest Internet Exchange 
>> 
>> 
>> 
>> The Brothers WISP 
>> 
>>
>>
>> 
>> --
>> *From: *"Steve Jones" 
>> *To: *"AnimalFarm Microwave Users Group" 
>> *Sent: *Thursday, December 12, 2019 3:34:13 PM
>> *Subject: *[AFMUG] powercode and mikrotik BMUs
>>
>> Powercode has become quite a joke. Half our probes havent worked for
>> months and they dont even respond to the ticket. We had to spin up Librenms
>> just to get monitoring data
>>
>> Trying to integrate mikrotik BMUs and having issues, they have zero
>> legitimate documentation and when you ask whats supposed to be
>> happening they tell you to seek out a consultant and that the info may be
>> proprietary.
>>
>> Thats all bad enough, but i figure ill do some packet sniffing to find
>> out what the communication is between the billing server and the mikrotik,
>> maybe find out I misconfigured something, come to find out the nitwits are
>> sending out the authentication in PLAIN TEXT. They dont even have a
>> disclaimer when you add one of these. but christ, if youre operating an off
>> network BMU, your infrastructure credentials are getting tossed into the
>> ether like its nothing.
>>
>> I wish simon hadnt left
>>
>> --
>> AF mailing list
>> AF@af.afmug.com
>> http://af.afmug.com/mailman/listinfo/af_af.afmug.com
>>
>> --
>> AF mailing list
>> AF@af.afmug.com
>> http://af.afmug.com/mailman/listinfo/af_af.afmug.com
>>
> --
> AF mailing list
> AF@af.afmug.com
> http://af.afmug.com/mailman/listinfo/af_af.afmug.com
>
-- 
AF mailing list
AF@af.afmug.com
http://af.afmug.com/mailman/listinfo/af_af.afmug.com

Re: [AFMUG] powercode and mikrotik BMUs

[Kurt Fankhauser]

probes been working fine for us in Powercode, the only probe problem i have
is AF5XHD's oid's are screwed up right now, but thats not a Powercode
problem.

On Fri, Dec 13, 2019 at 7:38 AM Mike Hammett  wrote:

> I wish billing\oss systems would stop trying to be everything to everybody.
>
>
>
> -
> Mike Hammett
> Intelligent Computing Solutions 
> 
> 
> 
> 
> Midwest Internet Exchange 
> 
> 
> 
> The Brothers WISP 
> 
>
>
> 
> --
> *From: *"Steve Jones" 
> *To: *"AnimalFarm Microwave Users Group" 
> *Sent: *Thursday, December 12, 2019 3:34:13 PM
> *Subject: *[AFMUG] powercode and mikrotik BMUs
>
> Powercode has become quite a joke. Half our probes havent worked for
> months and they dont even respond to the ticket. We had to spin up Librenms
> just to get monitoring data
>
> Trying to integrate mikrotik BMUs and having issues, they have zero
> legitimate documentation and when you ask whats supposed to be
> happening they tell you to seek out a consultant and that the info may be
> proprietary.
>
> Thats all bad enough, but i figure ill do some packet sniffing to find out
> what the communication is between the billing server and the mikrotik,
> maybe find out I misconfigured something, come to find out the nitwits are
> sending out the authentication in PLAIN TEXT. They dont even have a
> disclaimer when you add one of these. but christ, if youre operating an off
> network BMU, your infrastructure credentials are getting tossed into the
> ether like its nothing.
>
> I wish simon hadnt left
>
> --
> AF mailing list
> AF@af.afmug.com
> http://af.afmug.com/mailman/listinfo/af_af.afmug.com
>
> --
> AF mailing list
> AF@af.afmug.com
> http://af.afmug.com/mailman/listinfo/af_af.afmug.com
>
-- 
AF mailing list
AF@af.afmug.com
http://af.afmug.com/mailman/listinfo/af_af.afmug.com

Re: [AFMUG] powercode and mikrotik BMUs

[Mike Hammett]

I wish billing\oss systems would stop trying to be everything to everybody. 




- 
Mike Hammett 
Intelligent Computing Solutions 

Midwest Internet Exchange 

The Brothers WISP 




- Original Message -

From: "Steve Jones"  
To: "AnimalFarm Microwave Users Group"  
Sent: Thursday, December 12, 2019 3:34:13 PM 
Subject: [AFMUG] powercode and mikrotik BMUs 


Powercode has become quite a joke. Half our probes havent worked for months and 
they dont even respond to the ticket. We had to spin up Librenms just to get 
monitoring data 


Trying to integrate mikrotik BMUs and having issues, they have zero legitimate 
documentation and when you ask whats supposed to be happening they tell you to 
seek out a consultant and that the info may be proprietary. 


Thats all bad enough, but i figure ill do some packet sniffing to find out what 
the communication is between the billing server and the mikrotik, maybe find 
out I misconfigured something, come to find out the nitwits are sending out the 
authentication in PLAIN TEXT. They dont even have a disclaimer when you add one 
of these. but christ, if youre operating an off network BMU, your 
infrastructure credentials are getting tossed into the ether like its nothing. 


I wish simon hadnt left 
-- 
AF mailing list 
AF@af.afmug.com 
http://af.afmug.com/mailman/listinfo/af_af.afmug.com 

-- 
AF mailing list
AF@af.afmug.com
http://af.afmug.com/mailman/listinfo/af_af.afmug.com

Re: [AFMUG] powercode and mikrotik BMUs

[Steve Jones]

Thats the plan, we are moving all critical monitoring to librenms, better
anyway cause we can keep long term without impacting powercodes db size. It
just is a pita to decide what to leave for tier 1 support to be able to see
in powercode since librenms is a little less user friendly

On Thu, Dec 12, 2019 at 6:05 PM Matt Hoppes <
mattli...@rivervalleyinternet.net> wrote:

> May I suggest using Powercode to ping your devices and use something like
> librenms to graph them?
>
> Either that or you may need a more powerful machine to keep up. My guess
> is the RRD files may have looped and got corrupted.
>
> On Dec 12, 2019, at 6:58 PM, Steve Jones 
> wrote:
>
> I had thought I identified which probes werent working, but its not
> limited to single OIDs, its across the board and random, thus far they
> haven been able to provide any functional probe report.
>
> One of the probe issues we found is that editing a device and changing its
> type, thus changing its probes, leaves the internal probe index name the
> same as the old probe (caused a major issue when we had a bunch of alvarion
> alerts when we dont have it anymore). worse yet is alot of the probes did
> work, but now dont. TBH, powercode should just do like theyre doing with
> bandwidth management/accounting and hand it off to a third party. basically
> make powercode an API skeleton/aggregator into systems that actually
> function reliably and make the core of powercode a glorified quickbooks
> instance/schedule management system
> I think the database is corrupt, but they apparently have no integrity
> checks. Im to the point that ive asked them about wiping the entirety of
> the probes and the rrd data as they have had to do twice in the past. this
> is a major pain, losing all that historic data, but considering without
> checking every single device, we dont know whats even probing and what is
> not and its random. Not to mention it would be nice to know the probe
> alerts will present with the actual probe names again.
> Way back in the day when the probing would fail over a bad OID there was a
> log i could check, but apparently thats not how it logs now. Powercode has
> always had an abysmally fragile probe system.
> If anybody can point me to logs, id be more than grateful.
>
> The API authentication was just the last thing with their mikrotik
> integration. They have garbage documentation, their support refuses to
> provide instruction sets, points you to outside consultants, which i find
> it odd that a consultant would have access to powercode documentation that
> neither powercode, nor powercodes paying customers have access to, maybe
> its some contract, though linktechs is unaware of it, maybe theres a secret
> handshake i need to know.  I find it absolutely ignorant that every time i
> update an ip range, powercode will delete the gateway from the mikrotik and
> ill have to go add it again. I literally can think of zero valid reason for
> it to do that. For whatever reason DHCP doesnt work, installed on the
> mikrotik, or using the powercode interface to set up a relay, yet when i
> configure a straight relay it works just fine. I have no major issue witht
> hat as id rather manage the relay myself so powercode doesnt randomly
> delete that too.
> I dont like that it set up a queue on the test router for my bosses
> personal account though i had exactly zero equipment added to the BMU and
> at the time, no ip ranges defined.
>
> Powercode has always ebbed and flowed, but right now its deplorable, being
> forced back to the third party router BMU is fine, i liked the imagestreams
> they made us deploy, then forced us to buy their BMUs. But at least in the
> imagestream days they actually supported their requirements. Theres the
> sesai or whatever flavor third party junk theyre pimping this week, just
> like all the others they pimped then dropped, so im not all that interested
> in going that route. Im still holding a grudge that on the morning of my
> wedding I woke to powercode randomly deciding to have massive phantom usage
> spikes (again) . Id recomend to the bosses migrating to another system, but
> the grass is never greener, if we move away, wed be better served to pay
> somebody to build us a proper solution, it would be cheaper than sasai or
> whetever is the flavor of the month with powercode. Or go to any of the
> free open source solutions out there since we are being forced to spin up
> all kinds of other servers anyway to mitigate their shortcomings. Powercode
> is still better than a bunch of spreadsheets though.
>
> that turned into more of a rant than anticipated, seeing my credentials in
> plain text just set me off, glad we arent hosted
>
> On Thu, Dec 12, 2019 at 5:15 PM Josh Luthman 
> wrote:
>
>> Your complaint seems to be probes and the Mikrotik API authentication.
>> If you have broken probes, it's your setup as they're working for me and
>> many others.  What exactly isn't working?  What OIDs?  The only caveat 

Re: [AFMUG] powercode and mikrotik BMUs

[Matt Hoppes]

May I suggest using Powercode to ping your devices and use something like 
librenms to graph them?

Either that or you may need a more powerful machine to keep up. My guess is the 
RRD files may have looped and got corrupted. 

> On Dec 12, 2019, at 6:58 PM, Steve Jones  wrote:
> 
> I had thought I identified which probes werent working, but its not limited 
> to single OIDs, its across the board and random, thus far they haven been 
> able to provide any functional probe report.
> 
> One of the probe issues we found is that editing a device and changing its 
> type, thus changing its probes, leaves the internal probe index name the same 
> as the old probe (caused a major issue when we had a bunch of alvarion alerts 
> when we dont have it anymore). worse yet is alot of the probes did work, but 
> now dont. TBH, powercode should just do like theyre doing with bandwidth 
> management/accounting and hand it off to a third party. basically make 
> powercode an API skeleton/aggregator into systems that actually function 
> reliably and make the core of powercode a glorified quickbooks 
> instance/schedule management system
> I think the database is corrupt, but they apparently have no integrity 
> checks. Im to the point that ive asked them about wiping the entirety of the 
> probes and the rrd data as they have had to do twice in the past. this is a 
> major pain, losing all that historic data, but considering without checking 
> every single device, we dont know whats even probing and what is not and its 
> random. Not to mention it would be nice to know the probe alerts will present 
> with the actual probe names again. 
> Way back in the day when the probing would fail over a bad OID there was a 
> log i could check, but apparently thats not how it logs now. Powercode has 
> always had an abysmally fragile probe system. 
> If anybody can point me to logs, id be more than grateful.
> 
> The API authentication was just the last thing with their mikrotik 
> integration. They have garbage documentation, their support refuses to 
> provide instruction sets, points you to outside consultants, which i find it 
> odd that a consultant would have access to powercode documentation that 
> neither powercode, nor powercodes paying customers have access to, maybe its 
> some contract, though linktechs is unaware of it, maybe theres a secret 
> handshake i need to know.  I find it absolutely ignorant that every time i 
> update an ip range, powercode will delete the gateway from the mikrotik and 
> ill have to go add it again. I literally can think of zero valid reason for 
> it to do that. For whatever reason DHCP doesnt work, installed on the 
> mikrotik, or using the powercode interface to set up a relay, yet when i 
> configure a straight relay it works just fine. I have no major issue witht 
> hat as id rather manage the relay myself so powercode doesnt randomly delete 
> that too.
> I dont like that it set up a queue on the test router for my bosses personal 
> account though i had exactly zero equipment added to the BMU and at the time, 
> no ip ranges defined.
> 
> Powercode has always ebbed and flowed, but right now its deplorable, being 
> forced back to the third party router BMU is fine, i liked the imagestreams 
> they made us deploy, then forced us to buy their BMUs. But at least in the 
> imagestream days they actually supported their requirements. Theres the sesai 
> or whatever flavor third party junk theyre pimping this week, just like all 
> the others they pimped then dropped, so im not all that interested in going 
> that route. Im still holding a grudge that on the morning of my wedding I 
> woke to powercode randomly deciding to have massive phantom usage spikes 
> (again) . Id recomend to the bosses migrating to another system, but the 
> grass is never greener, if we move away, wed be better served to pay somebody 
> to build us a proper solution, it would be cheaper than sasai or whetever is 
> the flavor of the month with powercode. Or go to any of the free open source 
> solutions out there since we are being forced to spin up all kinds of other 
> servers anyway to mitigate their shortcomings. Powercode is still better than 
> a bunch of spreadsheets though.
> 
> that turned into more of a rant than anticipated, seeing my credentials in 
> plain text just set me off, glad we arent hosted
> 
>> On Thu, Dec 12, 2019 at 5:15 PM Josh Luthman  
>> wrote:
>> Your complaint seems to be probes and the Mikrotik API authentication.  If 
>> you have broken probes, it's your setup as they're working for me and many 
>> others.  What exactly isn't working?  What OIDs?  The only caveat I'd say is 
>> that if one OID is broken in the query, they start responding poorly - it's 
>> done this way for scaling and irrelevant if you've got it set up right.
>> 
>> Not sure about the API auth but I do agree it should be secured.
>> 
>> Josh Luthman
>> Office: 937-552-2340
>> Direct: 937-552-2343
>> 1100 Wayne St

Re: [AFMUG] powercode and mikrotik BMUs

[Steve Jones]

I had thought I identified which probes werent working, but its not limited
to single OIDs, its across the board and random, thus far they haven been
able to provide any functional probe report.

One of the probe issues we found is that editing a device and changing its
type, thus changing its probes, leaves the internal probe index name the
same as the old probe (caused a major issue when we had a bunch of alvarion
alerts when we dont have it anymore). worse yet is alot of the probes did
work, but now dont. TBH, powercode should just do like theyre doing with
bandwidth management/accounting and hand it off to a third party. basically
make powercode an API skeleton/aggregator into systems that actually
function reliably and make the core of powercode a glorified quickbooks
instance/schedule management system
I think the database is corrupt, but they apparently have no integrity
checks. Im to the point that ive asked them about wiping the entirety of
the probes and the rrd data as they have had to do twice in the past. this
is a major pain, losing all that historic data, but considering without
checking every single device, we dont know whats even probing and what is
not and its random. Not to mention it would be nice to know the probe
alerts will present with the actual probe names again.
Way back in the day when the probing would fail over a bad OID there was a
log i could check, but apparently thats not how it logs now. Powercode has
always had an abysmally fragile probe system.
If anybody can point me to logs, id be more than grateful.

The API authentication was just the last thing with their mikrotik
integration. They have garbage documentation, their support refuses to
provide instruction sets, points you to outside consultants, which i find
it odd that a consultant would have access to powercode documentation that
neither powercode, nor powercodes paying customers have access to, maybe
its some contract, though linktechs is unaware of it, maybe theres a secret
handshake i need to know.  I find it absolutely ignorant that every time i
update an ip range, powercode will delete the gateway from the mikrotik and
ill have to go add it again. I literally can think of zero valid reason for
it to do that. For whatever reason DHCP doesnt work, installed on the
mikrotik, or using the powercode interface to set up a relay, yet when i
configure a straight relay it works just fine. I have no major issue witht
hat as id rather manage the relay myself so powercode doesnt randomly
delete that too.
I dont like that it set up a queue on the test router for my bosses
personal account though i had exactly zero equipment added to the BMU and
at the time, no ip ranges defined.

Powercode has always ebbed and flowed, but right now its deplorable, being
forced back to the third party router BMU is fine, i liked the imagestreams
they made us deploy, then forced us to buy their BMUs. But at least in the
imagestream days they actually supported their requirements. Theres the
sesai or whatever flavor third party junk theyre pimping this week, just
like all the others they pimped then dropped, so im not all that interested
in going that route. Im still holding a grudge that on the morning of my
wedding I woke to powercode randomly deciding to have massive phantom usage
spikes (again) . Id recomend to the bosses migrating to another system, but
the grass is never greener, if we move away, wed be better served to pay
somebody to build us a proper solution, it would be cheaper than sasai or
whetever is the flavor of the month with powercode. Or go to any of the
free open source solutions out there since we are being forced to spin up
all kinds of other servers anyway to mitigate their shortcomings. Powercode
is still better than a bunch of spreadsheets though.

that turned into more of a rant than anticipated, seeing my credentials in
plain text just set me off, glad we arent hosted

On Thu, Dec 12, 2019 at 5:15 PM Josh Luthman 
wrote:

> Your complaint seems to be probes and the Mikrotik API authentication.  If
> you have broken probes, it's your setup as they're working for me and many
> others.  What exactly isn't working?  What OIDs?  The only caveat I'd say
> is that if one OID is broken in the query, they start responding poorly -
> it's done this way for scaling and irrelevant if you've got it set up right.
>
> Not sure about the API auth but I do agree it should be secured.
>
> Josh Luthman
> Office: 937-552-2340
> Direct: 937-552-2343
> 1100 Wayne St
> Suite 1337
> Troy, OH 45373
>
>
> On Thu, Dec 12, 2019 at 4:35 PM Steve Jones 
> wrote:
>
>> Powercode has become quite a joke. Half our probes havent worked for
>> months and they dont even respond to the ticket. We had to spin up Librenms
>> just to get monitoring data
>>
>> Trying to integrate mikrotik BMUs and having issues, they have zero
>> legitimate documentation and when you ask whats supposed to be
>> happening they tell you to seek out a consultant and that the 

Re: [AFMUG] powercode and mikrotik BMUs

[Josh Luthman]

Your complaint seems to be probes and the Mikrotik API authentication.  If
you have broken probes, it's your setup as they're working for me and many
others.  What exactly isn't working?  What OIDs?  The only caveat I'd say
is that if one OID is broken in the query, they start responding poorly -
it's done this way for scaling and irrelevant if you've got it set up right.

Not sure about the API auth but I do agree it should be secured.

Josh Luthman
Office: 937-552-2340
Direct: 937-552-2343
1100 Wayne St
Suite 1337
Troy, OH 45373


On Thu, Dec 12, 2019 at 4:35 PM Steve Jones 
wrote:

> Powercode has become quite a joke. Half our probes havent worked for
> months and they dont even respond to the ticket. We had to spin up Librenms
> just to get monitoring data
>
> Trying to integrate mikrotik BMUs and having issues, they have zero
> legitimate documentation and when you ask whats supposed to be
> happening they tell you to seek out a consultant and that the info may be
> proprietary.
>
> Thats all bad enough, but i figure ill do some packet sniffing to find out
> what the communication is between the billing server and the mikrotik,
> maybe find out I misconfigured something, come to find out the nitwits are
> sending out the authentication in PLAIN TEXT. They dont even have a
> disclaimer when you add one of these. but christ, if youre operating an off
> network BMU, your infrastructure credentials are getting tossed into the
> ether like its nothing.
>
> I wish simon hadnt left
> --
> AF mailing list
> AF@af.afmug.com
> http://af.afmug.com/mailman/listinfo/af_af.afmug.com
>
-- 
AF mailing list
AF@af.afmug.com
http://af.afmug.com/mailman/listinfo/af_af.afmug.com

Re: [AFMUG] powercode and mikrotik BMUs

[Ryan Ray]

We also moved from Powercode to Sonar. I wasn't happy with the direction
the company was going and I feel a lot more comfortable back in Simon's
hands.

On Thu, Dec 12, 2019 at 2:14 PM David Coudron 
wrote:

> We made the switch from Powercode to Sonar a little over a year ago.   All
> in all I think we are happy we made the switch, but polling is a challenge
> in Sonar as well.  Before making that switch, I’d love to talk to folks
> about some unexpected issues they are likely to encounter.   We also spun
> up LibreNMS to resolve many monitoring issues.   It really stinks to have
> to manage another system to do basic monitoring, but that is what we have
> to do.
>
>
>
> I would love to see a hosted version of LibreNMS with an agent/appliance
> that could be deployed inside your network.   We don’t want to be in the
> server build/backup/management business, we’d rather be putting up
> towers.   Not sure if anything like that exists out there.
>
>
>
> Regards,
>
>
>
> David Coudron
>
> *From:* AF  *On Behalf Of * ch...@wbmfg.com
> *Sent:* Thursday, December 12, 2019 3:42 PM
> *To:* AnimalFarm Microwave Users Group 
> *Subject:* Re: [AFMUG] powercode and mikrotik BMUs
>
>
>
> There is always sonar...
>
>
>
> *From:* Steve Jones
>
> *Sent:* Thursday, December 12, 2019 2:34 PM
>
> *To:* AnimalFarm Microwave Users Group
>
> *Subject:* [AFMUG] powercode and mikrotik BMUs
>
>
>
> Powercode has become quite a joke. Half our probes havent worked for
> months and they dont even respond to the ticket. We had to spin up Librenms
> just to get monitoring data
>
>
>
> Trying to integrate mikrotik BMUs and having issues, they have zero
> legitimate documentation and when you ask whats supposed to be happening
> they tell you to seek out a consultant and that the info may be proprietary.
>
>
>
> Thats all bad enough, but i figure ill do some packet sniffing to find out
> what the communication is between the billing server and the mikrotik,
> maybe find out I misconfigured something, come to find out the nitwits are
> sending out the authentication in PLAIN TEXT. They dont even have a
> disclaimer when you add one of these. but christ, if youre operating an off
> network BMU, your infrastructure credentials are getting tossed into the
> ether like its nothing.
>
>
>
> I wish simon hadnt left
> --
>
> --
> AF mailing list
> AF@af.afmug.com
> http://af.afmug.com/mailman/listinfo/af_af.afmug.com
> --
> AF mailing list
> AF@af.afmug.com
> http://af.afmug.com/mailman/listinfo/af_af.afmug.com
>
-- 
AF mailing list
AF@af.afmug.com
http://af.afmug.com/mailman/listinfo/af_af.afmug.com

Re: [AFMUG] powercode and mikrotik BMUs

[David Coudron]

We made the switch from Powercode to Sonar a little over a year ago.   All in 
all I think we are happy we made the switch, but polling is a challenge in 
Sonar as well.  Before making that switch, I’d love to talk to folks about some 
unexpected issues they are likely to encounter.   We also spun up LibreNMS to 
resolve many monitoring issues.   It really stinks to have to manage another 
system to do basic monitoring, but that is what we have to do.

I would love to see a hosted version of LibreNMS with an agent/appliance that 
could be deployed inside your network.   We don’t want to be in the server 
build/backup/management business, we’d rather be putting up towers.   Not sure 
if anything like that exists out there.

Regards,

David Coudron
From: AF  On Behalf Of ch...@wbmfg.com
Sent: Thursday, December 12, 2019 3:42 PM
To: AnimalFarm Microwave Users Group 
Subject: Re: [AFMUG] powercode and mikrotik BMUs

There is always sonar...

From: Steve Jones
Sent: Thursday, December 12, 2019 2:34 PM
To: AnimalFarm Microwave Users Group
Subject: [AFMUG] powercode and mikrotik BMUs

Powercode has become quite a joke. Half our probes havent worked for months and 
they dont even respond to the ticket. We had to spin up Librenms just to get 
monitoring data

Trying to integrate mikrotik BMUs and having issues, they have zero legitimate 
documentation and when you ask whats supposed to be happening they tell you to 
seek out a consultant and that the info may be proprietary.

Thats all bad enough, but i figure ill do some packet sniffing to find out what 
the communication is between the billing server and the mikrotik, maybe find 
out I misconfigured something, come to find out the nitwits are sending out the 
authentication in PLAIN TEXT. They dont even have a disclaimer when you add one 
of these. but christ, if youre operating an off network BMU, your 
infrastructure credentials are getting tossed into the ether like its nothing.

I wish simon hadnt left

--
AF mailing list
AF@af.afmug.com<mailto:AF@af.afmug.com>
http://af.afmug.com/mailman/listinfo/af_af.afmug.com
-- 
AF mailing list
AF@af.afmug.com
http://af.afmug.com/mailman/listinfo/af_af.afmug.com

Re: [AFMUG] powercode and mikrotik BMUs

[Matt Hoppes]

Probes not working -- this sounds like an internal configuration issue, 
have you looked at the logs?  What are the errors?  What is happening? 
What version of PowerCode are you on?  Most development is on version 
19/20, so if you're still on 18, you won't get bug fixes.


What issues are you having with the MikroTiks?   Yes, PC does not 
support higher level MikroTik configs, but there's not much to 
configure... it's pretty much plug and play.


The authentication is only plain text if you haven't turned on 
encryption in the API (agreed it should default to that, but it doesn't).


Simon is half the reason PowerCode is in the state it is today... don't 
blame him.


On 12/12/19 4:34 PM, Steve Jones wrote:
Powercode has become quite a joke. Half our probes havent worked for 
months and they dont even respond to the ticket. We had to spin up 
Librenms just to get monitoring data


Trying to integrate mikrotik BMUs and having issues, they have zero 
legitimate documentation and when you ask whats supposed to be 
happening they tell you to seek out a consultant and that the info may 
be proprietary.


Thats all bad enough, but i figure ill do some packet sniffing to find 
out what the communication is between the billing server and the 
mikrotik, maybe find out I misconfigured something, come to find out the 
nitwits are sending out the authentication in PLAIN TEXT. They dont even 
have a disclaimer when you add one of these. but christ, if youre 
operating an off network BMU, your infrastructure credentials are 
getting tossed into the ether like its nothing.


I wish simon hadnt left



--
AF mailing list
AF@af.afmug.com
http://af.afmug.com/mailman/listinfo/af_af.afmug.com

Re: [AFMUG] powercode and mikrotik BMUs

[chuck]

There is always sonar...

From: Steve Jones 
Sent: Thursday, December 12, 2019 2:34 PM
To: AnimalFarm Microwave Users Group 
Subject: [AFMUG] powercode and mikrotik BMUs

Powercode has become quite a joke. Half our probes havent worked for months and 
they dont even respond to the ticket. We had to spin up Librenms just to get 
monitoring data 

Trying to integrate mikrotik BMUs and having issues, they have zero legitimate 
documentation and when you ask whats supposed to be happening they tell you to 
seek out a consultant and that the info may be proprietary.

Thats all bad enough, but i figure ill do some packet sniffing to find out what 
the communication is between the billing server and the mikrotik, maybe find 
out I misconfigured something, come to find out the nitwits are sending out the 
authentication in PLAIN TEXT. They dont even have a disclaimer when you add one 
of these. but christ, if youre operating an off network BMU, your 
infrastructure credentials are getting tossed into the ether like its nothing.

I wish simon hadnt left



-- 
AF mailing list
AF@af.afmug.com
http://af.afmug.com/mailman/listinfo/af_af.afmug.com
-- 
AF mailing list
AF@af.afmug.com
http://af.afmug.com/mailman/listinfo/af_af.afmug.com