And how that change in architecture would disconnect you? Your SD-WAN is cutting the feed?
XCP-ng Team
Developers of XCP-ng
Posts
-
RE: XO-6 Cannot connect to server over Unifi SD-WAN, XO-5 works well
-
RE: Trying to enable v2v and difficulty adding nbdinfo on xo 6
Hi,
Can you be more specific on the error you have?
-
RE: MTU change
@Andrew I did suspect that would be sufficient, but we need to think at feature level, and as mentionned there is no such thing we could do "quickly" for linux and other OSes. I anyway did a brain dump of my investigation before posting my previous message and we do now have an entry in the roadmap for it, which was not the case previously.
-
RE: MTU change
Unfortunately, that's not trivial.
Currently in windows, the PV driver reads that info inheritance from the network setting at startup and applies it, it would not allow live modification.
On the other hand, the Linux driver does not do that, therefore it would not be at feature parity. So it would likely be possible to have a "quick and dirty" implementation that works only at boot and only on windows, that would help your case indeed, but that's not a great product feature
We will discuss that internally and see what can be added to the roadmap and to which depth we want to dig that hole as well as this can go pretty far, we'll need to split that in smaller steps to be able to deliver something in a timely fashion.
-
RE: Adding new host to pool fails - Stunnel SSL certiticate verification failure
@Bryanvh Looking at the code, I saw that an exchange was taking place via this certificate.
So when you told me that the master certificate was missing, I tried to put myself in the same situation as you (by removing the certificate) and trying to join the pool.
Having encountered the same error as you, I determined that running these commands fixed the problem.Indeed, I think the upgrade from 8.2 to 8.3 is the cause. To be more precise, a change occurred in the XAPI during the certificate exchange in version 8.2, and I think it's possible that your 8.2 host wasn't up to date when it upgraded to 8.3 (I'm not sure).
In any case, I'm glad your problem is solved.
