You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my observation, this is what happens in regard to tap3 (we'll ignore tap1):
If the device does not exist on the host OS level at startup of dynamips, dynamips will create it (assuming sufficient permissions of the user account starting dynamips) and destroy the device when dynamips is being shut down.
If the device does exist on the host OS level at startup of dynamips, it'll be used as is and not destroyed when dynamips is being shut down.
That behavior is perfectly acceptable as far as I am concerned, though I did not find a description of the behavior in the documentation and want to make sure this behavior can be assumed to be consistent.
The text was updated successfully, but these errors were encountered:
Let's assume this configuration:
In my observation, this is what happens in regard to
tap3
(we'll ignoretap1
):If the device does not exist on the host OS level at startup of dynamips, dynamips will create it (assuming sufficient permissions of the user account starting dynamips) and destroy the device when dynamips is being shut down.
If the device does exist on the host OS level at startup of dynamips, it'll be used as is and not destroyed when dynamips is being shut down.
That behavior is perfectly acceptable as far as I am concerned, though I did not find a description of the behavior in the documentation and want to make sure this behavior can be assumed to be consistent.
The text was updated successfully, but these errors were encountered: