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

    SG3100 Single WAN NAT Issues.

    Scheduled Pinned Locked Moved Firewalling
    55 Posts 2 Posters 9.8k 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.
    • M
      mcury Rebel Alliance @wc2l
      last edited by

      @wc2l You need firewall rules inside this last image, WC2LWIFIGUEST
      You need to allow the GUEST network to go out to the internet.

      Do you see the difference between LAN and WC2LWIfIGUEST?

      The last two rules in LAN, try to create them inside WC2LWIfIGUEST, this will allow internet access for these guests.

      dead on arrival, nowhere to be found.

      W 1 Reply Last reply Reply Quote 0
      • W
        wc2l @mcury
        last edited by

        @mcury Protocol - Any, Source - Any, Destination Any?
        I remember something that I saw online. I will have to see if I can find it

        M 1 Reply Last reply Reply Quote 0
        • M
          mcury Rebel Alliance @wc2l
          last edited by

          @wc2l It's easy to create a firewall rule.

          Protocol: any
          Source: WC2LWIfIGUEST_NET
          source port: *
          destination: *
          port: *

          Exactly as it is inside LAN, you replicate that but now for WC2LWIfIGUEST

          dead on arrival, nowhere to be found.

          W 1 Reply Last reply Reply Quote 0
          • W
            wc2l @mcury
            last edited by

            @mcury
            That was it!! I can get out to the internet.. I can't get to ddns.example.com, but I'm not sure I truly care.. more of a way for me to test some stuff.

            M 1 Reply Last reply Reply Quote 0
            • M
              mcury Rebel Alliance @wc2l
              last edited by

              @wc2l Ok, to users in the WC2LWIfIGUEST to be able to access ddns.example.com
              You will need the host override in place, and confirm that the users inside WC2LWIfIGUEST are using the pfsense DNS and not other DNS server.

              dead on arrival, nowhere to be found.

              W 1 Reply Last reply Reply Quote 0
              • W
                wc2l @mcury
                last edited by

                @mcury I had already placed the Host override in place.
                When I check the ipconfig of the device it is 172.30.32.1

                M 1 Reply Last reply Reply Quote 0
                • M
                  mcury Rebel Alliance @wc2l
                  last edited by

                  @wc2l Is 172.30.32.1 the interface WC2LWIfIGUEST IP address?
                  If so, the host override to ddns.example.com should be working.

                  Ping ddns.example.com from inside the WC2LWIfIGUEST network and confirm if the IP matches the host override configuration.

                  dead on arrival, nowhere to be found.

                  W 1 Reply Last reply Reply Quote 0
                  • W
                    wc2l @mcury
                    last edited by

                    @mcury When I ping the DDNS name it does match the actual IP address

                    M 1 Reply Last reply Reply Quote 0
                    • M
                      mcury Rebel Alliance @wc2l
                      last edited by

                      @wc2l Ok, can you show a screenshot of the host override ?

                      dead on arrival, nowhere to be found.

                      W 1 Reply Last reply Reply Quote 0
                      • W
                        wc2l @mcury
                        last edited by

                        @mcury prefer not to make that public

                        Host: ddns
                        domain example.com
                        IP to return for host 172.30.30.40
                        Description empty

                        M 1 Reply Last reply Reply Quote 1
                        • M
                          mcury Rebel Alliance @wc2l
                          last edited by

                          @wc2l It's correct, it should be working..

                          Try to do a ipconfig /flushdns inside the PC you are testing.
                          Clear the browser history and try again.

                          dead on arrival, nowhere to be found.

                          W 1 Reply Last reply Reply Quote 1
                          • W
                            wc2l @mcury
                            last edited by

                            @mcury flushdns did the trick!!
                            I can now telnet, browse and have to check out some of the services.. Looks like were successful! Now I can do some of the other things on my list!! Good new, the office is quiet and I'm working from home today. I may be able to make myself useful ๐Ÿ˜

                            M 1 Reply Last reply Reply Quote 1
                            • M
                              mcury Rebel Alliance @wc2l
                              last edited by

                              @wc2l said in SG3100 Single WAN NAT Issues.:

                              @mcury flushdns did the trick!!
                              I can now telnet, browse and have to check out some of the services.. Looks like were successful! Now I can do some of the other things on my list!! Good new, the office is quiet and I'm working from home today. I may be able to make myself useful ๐Ÿ˜

                              Nice, enjoy :)

                              dead on arrival, nowhere to be found.

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