mirror of
https://github.com/reconurge/flowsint.git
synced 2026-05-07 20:28:48 -05:00
[GH-ISSUE #43] ASN node Automatically Connects to wrong domain and IP nodes #315
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/flowsint#315
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ameygat on GitHub (Nov 12, 2025).
Original GitHub issue: https://github.com/reconurge/flowsint/issues/43
I had manually created a ASN node with CIDR 202.3.64.0/24
Then manually added a domain node with value : avtechupdate[.]com
Then added two IP address nodes manually 206.206.123.209 and 45.129.199.214
The ASN node is now automatically connected to above domain and two IP address. I am not sure why these nodes are connected.
Graph view:
ASN properties
Domain node properties
IP address node 45.129.199.214 properties:
IP address node 206.206.123.209 properties:
@dextmorgn commented on GitHub (Nov 12, 2025):
Hey @ameygat,
Thanks for raising the issue. It's likely related to how the nodes were created in the frontend, and I might have an idea where the bug might come from.
Just to make sure, if I understand correctly, none of these nodes should be related for now?
And to know how you proceded, which button did you use to add new items?
By right clicking on the node then the
+button:or from the left panel:
Let me know !
@ameygat commented on GitHub (Nov 12, 2025):
Yes these nodes are not at all related to this ASN.
I had used left panel to add the nodes.
P.S. There are some other nodes also in the graph but not connected to these nodes.
@dextmorgn commented on GitHub (Nov 12, 2025):
thanks @ameygat, I'll try to reproduce your issue and investigate on this
@dextmorgn commented on GitHub (Nov 12, 2025):
@ameygat, I found another issue that I just fixed, I don't know if it's related to that issue. Did you happen to have the same nodes (same label and types) in another sketch ?
@ameygat commented on GitHub (Nov 13, 2025):
Yes as matter of fact I had same node in another sketch in the same investigation. And in that other sketch they are connected. Are all nodes global or private to investigation or private to sketch ?
Thought: Well if it gets information from other investigation, it can be optionally kept as a feature also. Where relationship from other investigation would help discover new nodes in new investigation.
@dextmorgn commented on GitHub (Nov 13, 2025):
Cool so this is very likely related.
Indeed, in theory, an entity is "unique" but what defines the uniqueness of an entity is tricky.
For now after the fix, a node is unique in the context of a sketch, and based on its type and label value. This prevents side effects like your had in your case.
Later, we indeed can question this and maybe provide "references" to other nodes: a visual copy that references the original node.
What do you think ?
@ameygat commented on GitHub (Nov 14, 2025):
Ya, I think while creating sketch we can have option to choose whether nodes from other sketches are referenced or not. That will let use decide if he wants isolated sketch or data from other sketch should be referenced.