xxxxzzz

Forum Replies Created

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • in reply to: Exit on bad config flag #12726
    xxxxzzz
    Participant

      Works perfectly!
      Unrelated suggestion: display version info in the initial notice message i.e.

      Wiresock WireGuard Vpn Client v1.2.14 running as..

      in reply to: Exit on bad config flag #12724
      xxxxzzz
      Participant

        Vadim, privet!
        It works if log level is debug/all, does not work in none log level mode it seems

        in reply to: Exit on bad config flag #12701
        xxxxzzz
        Participant

          wiresock-client is running as an application

          Exactly, you got my idea 🙂

          in reply to: Exit on bad config flag #12699
          xxxxzzz
          Participant

            Hey Vadim!
            I do not use the service as you can see from my command line (I assume running wiresock-client does not interact with services by any means).

            But in my opinion the situation when config is ok and Wireguard server is unreachable VS config is bad/missing are two completely different situations, and I would expect wiresock exiting on trying to import a bad config.

            May sound not intuitive but with a flag it sounds like a good idea in my head.
            So something like wiresock-client.exe run -config vpn.conf -exitonbadconfig would just close the process after failing to import/validate the vpn.conf file

            in reply to: Tray Icon for WireSock #12667
            xxxxzzz
            Participant

              Great, spasibo bolshoe!

            Viewing 5 posts - 1 through 5 (of 5 total)