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

    WAN Interface IP address - noob config question

    Scheduled Pinned Locked Moved General pfSense Questions
    21 Posts 7 Posters 2.0k 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.
    • NogBadTheBadN
      NogBadTheBad @JKnott
      last edited by NogBadTheBad

      @JKnott said in WAN Interface IP address - noob config question:

      @zzkazu said in WAN Interface IP address - noob config question:

      My setup is

      Why do you have a Netgear router and pfSense? That's 2 routers and double NAT.

      This ^^

      Set the pfSense WAN interface to PPPOE and remove the Netgear.

      Andy

      1 x Netgate SG-4860 - 3 x Linksys LGS308P - 1 x Aruba InstantOn AP22

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

        You can double nat if you need too - but you can not have the same network on pfsense wan as you do its lan and expect it to route correctly.

        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
        • Z
          zzkazu
          last edited by zzkazu

          Thanks for the advice. I have tried a PPPoE configuration.

          DSL Modem "Bridged" to
          APU2 WAN interface
          APU2 LAN interface to
          L-SG108PE switch

          WAN interface set to PPPoE
          LAN Static IP

          On LAN side still cant ping out publicly.

          DCHP service running and allocating leases
          No FW rules running on WAN

          Pfsense PPPoE.JPG

          Firewall rules.JPG

          Ping Interface Test.JPG

          1 Reply Last reply Reply Quote 0
          • NogBadTheBadN
            NogBadTheBad
            last edited by

            Try killing the firewall states.

            Andy

            1 x Netgate SG-4860 - 3 x Linksys LGS308P - 1 x Aruba InstantOn AP22

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

              And what are you outbound nat rules?

              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
              • Z
                zzkazu
                last edited by

                Automatic outbound NAT rule generation.

                Is that sufficient?

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

                  let see it please
                  If you can ping from your public wan, but not from your lan - points to outbound nat not being correct.

                  I would sniff on your wan while your doing your ping from lan test.. Do you see the ping go out with your actual wan IP?

                  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
                  • stephenw10S
                    stephenw10 Netgate Administrator
                    last edited by stephenw10

                    Check the state table size on the dashboard also. Something breaking the ruleset can present like this but you would see 0 open states in that case. You have some rules showing open states so it's probably not that. Worth checking though.

                    Check you have a default route in Diag > Routes.

                    Steve

                    1 Reply Last reply Reply Quote 0
                    • Z
                      zzkazu
                      last edited by zzkazu

                      Thanks for the help here, learning lots.

                      Still can ping and resolve via WAN but not LAN

                      Only taking a guess but LAN active states seem closed, could that be the issue? I have reset states a couple of times.

                      using Packet capture (WAN side) cant see any private IP addresses...

                      thanks

                      Outbound NAT

                      NAT outbound.JPG

                      Diag Routes.JPG

                      Active States.JPG

                      Packet Capture.JPG

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

                        Where is your default route?

                        default.png

                        That looks like your wan pinging your gateway.. But I see no default route in your routing table.. So if your client pings 8.8.8.8 why would it get routed out your internet?

                        Lets see your gateways

                        gateways.png

                        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
                        • Z
                          zzkazu
                          last edited by zzkazu

                          Default gateway IPv4 was set to automatic. Setting it to WAN_PPPOE seems to have allowed me to ping public via LAN now..

                          Seems a bit strange noting I have only one Gateway PPPoE.. ... cheers saved further headaches for me

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

                            I have seen a bit of strangeness with the automatic gateway selection.. Maybe your pppoe connection is taking awhile to come up.. Not sure.. I don't use those types of connection, and never a lot of experience even with them with pfsense..

                            We can see if anyone else with more info on the details of how the automatic selection is suppose to work, and how pppoe might come into play with that, etc.

                            Glad we finally got it sorted! ;)

                            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
                            • stephenw10S
                              stephenw10 Netgate Administrator
                              last edited by

                              Yeah, I would recommend always setting the gateway to something specific there.

                              Steve

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