Yep routers can store logs. There are many types of logs and log levels. One type of log is the command log. If any one is familiar with a command line it is the same concept (you can press the up arrow to call back issued commands).

In more advanced routers a command can be issued to see that command buffer. That buffer itself usually has a default number of "history" and in some cases can be configured to "remember" more or less commands. I know with cisco routers there are a few ways to clear/purge/delete/reset the command history.

Network traffic logs, over time, take up a considerable amount of space - obviously the more traffic there is the more logs are generated. Routers don't typically have a large storage space for logs (they certainly can store network traffic logs if configured to do so). Also having one router handle all logging is bad practice as it is a single point of failure. It is better to configure the router to send all logs to a log server that can easily be mirrored/replicated and backed up on a regular basis.

I doubt that the router was specifically deployed for the election. The router(s) in question I believe are for the local county government. So it is just part of the normal local government network that runs all the day to day things county wide. From the tax assessor to the sheriff etc.

When the election happened allegedly election equipment was connected to the LAN (Local Area Network) of whatever building they held the election equipment in. That LAN would have been connected to the county wide network and could potentially have access to the outside world. Once they have some one look at the router(s), they would be able to see how they were configured and be able to determine if network traffic would have been able to flow from election equipment to the outside world. (if there was mobile data involved that is a whole 'nother can of worms)

Yep routers can store logs. There are many types of logs and log levels. One type of log is the command log. If any one is familiar with a command line it is the same concept (you can press the up arrow to call back issued commands).

In more advanced routers a command can be issued to see that command buffer. That buffer itself usually has a default number of "history" and in some cases can be configured to "remember" more or less commands. I know with cisco routers there are a few ways to clear/purge/delete/reset the command history.

Network traffic logs, over time, take up a considerable ammount of space - obviously the more traffic there is the more logs are generated. Routers don't typically have a large storage space for logs. Also having one router handle all logging is a bad practice as it is a single point of failure. It is better to configure the router to send all logs to a log server that can easily be mirrored/replicated and backed up on a regular basis.

I doubt that the router was specifically deployed for the election. The router(s) in question I believe are for the local county government. So it is just part of the normal local government network that runs all the day to day things county wide. From the tax assessor to the sheriff etc.

When the election happened allegedly election equipment was connected to the LAN (Local Area Network) of whatever building they held the election equipment in. That LAN would have been connected to the county wide network and could potentially have access to the outside world. Once they have some one look at the router(s), they would be able to se how they were configured and be able to determine if network traffic would have been able to flow from election equipment to the outside world (if there was mobile data involved that is a whole 'nother can of worms)