Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Super weird case

    Off-Topic & Non-Support Discussion
    3
    14
    2.1k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • M
      maverick_slo
      last edited by

      Hi all!

      I have really weird situation which I can`t find cause for.

      Have 2 pfSenses on 2 locations FTTH on both and OpenVPN site 2 site between.

      Everything works great, except for one notebook.

      Now to the weirdness…

      Notebook is on location A.
      Internet works great.
      All internal subnets notebook can access works great (192.168.1.0/24 to 192.168.X.0/24)
      My remote site network works slow and it`s really unresponsive (HTTP/HTTPS or fileshare for example)

      Now the weird part.

      a) If I use utp cable on that same notebook things fly and I can browse fileshare normally
      b) No other device (on wifi or cable) is experiencing this
      c) This was orking just fine 2-3 days ago
      d) If I run Wireshark (just run and do nothing) on that same notebook, remote fileshare starts to fly like normal.

      WTF?

      I DID upgrade to Win10 creators from anniversary and I suspect this coukd be the cause.
      But why only my remote site is working slowly as hell, but different local subnetworks are working just fine?

      Did capture on fileserver on remote location and I get tons of:

      DUP ACK`s
      TCP retransmissions
      TCP fast retransmissions

      I`m really stuck here and I appreciate any idea :)

      Thanks!

      1 Reply Last reply Reply Quote 0
      • D
        doktornotor Banned
        last edited by

        You'd better roll back the upgrade and avoid any updates for a couple of weeks (and the upgrade for half year at least.) The state of MS patches is an absolute disaster currently, with SNAFUs like killing WU altogether on certain CPUs.

        1 Reply Last reply Reply Quote 0
        • JailerJ
          Jailer
          last edited by

          Not an option for home users. Forced updates are the rule now.

          1 Reply Last reply Reply Quote 0
          • M
            maverick_slo
            last edited by

            Windows update aside, weird is, that when I only run wireshark, traffic starts to flow normally and dup ack`s and retransmissions are gone.

            1 Reply Last reply Reply Quote 0
            • D
              doktornotor Banned
              last edited by

              Sounds like some updated drivers screwup to me (which "fixes" itself when you put the interface into promiscuous mode).

              1 Reply Last reply Reply Quote 0
              • M
                maverick_slo
                last edited by

                I tought this at first too.
                But why all networks work just fine, problem is only with remote LAN?
                Updated nic drivers and still the same.

                I just hope they didnt f**k up on OS level. Drivers can easily be updated while base stuff cant.

                And yeah they fu**ed a lot of things lately…

                1 Reply Last reply Reply Quote 0
                • M
                  maverick_slo
                  last edited by

                  But it`s funny.

                  If I use same wifi and connect via openvpn app roadwarrior instead of s2s it works great…

                  1 Reply Last reply Reply Quote 0
                  • M
                    maverick_slo
                    last edited by

                    Ha, tried with dlink USB wifi card and it works normally.
                    So Intel nic + creators = shitload of problems…

                    1 Reply Last reply Reply Quote 0
                    • D
                      doktornotor Banned
                      last edited by

                      Hmmm, not surprised. Perhaps try drivers directly from Intel.

                      1 Reply Last reply Reply Quote 0
                      • M
                        maverick_slo
                        last edited by

                        Tried 2 versions… It must be combo problem...

                        1 Reply Last reply Reply Quote 0
                        • D
                          doktornotor Banned
                          last edited by

                          Lately, it's just best to skip patching anything altogether. After being unable to produce anything for 3 months, they've dumped heap of untested buggy shit on users, broken left and right.

                          1 Reply Last reply Reply Quote 0
                          • M
                            maverick_slo
                            last edited by

                            Yeah I know but I'm in it so I have to test this untested shit for myself 😁

                            1 Reply Last reply Reply Quote 0
                            • D
                              doktornotor Banned
                              last edited by

                              1 Reply Last reply Reply Quote 0
                              • M
                                maverick_slo
                                last edited by

                                OMG…
                                Found the cause...

                                I had LZ4 enabled on both ends. Disabled and things fly like normal...
                                OK, OK...
                                Reenabled, rebooted everything, problem again.
                                Disabled and rebooted again and things are back to normal.

                                WTF?

                                1 Reply Last reply Reply Quote 0
                                • First post
                                  Last post