We are having massive network wide issues since upgrading our cnPilot routers to 4.7.4-R19 .
SYMPTOMS: Devices don’t get DHCP addresses, cnPilots vanish from the cloud, config changes can’t be made, software updated/downgrades can’t be made, and eventually routers crash.
The core issues seems to stem from a massive crit_techsup file generated in /etc/cambium
This issue prevents any firmware updates/downgrades from happening. It prevents any config changes from being made. And it eventually crashes the router and requires a truck roll to fix.
We have been talking to Cambium support for over 3 weeks and get only “This is a critical issue internally”, yet as we’re having a literal core meltdown there isn’t even so much as a work around or solution provided yet.
I’ve e-mailed and talked to on the phone our RTM on Thursday and have not heard anything further from him.
Where can I take this further up the chain in Cambium, and is anyone else seeing this issue?
Apparently between certain versions, a factory reset was was needed. Whether it merely needed a fresh config (thereby omitting erroneous parameters), or it actually changed something more permanently, I cannot confirm. that being said, every time I get a new router I upgrade the firmware and factory reset the config, then load a config template.I can’t recall the version past which need this procedure was needed (check release notes).
Yes I am running 4.7.4-R19. I’ll check the output of those commands when I get a gap. What is your output?
I would check that your MTUs are correct (at least 1518) and that you don’t have any fragmentation through your network. If there is, then set the desired MTU in the WAN interface settings (accounting for TCP overhead and the protocol over your network. I take it you don’t have a management network? I only use VLANs, but at the very least you should have a management network on a VLAN.
I’m facing a similar issue, customers “stop getting internet from un-explainable reasons”, the typical resolution is to reboot the router (R190V/W & 195W) and everything works again.
However, this morning I accessed to into the logs and found:
<Mon Oct 24 19:36:23 2022> udhcpd[17608]: Sending OFFER of 192.168.11.199
<Mon Oct 24 19:36:23 2022> udhcpd[17608]: Sending ACK to 192.168.11.199
<Mon Oct 24 19:36:23 2022> udhcpd[17608]: can't open '/etc/cambium/udhcpd.leases': No space left on device
Multiple times, so is like right before assigning the IP the system fails to write some files.
I will submit a support ticket tomorrow, but I really appreciate if someone from Cambium jump here to explain what is going on.
I’ve 250+ units deployed, and this is the most common problem I’ve (un-explainable lost of connection), everything looks great from cnMaestro, all the way from the AP to the Router, I’m even able to ping/traceroute in cnMaestro from the router to any website.
We ran into this issue when upgrade to 4.7.5-R2 from 4.7.2R-10. So I would say no it was not fixed in 4.7.5-R2. To fix the issue we had a beta of 4.8R-X
On the R-Series. There is a feature called DNS proxy on the LAN. Originally I found that if there is interference, this hangs and stops providing DNS. Only a reboot fixes this. I have it turned off by default, so I can’t say for sure that it still exists on newer firmware versions. Printer direct WiFi, Roku media players often purposefully (or unintelligently) select their channels.
A good test would be to see if an IP is still ping-able…
@iBound I’ll look. But I don’t think this is the current issue.
The current issues that if the modem and the wireless router come up at the same time from say a power outage, the modem doesn’t yet have internet so this young pilot doesn’t get an IP address. The cnpilot just never gets an IP address and hangs with an empty DHCP on the WAN interface until you hard reboot it
I’m assuming this is is IPv4? IPv6 was / is broken (haven’t tested in a while). When the session drops iPv6 stops functioning. Thinking about it, could be a DHCP issue over IPv4/6 in general.
Check LAN/Advanced and set the MTU. Maybe play with that. There’s also MTU setting for the WAN interfaces. To be honest, I haven’t tested the WAN MTU thing. Test pings with allow fragmentation off.
What is the latency from the DHCP server to Router?