[Touch-packages] [Bug 1567744] Re: USB NICs get too long name for ifupdown aliases
Additionally, Juju creates bridges on top of both physical and VLAN interfaces to allow for the same level of addressability for containers as regular machines. The bridges currently use the "br-" prefix and the underlying device name, which if it happens to be "enxxaabbccddeef0.1234" already, obviously won't work. So the length limit on interface names can be even lower than what Mike suggested. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1567744 Title: USB NICs get too long name for ifupdown aliases Status in systemd package in Ubuntu: Triaged Bug description: I have a USB NIC that is connected to my denial system. I tried to create an alias, and after reboot, it wasn't created. When I manually try to bring it up I have the error. /e/n/i: auto enx000ec688b79f iface enx000ec688b79f inet static address 10.90.90.1 netmask 255.255.255.0 auto enx000ec688b79f:1 iface enx000ec688b79f:1 inet static address 192.168.100.1 netmask 255.255.255.0 ubuntu@maas00:~$ sudo ifup enx000ec688b79f ubuntu@maas00:~$ sudo ifup enx000ec688b79f:1 RTNETLINK answers: Numerical result out of range Failed to bring up enx000ec688b79f:1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1567744/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1403955] Re: DHCP's Option interface-mtu 9000 is being ignored on bridge interface br0
Depending on the version of juju used, one option is to set:
lxc-default-mtu: 9000
in environments.yaml for that environment and re-bootstrap. All LXC
containers juju creates should use 9000 as MTU for the eth0 of the
container.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1403955
Title:
DHCP's Option interface-mtu 9000 is being ignored on bridge
interface br0
Status in juju-core:
Triaged
Status in isc-dhcp package in Ubuntu:
Confirmed
Bug description:
In an env with jumbo frames enabled, and using MAAS as DHCP server,
the client receives the following IPv4 lease:
$ cat /var/lib/dhcp/dhclient.br0.leases
lease {
interface br0;
fixed-address 10.230.20.26;
filename pxelinux.0;
option subnet-mask 255.255.248.0;
option dhcp-lease-time 43200;
option routers 10.230.16.1;
option dhcp-message-type 5;
option dhcp-server-identifier 10.230.20.1;
option domain-name-servers 10.230.20.1;
option interface-mtu 9000;
option broadcast-address 10.230.23.255;
option domain-name ctsstack.qa.1ss;
renew 3 2014/12/17 16:48:15;
rebind 3 2014/12/17 21:52:09;
expire 3 2014/12/17 23:22:09;
}
The interfaces show the following config after boot:
$ ifconfig br0
br0 Link encap:Ethernet HWaddr a0:d3:c1:01:9d:58
inet addr:10.230.20.26 Bcast:10.230.23.255 Mask:255.255.248.0
inet6 addr: fe80::a2d3:c1ff:fe01:9d58/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:530530 errors:0 dropped:0 overruns:0 frame:0
TX packets:1591569 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:68713489 (68.7 MB) TX bytes:213710979 (213.7 MB)
$ ifconfig eth0
eth0 Link encap:Ethernet HWaddr a0:d3:c1:01:9d:58
inet6 addr: fe80::a2d3:c1ff:fe01:9d58/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:10539274 errors:0 dropped:3394 overruns:0 frame:454
TX packets:2627412 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2320560616 (2.3 GB) TX bytes:3562885157 (3.5 GB)
Interrupt:32
option interface-mtu 9000; from the lease file is being ignored by br0.
Could it be related to eth0 MTU size? If that's the case, shouldn't both
interfaces be updated?
Other info:
$ brctl show br0
bridge name bridge id STP enabled interfaces
br0 8000.a0d3c1019d58 no eth0
$ cat /etc/network/eth0.config
iface eth0 inet manual
auto br0
iface br0 inet dhcp
bridge_ports eth0
To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1403955/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1403955] Re: DHCP's Option interface-mtu 9000 is being ignored on bridge interface br0
juju-br0 was reintroduced in 1.23.3 as the default behavior in MAAS,
unless the address-allocation feature flag is enabled.
AIUI the juju-br0 swallows the interface-mtu DHCP setting coming
from MAAS. It doesn't happen when eth0 is not bound to juju-br0. So it
looks like this is a pre-existing issue since for ever.
I'm open to suggestions how Juju can work around the issue (e.g. by
generating a slightly different /etc/network/interfaces file with the
juju-br0 definition and/or brctl commands).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1403955
Title:
DHCP's Option interface-mtu 9000 is being ignored on bridge
interface br0
Status in juju-core:
Triaged
Status in isc-dhcp package in Ubuntu:
Confirmed
Bug description:
In an env with jumbo frames enabled, and using MAAS as DHCP server,
the client receives the following IPv4 lease:
$ cat /var/lib/dhcp/dhclient.br0.leases
lease {
interface br0;
fixed-address 10.230.20.26;
filename pxelinux.0;
option subnet-mask 255.255.248.0;
option dhcp-lease-time 43200;
option routers 10.230.16.1;
option dhcp-message-type 5;
option dhcp-server-identifier 10.230.20.1;
option domain-name-servers 10.230.20.1;
option interface-mtu 9000;
option broadcast-address 10.230.23.255;
option domain-name ctsstack.qa.1ss;
renew 3 2014/12/17 16:48:15;
rebind 3 2014/12/17 21:52:09;
expire 3 2014/12/17 23:22:09;
}
The interfaces show the following config after boot:
$ ifconfig br0
br0 Link encap:Ethernet HWaddr a0:d3:c1:01:9d:58
inet addr:10.230.20.26 Bcast:10.230.23.255 Mask:255.255.248.0
inet6 addr: fe80::a2d3:c1ff:fe01:9d58/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:530530 errors:0 dropped:0 overruns:0 frame:0
TX packets:1591569 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:68713489 (68.7 MB) TX bytes:213710979 (213.7 MB)
$ ifconfig eth0
eth0 Link encap:Ethernet HWaddr a0:d3:c1:01:9d:58
inet6 addr: fe80::a2d3:c1ff:fe01:9d58/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:10539274 errors:0 dropped:3394 overruns:0 frame:454
TX packets:2627412 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2320560616 (2.3 GB) TX bytes:3562885157 (3.5 GB)
Interrupt:32
option interface-mtu 9000; from the lease file is being ignored by br0.
Could it be related to eth0 MTU size? If that's the case, shouldn't both
interfaces be updated?
Other info:
$ brctl show br0
bridge name bridge id STP enabled interfaces
br0 8000.a0d3c1019d58 no eth0
$ cat /etc/network/eth0.config
iface eth0 inet manual
auto br0
iface br0 inet dhcp
bridge_ports eth0
To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1403955/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1355813] Re: Interface MTU management across MAAS/juju
See also the related bug 1442257 which has a proposed fix. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1355813 Title: Interface MTU management across MAAS/juju Status in juju-core: Fix Released Status in MAAS: Triaged Status in juju-core package in Ubuntu: Triaged Status in lxc package in Ubuntu: Invalid Bug description: Context: juju + MAAS deployed OpenStack environment, misc services deployed under LXC on the bootstrap node, interfaces configured for jumbo frames - note that I had to manually set the LXC container interfaces to mtu 9000 before the bridge would do the same. Action: Reboot one of the containers; MTU on br0 resets from 9000 - 1500. This feels like more of a 'we need a better way to orchestrate MTU configuration across different services' so raising tasks for MAAS and Juju as well. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lxc 1.0.5-0ubuntu0.1 ProcVersionSignature: User Name 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 Date: Tue Aug 12 13:26:00 2014 KernLog: SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx lxcsyslog: To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1355813/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1403955] Re: DHCP's Option interface-mtu 9000 is being ignored on bridge interface br0
Since 1.23 there's no need to create juju-br0 (or as it used to be
called before - br0) at initial boot, so this should solve the issue.
** Changed in: juju-core
Status: Triaged = Fix Committed
** Changed in: juju-core
Milestone: None = 1.23-beta1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1403955
Title:
DHCP's Option interface-mtu 9000 is being ignored on bridge
interface br0
Status in juju-core:
Fix Committed
Status in isc-dhcp package in Ubuntu:
Confirmed
Bug description:
In an env with jumbo frames enabled, and using MAAS as DHCP server,
the client receives the following IPv4 lease:
$ cat /var/lib/dhcp/dhclient.br0.leases
lease {
interface br0;
fixed-address 10.230.20.26;
filename pxelinux.0;
option subnet-mask 255.255.248.0;
option dhcp-lease-time 43200;
option routers 10.230.16.1;
option dhcp-message-type 5;
option dhcp-server-identifier 10.230.20.1;
option domain-name-servers 10.230.20.1;
option interface-mtu 9000;
option broadcast-address 10.230.23.255;
option domain-name ctsstack.qa.1ss;
renew 3 2014/12/17 16:48:15;
rebind 3 2014/12/17 21:52:09;
expire 3 2014/12/17 23:22:09;
}
The interfaces show the following config after boot:
$ ifconfig br0
br0 Link encap:Ethernet HWaddr a0:d3:c1:01:9d:58
inet addr:10.230.20.26 Bcast:10.230.23.255 Mask:255.255.248.0
inet6 addr: fe80::a2d3:c1ff:fe01:9d58/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:530530 errors:0 dropped:0 overruns:0 frame:0
TX packets:1591569 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:68713489 (68.7 MB) TX bytes:213710979 (213.7 MB)
$ ifconfig eth0
eth0 Link encap:Ethernet HWaddr a0:d3:c1:01:9d:58
inet6 addr: fe80::a2d3:c1ff:fe01:9d58/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:10539274 errors:0 dropped:3394 overruns:0 frame:454
TX packets:2627412 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2320560616 (2.3 GB) TX bytes:3562885157 (3.5 GB)
Interrupt:32
option interface-mtu 9000; from the lease file is being ignored by br0.
Could it be related to eth0 MTU size? If that's the case, shouldn't both
interfaces be updated?
Other info:
$ brctl show br0
bridge name bridge id STP enabled interfaces
br0 8000.a0d3c1019d58 no eth0
$ cat /etc/network/eth0.config
iface eth0 inet manual
auto br0
iface br0 inet dhcp
bridge_ports eth0
To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1403955/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1355813] Re: Interface MTU management across MAAS/juju
Proposed a fix with http://reviews.vapour.ws/r/686/ - before starting a container, the host's primary physical NIC's MTU value is detected and applied to the container's veth device. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1355813 Title: Interface MTU management across MAAS/juju Status in juju-core: In Progress Status in MAAS: New Status in juju-core package in Ubuntu: Triaged Status in lxc package in Ubuntu: Invalid Bug description: Context: juju + MAAS deployed OpenStack environment, misc services deployed under LXC on the bootstrap node, interfaces configured for jumbo frames - note that I had to manually set the LXC container interfaces to mtu 9000 before the bridge would do the same. Action: Reboot one of the containers; MTU on br0 resets from 9000 - 1500. This feels like more of a 'we need a better way to orchestrate MTU configuration across different services' so raising tasks for MAAS and Juju as well. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lxc 1.0.5-0ubuntu0.1 ProcVersionSignature: User Name 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 Date: Tue Aug 12 13:26:00 2014 KernLog: SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx lxcsyslog: To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1355813/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1355813] Re: Interface MTU management across MAAS/juju
** Changed in: juju-core Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1355813 Title: Interface MTU management across MAAS/juju Status in juju-core: Fix Committed Status in MAAS: New Status in juju-core package in Ubuntu: Triaged Status in lxc package in Ubuntu: Invalid Bug description: Context: juju + MAAS deployed OpenStack environment, misc services deployed under LXC on the bootstrap node, interfaces configured for jumbo frames - note that I had to manually set the LXC container interfaces to mtu 9000 before the bridge would do the same. Action: Reboot one of the containers; MTU on br0 resets from 9000 - 1500. This feels like more of a 'we need a better way to orchestrate MTU configuration across different services' so raising tasks for MAAS and Juju as well. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lxc 1.0.5-0ubuntu0.1 ProcVersionSignature: User Name 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 Date: Tue Aug 12 13:26:00 2014 KernLog: SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx lxcsyslog: To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1355813/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1355813] Re: Interface MTU management across MAAS/juju
** Changed in: juju-core Assignee: (unassigned) = Dimiter Naydenov (dimitern) ** Changed in: juju-core Status: Triaged = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1355813 Title: Interface MTU management across MAAS/juju Status in juju-core: In Progress Status in MAAS: New Status in juju-core package in Ubuntu: Triaged Status in lxc package in Ubuntu: Invalid Bug description: Context: juju + MAAS deployed OpenStack environment, misc services deployed under LXC on the bootstrap node, interfaces configured for jumbo frames - note that I had to manually set the LXC container interfaces to mtu 9000 before the bridge would do the same. Action: Reboot one of the containers; MTU on br0 resets from 9000 - 1500. This feels like more of a 'we need a better way to orchestrate MTU configuration across different services' so raising tasks for MAAS and Juju as well. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lxc 1.0.5-0ubuntu0.1 ProcVersionSignature: User Name 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 Date: Tue Aug 12 13:26:00 2014 KernLog: SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx lxcsyslog: To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1355813/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
