Replies: 1 comment 3 replies
-
|
You can disable/enable channels instead of disconnect/reconnect. See examples/tcp_eth_reconnect/scenario2.xml for an example:
|
Beta Was this translation helpful? Give feedback.
-
|
I see, is it mechanically the same though? Does the simulator act differently depending on whether a module was disconneted vs a module's channel was disabled? |
Beta Was this translation helpful? Give feedback.
-
|
It's not entirely the same, the modules can distinguish between disconnecting or disabling a connection. It also looks different in the user interface, because the connection is still there, it's just disabled. But in both cases the packets can't be sent through the connection. So depending on what you want to do, it may behave the same way from your perspective. |
Beta Was this translation helpful? Give feedback.
-
|
Ok i see, thanks for the clarification |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
As it stands (at least from what I can understand from the documentation) the disconnect command requires manual reconnection. Is there a possibility of adding a "reconnect" command in the future? It would be cool not to have to manually connect and specify all the necessary ports and channel types every time I want to disconnect something and then connect it again, in the exact same way.
Beta Was this translation helpful? Give feedback.
All reactions