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
node will take the domain of the gateways a kernel param during startup (no pub config on the chain)
now we have mycelium process running in ndmz namespace so the gateway will run on the same namespace ( also there is a suggestion that we drop the ndmz namespace in zos and keep only the ndmz bridge on host in this case we need to run the gateway process on the host)
in this case gateway can serve any backend out of the box since we have mycelium as a hard requirement for zos4 we can depend on it
The text was updated successfully, but these errors were encountered:
Could you also fill me in on the possibility of continuing to use wireguard for backend connections with zos4 gateways? Is this already supported with this plan in addition to mycelium or would it require additional work?
Could you also fill me in on the possibility of continuing to use wireguard for backend connections with zos4 gateways? Is this already supported with this plan in addition to mycelium or would it require additional work?
I started integrating the gateways. we need to do some refactor to the networking of zos4 also doing it now
for wireguard we paused its integration for a while
As in zos3 we need to have gateways in zos4
Specs
The text was updated successfully, but these errors were encountered: