There is nothing in the event section of the AC2 server, nor is there any indication of the MTU size getting changed in the radio's logs. (There is an entry in the event log from when I changed it from 1492 -> 1500 bytes, but that's the only thing related to this.) (I checked Saturday and Sunday's logs - nothing to indicate the MTU size was changed.) I'm continuing to investigate - if anyone has another thought I'd welcome it :)
Sam On 8/18/2016 8:19 AM, Alasdair MacLeod wrote: > Are you using AC2? Check the events logs for changes for changes (a cog > icon should show on the graphs if any changes occurred and a new config > was backed up). > > On 18 August 2016 at 14:04, Sam Morris <w...@csilogan.com > <mailto:w...@csilogan.com>> wrote: > > Yes. AC2 latest beta. > > On 8/18/2016 7:34 AM, Adair Winter wrote: > > are you running aircontrol? > > > > On Thu, Aug 18, 2016 at 6:45 AM, Sam Morris <w...@csilogan.com > <mailto:w...@csilogan.com> > > <mailto:w...@csilogan.com <mailto:w...@csilogan.com>>> wrote: > > > > Have any of you ever known the MTU setting in the Network Tab > on a > > Rocket M2 (AP) to change itself? I started getting calls > Sunday morning > > (primarily from Mac users) saying some of their websites > wouldn't load. > > To make too long of a story short, I found that the MTU size > was set to > > 1492 on the AP. (We do use PPPoE, and the MTU on the CPEs is > set to > > 1492.) It should have been 1500. Changing it back to 1500 > fixed all the > > issues. > > > > My question is this: Other than me, no one has the password > to get into > > the AP. I hadn't been into it in many days (or weeks). Yet > somehow the > > MTU size changed and it obviously happened sometime between > Saturday > > (when things for my users were fine) and Sunday morning (when > things > > became hinky). There were some storms in the area, however I > don't > > believe there was a lightning strike (as if that would only > change the > > MTU setting and not affect anything else on the radio, or the > other 11 > > radios on the same tower). There *was* a bad port on the > Netonix switch > > it was plugged into, however as with a lightning strike, I > wouldn't > > think even a shorted port on the switch would change only > that one > > setting - I could see it defaulting the entire radio, but not one > > setting like that. > > > > Anyone ever seen anything like that? > > > > Thanks > > Sam > > _______________________________________________ > > Ubnt_users mailing list > > Ubnt_users@wispa.org <mailto:Ubnt_users@wispa.org> > <mailto:Ubnt_users@wispa.org <mailto:Ubnt_users@wispa.org>> > > http://lists.wispa.org/mailman/listinfo/ubnt_users > <http://lists.wispa.org/mailman/listinfo/ubnt_users> > > <http://lists.wispa.org/mailman/listinfo/ubnt_users > <http://lists.wispa.org/mailman/listinfo/ubnt_users>> > > > > > > > > > > -- > > > > Adair Winter > > VP, Network Operations / Co-Owner > > Amarillo Wireless | 806.316.5071 <tel:806.316.5071> > > C: 806.231.7180 <tel:806.231.7180> > > http://www.amarillowireless.net <http://www.amarillowireless.net> > <http://www.amarillowireless.net/ <http://www.amarillowireless.net/>> > > <http://www.amarillowireless.net <http://www.amarillowireless.net>> > > > > > > > > > > _______________________________________________ > > Ubnt_users mailing list > > Ubnt_users@wispa.org <mailto:Ubnt_users@wispa.org> > > http://lists.wispa.org/mailman/listinfo/ubnt_users > <http://lists.wispa.org/mailman/listinfo/ubnt_users> > > > > _______________________________________________ > Ubnt_users mailing list > Ubnt_users@wispa.org <mailto:Ubnt_users@wispa.org> > http://lists.wispa.org/mailman/listinfo/ubnt_users > <http://lists.wispa.org/mailman/listinfo/ubnt_users> > > > > > _______________________________________________ > Ubnt_users mailing list > Ubnt_users@wispa.org > http://lists.wispa.org/mailman/listinfo/ubnt_users > _______________________________________________ Ubnt_users mailing list Ubnt_users@wispa.org http://lists.wispa.org/mailman/listinfo/ubnt_users
