Tunnet
Rebop Dec 14, 2023 @ 6:16pm
How do you deal with the hacking bots?
Basicaly titles, this jerks are just hanging around on my endpoints, sending obvious scammms! halp me
Originally posted by Polygonal Person:
If you have filters, make them one-way, nothing comes out from them, anything else can go in. If you don't, cut them out of the network entirely.
< >
Showing 1-15 of 21 comments
The author of this thread has indicated that this post answers the original topic.
Polygonal Person Dec 14, 2023 @ 6:28pm 
If you have filters, make them one-way, nothing comes out from them, anything else can go in. If you don't, cut them out of the network entirely.
Originally posted by Polygonal Person:
If you have filters, make them one-way, nothing comes out from them, anything else can go in. If you don't, cut them out of the network entirely.

But what about situations where there is a matching *.*.*.3 as an example, as it only looks to see if there is a .3 in the ending, that heads in but now can't make it back out causing packet loss
SlayersGod Dec 15, 2023 @ 7:17am 
Originally posted by Tired Gamer Syndrome:
Originally posted by Polygonal Person:
If you have filters, make them one-way, nothing comes out from them, anything else can go in. If you don't, cut them out of the network entirely.

But what about situations where there is a matching *.*.*.3 as an example, as it only looks to see if there is a .3 in the ending, that heads in but now can't make it back out causing packet loss

use more filters?
JacobMIX Dec 15, 2023 @ 8:03am 
Originally posted by Tired Gamer Syndrome:
Originally posted by Polygonal Person:
If you have filters, make them one-way, nothing comes out from them, anything else can go in. If you don't, cut them out of the network entirely.

But what about situations where there is a matching *.*.*.3 as an example, as it only looks to see if there is a .3 in the ending, that heads in but now can't make it back out causing packet loss

Filteres only filter from one direction. You can just set a an extra filter to "From 0 if MATCH *.*.*.* SEND BACK"
As far as i know packets don't have TTL outside of subnetworks. At least doesn't show it.
Thanks for the info. I just can't find a balance of filters that will prevent only just 0.0.0.3 and not some how catch 0.1.0.3 and end up killing the packet
SlayersGod Dec 15, 2023 @ 10:25am 
chain filters. -> 0,*,*,* -> *,0,*,* -> *,*,0,* -> *,*,*,3 ->


https://steamcommunity.com/app/2286390/discussions/0/4031347532797614253/
I think we should be able to strict set filters. still wouldn't really change subnet filtering.
Last edited by SlayersGod; Dec 15, 2023 @ 10:27am
Tokoshoran May 29, 2024 @ 7:07pm 
Filters can now be upgraded to filter out the entire sequence, but have there been any additions that allow you to remove the hacker "monster" itself?
deadbeef May 29, 2024 @ 9:17pm 
Originally posted by Tokoshoran:
Filters can now be upgraded to filter out the entire sequence, but have there been any additions that allow you to remove the hacker "monster" itself?

Apparently if the packet gets routed to one of the "military base" endpoints, then the military droids will go stop the hacker. But I never bothered with this, because I understand that if you do this, the hacker will just go to a different endpoint and you'll have to keep dealing with him. I just let him take over an endpoint permanently and filtered out all the packets that come out of the endpoint.
FUS Jun 2, 2024 @ 7:48am 
Originally posted by deadbeef:
Originally posted by Tokoshoran:
Filters can now be upgraded to filter out the entire sequence, but have there been any additions that allow you to remove the hacker "monster" itself?

Apparently if the packet gets routed to one of the "military base" endpoints, then the military droids will go stop the hacker. But I never bothered with this, because I understand that if you do this, the hacker will just go to a different endpoint and you'll have to keep dealing with him. I just let him take over an endpoint permanently and filtered out all the packets that come out of the endpoint.
Hacker removal that way is permanent, so long as you don't re-enable the endpoint he was on. I've heard that there can be multiple hackers at the same time, but have't been able to confirm that yet.
Last edited by FUS; Jun 2, 2024 @ 7:48am
Tokoshoran Jun 7, 2024 @ 2:36pm 
Originally posted by FUS:
Hacker removal that way is permanent, so long as you don't re-enable the endpoint he was on. I've heard that there can be multiple hackers at the same time, but have't been able to confirm that yet.
I had hackers show up on 0001 and 0003 at the same time, so it's possible. Those endpoints aren't really used for much but testing, so I went ahead and left the hackers there, but if it happens somewhere that actually sends out meaningful packets, such as shelters sending frequent Mining requests to Caves, then removing them is helpful.
Sheriph Jun 7, 2024 @ 11:22pm 
Originally posted by FUS:
Originally posted by deadbeef:

Apparently if the packet gets routed to one of the "military base" endpoints, then the military droids will go stop the hacker. But I never bothered with this, because I understand that if you do this, the hacker will just go to a different endpoint and you'll have to keep dealing with him. I just let him take over an endpoint permanently and filtered out all the packets that come out of the endpoint.
Hacker removal that way is permanent, so long as you don't re-enable the endpoint he was on. I've heard that there can be multiple hackers at the same time, but have't been able to confirm that yet.
From what i have seen hackers spawn each time you clean a mainframe. So by the end of the game you will have 3 hackers.
Sean Jun 10, 2024 @ 2:30am 
Once you have all of the technician's handbook (or just snoop on every terminal over a long enough time period), you can create a secondary network which sends any suspicious activity to the nearest security station.

This doesn't completely automate the process, but it significantly reduces harm and if set up correctly, will automate the shutdown of hackers.
Last edited by Sean; Jun 10, 2024 @ 2:30am
Tokoshoran Jun 15, 2024 @ 9:42am 
Originally posted by Sean:
Once you have all of the technician's handbook (or just snoop on every terminal over a long enough time period), you can create a secondary network which sends any suspicious activity to the nearest security station.

This doesn't completely automate the process, but it significantly reduces harm and if set up correctly, will automate the shutdown of hackers.
You can filter things based on subject line?
Sean Jun 17, 2024 @ 8:19am 
No, but you can identify regular traffic/addresses an endpoint normally contacts. Anything else would be suspicious activity which can be sent to security.
Skellitor301 Jun 17, 2024 @ 1:51pm 
It's entirely possible for hackers to be gotten rid of completely after a certain number of them were hit with law enforcement.

Still currently testing but I read that it's possible to get rid of them and keep them away since they mainly only appear after each mainframe is connected. Taking that into consideration and noticing there was an increase after a mainframe is connected I watched and took out hackers until now where the map has no more red for a while now. Gonna keep an eye on it and work on the network, but so far I think there's a certain quantity of hackers you'll get through out the game based mainly on mainframes cleaned. Then, I think the game just adds a certain quantity of hackers to go through sporadically through out your playthrough until that queue is cleared.
< >
Showing 1-15 of 21 comments
Per page: 1530 50