Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

URGENT Impossible to connect to any container from the same network #1284

Closed
falves1 opened this issue Nov 7, 2016 · 1 comment
Closed

Comments

@falves1
Copy link

falves1 commented Nov 7, 2016

The issue is very simple, and it started a few days ago, after an update.
You cannot communicate from the same network to a container, but from the container you can initiate any connection just fine. Also from outside my network I can ssh into a container and ping it. From the same network I cannot even ping a container.
I did not change anything on my end, except the daily update to my hosts,
Ubuntu 16.04.1 LTS (GNU/Linux 4.4.0-45-generic x86_64)
This happens in two separate sites, so the issue is LXC, not my network.

Strange enough, if I run this command from another computer, not a container, on the same network, it works,
arping -I eth0 ip.add.res.ss
where the IP address is the container's

so what does it all mean?

@stgraber
Copy link
Member

stgraber commented Nov 8, 2016

Closing this issue as nothing changed in LXC which would explain such behavior. Such network problems are usually related to firewalling, misconfiguration or in the worst case, a kernel bug.

Since you've already posted about this on the lxc-users list, I suggest we keep the conversation going on there rather than in this issue.

@stgraber stgraber closed this as completed Nov 8, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants