*** This bug is a duplicate of bug 1752411 ***
https://bugs.launchpad.net/bugs/1752411
**accepting duplication**
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1786261
Title:
strongswan ipsec
*** This bug is a duplicate of bug 1752411 ***
https://bugs.launchpad.net/bugs/1752411
I also note;
I think this is (at least partially) due to strongswan leaving a
dangling duplicate DNS entry in resolve.conf.
It's 100% consistent, that after step #3 above, there is a dangling DNS
entry in
*** This bug is a duplicate of bug 1752411 ***
https://bugs.launchpad.net/bugs/1752411
** This bug has been marked a duplicate of bug 1752411
bind9-host, avahi-daemon-check-dns.sh hang forever causes network
connections to get stuck
--
You received this bug notification because you are
*** This bug is a duplicate of bug 1752411 ***
https://bugs.launchpad.net/bugs/1752411
The relationship to LP #1752411 certainly feels valid.
(I think I agree to the duplication)
Check this out btw (perhaps better submitted to the other bug) -- but --
despite "host" claiming a default
*** This bug is a duplicate of bug 1752411 ***
https://bugs.launchpad.net/bugs/1752411
$ dpkg --list | grep bind9
ii bind9-host
1:9.11.3+dfsg-1ubuntu1.1 amd64DNS lookup utility
(deprecated)
ii
*** This bug is a duplicate of bug 1752411 ***
https://bugs.launchpad.net/bugs/1752411
Yes, this is definitely another symptom (duplicate) of bug 1752411 . The
folks on that bug might be people who will know if dig can be used
instead.
--
You received this bug notification because you are a
Hi,
I just realized with you tracking it down so far - could it be "another
symptom" of bug 1752411 ?
If so we should add strongswan there as affected and make this bug a
Dup, so that ALL effects of this one issue are in one place.
I'd be glad if one of you could make the detail check if you
@paelzer, it is making an usual call to host and checking the return:
LC_ALL=C host -t soa local. 2>&1
and theoretically this maps to:
LC_ALL=C dig -t soa local. 2>&1
Practically, I don't think this works. I do not have a "local." start
of authority record and when I run these commands I get a 1
bind9-host is deprecated anyway isn't it?
Could the avahi shell script easily be modified to try dig at the same place?
Also as requested since you isolated it towards resolveconf I'm adding a
bug task for that as well.
** Also affects: bind9 (Ubuntu)
Importance: Undecided
Status: New
@ehoover; great isolation! that's absolutely it
I too noticed it hangs in several other ways randomly.
One other example I had not mentioned was failing here:
{{{
Aug 20 09:02:49 fermmy charon[3698]: 14[IKE] maximum IKE_SA lifetime 56591s
Aug 20 09:02:49 fermmy charon[3698]: 14[IKE] processing
fwiw
{{{
$ dpkg --list | grep avahi-daemon
ii avahi-daemon
0.7-3.1ubuntu1 amd64Avahi mDNS/DNS-SD
daemon
$ dpkg --list | grep resolvconf
ii resolvconf
I think I may have somewhat figured it out. @fermulator, could you get
it to lockup and then run "sudo killall host" in another terminal
window?
It looks like this is some sort of integration issue between the latest
bind9-host (used by avahi-daemon) and the latest systemd, downgrading
either one
So, I've noticed something else that may be relevant. My work's configuration
actually has two DNS servers, which show up like so:
installing DNS server 10.10.0.8 via resolvconf
installing DNS server 10.10.0.2 via resolvconf
However, I saw that there was some probability that it failed after
(yes, the upstream report back-refs this downstream report, myself or
someone else should do the needful communication once upstream is fixed)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1786261
Thanks Fermulator, no auto-import from this type of bug tracker, but the URL is
great to check!.
Since remote tracking can't be done automatically, can you ping here once
something interesting is coming back there?
** Also affects: strongswan
Importance: Undecided
Status: New
--
You
I am having a similar problem, but I have some additional tidbits:
1) I had the same issue after upgrading from 17.10 to 18.04, but before
rebooting
2) I have the same problem if I downgrade all the strongswan/charon packages to
5.5.1-4ubuntu2.2
3) First connection attempt after reboot does not
Upstream report: https://wiki.strongswan.org/issues/2724
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1786261
Title:
strongswan ipsec fails to finish connection (hangs after installing
DNS
FYI upstream issue tracker is at
https://wiki.strongswan.org/projects/strongswan/issues
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1786261
Title:
strongswan ipsec fails to finish connection
Hi Fermulator,
while I regularly pick up new strongswan versions I'm not enough of an expert
to give good suggestions on what the reason might be.
But fortunately there are often a few community members here using strongswan
that can chime in.
Never the less for a technical discussion on the
** Description changed:
as a continuation of
https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1786250 ...
(that bug can be focused on the apparmor profile issue in Ubuntu +
strongswan)
--
this bug report is for the stuck VPN connection issue
Used to work fine in
20 matches
Mail list logo
