random ports blocked on client's firewall when mounting nfs share - why?











up vote
0
down vote

favorite












Could you help me, how can I prevent this?
Every time, when I mount an nfs share, I see 6-7 blocked packets in the client's firewall log. These packets come from and to random tcp ports, but they are the same at every mount.
For example, after this command:



mount -t nfs server:/logs /logs


I see in the firewall log/journalctl output:



nov 16 15:46:22 machine kernel: [UFW BLOCK] IN=wlp1s0 OUT= MAC=<mac addresses> SRC=<NFS server's IP> DST=<client's IP> LEN=60 TOS=0x00 PREC=0x00 TTL=63 ID=34612 DF PROTO=TCP SPT=695 DPT=37123 WINDOW=29200 RES=0x00 SYN URGP=0i


repeated 6 times.
After umounting, then mounting it again, I see:



nov 16 16:16:18 machine kernel: [UFW BLOCK] IN=wlp1s0 OUT= MAC=<mac addresses> SRC=<NFS server's IP> DST=<client's IP> LEN=60 TOS=0x00 PREC=0x00 TTL=63 ID=54001 DF PROTO=TCP SPT=915 DPT=37123 WINDOW=29200 RES=0x00 SYN URGP=0 


repeated 6 times again.
Etc.



First of all: why? What the NFS server wants from my client? And how can I fix it (to use the same port every time)?










share|improve this question


























    up vote
    0
    down vote

    favorite












    Could you help me, how can I prevent this?
    Every time, when I mount an nfs share, I see 6-7 blocked packets in the client's firewall log. These packets come from and to random tcp ports, but they are the same at every mount.
    For example, after this command:



    mount -t nfs server:/logs /logs


    I see in the firewall log/journalctl output:



    nov 16 15:46:22 machine kernel: [UFW BLOCK] IN=wlp1s0 OUT= MAC=<mac addresses> SRC=<NFS server's IP> DST=<client's IP> LEN=60 TOS=0x00 PREC=0x00 TTL=63 ID=34612 DF PROTO=TCP SPT=695 DPT=37123 WINDOW=29200 RES=0x00 SYN URGP=0i


    repeated 6 times.
    After umounting, then mounting it again, I see:



    nov 16 16:16:18 machine kernel: [UFW BLOCK] IN=wlp1s0 OUT= MAC=<mac addresses> SRC=<NFS server's IP> DST=<client's IP> LEN=60 TOS=0x00 PREC=0x00 TTL=63 ID=54001 DF PROTO=TCP SPT=915 DPT=37123 WINDOW=29200 RES=0x00 SYN URGP=0 


    repeated 6 times again.
    Etc.



    First of all: why? What the NFS server wants from my client? And how can I fix it (to use the same port every time)?










    share|improve this question
























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      Could you help me, how can I prevent this?
      Every time, when I mount an nfs share, I see 6-7 blocked packets in the client's firewall log. These packets come from and to random tcp ports, but they are the same at every mount.
      For example, after this command:



      mount -t nfs server:/logs /logs


      I see in the firewall log/journalctl output:



      nov 16 15:46:22 machine kernel: [UFW BLOCK] IN=wlp1s0 OUT= MAC=<mac addresses> SRC=<NFS server's IP> DST=<client's IP> LEN=60 TOS=0x00 PREC=0x00 TTL=63 ID=34612 DF PROTO=TCP SPT=695 DPT=37123 WINDOW=29200 RES=0x00 SYN URGP=0i


      repeated 6 times.
      After umounting, then mounting it again, I see:



      nov 16 16:16:18 machine kernel: [UFW BLOCK] IN=wlp1s0 OUT= MAC=<mac addresses> SRC=<NFS server's IP> DST=<client's IP> LEN=60 TOS=0x00 PREC=0x00 TTL=63 ID=54001 DF PROTO=TCP SPT=915 DPT=37123 WINDOW=29200 RES=0x00 SYN URGP=0 


      repeated 6 times again.
      Etc.



      First of all: why? What the NFS server wants from my client? And how can I fix it (to use the same port every time)?










      share|improve this question













      Could you help me, how can I prevent this?
      Every time, when I mount an nfs share, I see 6-7 blocked packets in the client's firewall log. These packets come from and to random tcp ports, but they are the same at every mount.
      For example, after this command:



      mount -t nfs server:/logs /logs


      I see in the firewall log/journalctl output:



      nov 16 15:46:22 machine kernel: [UFW BLOCK] IN=wlp1s0 OUT= MAC=<mac addresses> SRC=<NFS server's IP> DST=<client's IP> LEN=60 TOS=0x00 PREC=0x00 TTL=63 ID=34612 DF PROTO=TCP SPT=695 DPT=37123 WINDOW=29200 RES=0x00 SYN URGP=0i


      repeated 6 times.
      After umounting, then mounting it again, I see:



      nov 16 16:16:18 machine kernel: [UFW BLOCK] IN=wlp1s0 OUT= MAC=<mac addresses> SRC=<NFS server's IP> DST=<client's IP> LEN=60 TOS=0x00 PREC=0x00 TTL=63 ID=54001 DF PROTO=TCP SPT=915 DPT=37123 WINDOW=29200 RES=0x00 SYN URGP=0 


      repeated 6 times again.
      Etc.



      First of all: why? What the NFS server wants from my client? And how can I fix it (to use the same port every time)?







      linux networking firewall mount nfs






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked 2 days ago









      user895804

      12




      12



























          active

          oldest

          votes











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "3"
          };
          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: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














           

          draft saved


          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1376041%2frandom-ports-blocked-on-clients-firewall-when-mounting-nfs-share-why%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown






























          active

          oldest

          votes













          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















           

          draft saved


          draft discarded



















































           


          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1376041%2frandom-ports-blocked-on-clients-firewall-when-mounting-nfs-share-why%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

          Mangá

           ⁒  ․,‪⁊‑⁙ ⁖, ⁇‒※‌, †,⁖‗‌⁝    ‾‸⁘,‖⁔⁣,⁂‾
”‑,‥–,‬ ,⁀‹⁋‴⁑ ‒ ,‴⁋”‼ ⁨,‷⁔„ ‰′,‐‚ ‥‡‎“‷⁃⁨⁅⁣,⁔
⁇‘⁔⁡⁏⁌⁡‿‶‏⁨ ⁣⁕⁖⁨⁩⁥‽⁀  ‴‬⁜‟ ⁃‣‧⁕‮ …‍⁨‴ ⁩,⁚⁖‫ ,‵ ⁀,‮⁝‣‣ ⁑  ⁂– ․, ‾‽ ‏⁁“⁗‸ ‾… ‹‡⁌⁎‸‘ ‡⁏⁌‪ ‵⁛ ‎⁨ ―⁦⁤⁄⁕