I found the addition of the 18.04 libnss-resolve package fixed my
(intermittent) problems with name-resolution failures. Earlier comments
indicate this package was not installed. The installation alters the
nsswitch.conf file's hosts line to add "resolve [!UNAVAIL=return]"
before "dns".
--
** Changed in: systemd (Ubuntu Artful)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727237
Title:
systemd-resolved is not finding a domain
To manage
The fix for this bug is causing me problems with name resolution on the
LAN using dnsmasq as an upstream server:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1785383/comments/4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
OK,
it's here now:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727237
Title:
systemd-resolved is not finding a domain
To manage
On Wed, Apr 25, 2018 at 07:18:34PM -, Pete wrote:
> I freshly installed the latest Kubuntu Bionic nightly image from today
> night. That should be rather close to tomorrow's release.
> There systemd 237-3ubuntu10 is installed. However, it still does not
> work. I can not resolve dns out of
Axel and Pete, please file new separate bugs for your issues. This
particular bug is closed for Ubuntu 18.04 LTS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727237
Title:
systemd-resolved is
I freshly installed the latest Kubuntu Bionic nightly image from today
night. That should be rather close to tomorrow's release.
There systemd 237-3ubuntu10 is installed. However, it still does not
work. I can not resolve dns out of the box in my Hotel wifi (Quality
Hotel Augsburg, Germany).
The
Hmm... I've installed systemd 237-3ubuntu8.
Nevertheless I don't get forwarded to the captive-portal website to
login :-(.
What do I do wrong?
Axel
** Attachment added: "Forwarding to Captive-Portal login not working."
** Changed in: systemd (Ubuntu Bionic)
Assignee: Tony (toekneemi) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727237
Title:
systemd-resolved is not finding a domain
To
** Changed in: systemd (Ubuntu Bionic)
Assignee: Dimitri John Ledkov (xnox) => Tony (toekneemi)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727237
Title:
systemd-resolved is not finding a
This bug was fixed in the package systemd - 237-3ubuntu8
---
systemd (237-3ubuntu8) bionic; urgency=medium
* Workaround captive portals not responding to EDNS0 queries (DVE-2018-0001).
(LP: #1727237)
* resolved: Listen on both TCP and UDP by default. (LP: #1731522)
*
Dimitri, can you please confirm what the effect of this patch is when a
user has manually reconfigured resolved to enable DNSSEC? Does this do
the right thing, or does it become a downgrade attack?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Description changed:
+
+ [Impact]
+
+ * Certain WiFi captive portals do not support EDNS0 queries, as per RFC.
+ * Instead of responding with the captive portal IP address, they resond with
domain not found
+ * This prevents the user from hitting the captive portal login page, able to
** Changed in: systemd (Ubuntu Bionic)
Status: Triaged => Fix Committed
** Changed in: systemd (Ubuntu Bionic)
Assignee: Mathieu Trudel-Lapierre (cyphermox) => Dimitri John Ledkov (xnox)
** Changed in: systemd (Ubuntu Artful)
Assignee: Mathieu Trudel-Lapierre (cyphermox) =>
** Tags added: id-5ab9403dee8a8479eed4dba6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727237
Title:
systemd-resolved is not finding a domain
To manage notifications about this bug go to:
Dimitri,
I've performed your tasks and can confirm with that PPA applied that it works
properly.
I've emailed you the packet captures privately to your @ubuntu.com address.
I also do note the following in my journal log:
Mar 26 12:18:43 test-XPS-13-9350 systemd-resolved[507]: DVE-2018-0001
Please note this issue is now documented as a DNS violation at
https://github.com/dns-violations/dns-violations/blob/master/2018/DVE-2018-0001.md
@superm1
1. Start wireshark, start recording traffic across all interfaces, turn
wifi on, try to connect to the guest network, fail, stop collecting
@cyphermox,
I can readily reproduce this using my company's guest network with
current systemd in Bionic. We use "securelogin.networks.dell.com" for
our redirector. If I can provide something useful, happy to do so.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Tags added: id-5a1c75741121466ff62dc286
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727237
Title:
systemd-resolved is not finding a domain
To manage notifications about this bug go to:
I can't seem to find where you sent me logs?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727237
Title:
systemd-resolved is not finding a domain
To manage notifications about this bug go to:
@Mathieu,
Were the logs I sent you of any value to you for the debugging?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727237
Title:
systemd-resolved is not finding a domain
To manage
@Axel, can you record what you see on the screen as you login (I do not
need to see keypresses, but maybe seeing what happens on screen as
things refresh would help).
Also, have you tried what I wrote in comment #8, stopping systemd-
networkd, restarting with the debugging enabled, and
I too am still encountering this issue.
Since I can't resolve the webpage to the captive portal I have to
manually enter its IP 1.1.1.1
Then accept the agreement. However afterwards DNS still fails to resolve
web-pages.
Today I edited /etc/resolv.conf as before, adding Google DNS to show
this.
@ #19: Mathieu,
I included the '234-2ubuntu12.3~mtrudel1' from the ppa you mention to my
computer.
Unfortunately no change in behavior. I am still not forwarded to the captive
portal after connecting to this particular wifi.
Do you have a suggestion what I could try?
@ #20: Does this: 'but it
I also have been experiencing this. Connecting to WiFi network that uses
any captive portal fails.
I dual boot with Windows, and everything is fine in Windows.
System:
Ubuntu 17.10 (Clean install)
Behavior:
After authenticating with the portal and connecting I cannot resolve DNS.
My work
Xenial is affected too (systemd v229 looks to be, in general), so when
SRUing we might as well push the fix there too, even if resolved is not
typically used on Xenial.
** Also affects: systemd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Xenial)
Packages are in my ppa:
https://launchpad.net/~cyphermox/+archive/ubuntu/sru/+packages
For bionic and xenial. I'll do one further build for artful.
>From the look of things though, this will only be built and ready for
amd64/i386, not for other architectures just yet.
** Changed in: systemd
I updated the importance and status as well, this bug was not in fact
Fix Committed, I checked with Dimitri. Fix Committed was set because of
the proposed change to caching, but it doesn't look like it helps.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I would like to test it here with our public company-network that uses
securelogin.arubanetworks.com.
However, I run 17.10 on my laptop and installing the whole new systemd
235 from Bionic is not so straightforward I experienced. I gave up with
too many unfulfilled dependencies.
So could you
So, after looking at it more, it seems the issue with Datavalet is due
to EDNS0-enabled queries failing to be captured and rewritten by the
captive portal. It might not in fact be the same issue as for
securelogin.arubanetworks.com, though the wireless hardware comes from
the same manufacturer.
I
Can we know what's the fix?
I apologize but I cannot recognize the patch in this thread.
I am running ubuntu 17.10 and am affected by a
securelogin.arubanetworks.com-company-public-network.
I would like to test the fix.
How can I do that?
Thank you very much in advance.
Best regards
--
You
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu Artful)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727237
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu Zesty)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727237
** Also affects: systemd (Ubuntu Zesty)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Bionic)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: systemd (Ubuntu Bionic)
Importance: High
Status: Triaged
** Also affects: systemd (Ubuntu Artful)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks all, and Dimitri allow me to sponsor that Starbucks coffee :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727237
Title:
systemd-resolved is not finding a domain
To manage notifications
I believe caching is enabled by default, this might be a regression in
behaviour since switching to 127.0.0.53 caching resolver. It does drop
caches upon every new connection / re-connection.
It is freezing out there and snowing out there. But I guess I'll have to
make trek to Starbucks with my
My understanding is that systemd-resolved as shipped in Ubuntu is meant
to not have DNS caching enabled at all.
https://lists.ubuntu.com/archives/ubuntu-devel/2016-June/039375.html
Looking at the default resolved.conf and the resolved.conf(5) manpage,
it appears we do have DNS caching enabled.
So I managed to reproduce this in a way that looks correct (Starbucks
WiFi here uses Datavalet but fails in a way that looks the same: it
thinks you're logged in once you clicked the "Login" button on the
captive portal page once, but then updates DNS, but still attempts to
look up
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727237
Title:
systemd-resolved is not finding a domain
To manage notifications about this bug go to:
Checking for the state of the domain from outside a captive portal won't
get much; "securelogin.arubanetworks.com" only exists while you're
behind the captive portal, in unauthenticated mode.
I think the next steps will be to do some testing with various captive
portals and see why
I thought I'd add the information from my favourite DNS debugging tool
while the data may still be close to useful:
dnsviz reports NXDOMAIN for securelogin.arubanetworks.com
http://dnsviz.net/d/securelogin.arubanetworks.com/dnssec/
dnsviz also currently reports three warnings:
- com to
** Changed in: systemd (Ubuntu)
Status: Incomplete => New
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727237
Title:
The issue is with systemd-resolvd not adding the captive portal DNS
after the logon. This worked fine with dnsmasq in 16.04 (and I assume
17.04).
For my laptop I have currently changed to 'unbound' for DNS resolution.
Note: If you are running Qemu/KVM you will want to keep dnsmasq-base
package.
All captive portal wifi connections are failing with Ubuntu 17.10. This
was confirmed on two different captive portals which both worked just
fine with other devices. The solution was to go back to Ubuntu 17.04.
You get to the portal page, put in whatever info, then afterwards the
redirect
What is the release / package version in use of systemd?
234-2ubuntu12.1
How is the networking configured: netplan, ifupdown, networkd, networkmanager?
networkmanager (I presume, ubuntu 17.10 default)
What is the contents of /etc/resolv.conf?
# This file is managed by man:systemd-resolved(8).
I also experienced this problem on Ubuntu 17.10. Tried to connect to a
wifi network, that utilized a captive portal, failed miserably. The DNS
redirect to the captive portal would not occur. Manually overwriting
/etc/resolv.conf with nameservers other than "127.0.0.53" got me to the
captive portal
Yes, this is a captive portal situation on up-to-date 17.10. The captive
portal popup fails with a DNS error looking for
securelogin.arubanetworks.com and then hilarity ensues. Manually editing
/etc/resolv.conf to use one of these DNS servers makes it all work. So
the problem is systemd-resolved
What is the release / package version in use of systemd?
How is the networking configured: netplan, ifupdown, networkd,
networkmanager?
What is the contents of /etc/resolv.conf?
Where does the symlink of /etc/resolv.conf point to? (if it is a
symlink)
What is the contents of
49 matches
Mail list logo
