yeah, I did that from the weekly backup. Lesson learned, set all static devices to use static IP not DHCP.
Lesson learned should be this one:
I've experienced trouble with v7.21.3 on my RB5009UG+S+.
About 12 hours after upgrading from 7.21.2, IPv4 packets stopped being routed to and from the public Internet (although IPv6 continued to work normally). Strangely, it was getting a DHCP lease from the ISP. It couldn’t ping the ISP’s IPv4 gateway successfully. Rebooting the router didn't help.
I know this sounds like an ISP issue, but downgrading to 7.21.2 (including the RouterBOARD firmware) resolved the problem immediately. Upgrading back to 7.21.3 caused the problem to reappear.
Sorry this is a bit vague - unfortunately the connection is too busy to do much more testing to identify the cause further.
since 2,5days of uptime in 7.21.3, no problem with routing v4/v6 (igmp snooping off)
When exporting config on some models (RB5009, CCR2004) the /ip/route commands contain the parameter “suppress-hw-offload=no” even when the device does not support hw offloading at all.
But on architectures where no device supports hw offloading (e.g. TILE), this parameter is not supported and commands that contain it are rejected.
Such choices make it difficult to migrate configurations. Please avoid that situation, either accept the parameter on all architectures or at least do not export it when it is not relevant. And when “no” is the default value, it is never relevant to export it.
update lab, and some PROD..
4 days withut issue on ARM/ARM64/Mipsbe routers..
you could do some packet capture.. on WAN interface.. it could help..
Yes, and before downgrading I really should have disabled hardware offloading to see if that made a difference. It’s difficult to justify re-applying the current release, though, because it’s a busy connection. Also, it might just be a weird anomaly. I’ll try the next release when that comes out, see what happens, and find the time to investigate further after hours if necessary.
I've more than 30 devices running on this release, ap, router, switches.
All are working fine. And since I've disabled igmp snooping everywhere, no more problems and strange behavior.
I would ask for sFlow/IPFix on hardware offloaded…
Bu if even the simple counters ar not working…
Some type of Flow for Hardware Off-loaded would be never-reach.
Has enough time passed before we can request again a public backlog of "not-fixed" topics?
Where were you when they released v7.21.1 stable and v7.21.2 stable LOL.
Probably spamming other forums… who would create a new account just to “congratulate on a new release”…? No, this account was created to spam the forum later, either by editing the post or exploiting the fact that existing users can post without pre-approval.
Support report some strange behavior when igmp snooping will be corrected on 7.22.
I can encourage you from disabling it if, like me, you have problems with 7.20x and 7.21x
That wasn't there when I first approved that post (and flagged the user for personal tracking because I was already suspecting something like this to happen).
Alas ... he's gone to Walhalla now ...
Carry on, peeps.
Anyone experiencing excessive sector writes on 7.21.2 and if so does this fix that? RB750r2 uptime 22d sector writes since reboot 400k.
No config update since a long time, all write intensive operations are either disabled or set to a very conservative interval.
140k after 9 days rb5009
870k after 4 days crs310
1300k after 9 days ax3
Yes that's write a lot
Yeah even 140k for 9 days is excessive, 1.3m though…
Did you noticed when the (potential) regression/bug happens? I'd like to pinpoint the last known good release in terms of writes and rollback
My 750r2 has been running for six years and 10% of its lifetime writes happens in the last 20 days
Store Configuration
Sub-menu: /ip dhcp-server config
Store Leases On Disk: The configuration of how often the DHCP leases will be stored on disk. If they would be saved on a disk on every lease change, a lot of disk writes would happen which is very bad for Compact Flash (especially, if lease times are very short). To minimize writes on disk, all changes are saved on disk every store-leases-disk seconds. Additionally, leases are always stored on disk on graceful shutdown and reboot.**
**
Is it set to immediately?