Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • NetworkManager NetworkManager
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 181
    • Issues 181
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 15
    • Merge requests 15
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • NetworkManager
  • NetworkManagerNetworkManager
  • Issues
  • #740
Closed
Open
Created Jun 04, 2021 by Manuel Buil@manuelbuil

nm-cloud-setup policy routing rule breaks connectivity to local containers

In AWS nm-cloud-setup creates a policy routing rule 30400 for eth0. If I try to ping my local container from the host, which has a direct route in the main routing table 10.42.1.2 dev cali02ad7e68ce1 scope link, it does not work. When doing tcpdump, I can see both the echo request and reply in the container's interface cali02ad7e68ce1 but the ping receives no packets. If I remove that policy routing rule, ping works.

Is there a config I could set to avoid this? Why does nm-cloud-setup create it own policy routing rule instead of using the main one? Thanks!

Edited Jun 04, 2021 by Manuel Buil
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking