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

    PFsense LAN interface TimeOut olması

    Turkish
    3
    8
    4.2k
    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.
    • S
      sinanc
      last edited by

      Merhabalar,

      yeni günde yeni bir problemle daha merhaba dedim :)  Pfsense imin LAN network ümün bağlı olduğu interface imde time outlar alıyorum 3 sn lik lost 10 sn lost lar onboard intel 1 gbt ethernet kartı vardı kurduğum sistemde  az önce TP link 1 gbt ethernet kartı taktım ayarları yaptım  ilk 10 dk gayet güzel göründü herşey ama yine aynı şekilde packet lostlar almaya başladım. sorunu çözmem için başka neler yapmalıyım ?

      iyi günler, iyi çalışmalar…

      1 Reply Last reply Reply Quote 0
      • S
        sgtr
        last edited by

        Selam,

        Bu gibi durumda aklıma ilk olarak networkunu dinlemek (sniffer ya da ethercap ile) geliyor. Buradan belki networkunde uyumsuz başka cihaz/cihazlar vardır. Bunu yapmadan önce system ve firewall loglarına baktınız mı?

        Sevgilerle,
        SGTR

        Bir umut olmasa bile Asla Pes Etme.

        1 Reply Last reply Reply Quote 0
        • S
          sinanc
          last edited by

          Merhabalar,
          firewall loglarımda bu hata çok çıkıyor bunu çözmeye çalışıyorum. layer 2 switch üzerinde bir hata göremedim, loglara baktığımda alakasız hatalar  port down up hataları görünmekte

          firewall loglarından en çok  gözüme çarpan hata

          :34	kernel: arp: 192.168.2.71 moved from 04:46:65:5d:1a:47 to 00:1d:7d:7a:2e:4e on re4
Oct 23 21:25:27	kernel: arp: 192.168.2.71 moved from 00:1d:7d:7a:2e:4e to 04:46:65:5d:1a:47 on re4
Oct 23 21:23:10	kernel: arp: 192.168.2.71 moved from 04:46:65:5d:1a:47 to 00:1d:7d:7a:2e:4e on re4
Oct 23 21:23:04	kernel: arp: 192.168.2.71 moved from 00:1d:7d:7a:2e:4e to 04:46:65:5d:1a:47 on re4
Oct 23 21:21:46	kernel: arp: 192.168.2.71 moved from 04:46:65:5d:1a:47 to 00:1d:7d:7a:2e:4e on re4
Oct 23 21:21:15	kernel: arp: 192.168.2.71 moved from 00:1d:7d:7a:2e:4e to 04:46:65:5d:1a:47 on re4
Oct 23 21:19:25	kernel: arp: 192.168.2.71 moved from 04:46:65:5d:1a:47 to 00:1d:7d:7a:2e:4e on re4
Oct 23 21:19:17	kernel: arp: 192.168.2.71 moved from 00:1d:7d:7a:2e:4e to 04:46:65:5d:1a:47 on re4
Oct 24 09:55:37	kernel: arp: 192.168.2.53 moved from 50:cc:f8:e5:63:6e to 1c:6f:65:d9:a9:98 on re4
Oct 24 09:55:37	kernel: arp: 192.168.2.53 moved from 1c:6f:65:d9:a9:98 to 50:cc:f8:e5:63:6e on re4
Oct 24 09:55:24	kernel: arp: 192.168.2.53 moved from 50:cc:f8:e5:63:6e to 1c:6f:65:d9:a9:98 on re4
Oct 24 09:55:24	kernel: arp: 192.168.2.53 moved from 1c:6f:65:d9:a9:98 to 50:cc:f8:e5:63:6e on re4
Oct 24 09:54:48	kernel: arp: 192.168.2.53 moved from 50:cc:f8:e5:63:6e to 1c:6f:65:d9:a9:98 on re4
Oct 24 09:54:48	kernel: arp: 192.168.2.53 moved from 1c:6f:65:d9:a9:98 to 50:cc:f8:e5:63:6e on re4
Oct 24 09:54:08	kernel: arp: 192.168.2.53 moved from 50:cc:f8:e5:63:6e to 1c:6f:65:d9:a9:98 on re4
Oct 24 09:54:08	kernel: arp: 192.168.2.53 moved from 1c:6f:65:d9:a9:98 to 50:cc:f8:e5:63:6e on re4
Oct 24 09:53:32	kernel: arp: 192.168.2.53 moved from 50:cc:f8:e5:63:6e to 1c:6f:65:d9:a9:98 on re4
Oct 24 09:53:32	kernel: arp: 192.168.2.53 moved from 1c:6f:65:d9:a9:98 to 50:cc:f8:e5:63:6e on re4
Oct 24 09:53:25	kernel: arp: 192.168.2.53 moved from 50:cc:f8:e5:63:6e to 1c:6f:65:d9:a9:98 on re4
Oct 24 09:53:25	kernel: arp: 192.168.2.53 moved from 1c:6f:65:d9:a9:98 to 50:cc:f8:e5:63:6e on re4
Oct 24 10:08:20	kernel: arp: 192.168.2.53 moved from 50:cc:f8:e5:63:6e to 1c:6f:65:d9:a9:98 on re4
Oct 24 10:08:20	kernel: arp: 192.168.2.53 moved from 1c:6f:65:d9:a9:98 to 50:cc:f8:e5:63:6e on re4
Oct 24 10:07:33	kernel: arp: 192.168.2.53 moved from 50:cc:f8:e5:63:6e to 1c:6f:65:d9:a9:98 on re4
Oct 24 10:07:32	kernel: arp: 192.168.2.53 moved from 1c:6f:65:d9:a9:98 to 50:cc:f8:e5:63:6e on re4
Oct 24 10:06:44	kernel: arp: 192.168.2.53 moved from 50:cc:f8:e5:63:6e to 1c:6f:65:d9:a9:98 on re4
Oct 24 10:06:43	kernel: arp: 192.168.2.53 moved from 1c:6f:65:d9:a9:98 to 50:cc:f8:e5:63:6e on re4
Oct 24 10:05:57	kernel: arp: 192.168.2.53 moved from 50:cc:f8:e5:63:6e to 1c:6f:65:d9:a9:98 on re4
Oct 24 10:05:57	kernel: arp: 192.168.2.53 moved from 1c:6f:65:d9:a9:98 to 50:cc:f8:e5:63:6e on re4
Oct 24 10:05:53	kernel: arp: 192.168.2.53 moved from 50:cc:f8:e5:63:6e to 1c:6f:65:d9:a9:98 on re4
Oct 24 10:05:53	kernel: arp: 192.168.2.53 moved from 1c:6f:65:d9:a9:98 to 50:cc:f8:e5:63:6e on re4
Oct 24 10:05:11	kernel: arp: 192.168.2.53 moved from 50:cc:f8:e5:63:6e to 1c:6f:65:d9:a9:98 on re4
Oct 24 10:05:11	kernel: arp: 192.168.2.53 moved from 1c:6f:65:d9:a9:98 to 50:cc:f8:e5:63:6e on re4
Oct 24 10:04:20	kernel: arp: 192.168.2.53 moved from 50:cc:f8:e5:63:6e to 1c:6f:65:d9:a9:98 on re4
Oct 24 10:04:15	kernel: arp: 192.168.2.53 moved from 1c:6f:65:d9:a9:98 to 50:cc:f8:e5:63:6e on re4
Oct 24 10:04:05	kernel: arp: 192.168.2.53 moved from 50:cc:f8:e5:63:6e to 1c:6f:65:d9:a9:98 on re4
Oct 24 10:04:00	kernel: arp: 192.168.2.53 moved from 1c:6f:65:d9:a9:98 to 50:cc:f8:e5:63:6e on re4
Oct 24 10:03:44	kernel: arp: 192.168.2.53 moved from 50:cc:f8:e5:63:6e to 1c:6f:65:d9:a9:98 on re4
Oct 24 10:03:39	kernel: arp: 192.168.2.53 moved from 1c:6f:65:d9:a9:98 to 50:cc:f8:e5:63:6e on re4
Oct 24 10:02:55	kernel: arp: 192.168.2.53 moved from 50:cc:f8:e5:63:6e to 1c:6f:65:d9:a9:98 on re4
Oct 24 10:02:50	kernel: arp: 192.168.2.53 moved from 1c:6f:65:d9:a9:98 to 50:cc:f8:e5:63:6e on re4
Oct 24 10:02:04	kernel: arp: 192.168.2.53 moved from 50:cc:f8:e5:63:6e to 1c:6f:65:d9:a9:98 on re4
Oct 24 10:01:59	kernel: arp: 192.168.2.53 moved from 1c:6f:65:d9:a9:98 to 50:cc:f8:e5:63:6e on re4
Oct 24 10:01:11	kernel: arp: 192.168.2.53 moved from 50:cc:f8:e5:63:6e to 1c:6f:65:d9:a9:98 on re4
Oct 24 10:01:06	kernel: arp: 192.168.2.53 moved from 1c:6f:65:d9:a9:98 to 50:cc:f8:e5:63:6e on re4

          sanırım network ü sniff etmek sorunumu çözmem de yardımcı olacaktır

          iyi çalışmalar…

          1 Reply Last reply Reply Quote 0
          • S
            sgtr
            last edited by

            Selam,

            Bu gönderdiğiniz loglardan gördüğüm kadarıyla ağınızda virüs olma ihtimali yüksek. Bir diğer nokta da ethernet kartı da olabilir bu sefer client tarafını kontrol etmenizi tavsiye ederim. Ağı dinlemekte faydalı bir yöntem olur.

            Sevgilerle,
            SGTR

            Bir umut olmasa bile Asla Pes Etme.

            1 Reply Last reply Reply Quote 0
            • Q
              Qbilay
              last edited by

              Merhaba
              bu mac adresli ethernetler bir makinaya mi takili yoksa farkli makinalara ait mac adresi mi?

              1 Reply Last reply Reply Quote 0
              • S
                sinanc
                last edited by

                Merhabalar,

                bu görünen ip adresleri sabit ip adresi kullanan kullanıcılar, static olarak gilirlen ip adreslerini sildim network ayarlarından dhcp ye rezerve ettirdim suan arp hata log u düşmüyor ama verdikleri mac adreslerinden 1 kullanıcıların kendi mac adresi diyer mac adresi bulamadım network de :/

                başka bir şey ise network de pfsense erişimin timeout olması, sanırım telefon yada pda gibi cihazlardan biri bu işlemi yapıyor çunku ara ara sıkıntı çıkıyor devamlı oluşan bir time out görünmüyor. Araştırmaya devam :)

                iyi çalışmalar…

                (Hayırlı bayramlar herkese )

                1 Reply Last reply Reply Quote 0
                • S
                  sgtr
                  last edited by

                  Selamlar,

                  Bu süreci paylaşırsanız elimizden geldiğince yardımcı olmaya çalışırız.

                  Sevgilerle,
                  SGTR

                  Bir umut olmasa bile Asla Pes Etme.

                  1 Reply Last reply Reply Quote 0
                  • S
                    sinanc
                    last edited by

                    Merhabalar,
                    sorun düzeldi gibi birkaç gündür, sanırım test için gelen  tablet yada mobile cihazlardan biri yapıyordu sorunu. sniff e devam yinede  sorun tekrar oluşursa topic' üzerinden bilgilendirmeye devam ederim

                    ilginiz için teşekkürler.

                    iyi çalışmalar…

                    1 Reply Last reply Reply Quote 0
                    • First post
                      Last post
                    Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.