strongswan get RANDOM dns

The name of the pictureThe name of the pictureThe name of the pictureClash 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?







share|improve this question















  • 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














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?







share|improve this question















  • 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












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?







share|improve this question











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?









share|improve this question










share|improve this question




share|improve this question









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












  • 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










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





share|improve this answer





















    Your Answer







    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "106"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    convertImagesToLinks: false,
    noModals: false,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );








     

    draft saved


    draft discarded


















    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






























    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





    share|improve this answer

























      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





      share|improve this answer























        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





        share|improve this answer













        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






        share|improve this answer













        share|improve this answer



        share|improve this answer











        answered May 28 at 8:47









        Tsumi

        1263




        1263






















             

            draft saved


            draft discarded


























             


            draft saved


            draft discarded














            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













































































            Popular posts from this blog

            How to check contact read email or not when send email to Individual?

            Bahrain

            Postfix configuration issue with fips on centos 7; mailgun relay