On Thursday 06 Mar 2014 23:01:30 arnaud gaboury wrote:
> On Thu, Mar 6, 2014 at 8:00 PM, arnaud gaboury
> wrote:
> >> 1) Two new virtual interfaces are create: one that is visible to the
> >> container, and one that is visible to the host. The host now has two
> >> interfaces, which may be bridge
On Thu, Mar 6, 2014 at 8:00 PM, arnaud gaboury wrote:
>>
>> 1) Two new virtual interfaces are create: one that is visible to the
>> container, and one that is
>> visible to the host. The host now has two interfaces, which may be bridged,
>> or it may act
>> as a NAT router on the interface that
>
> 1) Two new virtual interfaces are create: one that is visible to the
> container, and one that is
> visible to the host. The host now has two interfaces, which may be bridged,
> or it may act
> as a NAT router on the interface that goes to the container. The container
> only sees the
> one i
2014-03-06 18:40 GMT+01:00 Guus Snijders :
>
> Op 6 mrt. 2014 14:15 schreef "Thomas Bächler" het
> volgende:
>
> [...]
>
> As for Dahlia; i don't know exactly how containers work in Linux, but i guess
> you'll need to configure some virtual network device and then add that to the
> bridge.
> My
Op 6 mrt. 2014 14:15 schreef "Thomas Bächler" het
volgende:
>
> Am 06.03.2014 14:03, schrieb arnaud gaboury:
> > Dear list,
> >
> > I am running a machine "hortensia" with a container "dahlia". As the
> > container will be a server, I want to have one IP for hortensia and
> > another one for dahli
To say it out in a manner as straight as possible, you have to include
every device that the bridge should have any effect on in your bridge.
And if you still think a device doesn't go in there, I'd have to
listen to your reason and read up if that is actually valid. No,
include all those devices a
Am 06.03.2014 16:19, schrieb Paul Gideon Dann:
>> If I understand correctly, in fact I took the set up upside down. I
>> tried br0 ---> enp7s0 when in fact the scheme is
>>
>> |-> dev 1
>>
>> enp7s0 > bridge br0 |
>>
>>
>
> I can't help you with your specific problem, but one thing is that you
> need to do, is to enable the machine to forward ip packets from one
> interface to another. Create something like
> a /etc/sysctl.d/99-sysctl.conf and add this:
>
> # Enable packet forwarding
> net.ipv4.ip_forward = 1
> n
On Thursday 06 Mar 2014 16:14:19 arnaud gaboury wrote:
> > This configuration make no sense whatsoever.
> >
> > 1) You create a bridge with no ports. What purpose does it serve?
> > 2) If you want to add enp7s0 as a port, why do you have a configuration
> > for enp7s0? If an interface is a bridge
> This configuration make no sense whatsoever.
>
> 1) You create a bridge with no ports. What purpose does it serve?
> 2) If you want to add enp7s0 as a port, why do you have a configuration
> for enp7s0? If an interface is a bridge port, it cannot be used for IP
> traffic, so assigning it an IP is
On 06-03-2014 13:03, arnaud gaboury wrote:
>
> My issue is that br0 is DOWN and can't make it up with this command:
> # ip link set dev br0 up
> This has no effect.
I use a systemd service file to setup a bridge for somewhat similar
purposes, the sequence of commands I use is this:
/usr/sbin/br
On 06-03-2014 13:23, Paul Gideon Dann wrote:
>
> Hi Arnaud. This doesn't seem right to me. The purpose of a bridge is to
> connect several
> interfaces together. Your bridge is not bound to any interfaces, so it's
> effectively useless,
> unless there's some special use of bridges I'm not fami
On Thu, 6 Mar 2014 14:03:54 +0100
arnaud gaboury wrote:
> I have no idea what part of the setup is missing.
>
> I run a custom kernel, so is there any wrong configuration on it ? The
> kernel is moderately customized, but maybe did I disabled some needed
> flag ?
I can't help you with your spec
On Thursday 06 Mar 2014 14:03:54 arnaud gaboury wrote:
> I am running a machine "hortensia" with a container "dahlia". As the
> container will be a server, I want to have one IP for hortensia and
> another one for dahlia.
>
> On hortensia, with dhcpcd.service and systemd-networkd both disabled,
>
Am 06.03.2014 14:03, schrieb arnaud gaboury:
> Dear list,
>
> I am running a machine "hortensia" with a container "dahlia". As the
> container will be a server, I want to have one IP for hortensia and
> another one for dahlia.
>
> On hortensia, with dhcpcd.service and systemd-networkd both disabl
Dear list,
I am running a machine "hortensia" with a container "dahlia". As the
container will be a server, I want to have one IP for hortensia and
another one for dahlia.
On hortensia, with dhcpcd.service and systemd-networkd both disabled,
I start at boot two netctl profiles.
/etc/netctl/bridg
16 matches
Mail list logo
