Description of problem:
after updating to 1.0.3 libreswan stopped working. It's connected but it says
[vbenes@trautenberg ~]$ ping 220.127.116.11
connect: Network is unreachable
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.connect to libreswan vpn (profile has option to use connection just for resources on the network)
2.ping some network in vpn
3.ping some network outside of vpn
both should work
Created attachment 1045763 [details]
I was connected to wired and wireless and connected to libreswan, at the end there is a disconnect
Created attachment 1045818 [details]
log from older version that's working well
I was connected on wireless network and connected to vpn that was actually working
I would say the problem is that you can't connect to VPN while you are on Red Hat wired network. You have to be on external network or Wi-Fi. Please try again with Wi-Fi only.
ERROR: asynchronous network error report on enp0s25 (sport=4500) for message to 18.104.22.168 port 4500, complainant 10.34.131.192: No route to host [errno 113, origin ICMP type 3 code 1 (not authenticated)]
no this is not true, it happened to me at home w/o wired network. I've connected to wireless only here and log is attached
Created attachment 1045871 [details]
log with new NM and wireless only
I am correctly connected (gnome shell's icon says that) but network is unavailable and it's crippled even after disconnect so I had to off/on wireless to get it back working
Fixed on master:
and relevant bits are backported to nm-1-0 branch too.
Should be fixed with the next build.
Not really fixed.
Created attachment 1069715 [details]
vpn-connection: fix unsetting the gateway
Created attachment 1069716 [details]
device: don't reset NM_UNMANAGED_DEFAULT when platform doesn't override this
(In reply to Lubomir Rintel from comment #10)
> Created attachment 1069715 [details]
> vpn-connection: fix unsetting the gateway
(In reply to Lubomir Rintel from comment #11)
> Created attachment 1069716 [details]
> device: don't reset NM_UNMANAGED_DEFAULT when platform doesn't override this
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.