@greygit wrote:
IPv4/33 would be weird; so would /32.
No, a /32 is a perfectly valid subnet. pfSense for example has specific range checking to allow a /32 subnet to be assigned to an IPv4 WAN interface, whereas the smallest it allows on a LAN interface is /31
@greygit wrote:
But /30 looks fairly standard to me.
Agreed, I have a router interface with a /30
@greygit wrote
Why should there be a consumer-grade network device that retains its log entries across reboots and factory resets?
A router that loses it's log file after a reboot, probably indicates that that log is held in RAM rather than written to 'disk' (i.e. SSD or flash memory), and would indicate the designer made the product a cheaply as possible. However a design with a non-volatile log file, especially on an ISP branded router, would show that there was a design consideration for "customer services" to be able to assist in diagnosing the end user problems by remotely downloading the log file to see what is really happening with the device, rather than relying on mostly non-technical customers reporting vague problems, or denying that they have been repeatedly rebooting the device when the log file might indicate otherwise.
Given the choice of whether I would want my router to retain it's logs across resets or not, I would always choose to have as much logging retained as possible, because you can then compare logs for reboots when you have tweaked one thing to see if it made a difference, also it is useful to be able to see whether a router that randomly rebooted had some event just before it reset.
I agree that it would be a nice to have feature, to have a GUI button or CLI command to clear a log file, as sometimes you get so deep in solving a problem that having to search a huge log for the start of a current diagnostic timeframe gets tedious.
It is unusual that the log files aren't cleared on a factory reset, because a factory reset is usually a last resort when a device is unresponsive due to memory corruption or a software fault, and so resetting the logs would generally be a good idea. However there was an occasion on this forum where a customer discovered by looking at the logs that survived a reset, that their child had worked out that in order to access the WiFi (that the parent had deliberately disabled), that the child had figured out that pressing the factory reset button got the router to auto-configure with TR-069 and by default switch the WiFi back on, without the child knowing the GUI login password. So seeing the factory reset in the log file, was able to understand how the cunning child was bypassing the router security.
