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

    PF 2.4.1 : HIGH BANDWIDTH

    Scheduled Pinned Locked Moved Off-Topic & Non-Support Discussion
    5 Posts 3 Posters 846 Views
    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.
    • B
      binhdh
      last edited by

      Hi everyone

      I have a problem with Pf 2.4.1, Can you help me.
      Now, i'm using Pf 2.4.1 with Quagga_OSPF 0.6.20_1 as a firewall in my network.
      This morning, network in my company is slow. When i check in monitoring, i saw that my bandwidth out to the internet was very hight.
      I came to Diagnostic -> States and saw a strange IPs : VLXX - tcp - 1.1.1.1:xxx -> 1.1.1.3:xxx. When i kill this states, everything OK.
      But after 4 - 5 minutes, the problem came back  :'(

      Appolozie about my English.

      Any body can help me !
      Thanks.

      1 Reply Last reply Reply Quote 0
      • chpalmerC
        chpalmer
        last edited by

        Do you have WIFI?

        Triggering snowflakes one by one..
        Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz on an M400 WG box.

        1 Reply Last reply Reply Quote 0
        • B
          binhdh
          last edited by

          @chpalmer:

          Do you have WIFI?

          Yes, How about it bro ?

          1 Reply Last reply Reply Quote 0
          • johnpozJ
            johnpoz LAYER 8 Global Moderator
            last edited by

            1.1.1.1 is typical ip used in cisco for the captive portal..

            So states from such an IP would point to that as your problem.. Its really bad practice to leave it using that IP if you ask me.. That is reserved IP range and shouldn't really be used in such a setup.  1.1.1.1 was handed off to apnic long time ago.. They could hand that out whenever even though currently they listed it as testing network..

            Its better to change that to a rfc1918 address that you do not use in your network or even a rfc3330 special use IPv4..

            But if your seeing odd traffic from 1.1.1.1 it would point cisco or maybe other wireless controller doing something funky..

            An intelligent man is sometimes forced to be drunk to spend time with his fools
            If you get confused: Listen to the Music Play
            Please don't Chat/PM me for help, unless mod related
            SG-4860 24.11 | Lab VMs 2.8, 24.11

            1 Reply Last reply Reply Quote 0
            • B
              binhdh
              last edited by

              @johnpoz:

              1.1.1.1 is typical ip used in cisco for the captive portal..

              So states from such an IP would point to that as your problem.. Its really bad practice to leave it using that IP if you ask me.. That is reserved IP range and shouldn't really be used in such a setup.  1.1.1.1 was handed off to apnic long time ago.. They could hand that out whenever even though currently they listed it as testing network..

              Its better to change that to a rfc1918 address that you do not use in your network or even a rfc3330 special use IPv4..

              But if your seeing odd traffic from 1.1.1.1 it would point cisco or maybe other wireless controller doing something funky..

              Thanks so much !

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