-
Notifications
You must be signed in to change notification settings - Fork 148
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
bridge: Epair name for ^15 characters #820
bridge: Epair name for ^15 characters #820
Conversation
ok I tested this one and it made the epair names work as advertised. I don't use bridged networking so this one I had to follow his steps above. @tschettervictor has anyone else tested this beside myself and you? @yaazkal this one can be tested whenever in the future you get time to test. |
Not yet. Waiting on @2Belette to also test. |
all working good, I have tested all the testing point listed.
I don't know if some logic can be tested and if epairX exists, trying to increment X by 1 ? The rest is all good to me thanks for that |
There is is a test that exists. I will have to check that out. |
Can you run the same command with -x to have debug mode enabled? |
Oh wait, you had the epair already on your system? The check will only check jail.conf files for the name. Should we also check the system with ifconfig? |
@2Belette This seems to be another bug that is unrelated. Basically, bastille will check every jail.conf file and gather a list of defined epairs from there. If you have one that you manually created, bastille will not know about it. I will put this on my list of things to fix. |
@tschettervictor that's exactly right and that the reason I said it is not due to this PR but more something we can improve in the future. So for this PR I think it is all good, but as I had this issue I thought a good idea to report but we may need another Feature Reauest for that |
It's actually a rather simple fix. I'll update this PR later with the fix included. |
@2Belette Can you test again? Make sure to purposely create an epair on your system that is not part of any jails. Then create a jail, you should notice wit will skip over that one and go to the next highest number for the new epair. |
Works perfectly ! I even tried to add multiple epair manually and confirmed it is taking the highest and take the next one. |
#786
Allow bridged-VNET interface to work when interface name exceeds 15 characters. This is done by using "epairX" as the name instead of "eXa_jailname" in such cases.
Testing (all with bridged VNET, nothing else should be affected)
Create jail called test, rename to test1, validate jail.conf, rc.conf, and networking
Create jail called test, rename to testtesttesttest, validate jail.conf, rc.conf, and networking
Create jail called testtesttesttest, rename to test1, validate jail.conf, rc.conf, and networking
Create jail called testtesttesttest, rename to testing12345678, validate jail.conf, rc.conf, and networking
The purpose of the above is to validate all use cases (short name to short and long name, and long name to short and long name)
You should find that anytime the new name exceeds 15 characters (plus the interface prefix of eXa_) it will be named "epairXa epairXb" but anytime is is shorter, the current default naming applies.