[Touch-packages] [Bug 1825470] [NEW] systemd-networkd: Deconfigures bridge after last attached interface disconnects (ie: LXC)
Public bug reported: Ubuntu 18.04 Bionic Beaver An issue was reported to systemd-networkd on GitHub - https://github.com/systemd/systemd/issues/11650 - and all the thorough details are there. Using anonymous bridges (ie: not attached to physical NICs) is problematic with systemd-networkd as they get deconfigured as soon as the last attached device disconnects (ie: a LXC container). Static IP configuration must be done again manually. The root cause is that systemd-networkd assumes that every network interface have a carrier signal. There's no notion of carrier signal on anonymous bridges, a case not properly handled by systemd-networkd. The systemd dev team provided a patch to address the issue and it would be nice to be integrated on the Ubuntu package. The PR is here : https://github.com/systemd/systemd/commit/93b4dab57e2e13bd804cbee999241be65a443e2e To get the proper fix, you'll need to combine 2 patches : - The one from the PR above - Another patch [1] which fixes a segfault introduced by the PR. [1] https://github.com/systemd/systemd/pull/11741/commits/a294af6810df3c18909a96b556deadba0e2ab0a9 On my test environment, I rebuild the Ubuntu package with the 2 patches above from "237-3ubuntu10.17" to "237-3ubuntu10.20" and made thorough tests without hiting a single issue so I think we can assume that these 2 patches are safe to use. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/1825470 Title: systemd-networkd: Deconfigures bridge after last attached interface disconnects (ie: LXC) Status in systemd package in Ubuntu: New Bug description: Ubuntu 18.04 Bionic Beaver An issue was reported to systemd-networkd on GitHub - https://github.com/systemd/systemd/issues/11650 - and all the thorough details are there. Using anonymous bridges (ie: not attached to physical NICs) is problematic with systemd-networkd as they get deconfigured as soon as the last attached device disconnects (ie: a LXC container). Static IP configuration must be done again manually. The root cause is that systemd-networkd assumes that every network interface have a carrier signal. There's no notion of carrier signal on anonymous bridges, a case not properly handled by systemd-networkd. The systemd dev team provided a patch to address the issue and it would be nice to be integrated on the Ubuntu package. The PR is here : https://github.com/systemd/systemd/commit/93b4dab57e2e13bd804cbee999241be65a443e2e To get the proper fix, you'll need to combine 2 patches : - The one from the PR above - Another patch [1] which fixes a segfault introduced by the PR. [1] https://github.com/systemd/systemd/pull/11741/commits/a294af6810df3c18909a96b556deadba0e2ab0a9 On my test environment, I rebuild the Ubuntu package with the 2 patches above from "237-3ubuntu10.17" to "237-3ubuntu10.20" and made thorough tests without hiting a single issue so I think we can assume that these 2 patches are safe to use. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1825470/+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 1813334] [NEW] isc-dhcp-server & isc-dhcp-server6 systemd service units both use $INTERFACES instead of $INTERFACESv4 and $INTERFACESv6
Public bug reported: Both isc-dhcp-server and isc-dhcp-server6 systemd service units both use $INTERFACES instead of $INTERFACESv4 and $INTERFACESv6 respectively which are declared in /etc/default/isc-dhcp-server It prevents the DHCP server to only operate on specific interfaces. isc-dhcp-server 4.3.5-3ubuntu7 Ubuntu 18.04 Bionic Beaver ** Affects: isc-dhcp (Ubuntu) Importance: Undecided Status: Invalid ** Description changed: Both isc-dhcp-server and isc-dhcp-server6 systemd service units both use $INTERFACES instead of $INTERFACESv4 and $INTERFACESv6 respectively which are declared in /etc/default/isc-dhcp-server It prevents the DHCP server to only operate on specific interfaces. + + isc-dhcp-server 4.3.5-3ubuntu7 + Ubuntu 18.04 Bionic Beaver ** Changed in: isc-dhcp (Ubuntu) Status: New => Invalid -- 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/1813334 Title: isc-dhcp-server & isc-dhcp-server6 systemd service units both use $INTERFACES instead of $INTERFACESv4 and $INTERFACESv6 Status in isc-dhcp package in Ubuntu: Invalid Bug description: Both isc-dhcp-server and isc-dhcp-server6 systemd service units both use $INTERFACES instead of $INTERFACESv4 and $INTERFACESv6 respectively which are declared in /etc/default/isc-dhcp-server It prevents the DHCP server to only operate on specific interfaces. isc-dhcp-server 4.3.5-3ubuntu7 Ubuntu 18.04 Bionic Beaver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1813334/+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 1813334] Re: isc-dhcp-server & isc-dhcp-server6 systemd service units both use $INTERFACES instead of $INTERFACESv4 and $INTERFACESv6
Please ignore, this is a duplicate of #1774342 which I missed when searching for previous reports -- 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/1813334 Title: isc-dhcp-server & isc-dhcp-server6 systemd service units both use $INTERFACES instead of $INTERFACESv4 and $INTERFACESv6 Status in isc-dhcp package in Ubuntu: Invalid Bug description: Both isc-dhcp-server and isc-dhcp-server6 systemd service units both use $INTERFACES instead of $INTERFACESv4 and $INTERFACESv6 respectively which are declared in /etc/default/isc-dhcp-server It prevents the DHCP server to only operate on specific interfaces. isc-dhcp-server 4.3.5-3ubuntu7 Ubuntu 18.04 Bionic Beaver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1813334/+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 1656352] Re: apt does not honor Proxy-Auto-Detect for HTTPS URLs
Why the "catch" isn't documented anywhere? There's another catch here : If the proxy setting needs to be of the same type as the URL, how exactly am I supposed to know in advance when querying the information? As you can imagine, the /etc/apt/souces.list.d is filed with mixed content such as HTTP and HTTPS so how can I sort this out? I've made a quick test and there's nothing in the environment nor arguments passed to "app" that would help make the decision. Anyway, given the info you provide, even if I decide to go full HTTPS on the proxy, this would break the classic HTTP URLs. This sounds like a big design mistake here... this forces people to HARDCODE things in configuration which really bad design :-( What's so harmful in using an HTTP proxy to fetch data from an HTTPS URL? That's just a proxy to get Internet access, nothing more, because depending on the environment, you may have (or not) direct Internet access, hence the use of Proxy-Auto-Detect. You really need to reconsider this! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1656352 Title: apt does not honor Proxy-Auto-Detect for HTTPS URLs Status in apt package in Ubuntu: Triaged Bug description: apt(-get) does not honor Proxy-Auto-Detect configuration in any way for HTTPS URLs. ex: vi /etc/apt/apt.conf.d/99-proxy-auto-detect Acquire::http:Proxy-Auto-Detect "/path/to/app"; "app" performs some actions and output the name of the proxy server according to some internal rules, in the form "http://proxy.domain.tld:1234/"; This works perfectly for all HTTP-like "deb http://example.com/ xxx" URLs but is ignored for HTTPS URLs. Setting "Acquire::https:Proxy- Auto-Detect" or even the legacy variable name "ProxyAutoDetect" (without dashes) does not help either. This is very annoying as the very purpose of this auto-detection is to be network environment aware instead of using a hardcoded value for the proxy setting. This should be fixed. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1656352/+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 1656352] [NEW] apt does not honor Proxy-Auto-Detect for HTTPS URLs
Public bug reported: apt(-get) does not honor Proxy-Auto-Detect configuration in any way for HTTPS URLs. ex: vi /etc/apt/apt.conf.d/99-proxy-auto-detect Acquire::http:Proxy-Auto-Detect "/path/to/app"; "app" performs some actions and output the name of the proxy server according to some internal rules, in the form "http://proxy.domain.tld:1234/"; This works perfectly for all HTTP-like "deb http://example.com/ xxx" URLs but is ignored for HTTPS URLs. Setting "Acquire::https:Proxy-Auto- Detect" or even the legacy variable name "ProxyAutoDetect" (without dashes) does not help either. This is very annoying as the very purpose of this auto-detection is to be network environment aware instead of using a hardcoded value for the proxy setting. This should be fixed. Thank you. ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Description changed: apt(-get) does not honor Proxy-Auto-Detect configuration in any way for HTTPS URLs. ex: vi /etc/apt/apt.conf.d/99-proxy-auto-detect Acquire::http:Proxy-Auto-Detect "/path/to/app"; "app" performs some actions and output the name of the proxy server according to some internal rules, in the form "http://proxy.domain.tld:1234/"; This works perfectly for all HTTP-like "deb http://example.com/ xxx" URLs but is ignored for HTTPS URLs. Setting "Acquire::https:Proxy-Auto- Detect" or even the legacy variable name "ProxyAutoDetect" (without - dashes) does help either. + dashes) does not help either. This is very annoying as the very purpose of this auto-detection is to be network environment aware instead of using a hardcoded value for the proxy setting. This should be fixed. Thank you. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1656352 Title: apt does not honor Proxy-Auto-Detect for HTTPS URLs Status in apt package in Ubuntu: New Bug description: apt(-get) does not honor Proxy-Auto-Detect configuration in any way for HTTPS URLs. ex: vi /etc/apt/apt.conf.d/99-proxy-auto-detect Acquire::http:Proxy-Auto-Detect "/path/to/app"; "app" performs some actions and output the name of the proxy server according to some internal rules, in the form "http://proxy.domain.tld:1234/"; This works perfectly for all HTTP-like "deb http://example.com/ xxx" URLs but is ignored for HTTPS URLs. Setting "Acquire::https:Proxy- Auto-Detect" or even the legacy variable name "ProxyAutoDetect" (without dashes) does not help either. This is very annoying as the very purpose of this auto-detection is to be network environment aware instead of using a hardcoded value for the proxy setting. This should be fixed. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1656352/+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
