Skip to content

Conversation

@MarcoPolo
Copy link
Contributor

@MarcoPolo MarcoPolo commented Oct 16, 2025

this is a bigger change than expected because I also added the gmlparser/shadowconfig/topology.json parser/reader. So that it can use the same files as shadow.

Normally, you wouldn't need all of that because you'd define your network in Go.

@haxxpop
Copy link
Contributor

haxxpop commented Oct 16, 2025

I think we should have both Shadow and simnet in attsim in a way that we can switch the simulator easily so that we can compare both simulators any time we want, instead of replacing one with the other.

@haxxpop
Copy link
Contributor

haxxpop commented Oct 17, 2025

I think it's looking good overall

@MarcoPolo
Copy link
Contributor Author

I'm pretty happy with how well this matches with shadow.

100 nodes
telegram-cloud-photo-size-1-5157006832365669249-y
telegram-cloud-photo-size-1-5157006832365669250-y

200 nodes

telegram-cloud-photo-size-1-5157006832365669254-y
telegram-cloud-photo-size-1-5157006832365669255-y


For the short term I think it's fine to have both. The work for using both is already done. Long term, I think using the simnet is more flexible and we may craft scenarios that are hard to translate to shadow. But we can cross that bridge when we come to it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants