Rogue Start-Up of Robot sweeper [closed]
up vote
2
down vote
favorite
I have an Xiaomi Mi robot sweeper and at 7:00:40pm each day it is being started up
by a rogue internet message. I saved the active IP table from the DD-WRT router
firmware immediately before and after several of the startups and have found
the following unique IP remote (foreign) addresses, where the source (local) ip was
that of the sweeper:
52.80.189.157
52.80.66.219
Is it possible to modify the firewall in the router's DD-WRT firmware to include all
52.80.xx.xx addresses via the "Command line" input under "administration"?
router dd-wrt
asked Oct 15 at 21:51
jerryt
393
closed as off-topic by Journeyman Geek♦ Dec 5 at 3:37
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "This question is not about computer hardware or software, within the scope defined in the help center." – Journeyman Geek
If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |
up vote
2
down vote
favorite
I have an Xiaomi Mi robot sweeper and at 7:00:40pm each day it is being started up
by a rogue internet message. I saved the active IP table from the DD-WRT router
firmware immediately before and after several of the startups and have found
the following unique IP remote (foreign) addresses, where the source (local) ip was
that of the sweeper:
52.80.189.157
52.80.66.219
Is it possible to modify the firewall in the router's DD-WRT firmware to include all
52.80.xx.xx addresses via the "Command line" input under "administration"?
router dd-wrt
asked Oct 15 at 21:51
jerryt
393
closed as off-topic by Journeyman Geek♦ Dec 5 at 3:37
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "This question is not about computer hardware or software, within the scope defined in the help center." – Journeyman Geek
If this question can be reworded to fit the rules in the help center, please edit the question.
1
Yes, it now appears to be reaching out as I turned off the robot and at that specified time there was nothing incoming. I am now blocking outgoing specific range which includes the noted IPs, namely 52.84.0.0/21.
– jerryt
Oct 16 at 19:33
add a comment |
up vote
2
down vote
favorite
up vote
2
down vote
favorite
I have an Xiaomi Mi robot sweeper and at 7:00:40pm each day it is being started up
by a rogue internet message. I saved the active IP table from the DD-WRT router
firmware immediately before and after several of the startups and have found
the following unique IP remote (foreign) addresses, where the source (local) ip was
that of the sweeper:
52.80.189.157
52.80.66.219
Is it possible to modify the firewall in the router's DD-WRT firmware to include all
52.80.xx.xx addresses via the "Command line" input under "administration"?
router dd-wrt
asked Oct 15 at 21:51
jerryt
393
I have an Xiaomi Mi robot sweeper and at 7:00:40pm each day it is being started up
by a rogue internet message. I saved the active IP table from the DD-WRT router
firmware immediately before and after several of the startups and have found
the following unique IP remote (foreign) addresses, where the source (local) ip was
that of the sweeper:
52.80.189.157
52.80.66.219
Is it possible to modify the firewall in the router's DD-WRT firmware to include all
52.80.xx.xx addresses via the "Command line" input under "administration"?
router dd-wrt
router dd-wrt
asked Oct 15 at 21:51
jerryt
393
asked Oct 15 at 21:51
jerryt
393
asked Oct 15 at 21:51
jerryt
393
asked Oct 15 at 21:51
jerryt
393
asked Oct 15 at 21:51
jerryt
393
393
closed as off-topic by Journeyman Geek♦ Dec 5 at 3:37
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "This question is not about computer hardware or software, within the scope defined in the help center." – Journeyman Geek
If this question can be reworded to fit the rules in the help center, please edit the question.
closed as off-topic by Journeyman Geek♦ Dec 5 at 3:37
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "This question is not about computer hardware or software, within the scope defined in the help center." – Journeyman Geek
If this question can be reworded to fit the rules in the help center, please edit the question.
1
Yes, it now appears to be reaching out as I turned off the robot and at that specified time there was nothing incoming. I am now blocking outgoing specific range which includes the noted IPs, namely 52.84.0.0/21.
– jerryt
Oct 16 at 19:33
add a comment |
1
Yes, it now appears to be reaching out as I turned off the robot and at that specified time there was nothing incoming. I am now blocking outgoing specific range which includes the noted IPs, namely 52.84.0.0/21.
– jerryt
Oct 16 at 19:33
1
1
Yes, it now appears to be reaching out as I turned off the robot and at that specified time there was nothing incoming. I am now blocking outgoing specific range which includes the noted IPs, namely 52.84.0.0/21.
– jerryt
Oct 16 at 19:33
Yes, it now appears to be reaching out as I turned off the robot and at that specified time there was nothing incoming. I am now blocking outgoing specific range which includes the noted IPs, namely 52.84.0.0/21.
– jerryt
Oct 16 at 19:33
add a comment |
3 Answers
3
active
oldest
votes
up vote
3
down vote
Per Scott's comment and ignoring the original question, the story is that apparently a firmware update for my robot sweeper included the option of an "automatic" mode with a default of turning it on at 1900 DST (and 1800 when DST ended). I say "apparently" because I was unaware of such an "automatic mode" until a week or so before the end of the forty some days mentioned in Scott's posting.
On my tablet where I follow the robot sweeper and restart it when it complained of blocked brush I finally stumbled into the "new" "automatic" part of the program and saw "1800". Wow! Part of the instructions and information in the automatic mode is in Chinese, so character by character I translated it to English and determined how to turn off the "automatic" option. Even in English these programs are not really user friendly.
In "automatic" the robot uses a program on any one of many Amazon clouds to implement its auto sweeping start up. I blocked 24 ranges of IP addresses in the router from being accessed by the sweeper and with no success I then finally blocked the sweeper from internet access for the 1 minute it was occurring. That did work. I was at the point of trying to block incoming instructions to the sweeper to identify the IP address of the culprit when I posted the original question.
I originally tried to contact the seller/factory of the subject but they claimed no obligation to "export" customers.
Yeah, the background to the question is more interesting than the question.
answered Dec 5 at 2:39
jerryt
393
add a comment |
up vote
2
down vote
According to the Amazon page, there is a cloud service available for the vacuum cleaner. Presumably, that's what the app is communicating with. You can also use Alexa with the vacuum cleaner, so there are many places packets might be coming from towards your vacuum.
One of the IPs you listed seems to be a company or part of a university in China, I can't tell which my the whois page.
Searching for that company some more, I found this page, showing that the company might be a datacenter.
So you're either looking at a feature that you or someone else signed up for and forgot about, or known bad IP addresses own your network. It's kind of a crapshoot at this point with the information provided. However, hackers in this day and age would be more interested in using the robot as part of a botnet or Bitcoin miner rather than just pranking you at the same time every day.
answered Oct 15 at 22:52
YetAnotherRandomUser
85831230
There are cloud services that the Xiaomia Mi works with but those IPs identify themselves ok. The two IPs I identified in the original question indicate a hostname of "ec2-52-80-189-157.cn-north-1.compute.amazonaws.com.cn" and "ec2-52-80-66-219.cn-north-1.compute.amazonaws.com.cn" in the Webanalysis site. This evening I will be blocking the vac from accessing 52.84.0.0/21 which includes both sites (and more) to see if it has any affect.
– jerryt
Oct 17 at 0:13
Since the "rogue" startup of the robot only occurs when connected to the internet the brute force solution is to simply deny internet access from 19:00 to 19:01 using a DD-WRT Access Restriction. Will try such this evening (10/17/18).
– jerryt
Oct 17 at 16:15
The deny of access to the internet of the robot vac for one minute at 19:00 worked. Now will to try just blocking specific IP address ranges related to those seen on the IP tables without the deny to get more in depth knowledge of source of "vac start", i.e.,42.62.64.0/18, etc.
– jerryt
Oct 18 at 17:43
Why not disconnect the robot from wifi or reset it to factory default, thereby unlinking it from whatever cloud account you have?
– YetAnotherRandomUser
Oct 18 at 21:39
As I mentioned in my last comment the deny of internet access via DD-WRT from 19:00 to 19:01 did just that when the problem occurs. All other times I need the wifi to operate it remotely using my tablet. It has become clear now that the Amazon related advertising IPs are the culprits.(52.xx.xx.xx & 54.xx.xx.xx). Thanks for the interest.
– jerryt
Oct 20 at 0:52
|
show 1 more comment
up vote
-1
down vote
The "Access Restrictions" in DD-WRT make it simple to limit a single address or the whole family of which it is a part, that the robot can contact. The version of DD-WRT referenced is v24-sp2 of (3/25/13) although many other releases likly can do the same. Command line input was not necessary.
answered Nov 26 at 3:06
jerryt
393
Wow! Your first answer was in response to your first and only question — after 42 days! You ought to get an award for that! Seriously, thanks for coming back to update this information. But it would be even better if you made your answer stand-alone. Imagine somebody read just your question and your answer — would it make sense? I don't think so; I think somebody would need to see the other answer and/or the comments. Imagine that they're all gone. Please edit your answer to make it clearer and more complete.
– Scott
Nov 26 at 4:11
add a comment |
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
Per Scott's comment and ignoring the original question, the story is that apparently a firmware update for my robot sweeper included the option of an "automatic" mode with a default of turning it on at 1900 DST (and 1800 when DST ended). I say "apparently" because I was unaware of such an "automatic mode" until a week or so before the end of the forty some days mentioned in Scott's posting.
On my tablet where I follow the robot sweeper and restart it when it complained of blocked brush I finally stumbled into the "new" "automatic" part of the program and saw "1800". Wow! Part of the instructions and information in the automatic mode is in Chinese, so character by character I translated it to English and determined how to turn off the "automatic" option. Even in English these programs are not really user friendly.
In "automatic" the robot uses a program on any one of many Amazon clouds to implement its auto sweeping start up. I blocked 24 ranges of IP addresses in the router from being accessed by the sweeper and with no success I then finally blocked the sweeper from internet access for the 1 minute it was occurring. That did work. I was at the point of trying to block incoming instructions to the sweeper to identify the IP address of the culprit when I posted the original question.
I originally tried to contact the seller/factory of the subject but they claimed no obligation to "export" customers.
Yeah, the background to the question is more interesting than the question.
answered Dec 5 at 2:39
jerryt
393
add a comment |
up vote
3
down vote
Per Scott's comment and ignoring the original question, the story is that apparently a firmware update for my robot sweeper included the option of an "automatic" mode with a default of turning it on at 1900 DST (and 1800 when DST ended). I say "apparently" because I was unaware of such an "automatic mode" until a week or so before the end of the forty some days mentioned in Scott's posting.
On my tablet where I follow the robot sweeper and restart it when it complained of blocked brush I finally stumbled into the "new" "automatic" part of the program and saw "1800". Wow! Part of the instructions and information in the automatic mode is in Chinese, so character by character I translated it to English and determined how to turn off the "automatic" option. Even in English these programs are not really user friendly.
In "automatic" the robot uses a program on any one of many Amazon clouds to implement its auto sweeping start up. I blocked 24 ranges of IP addresses in the router from being accessed by the sweeper and with no success I then finally blocked the sweeper from internet access for the 1 minute it was occurring. That did work. I was at the point of trying to block incoming instructions to the sweeper to identify the IP address of the culprit when I posted the original question.
I originally tried to contact the seller/factory of the subject but they claimed no obligation to "export" customers.
Yeah, the background to the question is more interesting than the question.
answered Dec 5 at 2:39
jerryt
393
add a comment |
up vote
3
down vote
up vote
3
down vote
Per Scott's comment and ignoring the original question, the story is that apparently a firmware update for my robot sweeper included the option of an "automatic" mode with a default of turning it on at 1900 DST (and 1800 when DST ended). I say "apparently" because I was unaware of such an "automatic mode" until a week or so before the end of the forty some days mentioned in Scott's posting.
On my tablet where I follow the robot sweeper and restart it when it complained of blocked brush I finally stumbled into the "new" "automatic" part of the program and saw "1800". Wow! Part of the instructions and information in the automatic mode is in Chinese, so character by character I translated it to English and determined how to turn off the "automatic" option. Even in English these programs are not really user friendly.
In "automatic" the robot uses a program on any one of many Amazon clouds to implement its auto sweeping start up. I blocked 24 ranges of IP addresses in the router from being accessed by the sweeper and with no success I then finally blocked the sweeper from internet access for the 1 minute it was occurring. That did work. I was at the point of trying to block incoming instructions to the sweeper to identify the IP address of the culprit when I posted the original question.
I originally tried to contact the seller/factory of the subject but they claimed no obligation to "export" customers.
Yeah, the background to the question is more interesting than the question.
answered Dec 5 at 2:39
jerryt
393
Per Scott's comment and ignoring the original question, the story is that apparently a firmware update for my robot sweeper included the option of an "automatic" mode with a default of turning it on at 1900 DST (and 1800 when DST ended). I say "apparently" because I was unaware of such an "automatic mode" until a week or so before the end of the forty some days mentioned in Scott's posting.
On my tablet where I follow the robot sweeper and restart it when it complained of blocked brush I finally stumbled into the "new" "automatic" part of the program and saw "1800". Wow! Part of the instructions and information in the automatic mode is in Chinese, so character by character I translated it to English and determined how to turn off the "automatic" option. Even in English these programs are not really user friendly.
In "automatic" the robot uses a program on any one of many Amazon clouds to implement its auto sweeping start up. I blocked 24 ranges of IP addresses in the router from being accessed by the sweeper and with no success I then finally blocked the sweeper from internet access for the 1 minute it was occurring. That did work. I was at the point of trying to block incoming instructions to the sweeper to identify the IP address of the culprit when I posted the original question.
I originally tried to contact the seller/factory of the subject but they claimed no obligation to "export" customers.
Yeah, the background to the question is more interesting than the question.
answered Dec 5 at 2:39
jerryt
393
answered Dec 5 at 2:39
jerryt
393
answered Dec 5 at 2:39
jerryt
393
answered Dec 5 at 2:39
jerryt
393
393
add a comment |
add a comment |
up vote
2
down vote
According to the Amazon page, there is a cloud service available for the vacuum cleaner. Presumably, that's what the app is communicating with. You can also use Alexa with the vacuum cleaner, so there are many places packets might be coming from towards your vacuum.
One of the IPs you listed seems to be a company or part of a university in China, I can't tell which my the whois page.
Searching for that company some more, I found this page, showing that the company might be a datacenter.
So you're either looking at a feature that you or someone else signed up for and forgot about, or known bad IP addresses own your network. It's kind of a crapshoot at this point with the information provided. However, hackers in this day and age would be more interested in using the robot as part of a botnet or Bitcoin miner rather than just pranking you at the same time every day.
answered Oct 15 at 22:52
YetAnotherRandomUser
85831230
There are cloud services that the Xiaomia Mi works with but those IPs identify themselves ok. The two IPs I identified in the original question indicate a hostname of "ec2-52-80-189-157.cn-north-1.compute.amazonaws.com.cn" and "ec2-52-80-66-219.cn-north-1.compute.amazonaws.com.cn" in the Webanalysis site. This evening I will be blocking the vac from accessing 52.84.0.0/21 which includes both sites (and more) to see if it has any affect.
– jerryt
Oct 17 at 0:13
Since the "rogue" startup of the robot only occurs when connected to the internet the brute force solution is to simply deny internet access from 19:00 to 19:01 using a DD-WRT Access Restriction. Will try such this evening (10/17/18).
– jerryt
Oct 17 at 16:15
The deny of access to the internet of the robot vac for one minute at 19:00 worked. Now will to try just blocking specific IP address ranges related to those seen on the IP tables without the deny to get more in depth knowledge of source of "vac start", i.e.,42.62.64.0/18, etc.
– jerryt
Oct 18 at 17:43
Why not disconnect the robot from wifi or reset it to factory default, thereby unlinking it from whatever cloud account you have?
– YetAnotherRandomUser
Oct 18 at 21:39
As I mentioned in my last comment the deny of internet access via DD-WRT from 19:00 to 19:01 did just that when the problem occurs. All other times I need the wifi to operate it remotely using my tablet. It has become clear now that the Amazon related advertising IPs are the culprits.(52.xx.xx.xx & 54.xx.xx.xx). Thanks for the interest.
– jerryt
Oct 20 at 0:52
|
show 1 more comment
up vote
2
down vote
According to the Amazon page, there is a cloud service available for the vacuum cleaner. Presumably, that's what the app is communicating with. You can also use Alexa with the vacuum cleaner, so there are many places packets might be coming from towards your vacuum.
One of the IPs you listed seems to be a company or part of a university in China, I can't tell which my the whois page.
Searching for that company some more, I found this page, showing that the company might be a datacenter.
So you're either looking at a feature that you or someone else signed up for and forgot about, or known bad IP addresses own your network. It's kind of a crapshoot at this point with the information provided. However, hackers in this day and age would be more interested in using the robot as part of a botnet or Bitcoin miner rather than just pranking you at the same time every day.
answered Oct 15 at 22:52
YetAnotherRandomUser
85831230
There are cloud services that the Xiaomia Mi works with but those IPs identify themselves ok. The two IPs I identified in the original question indicate a hostname of "ec2-52-80-189-157.cn-north-1.compute.amazonaws.com.cn" and "ec2-52-80-66-219.cn-north-1.compute.amazonaws.com.cn" in the Webanalysis site. This evening I will be blocking the vac from accessing 52.84.0.0/21 which includes both sites (and more) to see if it has any affect.
– jerryt
Oct 17 at 0:13
Since the "rogue" startup of the robot only occurs when connected to the internet the brute force solution is to simply deny internet access from 19:00 to 19:01 using a DD-WRT Access Restriction. Will try such this evening (10/17/18).
– jerryt
Oct 17 at 16:15
The deny of access to the internet of the robot vac for one minute at 19:00 worked. Now will to try just blocking specific IP address ranges related to those seen on the IP tables without the deny to get more in depth knowledge of source of "vac start", i.e.,42.62.64.0/18, etc.
– jerryt
Oct 18 at 17:43
Why not disconnect the robot from wifi or reset it to factory default, thereby unlinking it from whatever cloud account you have?
– YetAnotherRandomUser
Oct 18 at 21:39
As I mentioned in my last comment the deny of internet access via DD-WRT from 19:00 to 19:01 did just that when the problem occurs. All other times I need the wifi to operate it remotely using my tablet. It has become clear now that the Amazon related advertising IPs are the culprits.(52.xx.xx.xx & 54.xx.xx.xx). Thanks for the interest.
– jerryt
Oct 20 at 0:52
|
show 1 more comment
up vote
2
down vote
up vote
2
down vote
According to the Amazon page, there is a cloud service available for the vacuum cleaner. Presumably, that's what the app is communicating with. You can also use Alexa with the vacuum cleaner, so there are many places packets might be coming from towards your vacuum.
One of the IPs you listed seems to be a company or part of a university in China, I can't tell which my the whois page.
Searching for that company some more, I found this page, showing that the company might be a datacenter.
So you're either looking at a feature that you or someone else signed up for and forgot about, or known bad IP addresses own your network. It's kind of a crapshoot at this point with the information provided. However, hackers in this day and age would be more interested in using the robot as part of a botnet or Bitcoin miner rather than just pranking you at the same time every day.
answered Oct 15 at 22:52
YetAnotherRandomUser
85831230
According to the Amazon page, there is a cloud service available for the vacuum cleaner. Presumably, that's what the app is communicating with. You can also use Alexa with the vacuum cleaner, so there are many places packets might be coming from towards your vacuum.
One of the IPs you listed seems to be a company or part of a university in China, I can't tell which my the whois page.
Searching for that company some more, I found this page, showing that the company might be a datacenter.
So you're either looking at a feature that you or someone else signed up for and forgot about, or known bad IP addresses own your network. It's kind of a crapshoot at this point with the information provided. However, hackers in this day and age would be more interested in using the robot as part of a botnet or Bitcoin miner rather than just pranking you at the same time every day.
answered Oct 15 at 22:52
YetAnotherRandomUser
85831230
answered Oct 15 at 22:52
YetAnotherRandomUser
85831230
answered Oct 15 at 22:52
YetAnotherRandomUser
85831230
answered Oct 15 at 22:52
YetAnotherRandomUser
85831230
85831230
There are cloud services that the Xiaomia Mi works with but those IPs identify themselves ok. The two IPs I identified in the original question indicate a hostname of "ec2-52-80-189-157.cn-north-1.compute.amazonaws.com.cn" and "ec2-52-80-66-219.cn-north-1.compute.amazonaws.com.cn" in the Webanalysis site. This evening I will be blocking the vac from accessing 52.84.0.0/21 which includes both sites (and more) to see if it has any affect.
– jerryt
Oct 17 at 0:13
Since the "rogue" startup of the robot only occurs when connected to the internet the brute force solution is to simply deny internet access from 19:00 to 19:01 using a DD-WRT Access Restriction. Will try such this evening (10/17/18).
– jerryt
Oct 17 at 16:15
The deny of access to the internet of the robot vac for one minute at 19:00 worked. Now will to try just blocking specific IP address ranges related to those seen on the IP tables without the deny to get more in depth knowledge of source of "vac start", i.e.,42.62.64.0/18, etc.
– jerryt
Oct 18 at 17:43
Why not disconnect the robot from wifi or reset it to factory default, thereby unlinking it from whatever cloud account you have?
– YetAnotherRandomUser
Oct 18 at 21:39
As I mentioned in my last comment the deny of internet access via DD-WRT from 19:00 to 19:01 did just that when the problem occurs. All other times I need the wifi to operate it remotely using my tablet. It has become clear now that the Amazon related advertising IPs are the culprits.(52.xx.xx.xx & 54.xx.xx.xx). Thanks for the interest.
– jerryt
Oct 20 at 0:52
|
show 1 more comment
There are cloud services that the Xiaomia Mi works with but those IPs identify themselves ok. The two IPs I identified in the original question indicate a hostname of "ec2-52-80-189-157.cn-north-1.compute.amazonaws.com.cn" and "ec2-52-80-66-219.cn-north-1.compute.amazonaws.com.cn" in the Webanalysis site. This evening I will be blocking the vac from accessing 52.84.0.0/21 which includes both sites (and more) to see if it has any affect.
– jerryt
Oct 17 at 0:13
Since the "rogue" startup of the robot only occurs when connected to the internet the brute force solution is to simply deny internet access from 19:00 to 19:01 using a DD-WRT Access Restriction. Will try such this evening (10/17/18).
– jerryt
Oct 17 at 16:15
The deny of access to the internet of the robot vac for one minute at 19:00 worked. Now will to try just blocking specific IP address ranges related to those seen on the IP tables without the deny to get more in depth knowledge of source of "vac start", i.e.,42.62.64.0/18, etc.
– jerryt
Oct 18 at 17:43
Why not disconnect the robot from wifi or reset it to factory default, thereby unlinking it from whatever cloud account you have?
– YetAnotherRandomUser
Oct 18 at 21:39
As I mentioned in my last comment the deny of internet access via DD-WRT from 19:00 to 19:01 did just that when the problem occurs. All other times I need the wifi to operate it remotely using my tablet. It has become clear now that the Amazon related advertising IPs are the culprits.(52.xx.xx.xx & 54.xx.xx.xx). Thanks for the interest.
– jerryt
Oct 20 at 0:52
There are cloud services that the Xiaomia Mi works with but those IPs identify themselves ok. The two IPs I identified in the original question indicate a hostname of "ec2-52-80-189-157.cn-north-1.compute.amazonaws.com.cn" and "ec2-52-80-66-219.cn-north-1.compute.amazonaws.com.cn" in the Webanalysis site. This evening I will be blocking the vac from accessing 52.84.0.0/21 which includes both sites (and more) to see if it has any affect.
– jerryt
Oct 17 at 0:13
There are cloud services that the Xiaomia Mi works with but those IPs identify themselves ok. The two IPs I identified in the original question indicate a hostname of "ec2-52-80-189-157.cn-north-1.compute.amazonaws.com.cn" and "ec2-52-80-66-219.cn-north-1.compute.amazonaws.com.cn" in the Webanalysis site. This evening I will be blocking the vac from accessing 52.84.0.0/21 which includes both sites (and more) to see if it has any affect.
– jerryt
Oct 17 at 0:13
Since the "rogue" startup of the robot only occurs when connected to the internet the brute force solution is to simply deny internet access from 19:00 to 19:01 using a DD-WRT Access Restriction. Will try such this evening (10/17/18).
– jerryt
Oct 17 at 16:15
Since the "rogue" startup of the robot only occurs when connected to the internet the brute force solution is to simply deny internet access from 19:00 to 19:01 using a DD-WRT Access Restriction. Will try such this evening (10/17/18).
– jerryt
Oct 17 at 16:15
The deny of access to the internet of the robot vac for one minute at 19:00 worked. Now will to try just blocking specific IP address ranges related to those seen on the IP tables without the deny to get more in depth knowledge of source of "vac start", i.e.,42.62.64.0/18, etc.
– jerryt
Oct 18 at 17:43
The deny of access to the internet of the robot vac for one minute at 19:00 worked. Now will to try just blocking specific IP address ranges related to those seen on the IP tables without the deny to get more in depth knowledge of source of "vac start", i.e.,42.62.64.0/18, etc.
– jerryt
Oct 18 at 17:43
Why not disconnect the robot from wifi or reset it to factory default, thereby unlinking it from whatever cloud account you have?
– YetAnotherRandomUser
Oct 18 at 21:39
Why not disconnect the robot from wifi or reset it to factory default, thereby unlinking it from whatever cloud account you have?
– YetAnotherRandomUser
Oct 18 at 21:39
As I mentioned in my last comment the deny of internet access via DD-WRT from 19:00 to 19:01 did just that when the problem occurs. All other times I need the wifi to operate it remotely using my tablet. It has become clear now that the Amazon related advertising IPs are the culprits.(52.xx.xx.xx & 54.xx.xx.xx). Thanks for the interest.
– jerryt
Oct 20 at 0:52
As I mentioned in my last comment the deny of internet access via DD-WRT from 19:00 to 19:01 did just that when the problem occurs. All other times I need the wifi to operate it remotely using my tablet. It has become clear now that the Amazon related advertising IPs are the culprits.(52.xx.xx.xx & 54.xx.xx.xx). Thanks for the interest.
– jerryt
Oct 20 at 0:52
|
show 1 more comment
up vote
-1
down vote
The "Access Restrictions" in DD-WRT make it simple to limit a single address or the whole family of which it is a part, that the robot can contact. The version of DD-WRT referenced is v24-sp2 of (3/25/13) although many other releases likly can do the same. Command line input was not necessary.
answered Nov 26 at 3:06
jerryt
393
Wow! Your first answer was in response to your first and only question — after 42 days! You ought to get an award for that! Seriously, thanks for coming back to update this information. But it would be even better if you made your answer stand-alone. Imagine somebody read just your question and your answer — would it make sense? I don't think so; I think somebody would need to see the other answer and/or the comments. Imagine that they're all gone. Please edit your answer to make it clearer and more complete.
– Scott
Nov 26 at 4:11
add a comment |
up vote
-1
down vote
The "Access Restrictions" in DD-WRT make it simple to limit a single address or the whole family of which it is a part, that the robot can contact. The version of DD-WRT referenced is v24-sp2 of (3/25/13) although many other releases likly can do the same. Command line input was not necessary.
answered Nov 26 at 3:06
jerryt
393
Wow! Your first answer was in response to your first and only question — after 42 days! You ought to get an award for that! Seriously, thanks for coming back to update this information. But it would be even better if you made your answer stand-alone. Imagine somebody read just your question and your answer — would it make sense? I don't think so; I think somebody would need to see the other answer and/or the comments. Imagine that they're all gone. Please edit your answer to make it clearer and more complete.
– Scott
Nov 26 at 4:11
add a comment |
up vote
-1
down vote
up vote
-1
down vote
The "Access Restrictions" in DD-WRT make it simple to limit a single address or the whole family of which it is a part, that the robot can contact. The version of DD-WRT referenced is v24-sp2 of (3/25/13) although many other releases likly can do the same. Command line input was not necessary.
answered Nov 26 at 3:06
jerryt
393
The "Access Restrictions" in DD-WRT make it simple to limit a single address or the whole family of which it is a part, that the robot can contact. The version of DD-WRT referenced is v24-sp2 of (3/25/13) although many other releases likly can do the same. Command line input was not necessary.
answered Nov 26 at 3:06
jerryt
393
answered Nov 26 at 3:06
jerryt
393
answered Nov 26 at 3:06
jerryt
393
answered Nov 26 at 3:06
jerryt
393
393
Wow! Your first answer was in response to your first and only question — after 42 days! You ought to get an award for that! Seriously, thanks for coming back to update this information. But it would be even better if you made your answer stand-alone. Imagine somebody read just your question and your answer — would it make sense? I don't think so; I think somebody would need to see the other answer and/or the comments. Imagine that they're all gone. Please edit your answer to make it clearer and more complete.
– Scott
Nov 26 at 4:11
add a comment |
Wow! Your first answer was in response to your first and only question — after 42 days! You ought to get an award for that! Seriously, thanks for coming back to update this information. But it would be even better if you made your answer stand-alone. Imagine somebody read just your question and your answer — would it make sense? I don't think so; I think somebody would need to see the other answer and/or the comments. Imagine that they're all gone. Please edit your answer to make it clearer and more complete.
– Scott
Nov 26 at 4:11
Wow! Your first answer was in response to your first and only question — after 42 days! You ought to get an award for that! Seriously, thanks for coming back to update this information. But it would be even better if you made your answer stand-alone. Imagine somebody read just your question and your answer — would it make sense? I don't think so; I think somebody would need to see the other answer and/or the comments. Imagine that they're all gone. Please edit your answer to make it clearer and more complete.
– Scott
Nov 26 at 4:11
Wow! Your first answer was in response to your first and only question — after 42 days! You ought to get an award for that! Seriously, thanks for coming back to update this information. But it would be even better if you made your answer stand-alone. Imagine somebody read just your question and your answer — would it make sense? I don't think so; I think somebody would need to see the other answer and/or the comments. Imagine that they're all gone. Please edit your answer to make it clearer and more complete.
– Scott
Nov 26 at 4:11
add a comment |
1
Yes, it now appears to be reaching out as I turned off the robot and at that specified time there was nothing incoming. I am now blocking outgoing specific range which includes the noted IPs, namely 52.84.0.0/21.
– jerryt
Oct 16 at 19:33