why did eth0 suddenly stop working?
I have some cameras connected with eth-cables to a switch and from there to a computer (OS 15.5, using zoneminder for the cameras). It works. But this morning I saw that tonight the connection to the cameras was lost. I could ping the switch, but not the cameras. "arp -a" showed the IP's of the cameras but with "[IP] at incomplete ...". I checked all cables. I rebooted. I switched off/on electricity for computer/switch/cameras. I unplugged the switch's cable to the computer and plugged it again. No change. I plugged the eth cable to my laptop (that I used before for this task, using OS 15.3) and all connections worked... Plugged back the eth cable to the computer - and the connections work again, all cameras pingable and visible. Magic. There are no messages in var/log, only the zoneminder-log said "no connection to..." What happened here? -- Daniel Bauer photographer Basel Málaga https://www.patreon.com/danielbauer https://www.daniel-bauer.com
Hello, In the Message; Subject : why did eth0 suddenly stop working? Message-ID : <b1336752-e3fd-7086-9bcd-8834fc7adf14@daniel-bauer.com> Date & Time: Sun, 2 Jul 2023 14:06:03 +0200 [DB] == Daniel Bauer <linux@daniel-bauer.com> has written: DB> I have some cameras connected with eth-cables to a switch and from there to a DB> computer (OS 15.5, using zoneminder for the cameras). It works. [...] DB> What happened here? Is this not helpful? https://askubuntu.com/questions/46518/wired-internet-eth0-suddenly-stopped-w... Regards & Good Night. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "No Windows, no gains!" ... "Why, I am wrong?" -- Bill --
Am 02.07.23 um 14:30 schrieb Masaru Nomiya:
Hello,
In the Message;
Subject : why did eth0 suddenly stop working? Message-ID : <b1336752-e3fd-7086-9bcd-8834fc7adf14@daniel-bauer.com> Date & Time: Sun, 2 Jul 2023 14:06:03 +0200
[DB] == Daniel Bauer <linux@daniel-bauer.com> has written:
DB> I have some cameras connected with eth-cables to a switch and from there to a DB> computer (OS 15.5, using zoneminder for the cameras). It works. [...] DB> What happened here?
Is this not helpful?
https://askubuntu.com/questions/46518/wired-internet-eth0-suddenly-stopped-w...
Not sure, but as I have configured eth0 to a fixed IP with "method: manual", dhcp shouldn't play any role in this. Or am I wrong? -- Daniel Bauer photographer Basel Málaga https://www.patreon.com/danielbauer https://www.daniel-bauer.com
Hello, In the Message; Subject : Re: why did eth0 suddenly stop working? Message-ID : <6c11258d-f562-377e-9c19-4fd72e9001a2@daniel-bauer.com> Date & Time: Sun, 2 Jul 2023 15:19:15 +0200 [DB] == Daniel Bauer <linux@daniel-bauer.com> has written: DB> Am 02.07.23 um 14:30 schrieb Masaru Nomiya: Sorry, but are you German? I did feel that your last name is not Spanish..... Anyway, [...] MN> > Is this not helpful? MN> > MN> > https://askubuntu.com/questions/46518/wired-internet-eth0-suddenly-stopped-w... DB> Not sure, but as I have configured eth0 to a fixed IP with DB> "method: manual", dhcp shouldn't play any role in this. Or am I wrong? You are correct. If you have configured eth0 to a fixed IP with “method: manual”, DHCP should not play any role in this. If you are still having issues with eth0, it could be due to a hardware failure, a software issue, or a configuration problem. Have you tried; $ sudo ifdown eth0 && sudo ifup eth0 But, I doubt the hardware around.... Regards. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Bill! You married with Computer. Not with Me!" "No..., with money."
Just the same as described in my first post happened again tonight: Suddenly (like after approx. 100 of running normal) the connections on eth0 tpo the IP's behind the switch get lost. I can ping the switch, but not the other IP's connected to that switch. There is nothing in /var/log/messages (except the camera software that complains for not being able to connect with the cameras). Networkmanager shows "connected". Disconnect-reconnect/unplugg-replug cables/rebooting/completely disconnect/reconnect PC, switch and cameras from electricity doesn't help. BUT: plugging the the switch to my laptop all IP's are available on the laptop immediately, then plugging back the cable to the PC they appear there as well... I cannot explain to myself why when I connect the switch to my laptop and then back to the PC it works again immediately, but I can't re-establish eth0 connection by any other means. What does my laptop do to do the magic? My laptop isn't connected to the PC in any way (no WiFi, no eth-connection), so it can't change something on the PC. To me it seems that it changes something on the switch, but what and how? Any ideas how I can find the error? Am 02.07.23 um 14:06 schrieb Daniel Bauer:
I have some cameras connected with eth-cables to a switch and from there to a computer (OS 15.5, using zoneminder for the cameras). It works.
But this morning I saw that tonight the connection to the cameras was lost. I could ping the switch, but not the cameras. "arp -a" showed the IP's of the cameras but with "[IP] at incomplete ...".
I checked all cables. I rebooted. I switched off/on electricity for computer/switch/cameras. I unplugged the switch's cable to the computer and plugged it again.
No change.
I plugged the eth cable to my laptop (that I used before for this task, using OS 15.3) and all connections worked...
Plugged back the eth cable to the computer - and the connections work again, all cameras pingable and visible. Magic.
There are no messages in var/log, only the zoneminder-log said "no connection to..."
What happened here?
-- Daniel Bauer photographer Basel Málaga https://www.patreon.com/danielbauer https://www.daniel-bauer.com
On 2023-07-09 13:00, Daniel Bauer wrote:
Just the same as described in my first post happened again tonight:
Suddenly (like after approx. 100 of running normal) the connections on eth0 tpo the IP's behind the switch get lost. I can ping the switch, but not the other IP's connected to that switch.
First idea: power cycle the switch. Is the switch manageable, does it have a web page for administration? Perhaps it has a log.
There is nothing in /var/log/messages (except the camera software that complains for not being able to connect with the cameras). Networkmanager shows "connected".
Disconnect-reconnect/unplugg-replug cables/rebooting/completely disconnect/reconnect PC, switch and cameras from electricity doesn't help.
Ah, then you did you power cycle the switch?
BUT: plugging the the switch to my laptop all IP's are available on the laptop immediately, then plugging back the cable to the PC they appear there as well...
Full buffer somewhere... Strange.
I cannot explain to myself why when I connect the switch to my laptop and then back to the PC it works again immediately, but I can't re-establish eth0 connection by any other means. What does my laptop do to do the magic?
The switch resets the "history" of that connector. Wild guess out of my hat.
My laptop isn't connected to the PC in any way (no WiFi, no eth-connection), so it can't change something on the PC. To me it seems that it changes something on the switch, but what and how?
Any ideas how I can find the error? If it is the switch, try to find a firmware update for it, and apply it.
I had a very weird problem with my switch, and it was that. (packets from router downstairs did not reach machines connected to switch upstairs, 30% failure. I some setup, ping failed completely. I'd have to dug out my notes to describe, it was weird. Telefonica man wasted more than hour, and finally replaced the router. First router lost 100% packets, second only 30% loss. "Madrecita, que me quede como estoy". Many moons later, a switch update solved the issue.) Switches being smart means they can have bugs. This is progress. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
(Sorry Carlos, I clicked to fast on the wrong replay button) Am 09.07.23 um 13:18 schrieb Carlos E. R.:
On 2023-07-09 13:00, Daniel Bauer wrote:
Just the same as described in my first post happened again tonight:
Suddenly (like after approx. 100 of running normal) the connections on eth0 tpo the IP's behind the switch get lost. I can ping the switch, but not the other IP's connected to that switch.
First idea: power cycle the switch.
You mean unplugging electricity and plug again after a while? I did that.
Is the switch manageable, does it have a web page for administration? Perhaps it has a log.
No, it's a powered, but unmanaged Netgear GS308PP
There is nothing in /var/log/messages (except the camera software that complains for not being able to connect with the cameras). Networkmanager shows "connected".
Disconnect-reconnect/unplugg-replug cables/rebooting/completely disconnect/reconnect PC, switch and cameras from electricity doesn't help.
Ah, then you did you power cycle the switch?
Yes
BUT: plugging the the switch to my laptop all IP's are available on the laptop immediately, then plugging back the cable to the PC they appear there as well...
Full buffer somewhere...
Strange.
I cannot explain to myself why when I connect the switch to my laptop and then back to the PC it works again immediately, but I can't re-establish eth0 connection by any other means. What does my laptop do to do the magic?
The switch resets the "history" of that connector. Wild guess out of my hat.
My laptop isn't connected to the PC in any way (no WiFi, no eth-connection), so it can't change something on the PC. To me it seems that it changes something on the switch, but what and how?
Any ideas how I can find the error? If it is the switch, try to find a firmware update for it, and apply it.
I had a very weird problem with my switch, and it was that.
I can't find anything on how to update firmware for this model. Apart I doubt it is that. The very same switch with the very same cameras, cables etc. have been working for a long time (and several months uptime) with my laptop without any problems. And still work immediately after plugging to the laptop. I just replaced the laptop with a new mini PC and since then this strange problem occurs.
...
Switches being smart means they can have bugs. This is progress.
This is a stupid switch :-) -- Daniel Bauer photographer Basel Málaga https://www.patreon.com/danielbauer https://www.daniel-bauer.com
Hello, In the Message; Subject : Re: why did eth0 suddenly stop working? Again and very strange! Message-ID : <c89e8cd2-66db-32cf-c739-f1b316dcaf1e@daniel-bauer.com> Date & Time: Sun, 9 Jul 2023 14:32:04 +0200 [DB] == Daniel Bauer <linux@daniel-bauer.com> has written: [...] DB> I can't find anything on how to update firmware for this model. DB> Apart I doubt it is that. The very same switch with the very same DB> cameras, cables etc. have been working for a long time (and DB> several months uptime) with my laptop without any problems. And DB> still work immediately after plugging to the laptop. DB> I just replaced the laptop with a new mini PC and since then this DB> strange problem occurs. How about testing with ethtool? Regards & Good Night. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ " Hassabis says that no one really knows for sure that AI will become a major danger. But he is certain that if progress continues at its current pace, there isn’t much time to develop safeguards. "I can see the kinds of things we're building into the Gemini series right, and we have no reason to believe that they won't work," he says." -- "Google DeepMind's CEO Says Its Next Algorithm Will Eclipse ChatGPT" --
Am 09.07.23 um 14:44 schrieb Masaru Nomiya:
DB> I can't find anything on how to update firmware for this model.
DB> Apart I doubt it is that. The very same switch with the very same DB> cameras, cables etc. have been working for a long time (and DB> several months uptime) with my laptop without any problems. And DB> still work immediately after plugging to the laptop.
DB> I just replaced the laptop with a new mini PC and since then this DB> strange problem occurs.
How about testing with ethtool?
I just tried to understand a bit ethtool's man page. With not much success, I must confess... What could I find out with it, and how? The problem is that everything works perfect for some days without any problems, and then all of a sudden it stops working. As much as I know, my switch doesn't have a log. I could do, of course, some tests after it happens the next time, but which ones? -- Daniel Bauer photographer Basel Málaga https://www.patreon.com/danielbauer https://www.daniel-bauer.com
Good Morning & Hello, In the Message; Subject : Re: why did eth0 suddenly stop working? Again and very strange! Message-ID : <fc703d0b-f0f9-7255-31ce-545312db1772@daniel-bauer.com> Date & Time: Sun, 9 Jul 2023 15:46:52 +0200 [DB] == Daniel Bauer <linux@daniel-bauer.com> has written: DB> Am 09.07.23 um 14:44 schrieb Masaru Nomiya: [...] DB> > How about testing with ethtool? DB> I just tried to understand a bit ethtool's man page. With not much success, I DB> must confess... What could I find out with it, and how? I've never used switch, but I thought ethtool could tell you the status of the connection to the switch. How about comparing these results when things are working well and when things go wrong? 1. # ethtool eth0 2. # ethtool --test eth0 3. # ethtool --test eth0 external_lb Here, 3. includes a test for external loopback, but I don't know if this test is meaningful or not. REgards. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ " Hassabis says that no one really knows for sure that AI will become a major danger. But he is certain that if progress continues at its current pace, there isn’t much time to develop safeguards. "I can see the kinds of things we're building into the Gemini series right, and we have no reason to believe that they won't work," he says." -- "Google DeepMind's CEO Says Its Next Algorithm Will Eclipse ChatGPT" --
On 2023-07-09 14:32, Daniel Bauer wrote:
(Sorry Carlos, I clicked to fast on the wrong replay button)
Am 09.07.23 um 13:18 schrieb Carlos E. R.:
On 2023-07-09 13:00, Daniel Bauer wrote:
Just the same as described in my first post happened again tonight:
Suddenly (like after approx. 100 of running normal) the connections on eth0 tpo the IP's behind the switch get lost. I can ping the switch, but not the other IP's connected to that switch.
First idea: power cycle the switch.
You mean unplugging electricity and plug again after a while? I did that.
Ok.
Is the switch manageable, does it have a web page for administration? Perhaps it has a log.
No, it's a powered, but unmanaged Netgear GS308PP
I found the manual. https://www.downloads.netgear.com/files/GDC/Unmanaged_Switches/300-Series_Po... https://www.downloads.netgear.com/files/GDC/GS308PP/GS308PP_IG_SP.pdf It gives instructions to register, install managing app, then says that this switch can not be managed. I find no place mentioning updates. ...
I can't find anything on how to update firmware for this model.
Apart I doubt it is that. The very same switch with the very same cameras, cables etc. have been working for a long time (and several months uptime) with my laptop without any problems. And still work immediately after plugging to the laptop.
Yeah, well, my switch did not exhibit any problem till Telefónica replaced my router.
I just replaced the laptop with a new mini PC and since then this strange problem occurs.
Try a different port :-?
...
Switches being smart means they can have bugs. This is progress.
This is a stupid switch :-)
It still has some software inside :-p -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
From: Daniel Bauer <linux@daniel-bauer.com> Date: Sun, 9 Jul 2023 13:00:39 +0200 Just the same as described in my first post happened again tonight: Suddenly (like after approx. 100 of running normal) the connections on eth0 tpo the IP's behind the switch get lost. I can ping the switch, but not the other IP's connected to that switch. There is nothing in /var/log/messages (except the camera software that complains for not being able to connect with the cameras). Networkmanager shows "connected". Disconnect-reconnect/unplugg-replug cables/rebooting/completely disconnect/reconnect PC, switch and cameras from electricity doesn't help. BUT: plugging the the switch to my laptop all IP's are available on the laptop immediately, then plugging back the cable to the PC they appear there as well... I cannot explain to myself why when I connect the switch to my laptop and then back to the PC it works again immediately, but I can't re-establish eth0 connection by any other means. What does my laptop do to do the magic? The only think I can think of that would cause this behavior is that somehow the switch is being fooled into thinking that the Ethernet address for that port has changed when in fact it hasn't. (That should only explain failure to receive packets, but depending on the nature of the failure, it might screw up sending as well.) Plugging in another system forces the switch to reconsider, which fixes the problem. And if attempting to make connections from your PC fails, then it's not surprising that unplugging/replugging doesn't help either. This also goes a long way to proving that it's not your PC's fault. Have you tried permuting the connections to the switch? (And sorry if this has already been suggested.) ================ From: Daniel Bauer <linux@daniel-bauer.com> Date: Sun, 9 Jul 2023 14:32:04 +0200 Am 09.07.23 um 13:18 schrieb Carlos E. R.:
Ah, then you did you power cycle the switch?
Yes How long did you leave it unplugged? Small switches don't need much power, so if they have an even halfway decent power supply, they can remember routing information for a surprisingly long time, perhaps a few minutes even. Or there may even be an NVRAM cache for routing info. -- Bob Rogers http://www.rgrjr.com/
Am 10.07.23 um 08:33 schrieb Bob Rogers:
From: Daniel Bauer <linux@daniel-bauer.com> Date: Sun, 9 Jul 2023 13:00:39 +0200
Just the same as described in my first post happened again tonight:
Suddenly (like after approx. 100 of running normal) the connections on eth0 tpo the IP's behind the switch get lost. I can ping the switch, but not the other IP's connected to that switch.
...
BUT: plugging the the switch to my laptop all IP's are available on the laptop immediately, then plugging back the cable to the PC they appear there as well...
...
The only think I can think of that would cause this behavior is that somehow the switch is being fooled into thinking that the Ethernet address for that port has changed when in fact it hasn't. (That should only explain failure to receive packets, but depending on the nature of the failure, it might screw up sending as well.)
What could make the switch being fooled - after 7 days working uptime?
Plugging in another system forces the switch to reconsider, which fixes the problem.
Ok, that explains to me why plugging it into the laptop makes a change.
And if attempting to make connections from your PC fails, then it's not surprising that unplugging/replugging doesn't help either. This also goes a long way to proving that it's not your PC's fault.
Have you tried permuting the connections to the switch? (And sorry if this has already been suggested.)
Sorry for my lack of English... With "permuting the connections to the switch" you mean plugging the cable into another port/plug of the switch? Actually I haven't tried this.
... How long did you leave it unplugged? Small switches don't need much power, so if they have an even halfway decent power supply, they can remember routing information for a surprisingly long time, perhaps a few minutes even. Or there may even be an NVRAM cache for routing info.
Only some seconds, maybe half a minute... -- Daniel Bauer photographer Basel Málaga https://www.patreon.com/danielbauer https://www.daniel-bauer.com
From: Daniel Bauer <linux@daniel-bauer.com> Date: Mon, 10 Jul 2023 10:45:30 +0200 Am 10.07.23 um 08:33 schrieb Bob Rogers:
The only think I can think of that would cause this behavior is that somehow the switch is being fooled into thinking that the Ethernet address for that port has changed when in fact it hasn't. (That should only explain failure to receive packets, but depending on the nature of the failure, it might screw up sending as well.)
What could make the switch being fooled - after 7 days working uptime? I have no theory there. I've been playing with networks for almost forty hears, but I have to say you have an unusually weird situation on your hands. Even in the early of dumb 10baseT switches, it was easy to persuade them to update their routing information by pinging in the other direction, a solution which obviously isn't working for you.
Plugging in another system forces the switch to reconsider, which fixes the problem.
Ok, that explains to me why plugging it into the laptop makes a change. Yes, that was a big clue in that particular direction.
And if attempting to make connections from your PC fails, then it's not surprising that unplugging/replugging doesn't help either. This also goes a long way to proving that it's not your PC's fault.
Have you tried permuting the connections to the switch? (And sorry if this has already been suggested.)
Sorry for my lack of English... With "permuting the connections to the switch" you mean plugging the cable into another port/plug of the switch? Yes. Actually I haven't tried this. It would be interesting to know if the problem stays with the port, or follows your PC. Or, if it requires the combination of port and PC, then moving the cable will "cure" it. In any case, you might then decide it would be worth replacing the switch.
... How long did you leave it unplugged? Small switches don't need much power, so if they have an even halfway decent power supply, they can remember routing information for a surprisingly long time, perhaps a few minutes even. Or there may even be an NVRAM cache for routing info.
Only some seconds, maybe half a minute... -- Daniel Bauer photographer Basel Málaga So perhaps long enough, perhaps not. Looking at the datasheet for the Netgear GS308PP [1], it doesn't look like it has an NVRAM cache for its MAC address table. So maybe next time this happens, you could try unplugging the switch for a probably-excessive 5 minutes while keeping the PC plugged in, and seeing if the PC can still connnect after repowering the switch. And unplug the adapter from the wall while keeping the switch connected to the adapter, so the switch can drain the capacitor(s) in the adaptor power supply. The datasheet also says that the Netgear GS308PP has 4K MAC address table entries, so we can rule out table overflow as a reason for "forgetting" your PC. ;-} -- Bob Rogers http://www.rgrjr.com/ [1] https://www.netgear.com/images/datasheet/switches/300-Series_Unmanaged_PoE_D...
On 2023-07-02 14:06, Daniel Bauer wrote:
I have some cameras connected with eth-cables to a switch and from there to a computer (OS 15.5, using zoneminder for the cameras). It works.
But this morning I saw that tonight the connection to the cameras was lost. I could ping the switch, but not the cameras. "arp -a" showed the IP's of the cameras but with "[IP] at incomplete ...".
I checked all cables. I rebooted. I switched off/on electricity for computer/switch/cameras. I unplugged the switch's cable to the computer and plugged it again.
No change.
I plugged the eth cable to my laptop (that I used before for this task, using OS 15.3) and all connections worked...
Plugged back the eth cable to the computer - and the connections work again, all cameras pingable and visible. Magic.
There are no messages in var/log, only the zoneminder-log said "no connection to..."
What happened here?
Your setup is, I think: +-----------------------------------+ | switch 8 mouths | | | +-----------------------------------+ | | | | | | | | | | mini cam cam cam router pc 1 2 3 Normally, it all works. When it fails: ping from mini pc to sw, works ping from mini pc to camera, fails ping to router? ping to laptop (tried)? The SW has to be involved in the failure somehow. The culprit can not be your computer alone. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
Am 09.07.23 um 20:39 schrieb Carlos E. R.:
On 2023-07-02 14:06, Daniel Bauer wrote:
I have some cameras connected with eth-cables to a switch and from there to a computer (OS 15.5, using zoneminder for the cameras). It works.
But this morning I saw that tonight the connection to the cameras was lost. I could ping the switch, but not the cameras. "arp -a" showed the IP's of the cameras but with "[IP] at incomplete ...".
I checked all cables. I rebooted. I switched off/on electricity for computer/switch/cameras. I unplugged the switch's cable to the computer and plugged it again.
No change.
I plugged the eth cable to my laptop (that I used before for this task, using OS 15.3) and all connections worked...
Plugged back the eth cable to the computer - and the connections work again, all cameras pingable and visible. Magic.
There are no messages in var/log, only the zoneminder-log said "no connection to..."
What happened here?
Your setup is, I think:
+-----------------------------------+ | switch 8 mouths | | | +-----------------------------------+ | | | | | | | | | | mini cam cam cam router pc 1 2 3
Normally, it all works.
When it fails:
ping from mini pc to sw, works
Not sure anymore, I think the switch itself has no IP (?). What works is ping to eth0, with the fixed IP I defined in networkmanager.
ping from mini pc to camera, fails
yes
ping to router?
There is no router. Only Mini_PC to switch, switch to cameras. WiFi is turned off. No internet connection wanted.
ping to laptop (tried)?
Haven't tried. Need another cable. Will try while everything works to check the new cable, and then try again, when the error occurs the next time.
The SW has to be involved in the failure somehow. The culprit can not be your computer alone.
I posted on it's forum yesterday, with not a lot of hope, because actually I cannot imagine that a software could stop my network working, especially because it's the same on the laptop and on the PC. But well... -- Daniel Bauer photographer Basel Málaga https://www.patreon.com/danielbauer https://www.daniel-bauer.com
On 2023-07-10 10:37, Daniel Bauer wrote:
Am 09.07.23 um 20:39 schrieb Carlos E. R.:
On 2023-07-02 14:06, Daniel Bauer wrote:
I have some cameras connected with eth-cables to a switch and from there to a computer (OS 15.5, using zoneminder for the cameras). It works.
But this morning I saw that tonight the connection to the cameras was lost. I could ping the switch, but not the cameras. "arp -a" showed the IP's of the cameras but with "[IP] at incomplete ...".
I checked all cables. I rebooted. I switched off/on electricity for computer/switch/cameras. I unplugged the switch's cable to the computer and plugged it again.
No change.
I plugged the eth cable to my laptop (that I used before for this task, using OS 15.3) and all connections worked...
Plugged back the eth cable to the computer - and the connections work again, all cameras pingable and visible. Magic.
There are no messages in var/log, only the zoneminder-log said "no connection to..."
What happened here?
Your setup is, I think:
+-----------------------------------+ | switch 8 mouths | | | +-----------------------------------+ | | | | | | | | | | mini cam cam cam router pc 1 2 3
Normally, it all works.
When it fails:
ping from mini pc to sw, works
Not sure anymore, I think the switch itself has no IP (?). What works is ping to eth0, with the fixed IP I defined in networkmanager.
Ah. Ping to eth0 is something to test, but it doesn't go outside. It is quite possible, though, that the switch doesn't have an IP, because it is unmanaged. Thus, you need to connect to it something different than cameras, like the laptop.
ping from mini pc to camera, fails
yes
ping to router?
There is no router. Only Mini_PC to switch, switch to cameras. WiFi is turned off. No internet connection wanted.
Ah, I thought so, wasn't sure. Wait, then there is no dhcp server, unless you put one in the computer. Are everything on fixed IPs? And there is no GW in the configuration. Try the "route" command in the computer.
ping to laptop (tried)?
Haven't tried. Need another cable. Will try while everything works to check the new cable, and then try again, when the error occurs the next time.
Yep. Try ping from laptop to everything.
The SW has to be involved in the failure somehow. The culprit can not be your computer alone.
I posted on it's forum yesterday, with not a lot of hope, because actually I cannot imagine that a software could stop my network working, especially because it's the same on the laptop and on the PC. But well...
Yes, I noticed the forum yesterday. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
Like every 8 days my mini-computer loses cabled network connection (see original post for details). It happened again today. Plugging the pc<->switch cable to another plug on the switch didn't change anything. I shot down the pc, unplugged pc and switch from the wall (electricity) and left it more than an hour. After boot the problem was still there, none of the cameras could be pinged. I additionally connected my laptop to the switch, leaving all other connections as is. As I used the mini-pc as a replacement for the laptop for the purpose of the cameras I copied the fixed IP-setting. Both machines thus have eth0 configured as xxx.xx.0.1. Ifconfig on the laptop told me that the laptop confirmed that it has the same IP as the mini-pc! I thought that such as misconfiguration should not run or lead to problems, but no: I could ping the cameras from the laptop. And then, immediately, I could also ping them again from the mini-pc. Why can the laptop ping the cameras, and after he does, suddenly the mini-pc can, too? But no other means to make the eth0 connection work again. For me this is very strange. Anybody can find an explanation and a hint to a way how I could solve the problem? Thanks for your time! Daniel (I then changed the fixed IP on the laptop to xxx.xx.0.2 so that I could ping or ssh to the mini-pc. It works) Am 02.07.23 um 14:06 schrieb Daniel Bauer:
I have some cameras connected with eth-cables to a switch and from there to a computer (OS 15.5, using zoneminder for the cameras). It works.
But this morning I saw that tonight the connection to the cameras was lost. I could ping the switch, but not the cameras. "arp -a" showed the IP's of the cameras but with "[IP] at incomplete ...".
I checked all cables. I rebooted. I switched off/on electricity for computer/switch/cameras. I unplugged the switch's cable to the computer and plugged it again.
No change.
I plugged the eth cable to my laptop (that I used before for this task, using OS 15.3) and all connections worked...
Plugged back the eth cable to the computer - and the connections work again, all cameras pingable and visible. Magic.
There are no messages in var/log, only the zoneminder-log said "no connection to..."
What happened here?
-- Daniel Bauer photographer Basel Málaga https://www.patreon.com/danielbauer https://www.daniel-bauer.com
On 2023-07-16 19:01, Daniel Bauer wrote:
Like every 8 days my mini-computer loses cabled network connection (see original post for details). It happened again today.
Is it every 8 days, like a clock?
Plugging the pc<->switch cable to another plug on the switch didn't change anything.
I shot down the pc, unplugged pc and switch from the wall (electricity) and left it more than an hour. After boot the problem was still there, none of the cameras could be pinged.
I additionally connected my laptop to the switch, leaving all other connections as is.
As I used the mini-pc as a replacement for the laptop for the purpose of the cameras I copied the fixed IP-setting. Both machines thus have eth0 configured as xxx.xx.0.1. Ifconfig on the laptop told me that the laptop confirmed that it has the same IP as the mini-pc!
I thought that such as misconfiguration should not run or lead to problems, but no: I could ping the cameras from the laptop.
And then, immediately, I could also ping them again from the mini-pc.
I had a wild hunch that this would be so :-)
Why can the laptop ping the cameras, and after he does, suddenly the mini-pc can, too? But no other means to make the eth0 connection work again.
No idea at all. No explanation. We could suspect the cameras... but what of?
For me this is very strange. Anybody can find an explanation and a hint to a way how I could solve the problem?
Thanks for your time!
Daniel
(I then changed the fixed IP on the laptop to xxx.xx.0.2 so that I could ping or ssh to the mini-pc. It works)
-- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
Am 16.07.23 um 20:47 schrieb Carlos E. R.:
On 2023-07-16 19:01, Daniel Bauer wrote:
Like every 8 days my mini-computer loses cabled network connection (see original post for details). It happened again today.
Is it every 8 days, like a clock?
I can only say from my emails here to that list that I sent the days it happened: 2., 9, and 16. of July, always during the night before (don't know the hour, just see in the morning that it doesn't work anymore) Always the night from Saturday to Sunday... ...
I additionally connected my laptop to the switch, leaving all other connections as is. ... I could ping the cameras from the laptop.
And then, immediately, I could also ping them again from the mini-pc.
I had a wild hunch that this would be so :-)
Why can the laptop ping the cameras, and after he does, suddenly the mini-pc can, too? But no other means to make the eth0 connection work again.
No idea at all. No explanation.
We could suspect the cameras... but what of?
I don't think so. This never happened with the laptop. Also IIRC (not 100% sure, but 99.9...) the lamps on the plugs on the switch where the cameras are connected were blinking fast as usual. Apart of the hardware the other difference is that the laptop runs OS 15.3 and the mini-pc 15.5. - Could there be a setting somewhere to shut down eth0 from time to time? - Could such a thing exist in the hardware? BIOS? It is strange that it always happens Saturday nights, but maybe its coincidence. -- Daniel Bauer photographer Basel Málaga Twitter: @Marsfotografo (often explicit nudes) https://www.patreon.com/danielbauer https://www.daniel-bauer.com (nudes)
On Sun, 16 Jul 2023 21:01:26 +0200 Daniel Bauer <linux@daniel-bauer.com> wrote:
Am 16.07.23 um 20:47 schrieb Carlos E. R.:
On 2023-07-16 19:01, Daniel Bauer wrote:
Like every 8 days my mini-computer loses cabled network connection (see original post for details). It happened again today.
Is it every 8 days, like a clock?
I can only say from my emails here to that list that I sent the days it happened: 2., 9, and 16. of July, always during the night before (don't know the hour, just see in the morning that it doesn't work anymore)
Always the night from Saturday to Sunday...
Err, so you're saying it is every seven days, not every eight days?! And always the same day of the week? What about the time; is that regular? (you could leave ping in a shell script loop every minute or so to see)
Am 16.07.23 um 21:19 schrieb Dave Howorth:
On Sun, 16 Jul 2023 21:01:26 +0200 Daniel Bauer <linux@daniel-bauer.com> wrote:
Am 16.07.23 um 20:47 schrieb Carlos E. R.:
On 2023-07-16 19:01, Daniel Bauer wrote:
Like every 8 days my mini-computer loses cabled network connection (see original post for details). It happened again today.
Is it every 8 days, like a clock?
I can only say from my emails here to that list that I sent the days it happened: 2., 9, and 16. of July, always during the night before (don't know the hour, just see in the morning that it doesn't work anymore)
Always the night from Saturday to Sunday...
Err, so you're saying it is every seven days, not every eight days?! And always the same day of the week?
Yeah, counting the days gets more complicated when one gets old, it seems :-) But yes, until now it occurred always in the night from Saturday to Sunday.
What about the time; is that regular?
I don't know. The last times I repaired it Sunday morning, today I did it in the afternoon. Maybe it stops later the next time?
(you could leave ping in a shell script loop every minute or so to see)
How could I do that so that it only pings once every half an hour and adds the result to a file? When I type "ping ..." it pings endless until I break it with ctrl-c... -- Daniel Bauer photographer Basel Málaga Twitter: @Marsfotografo (often explicit nudes) https://www.patreon.com/danielbauer https://www.daniel-bauer.com (nudes)
* Daniel Bauer <linux@daniel-bauer.com> [07-16-23 15:36]:
Am 16.07.23 um 21:19 schrieb Dave Howorth:
On Sun, 16 Jul 2023 21:01:26 +0200 Daniel Bauer <linux@daniel-bauer.com> wrote:
Am 16.07.23 um 20:47 schrieb Carlos E. R.:
On 2023-07-16 19:01, Daniel Bauer wrote:
Like every 8 days my mini-computer loses cabled network connection (see original post for details). It happened again today.
Is it every 8 days, like a clock?
I can only say from my emails here to that list that I sent the days it happened: 2., 9, and 16. of July, always during the night before (don't know the hour, just see in the morning that it doesn't work anymore)
Always the night from Saturday to Sunday...
Err, so you're saying it is every seven days, not every eight days?! And always the same day of the week?
Yeah, counting the days gets more complicated when one gets old, it seems :-)
But yes, until now it occurred always in the night from Saturday to Sunday.
What about the time; is that regular?
I don't know.
The last times I repaired it Sunday morning, today I did it in the afternoon. Maybe it stops later the next time?
(you could leave ping in a shell script loop every minute or so to see)
How could I do that so that it only pings once every half an hour and adds the result to a file? When I type "ping ..." it pings endless until I break it with ctrl-c...
use the force Luke, look at the man file for "-i" and "-c" -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
On Sun, 16 Jul 2023 15:45:46 -0400 Patrick Shanahan <paka@opensuse.org> wrote:
* Daniel Bauer <linux@daniel-bauer.com> [07-16-23 15:36]:
Am 16.07.23 um 21:19 schrieb Dave Howorth:
On Sun, 16 Jul 2023 21:01:26 +0200 Daniel Bauer <linux@daniel-bauer.com> wrote:
Am 16.07.23 um 20:47 schrieb Carlos E. R.:
On 2023-07-16 19:01, Daniel Bauer wrote:
Like every 8 days my mini-computer loses cabled network connection (see original post for details). It happened again today.
Is it every 8 days, like a clock?
I can only say from my emails here to that list that I sent the days it happened: 2., 9, and 16. of July, always during the night before (don't know the hour, just see in the morning that it doesn't work anymore)
Always the night from Saturday to Sunday...
Err, so you're saying it is every seven days, not every eight days?! And always the same day of the week?
Yeah, counting the days gets more complicated when one gets old, it seems :-)
But yes, until now it occurred always in the night from Saturday to Sunday.
What about the time; is that regular?
I don't know.
The last times I repaired it Sunday morning, today I did it in the afternoon. Maybe it stops later the next time?
(you could leave ping in a shell script loop every minute or so to see)
How could I do that so that it only pings once every half an hour and adds the result to a file? When I type "ping ..." it pings endless until I break it with ctrl-c...
use the force Luke, look at the man file for "-i" and "-c"
True, thanks Patrick. In a new terminal you could just start $ while [ 1 == 1 ]; do ping -i 60 -c 10 100.100.100.100; date; done where 100.100.100.100 is whatever network address
On Sun, 16 Jul 2023 15:45:46 -0400, Patrick Shanahan <paka@opensuse.org> wrote:
* Daniel Bauer <linux@daniel-bauer.com> [07-16-23 15:36]:
How could I do that so that it only pings once every half an hour and adds the result to a file? When I type "ping ..." it pings endless until I break it with ctrl-c...
use the force Luke, look at the man file for "-i" and "-c"
As the ping(8) man page suggests, when you ping your cameras to check connectivity, ping the local host's IP also, first, to verify that the local network interface is up. -- Robert Webb
On 2023-07-16 21:34, Daniel Bauer wrote:
Am 16.07.23 um 21:19 schrieb Dave Howorth:
On Sun, 16 Jul 2023 21:01:26 +0200 Daniel Bauer <linux@daniel-bauer.com> wrote:
Am 16.07.23 um 20:47 schrieb Carlos E. R.:
On 2023-07-16 19:01, Daniel Bauer wrote:
Like every 8 days my mini-computer loses cabled network connection (see original post for details). It happened again today.
Is it every 8 days, like a clock?
I can only say from my emails here to that list that I sent the days it happened: 2., 9, and 16. of July, always during the night before (don't know the hour, just see in the morning that it doesn't work anymore)
Always the night from Saturday to Sunday...
Err, so you're saying it is every seven days, not every eight days?! And always the same day of the week?
Yeah, counting the days gets more complicated when one gets old, it seems :-)
But yes, until now it occurred always in the night from Saturday to Sunday.
Ok, another wild idea: check the journal or syslog those nights, something else happening that night. Perhaps a cron job or a timer.
What about the time; is that regular?
I don't know.
The last times I repaired it Sunday morning, today I did it in the afternoon. Maybe it stops later the next time?
(you could leave ping in a shell script loop every minute or so to see)
How could I do that so that it only pings once every half an hour and adds the result to a file? When I type "ping ..." it pings endless until I break it with ctrl-c...
It is possible to put a ping in the crontab every five minutes. ping -c 3 cameras_ips crontab -e [enter] */5 * * * * ping -c 3 cameras_ips >> /home/yourname/ping.log Not the only way to do it, there are ping versions where you can adjust the cycle time: ping -T -i 60 cameras_ips | tee -a ping2.log -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
From: "Carlos E. R." <robin.listas@telefonica.net> Date: Sun, 16 Jul 2023 21:48:58 +0200 . . . Not the only way to do it, there are ping versions where you can adjust the cycle time: ping -T -i 60 cameras_ips | tee -a ping2.log -- Cheers / Saludos, Carlos E. R. Another approach is setting up a terminal window, doing SSH to another system, and running the following command: while true; do date; sleep 300; done That will give you a date stamp every five minutes (depending on the sleep arg) that will stop when the connection goes down. -- Bob
On 2023-07-16 21:54, Bob Rogers wrote:
From: "Carlos E. R." <> Date: Sun, 16 Jul 2023 21:48:58 +0200
Another approach is setting up a terminal window, doing SSH to another system, and running the following command:
while true; do date; sleep 300; done
That will give you a date stamp every five minutes (depending on the sleep arg) that will stop when the connection goes down.
AFAIK this is an isolated LAN with only the cameras and a single computer to log what they see. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On 7/16/23 11:34, Daniel Bauer wrote:
Am 16.07.23 um 21:19 schrieb Dave Howorth:
On Sun, 16 Jul 2023 21:01:26 +0200 Daniel Bauer <linux@daniel-bauer.com> wrote:
Am 16.07.23 um 20:47 schrieb Carlos E. R.:
On 2023-07-16 19:01, Daniel Bauer wrote:
Like every 8 days my mini-computer loses cabled network connection (see original post for details). It happened again today.
Is it every 8 days, like a clock?
I can only say from my emails here to that list that I sent the days it happened: 2., 9, and 16. of July, always during the night before (don't know the hour, just see in the morning that it doesn't work anymore)
Always the night from Saturday to Sunday...
Err, so you're saying it is every seven days, not every eight days?! And always the same day of the week?
Yeah, counting the days gets more complicated when one gets old, it seems :-)
But yes, until now it occurred always in the night from Saturday to Sunday.
What about the time; is that regular?
I don't know.
The last times I repaired it Sunday morning, today I did it in the afternoon. Maybe it stops later the next time?
(you could leave ping in a shell script loop every minute or so to see)
How could I do that so that it only pings once every half an hour and adds the result to a file? When I type "ping ..." it pings endless until I break it with ctrl-c...
I have a little "smart" gizmo to turn the power off, for 1 minute, every Thursday morning at 2:24. The cable modem/router and my wifi router are plugged into it. To verify it was working I... From the crontab: # Minute Hour mday month wday command 23 02 * * 4 /home/bill/bin/ptyd You could use */2 for the hour. ptyd (ping till you drop) looks like: date ping -c2 www.yahoo.com <actually I use my domain> sleep 20 <and that's repeated for a couple of minutes>
On 7/16/23 12:01, Daniel Bauer wrote:
We could suspect the cameras... but what of?
I don't think so. This never happened with the laptop. Also IIRC (not 100% sure, but 99.9...) the lamps on the plugs on the switch where the cameras are connected were blinking fast as usual.
Apart of the hardware the other difference is that the laptop runs OS 15.3 and the mini-pc 15.5.
- Could there be a setting somewhere to shut down eth0 from time to time? - Could such a thing exist in the hardware? BIOS?
It is strange that it always happens Saturday nights, but maybe its coincidence.
Hi Daniel, I have no idea if this is related, but I've got a couple of Reolink PoE cameras now, and they automatically reboot themselves every every Sunday morning by default. I think they do this to make sure that any malware collected during the week is completely removed. It probably improves overall reliability too. The timing of the reboot can be changed, and it can be turned off. Does your system have such a feature? Could it be related somehow to your problem? Regards, Lew
Am 16.07.23 um 23:08 schrieb Lew Wolfgang:
On 7/16/23 12:01, Daniel Bauer wrote: ...
It is strange that it always happens Saturday nights, but maybe its coincidence.
Hi Daniel,
I have no idea if this is related, but I've got a couple of Reolink PoE cameras now, and they automatically reboot themselves every every Sunday morning by default. I think they do this to make sure that any malware collected during the week is completely removed. It probably improves overall reliability too. The timing of the reboot can be changed, and it can be turned off. Does your system have such a feature? Could it be related somehow to your problem?
Regards, Lew
That was the right hint. Thank you Lew! In fact my cameras (also Reolink) are set to reboot every Sunday morning at 02am. So I logged in directly to the web-interface of one of the cameras from the mini-PC and clicked "reboot". The camera disappeared and the "waiting symbol" was shown - for ever. The camera didn't come back and wasn't reachable per ping. So this part of the problem is clear now. The cameras want to reboot on Sunday morning and then don't boot... BUT: Switching the cable again to the laptop, the camera booted. Also, I then went to the web interface of the same camera, but this time from the laptop, clicked "reboot". It rebooted immediately. I repeated several times: I go to the web interface of the camera from the mini-pc: reboot does /not/ work. I do the same from the laptop: camera reboots immediately and connection is re-established automatically. Note: the only thing I changed was unplugging the eth-cable that connects mini-pc and switch on the side of the pc and plugged it into the laptop. All the rest is the same, untouched. Question: - Why does the reboot of the camera work if it is connected to the laptop, but not when connected to the pc? There must be something wrong on the pc's side, but what? Does OS 15.5 (pc) handle eth connections differently than 15.3 (laptop)? How can I come even closer to the solution? -- Daniel Bauer photographer Basel Málaga Twitter: @Marsfotografo (often explicit nudes) https://www.patreon.com/danielbauer https://www.daniel-bauer.com (nudes)
Op maandag 17 juli 2023 17:40:42 CEST schreef Daniel Bauer:
BUT:
Switching the cable again to the laptop, the camera booted.
Where does the camera boot from? An internal resource or an external resource, like from your laptop. During boot where does it get its IP address from? A DHCP server on your laptop? Is there another outside resource needed when booting, which is not available. -- fr.gr. member openSUSE Freek de Kruijf
Am 17.07.23 um 17:52 schrieb Freek de Kruijf:
Op maandag 17 juli 2023 17:40:42 CEST schreef Daniel Bauer:
BUT:
Switching the cable again to the laptop, the camera booted.
Where does the camera boot from? An internal resource or an external resource, like from your laptop.
The cameras have their own web-interface that is reachable via their IP with firefox (in my case).
During boot where does it get its IP address from? A DHCP server on your laptop?
The cameras have a settings page, where (beneath a lot of other things) their fixed IP is set. The eth0 IP is set fixed ("manual" for IPv4 in Network manager settings) on both the laptop and the pc, so there should be no DHCP.
Is there another outside resource needed when booting, which is not available.
No. There is a "reset" (to factory default) button, and a "reboot" button in the camera's web-interface. I think it does the reboot all by itself. As much as I know everything is saved within the camera (settings are the same, no matter from which computer I connect to them). -- Daniel Bauer photographer Basel Málaga Twitter: @Marsfotografo (often explicit nudes) https://www.patreon.com/danielbauer https://www.daniel-bauer.com (nudes)
On 2023-07-17 18:10, Daniel Bauer wrote:
Am 17.07.23 um 17:52 schrieb Freek de Kruijf:
Op maandag 17 juli 2023 17:40:42 CEST schreef Daniel Bauer:
BUT:
Switching the cable again to the laptop, the camera booted.
Where does the camera boot from? An internal resource or an external resource, like from your laptop.
The cameras have their own web-interface that is reachable via their IP with firefox (in my case).
During boot where does it get its IP address from? A DHCP server on your laptop?
The cameras have a settings page, where (beneath a lot of other things) their fixed IP is set.
The eth0 IP is set fixed ("manual" for IPv4 in Network manager settings) on both the laptop and the pc, so there should be no DHCP.
Is there another outside resource needed when booting, which is not available.
No. There is a "reset" (to factory default) button, and a "reboot" button in the camera's web-interface. I think it does the reboot all by itself.
As much as I know everything is saved within the camera (settings are the same, no matter from which computer I connect to them).
Nevertheless, there is something the cameras want from the laptop, and if the laptop is not present, they stall. You could use "ethereal" or "tcdump" to log the connection of one camera to the laptop when you boot that camera. As your cameras and computer are on an isolated network, they can not get infected by malware, so you could disable the automatic boot. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On 7/17/2023 4:30 PM, Carlos E. R. wrote:
On 2023-07-17 18:10, Daniel Bauer wrote:
Am 17.07.23 um 17:52 schrieb Freek de Kruijf:
Op maandag 17 juli 2023 17:40:42 CEST schreef Daniel Bauer:
BUT:
Switching the cable again to the laptop, the camera booted.
Where does the camera boot from? An internal resource or an external resource, like from your laptop.
The cameras have their own web-interface that is reachable via their IP with firefox (in my case).
During boot where does it get its IP address from? A DHCP server on your laptop?
The cameras have a settings page, where (beneath a lot of other things) their fixed IP is set.
The eth0 IP is set fixed ("manual" for IPv4 in Network manager settings) on both the laptop and the pc, so there should be no DHCP.
Is there another outside resource needed when booting, which is not available.
No. There is a "reset" (to factory default) button, and a "reboot" button in the camera's web-interface. I think it does the reboot all by itself.
As much as I know everything is saved within the camera (settings are the same, no matter from which computer I connect to them).
Nevertheless, there is something the cameras want from the laptop, and if the laptop is not present, they stall.
You could use "ethereal" or "tcdump" to log the connection of one camera to the laptop when you boot that camera.
I've not read each and every post, but I suspect the cameras will turn out to be set to obtain address via DHCP, the LAPTOP is enabled to provide DHCP (as server) and the PC is not.
As your cameras and computer are on an isolated network, they can not get infected by malware, so you could disable the automatic boot.
Not a sure bet. MALWARE can hitch a ride on removable media. "AIR GAP" is not a panacea. joe a.
On 2023-07-17 22:47, joe a wrote:
On 7/17/2023 4:30 PM, Carlos E. R. wrote:
On 2023-07-17 18:10, Daniel Bauer wrote:
Am 17.07.23 um 17:52 schrieb Freek de Kruijf:
Op maandag 17 juli 2023 17:40:42 CEST schreef Daniel Bauer:
BUT:
Switching the cable again to the laptop, the camera booted.
Where does the camera boot from? An internal resource or an external resource, like from your laptop.
The cameras have their own web-interface that is reachable via their IP with firefox (in my case).
During boot where does it get its IP address from? A DHCP server on your laptop?
The cameras have a settings page, where (beneath a lot of other things) their fixed IP is set.
...........************************
The eth0 IP is set fixed ("manual" for IPv4 in Network manager settings) on both the laptop and the pc, so there should be no DHCP.
Is there another outside resource needed when booting, which is not available.
No. There is a "reset" (to factory default) button, and a "reboot" button in the camera's web-interface. I think it does the reboot all by itself.
As much as I know everything is saved within the camera (settings are the same, no matter from which computer I connect to them).
Nevertheless, there is something the cameras want from the laptop, and if the laptop is not present, they stall.
You could use "ethereal" or "tcdump" to log the connection of one camera to the laptop when you boot that camera.
I've not read each and every post, but I suspect the cameras will turn out to be set to obtain address via DHCP, the LAPTOP is enabled to provide DHCP (as server) and the PC is not.
No, he said they are configured on fixed addresses.
As your cameras and computer are on an isolated network, they can not get infected by malware, so you could disable the automatic boot.
Not a sure bet. MALWARE can hitch a ride on removable media. "AIR GAP" is not a panacea.
Common... it is Linux, and he is not daft. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On 7/17/2023 5:28 PM, Carlos E. R. wrote:
On 2023-07-17 22:47, joe a wrote:
On 7/17/2023 4:30 PM, Carlos E. R. wrote:
On 2023-07-17 18:10, Daniel Bauer wrote:
Am 17.07.23 um 17:52 schrieb Freek de Kruijf:
Op maandag 17 juli 2023 17:40:42 CEST schreef Daniel Bauer:
BUT:
Switching the cable again to the laptop, the camera booted.
Where does the camera boot from? An internal resource or an external resource, like from your laptop.
The cameras have their own web-interface that is reachable via their IP with firefox (in my case).
During boot where does it get its IP address from? A DHCP server on your laptop?
The cameras have a settings page, where (beneath a lot of other things) their fixed IP is set.
...........************************
The eth0 IP is set fixed ("manual" for IPv4 in Network manager settings) on both the laptop and the pc, so there should be no DHCP.
Is there another outside resource needed when booting, which is not available.
No. There is a "reset" (to factory default) button, and a "reboot" button in the camera's web-interface. I think it does the reboot all by itself.
As much as I know everything is saved within the camera (settings are the same, no matter from which computer I connect to them).
Nevertheless, there is something the cameras want from the laptop, and if the laptop is not present, they stall.
You could use "ethereal" or "tcdump" to log the connection of one camera to the laptop when you boot that camera.
I've not read each and every post, but I suspect the cameras will turn out to be set to obtain address via DHCP, the LAPTOP is enabled to provide DHCP (as server) and the PC is not.
No, he said they are configured on fixed addresses.
As your cameras and computer are on an isolated network, they can not get infected by malware, so you could disable the automatic boot.
Not a sure bet. MALWARE can hitch a ride on removable media. "AIR GAP" is not a panacea.
Common... it is Linux, and he is not daft.
Since when is Linux immune to malware?
On 7/17/2023 5:28 PM, Carlos E. R. wrote:
On 2023-07-17 22:47, joe a wrote:
On 7/17/2023 4:30 PM, Carlos E. R. wrote:
On 2023-07-17 18:10, Daniel Bauer wrote:
Am 17.07.23 um 17:52 schrieb Freek de Kruijf:
Op maandag 17 juli 2023 17:40:42 CEST schreef Daniel Bauer:
BUT:
Switching the cable again to the laptop, the camera booted.
Where does the camera boot from? An internal resource or an external resource, like from your laptop.
The cameras have their own web-interface that is reachable via their IP with firefox (in my case).
During boot where does it get its IP address from? A DHCP server on your laptop?
The cameras have a settings page, where (beneath a lot of other things) their fixed IP is set.
...........************************
The eth0 IP is set fixed ("manual" for IPv4 in Network manager settings) on both the laptop and the pc, so there should be no DHCP.
Is there another outside resource needed when booting, which is not available.
No. There is a "reset" (to factory default) button, and a "reboot" button in the camera's web-interface. I think it does the reboot all by itself.
As much as I know everything is saved within the camera (settings are the same, no matter from which computer I connect to them).
Nevertheless, there is something the cameras want from the laptop, and if the laptop is not present, they stall.
You could use "ethereal" or "tcdump" to log the connection of one camera to the laptop when you boot that camera.
I've not read each and every post, but I suspect the cameras will turn out to be set to obtain address via DHCP, the LAPTOP is enabled to provide DHCP (as server) and the PC is not.
No, he said they are configured on fixed addresses.
As stated, I did not read every post. You may note I asked for clarification in that regard in a query to the OP just a "few moments ago".
Op maandag 17 juli 2023 22:47:32 CEST schreef joe a:
On 7/17/2023 4:30 PM, Carlos E. R. wrote:
Nevertheless, there is something the cameras want from the laptop, and if the laptop is not present, they stall.
You could use "ethereal" or "tcdump" to log the connection of one camera to the laptop when you boot that camera.
I've not read each and every post, but I suspect the cameras will turn out to be set to obtain address via DHCP, the LAPTOP is enabled to provide DHCP (as server) and the PC is not.
So the mystery is solved. When you make the camera to use a static address and don't forget, in that case, to provide a gateway address and netmask, your camera will be independent of the laptop and the reboot will succeed. Maybe the gateway address is not even necessary, but the netmask is crucial to be able to communicate with your laptop or PC, provided these systems have address in the same network with the same netmask. -- fr.gr. member openSUSE Freek de Kruijf
On 2023-07-17 23:29, Freek de Kruijf wrote:
Op maandag 17 juli 2023 22:47:32 CEST schreef joe a:
On 7/17/2023 4:30 PM, Carlos E. R. wrote:
Nevertheless, there is something the cameras want from the laptop, and if the laptop is not present, they stall.
You could use "ethereal" or "tcdump" to log the connection of one camera to the laptop when you boot that camera.
I've not read each and every post, but I suspect the cameras will turn out to be set to obtain address via DHCP, the LAPTOP is enabled to provide DHCP (as server) and the PC is not.
So the mystery is solved.
When you make the camera to use a static address and don't forget, in that case, to provide a gateway address and netmask, your camera will be independent of the laptop and the reboot will succeed. Maybe the gateway address is not even necessary, but the netmask is crucial to be able to communicate with your laptop or PC, provided these systems have address in the same network with the same netmask.
being an isolated LAN, there can not be a gateway. Ok, you can configure one, but it would be a fake. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On 7/17/23 13:47, joe a wrote:
You could use "ethereal" or "tcdump" to log the connection of one camera to the laptop when you boot that camera.
I've not read each and every post, but I suspect the cameras will turn out to be set to obtain address via DHCP, the LAPTOP is enabled to provide DHCP (as server) and the PC is not.
Daniel said he configured the cameras for static IP. IIRC. I've got mine (same brand) for DHCP from my Zyxel router. But there's also a setting there for DNS. It can be "Auto" or "Static". Mine is auto, how about yours, Daniel? Also have you tried running nmap against the cameras? Maybe try it from each of your computers. Here's one of mine: Starting Nmap 7.92 ( https://nmap.org ) at 2023-07-17 15:45 PDT Nmap scan report for 192.168..x.y Host is up (0.00093s latency). Not shown: 996 closed tcp ports (reset) PORT STATE SERVICE 53/tcp filtered domain 80/tcp open http 443/tcp open https 9000/tcp open cslistener No exact OS matches for host (If you know what OS is running on it, see https://nmap.org/submit/ ).
As your cameras and computer are on an isolated network, they can not get infected by malware, so you could disable the automatic boot.
Not a sure bet. MALWARE can hitch a ride on removable media. "AIR GAP" is not a panacea.
That's true. You can add a SD card in these cameras for local storage. so they can operate independent of cloud services. Malware could conceivably hitch a ride on the SD card I guess. The camera's run embedded Linux. If you're interested, here's an analysis of hacking into a Reolink camera. Great sport! https://www.thirtythreeforty.net/posts/2020/05/hacking-reolink-cameras-for-f... Regards, Lew
Thanks a lot everybody for the very valued input! Am 18.07.23 um 02:10 schrieb Lew Wolfgang:
Daniel said he configured the cameras for static IP. IIRC. I've got mine (same brand) for DHCP from my Zyxel router.
But there's also a setting there for DNS. It can be "Auto" or "Static". Mine is auto, how about yours, Daniel?
Hm. So I went again to the cameras web-interface. In fact there is a fixed IP-adress, BUT also DHCP was activated (this is only visible if you click a button, so I haven't seen it before). I changed this to "static" and rebooted the camera: success. Just to be sure, connected from the mini-pc I changed back to DHCP - reboot did /not/ work. Changed again to "static" - reboot works. Did the same on the laptop - camera reboot worked no matter if that camera setting was DHCP or static... So now I changed that in all cameras to static and hope my problem is solved... What I still don't understand is why it works on the laptop with that camera-setting to DHCP, but not on the mini-PC. With my extremely limited knowledge I just typed "DHCP" in Yast software search, and see that laptop and pc have the same packages installed. They must be with default values because I never changed anything in these things... Well, I'll see next Sunday what happens. If it didn't solve the problem I'll annoy you with another message here :-) Thanks again for all the help! Daniel -- Daniel Bauer photographer Basel Málaga Twitter: @Marsfotografo (often explicit nudes) https://www.patreon.com/danielbauer https://www.daniel-bauer.com (nudes)
On 2023-07-18 11:05, Daniel Bauer wrote:
Thanks a lot everybody for the very valued input!
Am 18.07.23 um 02:10 schrieb Lew Wolfgang:
Daniel said he configured the cameras for static IP. IIRC. I've got mine (same brand) for DHCP from my Zyxel router.
But there's also a setting there for DNS. It can be "Auto" or "Static". Mine is auto, how about yours, Daniel?
Hm. So I went again to the cameras web-interface. In fact there is a fixed IP-adress, BUT also DHCP was activated (this is only visible if you click a button, so I haven't seen it before).
Ohhh.
I changed this to "static" and rebooted the camera: success.
:-))
Just to be sure, connected from the mini-pc I changed back to DHCP - reboot did /not/ work. Changed again to "static" - reboot works.
Did the same on the laptop - camera reboot worked no matter if that camera setting was DHCP or static...
Maybe you have a dhcp server running in the laptop for some forgotten reason ;-)
So now I changed that in all cameras to static and hope my problem is solved...
What I still don't understand is why it works on the laptop with that camera-setting to DHCP, but not on the mini-PC. With my extremely limited knowledge I just typed "DHCP" in Yast software search, and see that laptop and pc have the same packages installed. They must be with default values because I never changed anything in these things...
Well, I'll see next Sunday what happens. If it didn't solve the problem I'll annoy you with another message here :-)
as root in a terminal: systemctl status dhcp[tab][tab] Also, dnsmasq can do it.
Thanks again for all the help!
Welcome. An intriguing problem. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On Mon, 17 Jul 2023 17:10:54 -0700 Lew Wolfgang <wolfgang@sweet-haven.com> wrote:
On 7/17/23 13:47, joe a wrote:
You could use "ethereal" or "tcdump" to log the connection of one camera to the laptop when you boot that camera.
I've not read each and every post, but I suspect the cameras will turn out to be set to obtain address via DHCP, the LAPTOP is enabled to provide DHCP (as server) and the PC is not.
Daniel said he configured the cameras for static IP. IIRC. I've got mine (same brand) for DHCP from my Zyxel router.
But there's also a setting there for DNS. It can be "Auto" or "Static". Mine is auto, how about yours, Daniel?
Also have you tried running nmap against the cameras? Maybe try it from each of your computers.
Here's one of mine:
Starting Nmap 7.92 ( https://nmap.org ) at 2023-07-17 15:45 PDT Nmap scan report for 192.168..x.y Host is up (0.00093s latency). Not shown: 996 closed tcp ports (reset) PORT STATE SERVICE 53/tcp filtered domain 80/tcp open http 443/tcp open https 9000/tcp open cslistener No exact OS matches for host (If you know what OS is running on it, see https://nmap.org/submit/ ).
As your cameras and computer are on an isolated network, they can not get infected by malware, so you could disable the automatic boot.
Not a sure bet. MALWARE can hitch a ride on removable media. "AIR GAP" is not a panacea.
That's true. You can add a SD card in these cameras for local storage. so they can operate independent of cloud services.
I have some Reolink cameras too. They can operate independent of the cloud regardless of whether they have an SD card fitted. My cameras are isolated from the Intertubes and work just fine.
Malware could conceivably hitch a ride on the SD card I guess.
The camera's run embedded Linux. If you're interested, here's an analysis of hacking into a Reolink camera. Great sport!
https://www.thirtythreeforty.net/posts/2020/05/hacking-reolink-cameras-for-f...
Interesting article but somewhat out of date. You can access the cameras with a web connection to them. You can configure them to send video over FTP to a server etc etc. I have them connected to a Reolink NVR and then the video is backed up to a Linux server in a different place. So hopefully I will have video if anybody attacks them. Their support is pretty good and their support website has new information almost daily. Can be confusing sometimes but at least it's up to date. Oh and they replaced a failed camera without quibble under guarantee.
Regards, Lew
On 7/17/2023 12:10 PM, Daniel Bauer wrote:
Am 17.07.23 um 17:52 schrieb Freek de Kruijf: Op maandag 17 juli 2023 17:40:42 CEST schreef Daniel Bauer:
BUT:
Switching the cable again to the laptop, the camera booted.
Where does the camera boot from? An internal resource or an external resource, like from your laptop.
The cameras have their own web-interface that is reachable via their IP with firefox (in my case).
During boot where does it get its IP address from? A DHCP server on your laptop?
The cameras have a settings page, where (beneath a lot of other things) their fixed IP is set.
The eth0 IP is set fixed ("manual" for IPv4 in Network manager settings) on both the laptop and the pc, so there should be no DHCP.
Please clarify where the camera is getting its IP address from. Static, as specified via their Web Interface, or, is it set to get it's IP via DHCP? The setting of "STATIC" as the IP for the PC and LAPTOP has not bearing on: - if they are also setup as DHCP servers - if the CAMERA is setup for STATIC or DHCP. joe a.
On Mon, 17 Jul 2023 17:40:42 +0200 Daniel Bauer <linux@daniel-bauer.com> wrote:
Am 16.07.23 um 23:08 schrieb Lew Wolfgang:
On 7/16/23 12:01, Daniel Bauer wrote: ...
It is strange that it always happens Saturday nights, but maybe its coincidence.
Hi Daniel,
I have no idea if this is related, but I've got a couple of Reolink PoE cameras now, and they automatically reboot themselves every every Sunday morning by default. I think they do this to make sure that any malware collected during the week is completely removed. It probably improves overall reliability too. The timing of the reboot can be changed, and it can be turned off. Does your system have such a feature? Could it be related somehow to your problem?
Regards, Lew
That was the right hint. Thank you Lew!
In fact my cameras (also Reolink) are set to reboot every Sunday morning at 02am.
So I logged in directly to the web-interface of one of the cameras from the mini-PC and clicked "reboot". The camera disappeared and the "waiting symbol" was shown - for ever. The camera didn't come back and wasn't reachable per ping.
So this part of the problem is clear now. The cameras want to reboot on Sunday morning and then don't boot...
What firmware version is in the cameras? Is it up to date?
BUT:
Switching the cable again to the laptop, the camera booted.
Also, I then went to the web interface of the same camera, but this time from the laptop, clicked "reboot". It rebooted immediately.
I repeated several times:
I go to the web interface of the camera from the mini-pc: reboot does /not/ work. I do the same from the laptop: camera reboots immediately and connection is re-established automatically.
Note: the only thing I changed was unplugging the eth-cable that connects mini-pc and switch on the side of the pc and plugged it into the laptop. All the rest is the same, untouched.
Question:
- Why does the reboot of the camera work if it is connected to the laptop, but not when connected to the pc?
There must be something wrong on the pc's side, but what? Does OS 15.5 (pc) handle eth connections differently than 15.3 (laptop)? How can I come even closer to the solution?
On 2023/07/16 12:01, Daniel Bauer wrote: --- Are your ethernet devices using hard-linked modules in the kernel or do they load dynamically at runtime? Does your laptop put any of those devices to sleep after some time -- could they come up and search for where they should be? FWIW, I wrote a script to ensure the right drivers are loaded @ system boot -- AND that the right ports are associated with right wires. As an example, I use data something like: (FWIW, built-in mods are hardcoded into my kernel, so they always come up with fixed names). # Links that we _expect_ will come up with right names (built-mods) #Default_good=( $(echo eth{0..1}) ) # store as hash, with intfname as key and it's ethernet addr as the data # if2hw=([eth0]="00:15:17:bf:be:b2" [eth1]="00:15:17:bf:be:b3" # [eth2]="00:26:b9:48:71:e2" [eth3]="00:26:b9:48:71:e4" # [eth4]="a0:36:9f:15:c9:c0" [eth5]="a0:36:9f:15:c9:c2" )
On 2023-07-16 19:01, Daniel Bauer wrote:
Like every 8 days my mini-computer loses cabled network connection (see original post for details). It happened again today.
This doesn't correspond to any dhcp timeout, does it? FWIW -- my dhcp assigns permanent addrs on my net for some random devices that I don't want to have to try to figure out how to program, but do want to have constant names. the dhcp demon knows the hw-addrs of various ethernet devices and assigns them fixed IP addrs (it also has a dynamic range for 'guests') But example(s): Some devices that I want to have 'fixed' names for on my net: host Samsung-TV-LR { hardware ethernet a0:d7:f3:2f:14:aa; fixed-address Samsung-TV-LR.sc.tlinx.org; option host-name "SamsungTV"; } host Sony-BRP-LR { hardware ethernet 00:24:be:54:c3:af; fixed-address Sony-BRP-LR.sc.tlinx.org; option host-name "Sony-BRP-LR"; } --- Anyway, just some random thoughts...I could post my scripts, but they are rather specific to devices on my net....
participants (13)
-
Bill Swisher -
Bob Rogers -
Carlos E. R. -
Daniel Bauer -
Dave Howorth -
Freek de Kruijf -
joe a -
L A Walsh -
Lew Wolfgang -
Masaru Nomiya -
Patrick Shanahan -
Robert Webb -
野宮 賢 / NOMIYA Masaru