It’s definitely a router from Apple. Can not tell you whether 2.4 GHz or 5GHz. Do not come without my admin to the data. Only on Monday again.
At home I have a Fritz box of AVM with 2.4GHz. I rarely crashed there. Mostly when the phone gets too hot from playing games. 
@edit the apple router has only 2.4GHz.
Thank you for the information. It seems the Apple router in your office is offering two WLAN’s, but that is something which might not affect your system.
Instead, please ask your IT which type of Apple router you are using in your office, and - probably more important - which topology (802.11b, 802.11g, or 802.11n) is available. Then, maybe @chrmhoffmann can/would like to do further research to find out if this setup is causing an issue with Lineage OS.
Oh … then I might have a quite simple explanation for the crashes you experience in your office: You play games at work excessively! 
I can give you more details about the router on Monday. 
Does it still crash with newest boot.img?
I also have router with 2.4 and 5 GhZ and that doesn’t seem to cause any issue.
Chris
IPv4 or IPv6?
DHCP or static?
I had a reboot as well but not since the latest firmware update. Applied a piece of paper on the battery, maybe that fixes it.
I will report to you on Monday. had a reboot on Friday with the new image as soon as I am connected to the apple router.
@chrmhoffmann Shouldn’t we just open a bug report for the random reboots on the official LineageOS bugtracker to collect logs and discuss the proceeding?
That would not help. There’s only me working on FP2.
I know you are the only maintainer of the FP2. I proposed it for having a central place to collect the logs instead of having them spread around in the forum. (If you count the logs from snevas’ releases) I mean the bug tracker is intended to serve for such kind of purposes.
On the other hand I don’t want to force you to use it.
I know your inquiry is not addressed to me, but if you want to know my opinion:
For now it seems that the bug reports do not provide (enough) details to file this bug (router model, protocol, etc.). I have been speculating if this could be a WLAN handshake issue, but I do not have a proof either.
Lots of different bugs causing reboots have been reported in the tracker, without any specific details. Usually these are the kind of bugs which cannot be reproduced, although of course there are exceptions, too…
My suggestion is: Let us wait until @StevenHachel provides some useful information, then maybe @chrmhoffmann will test and find out something which can be reported in the tracker.
We have the lineage bug tracker on fairphone. I’d prefer to use that for the moment.
Chris
Good morning,
still have no answer from our admin … have to wait a bit.
But this morning I had a reboot, without a WLAN and without SDCard. Have the file uploaded.
last_kmsg_13112017_1.txt
I really have the feeling that my hardware is broken …
In this case I think you may be right. Looks like corrupted memory to me:
mdss_set_rgb: mdss_set_rgb: r=32768 g=316dle kernÿÿÿÿ
£ RQ Unable to hantual addel paging request at vir00, qcomress 0pgd = e2ff8000
Nevertheless the investigation of a possible WLAN issue (in conjunction with corporate Apple WiFi) should be continued. Should you have any information from your administrator, please forward them. I have a feeling that your company might use a protocol, namely 802.11r, which could be the culprit…
I have had a number of reboots since moving over to LOS. I’m not rooted through or know how to get the logs.
I’ve had problems on LTE/3G and Wifi. I’ve noticed the phone reboots a number of times when charging (often when it gets to 90+ charged).
I’ve reformatted my SD, but still have issues
I currently have a broken mic, but I doubt that has anything to do with it.
Edit: Just read “LOS” in the thread subject, but it happens with Open OS, too:
sorry that it took so long.
Steven
Never mind, thank you for the information.
So you do not use DHCP in the company?
But yes, but this router hangs on a network hub in our office and has a static IP. We basically use DHCP already.
It would be good to know if other Android phones within your WLAN are affected as well, just to rule out some Airport specific settings (for Mac, iPhone & Co.).