Christopher Adigun
Christopher Adigun
@dougbtv - Any update on which version has this fix? This is also affecting whereabouts.
@linhanphan - I was testing on AWS platform, it's been a while now since I did the test but I think I used a c5.4xlarge instance for the UERANSIM, this...
@koromochu9999 - If you were able to build for the ARM architecture, can you share the Dockerfile that you used? Thanks
Or can you share the Dockerfile of the upg-vpp version (maybe 1.2 release) you were able to build before?
For EKS, thick-plugin is now available, so far the token issue seems to be resolved using it. https://github.com/aws/amazon-vpc-cni-k8s/blob/master/config/multus/v4.0.2-eksbuild.1/multus-daemonset-thick.yml
Also getting the same issue but looks like this is the in security capabilties exchange.. srsRAN is making mandatory **_(ESM information transfer): Security protected ESM information transfer required_** but MME...
Using latest MME release seems to fix the ESM problem, currently MME is responding with successful IP allocation but srsUE is still showing attach failed.. ``` root@srslte-85cf55cc44-tcq24:/srsRAN/build/srsue/src# ./srsue ue.conf Active...
UE debug logs [ue.zip](https://github.com/srsran/srsRAN_4G/files/11366696/ue.zip)
@n30gupta - Following link might be of benefit: https://bitbucket.org/infinitydon/opensource-5g-core-service-mesh/src/main/helm-chart/
Thanks @jnummelin - Should I keep this issue open or close it in favor of #4255 and use that to track this feature also?