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

    Help i have hit a brick Wall with Setup

    Scheduled Pinned Locked Moved General pfSense Questions
    20 Posts 2 Posters 3.1k 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.
    • D
      dcl66
      last edited by

      Also now I can ping 8.8.8.8 or 8.8.4.4 from the shell and webgui and it is successfulw/no packet loss but still no internet conncetion via a lan connection

      1 Reply Last reply Reply Quote 0
      • KOMK
        KOM
        last edited by

        Make sure your clients have an IP address in the 192.168.1.x range with a gateway of your pfSense LAN IP address.  Also make sure that you did NOT specify a gateway for your pfSense LAN configuration.  pfSense LAN interface does not require a gateway, only your WAN and your clients do.  I have to go but will be back tomorrow if someone else hasn't already stepped in.

        1 Reply Last reply Reply Quote 0
        • D
          dcl66
          last edited by

          Thanks for your help and no problem

          I just have a question should my client PCs be configured for the 192.168.2.x since my setup set to allow Pfsense to issue DHCP addresses

          Gateway 192.168.1.x ==> Pfsense WAN 192.168.1.85 to LAN 192.168.2.x ==> Managed Switch ==> Clients

          And I have restarted every device in my LAN and its the same behavior out the gate I have internet access and speed test 16 down 2 up then something happens and it sinks to less than a meg down and it errors out on the up test.

          And I dont know if this is of any consequence but after setting WAN to get DHCP address from uverse gateway now in the Shell the IP is showing as my public Ip and not the 192.168.1.85/24 that it previously registered
          So yeah I am 100 percent stumped

          1 Reply Last reply Reply Quote 0
          • KOMK
            KOM
            last edited by

            should my client PCs be configured for the 192.168.2.x since my setup set to allow Pfsense to issue DHCP addresses

            Yes.  If your LAN is 192.168.2.0/24 then all of your clients on LAN should also be on the same network.  And as I said earlier, make sure that your DHCP server on LAN is giving out IP addresses that are appropriate for your LAN network eg. 192.168.2.10-192.168.2.40.

            Is there anything in your System log of note from when it starts to lose connectivity?  Can your LAN clients ping pfSense LAN NIC at 192.168.2.1?  Can they ping 8.8.8.8?

            If your pfSense WAN is in DHCP mode and is getting a public IP address then that means your Uverse was likely in bridged mode all along.

            1 Reply Last reply Reply Quote 0
            • D
              dcl66
              last edited by

              Ok thanks well i have all my devices set to dhcp on 192.168.2.x and i checked th few that are currently on in the LAN and they look good

              Now as far as being able to ping 8.8.8.8
              PING 8.8.8.8 (8.8.8.8): 56 data bytes
              64 bytes from 8.8.8.8: icmp_seq=1 ttl=55 time=23.213 ms
              64 bytes from 8.8.8.8: icmp_seq=2 ttl=55 time=23.189 ms
              64 bytes from 8.8.8.8: icmp_seq=3 ttl=55 time=22.982 ms
              64 bytes from 8.8.8.8: icmp_seq=5 ttl=55 time=23.043 ms
              64 bytes from 8.8.8.8: icmp_seq=7 ttl=55 time=23.499 ms
              64 bytes from 8.8.8.8: icmp_seq=8 ttl=55 time=22.890 ms
              64 bytes from 8.8.8.8: icmp_seq=9 ttl=55 time=23.536 ms

              –- 8.8.8.8 ping statistics ---
              10 packets transmitted, 7 packets received, 30.0% packet loss
              round-trip min/avg/max/stddev = 22.890/23.193/23.536/0.230 ms

              And when I ping 192.168.2.2 (pfsense LAN address) from a PC on the LAN it is flawless with zero dropped packets

              and as far as the Logs go on Pfsense the only thing I see happening around the time everything goes awry is

              Feb 15 12:49:15 check_reload_status: updating dyndns WAN_DHCP
              Feb 15 12:49:15 check_reload_status: Restarting ipsec tunnels
              Feb 15 12:49:15 check_reload_status: Restarting OpenVPN tunnels/interfaces
              Feb 15 12:49:15 check_reload_status: Reloading filter

              Gateway Log
              Feb 15 12:51:09 apinger: ALARM: WAN_DHCP(Public IP) *** loss ***
              Feb 15 12:52:40 apinger: alarm canceled: WAN_DHCP(Public IP) *** loss ***
              Feb 15 12:55:57 apinger: ALARM: WAN_DHCP(Public ip) *** loss ***

              Other than that nothing that I can tell stands out

              1 Reply Last reply Reply Quote 0
              • KOMK
                KOM
                last edited by

                30% packet loss is pretty crappy.  You can disable the gateway monitoring and that may help with the gateway errors in the log but that 30% is nasty.  Were you pinging from the pfSense interface when you got that 30% loss or from a LAN client?  I assume you're running 2.2.6?

                1 Reply Last reply Reply Quote 0
                • D
                  dcl66
                  last edited by

                  Ok if the errors for gateway monitoring aren't doing any damage Ill leave them alone But I am running 2.2.6 64bit and when I was getting the 30% loss it was via Pfsense.

                  And yeah the dropped packets make it a pain.

                  1 Reply Last reply Reply Quote 0
                  • D
                    dcl66
                    last edited by

                    Now I dont know if this is a good or bad thing but I started a page by page trial and error just to see what would change and I enabled UPnP and NAT-PMP

                    and my packet loss for 8.8.8.8 which was north of 20% its back and forth between 10% and I have sustained download speeds but my upload ….....is in a new category of laughable

                    IMG_0232.PNG
                    IMG_0232.PNG_thumb

                    1 Reply Last reply Reply Quote 0
                    • KOMK
                      KOM
                      last edited by

                      Poor upload speeds can be caused by incorrect speed or duplex issues.  I've even seen an MTU too high causing such things due to excessive packet fragmentation.  Speed tests on a wireless device introduce all kinds of other variables to the mix, so you might want to stay with a wired connection for that.  Have you tried a different network cable between pfSense WAN and the Uverse?  You also might want to check with your ISP about that packet loss.  Your poor connectivity might be due to a bad WAN NIC or line issues.

                      1 Reply Last reply Reply Quote 0
                      • D
                        dcl66
                        last edited by

                        I will try another cable and check the MTU setting to see if that helps

                        But the only thing is this issue with the speed taking a nosedive happened after I put Pfsense into the equation before 15down 2 up was the norm. but back to the drawing board

                        And, KOM man i cant thank you enough for all the you have offered so far!!

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