Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarification of dynamips behavior regarding tap interfaces #140

Open
blackbit42 opened this issue Nov 2, 2023 · 0 comments
Open

Clarification of dynamips behavior regarding tap interfaces #140

blackbit42 opened this issue Nov 2, 2023 · 0 comments

Comments

@blackbit42
Copy link

Let's assume this configuration:

dynamips \
        -i R1 \
        -X \
        -T 1024 \
        --idle-pc=0x6062dbb8 \
        -p 0:C7200-IO-FE \
        -s 0:0:tap:tap1 \
        -p 1:PA-FE-TX \
        -s 1:0:tap:tap3 \
        c7200-adventerprisek9-mz.152-4.M11.image

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.

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

No branches or pull requests

1 participant