strongswan get RANDOM dns
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I'm getting a really strange issue on fresh Fedora 28 MATE with an IKEv2 IPSEC VPN.
First thing: this VPN is currently used by some other clients (some windows and my old Fedora 26) with NO issue.
Configuring it on a fresh installed Fedora 28 i can connect, but, from server, i get "random" DNS servers (random in the real way, the change from a connection to another and are random IP from random classes around the world):
Logs show something like:
May 9 14:22:30 localhost NetworkManager[783]: <info> [1525868550.0975] vpn-connection[0x55f878e58350,067f1bf4-0581-49a7-a18b-542b64fe8b7a,"VPN",0]: Data: Internal DNS: 144.202.1.204
May 9 14:22:30 localhost NetworkManager[783]: <info> [1525868550.0975] vpn-connection[0x55f878e58350,067f1bf4-0581-49a7-a18b-542b64fe8b7a,"VPN",0]: Data: Internal DNS: 80.203.1.204
May 9 14:22:30 localhost NetworkManager[783]: <info> [1525868550.0975] vpn-connection[0x55f878e58350,067f1bf4-0581-49a7-a18b-542b64fe8b7a,"VPN",0]: Data: Internal DNS: 112.90.1.204
May 9 14:22:30 localhost NetworkManager[783]: <info> [1525868550.0975] vpn-connection[0x55f878e58350,067f1bf4-0581-49a7-a18b-542b64fe8b7a,"VPN",0]: Data: Internal DNS: 16.82.1.204
Trying to force on network manager the correct internal DNS everything work fine instead.
I already googled searching for a bug or a known issue but i didn't found anything, someone has/had a similar issue?
fedora vpn ipsec strongswan
add a comment |Â
up vote
0
down vote
favorite
I'm getting a really strange issue on fresh Fedora 28 MATE with an IKEv2 IPSEC VPN.
First thing: this VPN is currently used by some other clients (some windows and my old Fedora 26) with NO issue.
Configuring it on a fresh installed Fedora 28 i can connect, but, from server, i get "random" DNS servers (random in the real way, the change from a connection to another and are random IP from random classes around the world):
Logs show something like:
May 9 14:22:30 localhost NetworkManager[783]: <info> [1525868550.0975] vpn-connection[0x55f878e58350,067f1bf4-0581-49a7-a18b-542b64fe8b7a,"VPN",0]: Data: Internal DNS: 144.202.1.204
May 9 14:22:30 localhost NetworkManager[783]: <info> [1525868550.0975] vpn-connection[0x55f878e58350,067f1bf4-0581-49a7-a18b-542b64fe8b7a,"VPN",0]: Data: Internal DNS: 80.203.1.204
May 9 14:22:30 localhost NetworkManager[783]: <info> [1525868550.0975] vpn-connection[0x55f878e58350,067f1bf4-0581-49a7-a18b-542b64fe8b7a,"VPN",0]: Data: Internal DNS: 112.90.1.204
May 9 14:22:30 localhost NetworkManager[783]: <info> [1525868550.0975] vpn-connection[0x55f878e58350,067f1bf4-0581-49a7-a18b-542b64fe8b7a,"VPN",0]: Data: Internal DNS: 16.82.1.204
Trying to force on network manager the correct internal DNS everything work fine instead.
I already googled searching for a bug or a known issue but i didn't found anything, someone has/had a similar issue?
fedora vpn ipsec strongswan
1
Self-replying... just noticed this bug report: bugzilla.redhat.com/show_bug.cgi?id=1574939
â Tsumi
May 9 at 13:10
1
You should put this as an answer
â Kiwy
May 9 at 14:12
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I'm getting a really strange issue on fresh Fedora 28 MATE with an IKEv2 IPSEC VPN.
First thing: this VPN is currently used by some other clients (some windows and my old Fedora 26) with NO issue.
Configuring it on a fresh installed Fedora 28 i can connect, but, from server, i get "random" DNS servers (random in the real way, the change from a connection to another and are random IP from random classes around the world):
Logs show something like:
May 9 14:22:30 localhost NetworkManager[783]: <info> [1525868550.0975] vpn-connection[0x55f878e58350,067f1bf4-0581-49a7-a18b-542b64fe8b7a,"VPN",0]: Data: Internal DNS: 144.202.1.204
May 9 14:22:30 localhost NetworkManager[783]: <info> [1525868550.0975] vpn-connection[0x55f878e58350,067f1bf4-0581-49a7-a18b-542b64fe8b7a,"VPN",0]: Data: Internal DNS: 80.203.1.204
May 9 14:22:30 localhost NetworkManager[783]: <info> [1525868550.0975] vpn-connection[0x55f878e58350,067f1bf4-0581-49a7-a18b-542b64fe8b7a,"VPN",0]: Data: Internal DNS: 112.90.1.204
May 9 14:22:30 localhost NetworkManager[783]: <info> [1525868550.0975] vpn-connection[0x55f878e58350,067f1bf4-0581-49a7-a18b-542b64fe8b7a,"VPN",0]: Data: Internal DNS: 16.82.1.204
Trying to force on network manager the correct internal DNS everything work fine instead.
I already googled searching for a bug or a known issue but i didn't found anything, someone has/had a similar issue?
fedora vpn ipsec strongswan
I'm getting a really strange issue on fresh Fedora 28 MATE with an IKEv2 IPSEC VPN.
First thing: this VPN is currently used by some other clients (some windows and my old Fedora 26) with NO issue.
Configuring it on a fresh installed Fedora 28 i can connect, but, from server, i get "random" DNS servers (random in the real way, the change from a connection to another and are random IP from random classes around the world):
Logs show something like:
May 9 14:22:30 localhost NetworkManager[783]: <info> [1525868550.0975] vpn-connection[0x55f878e58350,067f1bf4-0581-49a7-a18b-542b64fe8b7a,"VPN",0]: Data: Internal DNS: 144.202.1.204
May 9 14:22:30 localhost NetworkManager[783]: <info> [1525868550.0975] vpn-connection[0x55f878e58350,067f1bf4-0581-49a7-a18b-542b64fe8b7a,"VPN",0]: Data: Internal DNS: 80.203.1.204
May 9 14:22:30 localhost NetworkManager[783]: <info> [1525868550.0975] vpn-connection[0x55f878e58350,067f1bf4-0581-49a7-a18b-542b64fe8b7a,"VPN",0]: Data: Internal DNS: 112.90.1.204
May 9 14:22:30 localhost NetworkManager[783]: <info> [1525868550.0975] vpn-connection[0x55f878e58350,067f1bf4-0581-49a7-a18b-542b64fe8b7a,"VPN",0]: Data: Internal DNS: 16.82.1.204
Trying to force on network manager the correct internal DNS everything work fine instead.
I already googled searching for a bug or a known issue but i didn't found anything, someone has/had a similar issue?
fedora vpn ipsec strongswan
asked May 9 at 13:02
Tsumi
1263
1263
1
Self-replying... just noticed this bug report: bugzilla.redhat.com/show_bug.cgi?id=1574939
â Tsumi
May 9 at 13:10
1
You should put this as an answer
â Kiwy
May 9 at 14:12
add a comment |Â
1
Self-replying... just noticed this bug report: bugzilla.redhat.com/show_bug.cgi?id=1574939
â Tsumi
May 9 at 13:10
1
You should put this as an answer
â Kiwy
May 9 at 14:12
1
1
Self-replying... just noticed this bug report: bugzilla.redhat.com/show_bug.cgi?id=1574939
â Tsumi
May 9 at 13:10
Self-replying... just noticed this bug report: bugzilla.redhat.com/show_bug.cgi?id=1574939
â Tsumi
May 9 at 13:10
1
1
You should put this as an answer
â Kiwy
May 9 at 14:12
You should put this as an answer
â Kiwy
May 9 at 14:12
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
It was a not-pached bug in the strongswan rpm package:
https://bugzilla.redhat.com/show_bug.cgi?id=1574939
Fixed in strongswan-5.6.2-6.fc28, issue solved with system upgrade:
dnf clean all
dnf update
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
It was a not-pached bug in the strongswan rpm package:
https://bugzilla.redhat.com/show_bug.cgi?id=1574939
Fixed in strongswan-5.6.2-6.fc28, issue solved with system upgrade:
dnf clean all
dnf update
add a comment |Â
up vote
1
down vote
accepted
It was a not-pached bug in the strongswan rpm package:
https://bugzilla.redhat.com/show_bug.cgi?id=1574939
Fixed in strongswan-5.6.2-6.fc28, issue solved with system upgrade:
dnf clean all
dnf update
add a comment |Â
up vote
1
down vote
accepted
up vote
1
down vote
accepted
It was a not-pached bug in the strongswan rpm package:
https://bugzilla.redhat.com/show_bug.cgi?id=1574939
Fixed in strongswan-5.6.2-6.fc28, issue solved with system upgrade:
dnf clean all
dnf update
It was a not-pached bug in the strongswan rpm package:
https://bugzilla.redhat.com/show_bug.cgi?id=1574939
Fixed in strongswan-5.6.2-6.fc28, issue solved with system upgrade:
dnf clean all
dnf update
answered May 28 at 8:47
Tsumi
1263
1263
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f442759%2fstrongswan-get-random-dns%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
1
Self-replying... just noticed this bug report: bugzilla.redhat.com/show_bug.cgi?id=1574939
â Tsumi
May 9 at 13:10
1
You should put this as an answer
â Kiwy
May 9 at 14:12