I've found a workaround for the issue: using `nm-connection-editor` I've
put my company's domains into the list of additional domain searches,
and this makes the split tunnel works with the domains propagating
correctly.
--
You received this bug notification because you are a member of Ubuntu
To confirm again:
$ systemd-resolve --status | grep "Current DNS" -A 2 -B 1
DNSSEC supported: no
Current DNS Server: 192.168.1.1
DNS Servers: 192.168.1.1
DNS Domain: ~.
This remains true even if I manually force the right DNS in the VPN
settings.
** Changed in: network-manager (Ubuntu)
Assignee: Till Kamppeter (till-kamppeter) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829838
Title:
1.10.14-0ubuntu2 breaks DNS
Changing status to this bug since:
- it affects multiple colleagues of mine with the same setup
- it affects me under Ubuntu 20.04 too, fully updated with the following
versions:
- systemd 245.4-4ubuntu3.1
- network-manager 1.22.10-1ubuntu2.1
- network-manager-openvpn 1.8.12-1
-
Status changed to 'Confirmed' because the bug affects multiple users.
** 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/1829838
Title:
** Project changed: null-and-void => systemd (Ubuntu)
** No longer affects: systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829838
Title:
1.10.14-0ubuntu2 breaks DNS propagation
** Package changed: network-manager (Debian) => null-and-void
** Changed in: null-and-void
Assignee: DKA (kopax) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829838
Title:
Sorry for that long post, I am having an issue I can't send SMS and it
seems to be related to a certain org.pacmac , any clue?
** Also affects: network-manager (Debian)
Importance: Undecided
Status: New
** Changed in: network-manager (Debian)
Assignee: (unassigned) => DKA (kopax)
Nope, behavior is the same between 1.10.6-2ubuntu1.1 and
1.10.6-2ubuntu1.2: broken if using split traffic between VPN and normal
connection.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829838
Jean, does this mean that 1.10.6-2ubuntu1.1 works perfectly for you and
1.10.6-2ubuntu1.2 shows the problem you mention?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829838
Title:
Hi Till, I've installed network-manager 1.10.6-2ubuntu1.2 from proposed
as suggested in https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/1754671/comments/143 and no, the issue is still there: if I
use the split VPN connection I do not get the DNS under systemd-resolve
--status; if I
Jean, a new Bionic SRU for bug 1754671 got issued, now much less
invasive simply backporting the fixes and not being a full upstream
update. Please follow the instructions in bug 1754671. If you are still
running 1.10.14 (the old SRU) please downgrade to the old network-
manager and then do the
Ouch, it go truncated locally, not during upload :( The local copy of
that file is truncated too.
Since you got the one without segmentation, you only got the logs from
the one that is currently working.
I re-did the experiment, and using the `--since` option of journalctl
I've cut the logs to
The shorter one ends at Jul 1, long before I asked you for the tests, and also
its last line looks broken. It is mot probably incomplete, somehow a part of it
got lost during upload.
In the longer one I have found one of your two tests. I have cut it at the
beginning of that test and uploaded
I did the tests in succession, obviously the longer one is the second in
the sequence. Sorry for not noticing that the logs had the whole
history.
So you can basically take the last timestamp from the shorter log and
use it to cut the longer one. The test spans just a couple of minutes
before and
The longer of your two attached log files, log-network-manager-without-
segmentation.txt, seems to contain at least one of your two tests, so I
extracted the part from your test starting (last start of network-
manager, with log verbosity set to contain and messages)
up to the end. I have
Sorru for the late reply, I had a lot to do.
I am not sure whether you have correctly taken the logs.
Both are taken on July 25 but when you look into them, they span the
following time frames:
log-network-manager-with-segmentation.txt:Jan 31 - July 1
** Attachment added: "log-network-manager-with-segmentation.txt"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829838/+attachment/5279222/+files/log-network-manager-with-segmentation.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: "log-network-manager-without-segmentation.txt"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829838/+attachment/5279221/+files/log-network-manager-without-segmentation.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Jean, thank you for the input, could you retest these two cases (with
and without split connection) but create debug logs of Network Manager
and systemd-resolved, following the instructions on
https://wiki.ubuntu.com/DebuggingNetworkManager (and/or of my comment
#10)?
--
You received this bug
My systemd is newer (237-3ubuntu10.24), instead network manager is
locked at 1.10.6 (1.10.6-2ubuntu1.1). I've upgraded network-manager as
suggested to 1.10.14-0ubuntu2 and rebooted.
I've shut down both my Wifi and LAN since I'm at the office, and hooked
up my phone with USB tethering to use an
Please make sure your system is fully up-to-date. Especially make sure
your systemd package is 237-3ubuntu10.22 or newer. Now check your
network-manager package. If it is not 1.10.14-0ubuntu2 (probably it is
1.10.6) update it from bionic-proposed as described in comment #11 of
bug #1754671. Then
Can you please explain step-by-step what I need to do to test? I
understand purging the script, but I don't know what should I do in
regard to the Network package. I'm still on 18.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Jean, could you for your tests in addition to installing the two SRUs
uninstall the openvpn-systemd-resolved package with
sudo apt purge openvpn-systemd-resolved
and then reboot?
The openvpn-systemd-resolved is actually not needed for network-manager
with systemd-resolved in Ubuntu and I have
Jean, we need your cooperation to find out whether our SRU of Network
Manager for Bionic (NM 1.10.14) actually has a regression or whether
your problem was caused by the missing update of systemd. With this
information we can help many other users of Bionic who suffer other bugs
and for which we
Jean, note that if you test the two SRUs and confirm us that they solve
the problem for you, you unblock this SRU and give us way to provide
further SRUs on Network Manager in the future, as Bionic has still some
years to go.
--
You received this bug notification because you are a member of
The SRU for systemd has arrived in bionic-proposed (see bug 1754671).
Could you make sure that you have installed BOTH the network-manager and
systemd SRUs from bionic-proposed (to make sure that I did not perhaps
do something wrong with the systemd update in my PPA). Versions should
be:
Sorry there was a part missing. Let us try again:
Please create the following files (and directories if needed for them):
1. /etc/systemd/journald.d/noratelimit.conf containing
RateLimitIntervalSec=0
RateLimitBurst=0
2. /etc/NetworkManager/conf.d/debug.conf
[logging]
level=TRACE
domains=ALL
1. /etc/systemd/journald.d/noratelimit.conf containing
RateLimitIntervalSec=0
RateLimitBurst=0
2. /etc/NetworkManager/conf.d/debug.conf
[logging]
level=TRACE
domains=ALL
Then restart journald:
sudo systemctl restart systemd-journald
and NetworkManager:
sudo systemctl restart network-manager
I am rather new to network-manager internals, but could you try the
command
sudo nmcli con modify "$COMPANY VPN" ipv4.dns-priority -1 ipv4.dns-
search ~.
Does this solve your problem?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829838
Title:
1.10.14-0ubuntu2 breaks DNS propagation from VPN
To manage notifications about this bug go to:
Due to the SRU regressions reported in LP: #1829838 and LP: #1829566, I
have reverted this SRU for the moment, restoring network-manager
1.10.6-2ubuntu1.1 to bionic-updates.
network-manager 1.10.14-0ubuntu2 remains available in bionic-proposed
for testing purposes.
--
You received this bug
Unfortunately, the SRU for systemd did not yet get processed. Therefore
I have now uploaded this version of systemd to my PPA:
https://launchpad.net/~till-kamppeter/+archive/ubuntu/ppa
Please follow this link, follow the instructions in the section "Adding
this PPA to your system", then update
Sorry, what fix are you referring to? Can you point me to a specific
comment?
> Does this mean that if you install the openvpn-systemd-resolved
package your problem gets solved without downgrading network-manager?
Nope, I need that package from the start anyway to make everything work,
I
In the initial posting you say that "systemd-resolve --status" shows the
new DNS but does not get used, could you also try out the systemd fix of
bug 1754671?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
> Does this mean that if you install the openvpn-systemd-resolved package
> your problem gets solved without downgrading network-manager? Perhaps we
> could add a dependency which would install this package automatically.
This is a universe package which NetworkManager should not require in
order
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829838
Title:
1.10.14-0ubuntu2 breaks DNS propagation from VPN
To manage
In bug 120 you say:
I had this same issue and I circumvented it installing the update-
systemd-resolved script through the openvpn-systemd-resolved package.
Does this mean that if you install the openvpn-systemd-resolved package
your problem gets solved without downgrading network-manager?
Thanks for new report and confirming that downgrading fixes the issue
** Tags added: regression-update
** Changed in: network-manager (Ubuntu)
Importance: Undecided => High
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Till Kamppeter (till-kamppeter)
--
You
39 matches
Mail list logo
