revert e3c5de1#425
Conversation
|
Alternatively, we can revert the commit just for OpenBSD (i.e., I can remove |
|
I'd just revert the whole change completely. It has broken expected operation on Linux too, as I reported in #392. |
That's unrelated. The reverted commit only impacts OpenBSD and FreeBSD as you can see with the preprocessor directive. I don't use FreeBSD, so I can't say for certain the commit is invalid for FreeBSD. I just know it's invalid for OpenBSD. The commit also only impacts IPv6. OpenBSD does not allow IPv6 sharing; thus when a route is attempted to be added for the same interface, it forbids it causing |
|
I haven't been able to replicate it, but I'll revert as is. |
|
Based on the original comment, you were unable to trigger a kernel panic in FreeBSD when you first wrote that code as well. Not sure why you are unable to trigger it. Perhaps it's a case of running in a VM vs. bare-metal? The lease file I e-mailed was of no help? |
|
Ah, I lost the lease file. Do you still have it? |
|
Re-sent. Did you receive it? [email protected], correct? |
|
Yes thanks. |
|
I'm glad you were able to re-create it. You can try submitting a kernel patch, but IPv6 is unfortunately still treated with disdain by some of the community so there may be pushback. I know OpenBSD (ab)uses the fact that currently only the |
Fixes #407.