**** BEGIN LOGGING AT Fri May 18 03:00:04 2018
May 18 10:02:36 <mrkiko> hello guys. Sorry if I repeat my message here, but I realized only then about the two different channels, I somehow got confused even knowing it. And this thing seems pretty entrenched. I am having a difficult time diagnosing a problem with my TP-Link Archer MR200 device. On openwrt git HEAD, communicating with LTE module become problematic - i.e.: pinging the internal 192.168.255.1 address won't
May 18 10:02:43 <mrkiko> give back an answer until you proceed in the module shell to turn down and up the internal LTE module bridge. The problem is that something on openwrt head is inducing the closed-source (more or less) lte module firmware to "misbehave" and forget about connection profiles and stuff like that, while on older LEDE releases this all worked fine. Could you help me out? I was wondering if git kernel
May 18 10:02:48 <mrkiko> commit a5a18bdf7453d505783e40e47ebb84bfdd35f93b. The device is MT7620-based.
May 18 11:26:12 <mrkiko> if I am able to pinpoint the commit, where can I publish it?
May 18 13:29:16 <mrkiko> Ok, guess it is not openwrt-related issue.
May 18 13:29:21 <mrkiko> sorry
May 18 13:36:23 <mrkiko> exiting, sorry. have a good time guys.
**** ENDING LOGGING AT Sat May 19 03:00:00 2018