On Wed, Feb 26, 2014 at 2:09 PM, arnaud gaboury
wrote:
> On Wed, Feb 26, 2014 at 1:37 PM, arnaud gaboury
> wrote:
>> --
>>>
>>> Now:
>>> * Populate the iptables FORWARD chain to route traffic from your physical
>>> interface to the bridge and back.
>>
>> I missed totally this part of the setup.
On Wed, Feb 26, 2014 at 1:37 PM, arnaud gaboury
wrote:
> --
>>
>> Now:
>> * Populate the iptables FORWARD chain to route traffic from your physical
>> interface to the bridge and back.
>
> I missed totally this part of the setup. I must admit this topic is a
> little bit new to me.
> Will try to
--
>
> Now:
> * Populate the iptables FORWARD chain to route traffic from your physical
> interface to the bridge and back.
I missed totally this part of the setup. I must admit this topic is a
little bit new to me.
Will try to go this way.
--
google.com/+arnaudgabourygabx
>
> This profile is wrong. Here is the right one:
> ---
> $ cat /etc/netctl/lxc_lan_bridge
> Description="LAN bridge for LXC containers"
> Connection=bridge
> Interface=br0
> SkipNoCarrier="yes"
> BindsToInterfaces=()
> IP=static
> Address=(10.137.0.1/24)
> ---
> Also, since you are running systemd
Note that the original
> author of [3] and [4] is Xyne, see his excellent tutorial [5].
>
> [5]: http://xyne.archlinux.ca/notes/network/dhcp_with_dns.html
>
> Regards,
>
Thank you for this very interesting link
Le 25/02/2014 12:47, arnaud gaboury a écrit :
> Now, I want to start the bridge:
> # netctl start bridge-hortensia
> % ping -c 3 8.8.8.8
> connect: Network is unreachable
To ping 8.8.8.8 you must have a default route or a gateway.
What is the result of "ip route" or "route"?
Regards,
BARA Ewen
Op 25 feb. 2014 20:56 schreef "Leonid Isaev" het
volgende:
>
[...]
> * The simplest way to take care of DNS (that is without any additional
host
> configuration) is to use a static resolv.conf inside the container with a
> public DNS service, e.g.
> ---
> $ cat /var/lib/lxc/appserver1/rootfs/etc/r
On Tue, 25 Feb 2014 12:47:02 +0100
arnaud gaboury wrote:
> Dear list,
>
> I am messing with assigning a static IP on a systemd-nspawn container,
> on both sides (host,container).
You assign an IP address only inside the container.
> My idea is to first create a bridge (br0) on the host.
> [...
On 25.02.14 at 16:33, arnaud gaboury wrote:
> On Tue, Feb 25, 2014 at 1:43 PM, arnaud gaboury
> wrote:
> >>
> >> Now, I want to start the bridge:
> >> # netctl start bridge-hortensia
> >> % ping -c 3 8.8.8.8
> >> connect: Network is unreachable
>
> I realized that starting the bridge profile empt
On Tue, Feb 25, 2014 at 1:43 PM, arnaud gaboury
wrote:
>>
>> Now, I want to start the bridge:
>> # netctl start bridge-hortensia
>> % ping -c 3 8.8.8.8
>> connect: Network is unreachable
I realized that starting the bridge profile empty the /etc/resolv.conf.
Even if I modified the bridge profile
>
> Now, I want to start the bridge:
> # netctl start bridge-hortensia
> % ping -c 3 8.8.8.8
> connect: Network is unreachable
>
To be more precise, here is the output of ip addr when starting the
bridge profile. As you can see, there is no more IP adress assigned on
enp7s0 neither on br0
% ip ad
Dear list,
I am messing with assigning a static IP on a systemd-nspawn container,
on both sides (host,container).
My idea is to first create a bridge (br0) on the host.
My config on host :
systemd-git
netctl to configure network
$ ifocnfig
enp7s0: flags=4163 mtu 1500
12 matches
Mail list logo
