Re: [lxc-users] Networking

I did not explain myself. Suppose you have a large network of machines and containers, all with public IPs, not private. You constantly bring up new containers and need to assigning new IPs. You either scan the network each time you need a new IP or use DHCP to give you one and then you change

Re: [lxc-users] Networking

Greetings, Saint Michael! > It is a common practice to trust the DHCP server to keep track of free IPs > in a large network, like /21, and once the DHCP assigns an IP address, we > adopt it as static and flag it a such in the router.  > Otherwise, you need to scan the whole network every time.

Re: [lxc-users] Networking

It is a common practice to trust the DHCP server to keep track of free IPs in a large network, like /21, and once the DHCP assigns an IP address, we adopt it as static and flag it a such in the router. Otherwise, you need to scan the whole network every time. On Wed, Mar 25, 2020 at 3:20 PM

Re: [lxc-users] Networking

Greetings, Saint Michael! > I use L2. Can somebody clarify what advantage/disadvantage is there for > L2,L3,L3S? > I need also to be able to use DHCP inside the container. In a first boot I > get an IP from DHCP, and set the interface down and turn that IP into static. This seems to be

Re: [lxc-users] Networking

I use L2. Can somebody clarify what advantage/disadvantage is there for L2,L3,L3S? I need also to be able to use DHCP inside the container. In a first boot I get an IP from DHCP, and set the interface down and turn that IP into static. Any way, ipvlan should work as simply as the other network

Re: [lxc-users] Networking

ajar A. Nugraha) >> 6. Re: Networking (Saint Michael) >> >> >> >> -- Forwarded message -- >> From: "Fajar A. Nugraha" >> To: LXC users mailing-list >> Cc: >> Bcc: >> Date: Mon, 23 Mar 2020 19:26:18 +0700 >&g

Re: [lxc-users] Networking

That scheme in my case would not work. I have two interfaces inside the container, and each one talks to a different network, for business reasons. I use policy-based-routing to make sure that packets go to the right places. I need that the container can hold a full configuration. In my case, I

Re: [lxc-users] Networking

On Mon, Mar 23, 2020 at 11:48 PM Saint Michael wrote: > > It is supported, there is no error, but there is no communication at all with > the gateway. If you start the same exact network configuration in the > container with the type=phys, it works fine, ergo, the issue is type=ipvlan. "exact

Re: [lxc-users] Networking

It is supported, there is no error, but there is no communication at all with the gateway. If you start the same exact network configuration in the container with the type=phys, it works fine, ergo, the issue is type=ipvlan. On Mon, Mar 23, 2020 at 12:37 PM Serge E. Hallyn wrote: > Hi, > >

Re: [lxc-users] Networking

Hi, just to make sure i understand right - you mean it is not supported in lxc-user-nic? And never was, so not a regression? Or has something regressed? On Mon, Mar 23, 2020 at 09:15:57AM -0400, Saint Michael wrote: > As I said, type=ipvlan does not work on the latest version if LXC from git.

Re: [lxc-users] Networking

As I said, type=ipvlan does not work on the latest version if LXC from git. BUT there is a workaround: create as many ipvlan interfaces as you need at the host level, which shall be used later as type="phys" networking on containers. That works. On Mon, Mar 23, 2020 at 8:26 AM Fajar A. Nugraha

Re: [lxc-users] Networking

On Fri, Mar 20, 2020 at 5:36 PM Saint Michael wrote: > > I use plain LXC, not LXD. is ipvlan supported? https://linuxcontainers.org/lxc/manpages//man5/lxc.container.conf.5.html -- Fajar ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org

Re: [lxc-users] Networking

I use plain LXC, not LXD. is ipvlan supported? Also my containers have public IPs, same network as the host. This is why I cannot use NAT. On Fri, Mar 20, 2020 at 12:02 AM Fajar A. Nugraha wrote: > On Thu, Mar 19, 2020 at 12:02 AM Saint Michael wrote: > > > > The question is: how do we

Re: [lxc-users] Networking

On Thu, Mar 19, 2020 at 12:02 AM Saint Michael wrote: > > The question is: how do we share the networking from the host to the > containers, all of if. each container will use one IP, but they could see all > the IPs in the host. This will solve the issue, since a single network > interface,

Re: [lxc-users] Networking Issues

Ok, I am starting from scratch. It's seems the more I google LXD MACVLAN, the more confused I get. I've seen at least 3 different ways to configure this and none of them seemed to work for me?? So right now I am sitting at a fresh and updated install of Ubuntu 16.04.04. I have created a partition

Re: [lxc-users] Networking issue

UPDATE I was right after all in the first place. My network changed, but in another subnet, not mine. What happens is that lxc networking mode=macvlan stopped working or works intermittently. How do I know? because I started using mode=phys, thus moving the interface inside the container, and all

Re: [lxc-users] Networking issue

I SOLVED Many thanks to all. Using your input I concluded that the issue was not in LXC or the Kernel. In fact. the colo changed the subnets without telling me. Yours Federico ​ ___ lxc-users mailing list lxc-users@lists.linuxcontainers.org

Re: [lxc-users] Networking issue

I want to confirm that both the LXC Host and the Container see the packets going back and forth with tcpdump -n -i eth1 "(icmp)" There is no rp_filter sysctl -a | grep [.]rp_filter net.ipv4.conf.all.rp_filter = 0 net.ipv4.conf.default.rp_filter = 0 net.ipv4.conf.eth0.rp_filter = 0

Re: [lxc-users] Networking issue

I don't know how to downgrade the kernel. This is Ubuntu 16.04.1 LTS (GNU/Linux 4.4.0-45-generic x86_64) I always use apt-get -y update and apt-get -y dist-upgrade On Wed, Nov 9, 2016 at 2:22 AM, Janjaap Bos wrote: > Downgrade the kernel to verify your guess, as the

Re: [lxc-users] Networking issue

On Wed, Nov 9, 2016 at 1:33 PM, Saint Michael wrote: > It was working fine until a week ago. > I have two sites, it happened on both, so the issue is not on my router or > my switch, since they are different sites and we did not upgrade anything. > Ubuntu 16.04.1 LTS

Re: [lxc-users] Networking issue

On Wednesday 09 of November 2016 01:33:55 Saint Michael wrote: > Now suppose I have a machine, not a container, in the same broadcast domain > as the containers, same subnet. > It cannot ping or ssh into a container, which is accessible from outside my > network. > However, from inside the

Re: [lxc-users] Networking issue

On Wednesday 09 of November 2016 01:33:55 Saint Michael wrote: > lxc.network.type=macvlan > lxc.network.hwaddr = XX:XX:XX:XX:XX:XX > > Now suppose I have a machine, not a container, in the same broadcast domain > as the containers, same subnet. > It cannot ping or ssh into a container, which is

Re: [lxc-users] Networking issue

Downgrade the kernel to verify your guess, as the other feedback you got also points to the kernel. If that solves it, go file a kernel bug. 2016-11-09 7:33 GMT+01:00 Saint Michael : > It was working fine until a week ago. > I have two sites, it happened on both, so the issue

Re: [lxc-users] Networking issues with LXC containers in EC2

On 01/12/2016 07:03 PM, Fajar A. Nugraha wrote: On Tue, Jan 12, 2016 at 9:29 PM, Peter Steele wrote: On 01/12/2016 05:59 AM, Fajar A. Nugraha wrote: On Tue, Jan 12, 2016 at 8:40 PM, Peter Steele wrote: I should have added that I have no issue running

Re: [lxc-users] Networking LXD containers

I found this article that describes several virtualization networking techniques in great detail. It is mostly based on the legacy lxc tools but was fairly easy for me to translate to the LXD tools. Hope it helps other networking dummies, like my self, that may be watching this mail

Re: [lxc-users] Networking LXD containers

After doing some homework on virtualization networking techniques and studying the contents of /usr/lib/x86_64-linux-gnu/lxc/lxc-net am I correct in deducing that the default lxc/lxd bridge (lxcbr0) is a NATed interface? If I wanted to attach containers to a simple bridged interface and give

Re: [lxc-users] Networking LXD containers

On Fri, Mar 11, 2016 at 3:12 PM, Kean Sum Ooi wrote: > Hi Steve, > > Do you mean LXC containers? On Ubuntu? @Kean: I think he means lxd, not lxc @Steve: I assume you use ubuntu host? Some info in https://help.ubuntu.com/lts/serverguide/lxc.html#lxc-network still apply. In

Re: [lxc-users] Networking LXD containers

Hi Steve, Do you mean LXC containers? On Ubuntu? PS: https://wiki.debian.org/LXC/SimpleBridge http://askubuntu.com/questions/231666/how-do-i-setup-an-lxc-guest-so-that-it-gets-a-dhcp-address-so-i-can-access-it-on https://www.flockport.com/lxc-macvlan-networking/ There are at least two ways to

Re: [lxc-users] Networking issues with LXC containers in EC2

On Wed, Jan 13, 2016 at 10:03 AM, Fajar A. Nugraha wrote: > On Tue, Jan 12, 2016 at 9:29 PM, Peter Steele wrote: >> On 01/12/2016 05:59 AM, Fajar A. Nugraha wrote: >>> >>> On Tue, Jan 12, 2016 at 8:40 PM, Peter Steele wrote: I

Re: [lxc-users] Networking issues with LXC containers in EC2

On Tue, Jan 12, 2016 at 9:29 PM, Peter Steele wrote: > On 01/12/2016 05:59 AM, Fajar A. Nugraha wrote: >> >> On Tue, Jan 12, 2016 at 8:40 PM, Peter Steele wrote: >>> >>> I should have added that I have no issue running our software on a single >>> EC2

Re: [lxc-users] Networking issues with LXC containers in EC2

On Tue, Jan 12, 2016 at 8:40 PM, Peter Steele wrote: > I should have added that I have no issue running our software on a single > EC2 instance with containers running on that instance. We can assign > multiple IPs to the instance itself, as well as to the containers running >

Re: [lxc-users] Networking issues with LXC containers in EC2

I should have added that I have no issue running our software on a single EC2 instance with containers running on that instance. We can assign multiple IPs to the instance itself, as well as to the containers running under the instance, and the containers can all communicate with each other as

Re: [lxc-users] Networking issues with LXC containers in EC2

On Tue, Jan 12, 2016 at 6:31 AM, Peter Steele wrote: > From what I've read, I understand that Amazon has implemented some > special/restricted behavior for the networking stack of EC2 instances. The > question I have is whether I can accomplish what I've attempted here, >

Re: [lxc-users] Networking not working in unconfined overlayfs container

Hi, before I try to reproduce this, can you confirm whether using the kernel from vivid-proposed fixes it? Quoting Frederico Araujo (arau...@gmail.com): > Hi Serge, > > Yes, I downloaded a fresh template for ubuntu and its overlay clones start > okay, and I'm able to attach and run commands on

Re: [lxc-users] Networking not working in unconfined overlayfs container

Hi Serge, Yes, I downloaded a fresh template for ubuntu and its overlay clones start okay, and I'm able to attach and run commands on them. However, eth0 has no IP assigned when unconfined. I think the problem might be related to changes in systemd (I'm using version 219) and overlayfs on vivid.

Re: [lxc-users] Networking not working in unconfined overlayfs container

Quoting Frederico Araujo (arau...@gmail.com): > Hi, > > I've been using LXC for over two years without problems. This week, I > upgraded my Ubuntu from Trusty to Vivid, and I noticed that my overlayfs > containers stopped getting IP assigned. In my machine the error can be > reproduced in this

Re: [lxc-users] networking and permissions questions

On Tue, Apr 28, 2015 at 6:53 AM, Joe McDonald ideafil...@gmail.com wrote: 1) Do I need to specify this IP in both the config file and the rootfs/etc/network/interfaces file? Is there a better way to do this? IMHO the best way is on container's interfaces file 2) why does one container

Re: [lxc-users] Networking LXC and VirtualBox on the same host

On 20/09/14 14:21, J Bc wrote: route -n Not sure what you mean, everything's on the same subnet. Also, if it were routing then pings wouldn't work either... My route -n is this Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 10.0.0.138

Re: [lxc-users] Networking in Ubuntu with 2 ip failover in LXC

Hey, I made some changes: root@ns321124:~# cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback auto br0

Re: [lxc-users] Networking in Ubuntu with 2 ip failover in LXC

Try traceroute, show route command output and things like that. BTW you setup looks the same as before. tamas On 08/13/2014 12:32 PM, bryn1u85 . wrote: Hey, I made some changes: root@ns321124:~# cat /etc/network/interfaces # This file describes the network interfaces available on your

Re: [lxc-users] Networking in Ubuntu with 2 ip failover in LXC

From LXC nothing: root@Oksymoron:~# route Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface ^C From Host: root@ns321124:~# route Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface default

Re: [lxc-users] Networking in Ubuntu with 2 ip failover in LXC

Resending.. On 08/13/2014 02:27 PM, Tamas Papp wrote: host machine: auto br0 iface br0 inet static bridge_ports eth0 bridge_stp off bridge_maxwait 0 bridge_fd 0 address 94.23.237.216 netmask 255.255.255.0 network 94.23.237.0

Re: [lxc-users] Networking in Ubuntu with 2 ip failover in LXC

W dniu 2014-08-13 16:57, Fajar A. Nugraha pisze: On Wed, Aug 13, 2014 at 7:34 PM, Tamas Papp tom...@martos.bme.hu wrote: Resending.. On 08/13/2014 02:27 PM, Tamas Papp wrote: host machine: auto br0 iface br0 inet static bridge_ports eth0 bridge_stp off

Re: [lxc-users] Networking in Ubuntu with 2 ip failover in LXC

On Wed, Aug 13, 2014 at 10:08 PM, m.byryn1u m.bry...@gmail.com wrote: W dniu 2014-08-13 16:57, Fajar A. Nugraha pisze: On Wed, Aug 13, 2014 at 7:34 PM, Tamas Papp tom...@martos.bme.hu wrote: Resending.. On 08/13/2014 02:27 PM, Tamas Papp wrote: host machine: auto br0 iface br0 inet

Re: [lxc-users] Networking in Ubuntu with 2 ip failover in LXC

W dniu 2014-08-13 17:24, Fajar A. Nugraha pisze: On Wed, Aug 13, 2014 at 10:08 PM, m.byryn1u m.bry...@gmail.com wrote: W dniu 2014-08-13 16:57, Fajar A. Nugraha pisze: On Wed, Aug 13, 2014 at 7:34 PM, Tamas Papp tom...@martos.bme.hu wrote: Resending.. On 08/13/2014 02:27 PM, Tamas Papp

Re: [lxc-users] Networking in Ubuntu with 2 ip failover in LXC

W dniu 2014-08-13 18:43, Fajar A. Nugraha pisze: On Wed, Aug 13, 2014 at 10:55 PM, m.byryn1u m.bry...@gmail.com wrote: 94.23.237.254 is not part of 91.121.239.0/24. @Bryn, how is the ROUTER (i.e. 94.23.237.254) setup? Is it configured to route the additional IP (91.121.239.228) thru host's IP

Re: [lxc-users] Networking in LXC

Thanks for the reply @Fajar. (From Host) # lxc-attach -n root -- echo $PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin (Inside container) # ifconfig -bash: ifconfig: command not found # echo $PATH /usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin As you