Hi everyone,
I already posted this to askubuntu.com
(http://askubuntu.com/questions/522457/lxc-container-no-outgoing-traffic-with-bridged-network-and-public-ip-address),
but I think this might be a better place to find help.
I try to setup a LXC container with bridged network on ubuntu 14.04.
On 09/11/2014 11:05 AM, othiman wrote:
Hi everyone,
I already posted this to askubuntu.com
(http://askubuntu.com/questions/522457/lxc-container-no-outgoing-traffic-with-bridged-network-and-public-ip-address),
but I think this might be a better place to find help.
I try to setup a LXC contai
We face this problem very often.
You can try to ping the Host IP and after that the gateway IP from
inside the container.
If that doesn't work you'll have to send arpings from inside the conainter:
arping -I [lxc-interfacename] -U 91.143.88.119 -c4 (arping from iputils
package)
After that you'll
Hi Andreas, hi tamas,
thanks for your fast answers. I removed the IP settings from the config,
but that was obviously not the problem.
I cannot ping the gateway from inside of the container:
ubuntu@ubuntu-test:~$ ping 91.143.88.1
PING 91.143.88.1 (91.143.88.1) 56(84) bytes of data.
^C
--- 91.1
hi,
Is it allowed by your provider?
tamas
On 09/11/2014 12:46 PM, othiman wrote:
Hi Andreas, hi tamas,
thanks for your fast answers. I removed the IP settings from the
config, but that was obviously not the problem.
I cannot ping the gateway from inside of the container:
ubuntu@ubuntu-test
On Thu, Sep 11, 2014 at 4:05 PM, othiman wrote:
> Hi everyone,
>
> I already posted this to askubuntu.com (http://askubuntu.com/
> questions/522457/lxc-container-no-outgoing-traffic-
> with-bridged-network-and-public-ip-address), but I think this might be a
> better place to find help.
>
> I try
Hi,
binding the 91.143.88.119 address to an aliasing interface of the host
(br0:0) directly, pinging inside and outside to the host is working
correctly.
Thomas
On 11.09.2014 13:01, Tamas Papp wrote:
hi,
Is it allowed by your provider?
tamas
On 09/11/2014 12:46 PM, othiman wrote:
Hi An
On 09/11/2014 01:06 PM, othiman wrote:
Hi,
binding the 91.143.88.119 address to an aliasing interface of the host
(br0:0) directly, pinging inside and outside to the host is working
correctly.
Yes, but as it was mentioned, you're trying with a different mac address.
What you need is I thin
Hmm. The old server is also at the same provider and there it is working
without a problem (ubuntu 12.04 and lxc 0.7.5). In addition binding the
91.143.88.119 address to the old server in the same way, the setup works
without a hassle.
Binding the 91.143.88.119 to an aliasing interface (br0:0) o
I'm still confused that is working at the old server, but not at the new
one. I wrote an email to my provider asking if they use a kind if MAC
filter. I will let you know if this is the solution.
Thanks for all your help,
Thomas
On 11.09.2014 13:08, Tamas Papp wrote:
On 09/11/2014 01:06 PM,
In your container config you set the IP gateway as:
lxc.network.ipv4.gateway=91.143.88.1
But I didn't see that IP addr anywhere else in your email. Where is 88.1 ?
Brian
___
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.lin
91.143.88.1 actually is the providers gateway for the subnet.
The whole IP configuration for the container looks like this:
IP address: 91.143.88.119
netmask: 255.255.255.0
broadcast: 91.143.88.255
gateway: 91.143.88.1
So the container is on a totally different subnet, but shouldn't that
work a
Depends on how your provider set it up.
If it WERE intended to work that way, they would've given you full
instructions (e.g. "use this IP, this netmask, and this gateway") instead
of just giving the IP (and probably say "add this as a secondary IP on your
server).
The fact that you say it works
13 matches
Mail list logo
