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

    Unable to access internet from remote site

    Routing and Multi WAN
    3
    27
    10.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.
    • P
      PhatBot
      last edited by

      bump  :)

      1 Reply Last reply Reply Quote 0
      • C
        cmb
        last edited by

        can you ping IP's on those subnets from pfsense itself?

        Do you see the traffic getting dropped in your firewall log?

        1 Reply Last reply Reply Quote 0
        • P
          PhatBot
          last edited by

          Yes, pinging from pfSense to the remote subnet works just fine.
          And no, the log show thats the traffic gets through.

          1 Reply Last reply Reply Quote 0
          • C
            cmb
            last edited by

            Based on what you said, your pfsense sounds fine. I didn't see it mentioned, what version are you running?

            1 Reply Last reply Reply Quote 0
            • P
              PhatBot
              last edited by

              Version 1.0.1

              Well it seems like it's doing fine yet it doesn't seem to NAT that subnet.

              Can't really see any other things in my network typology that could cause this problem.

              1 Reply Last reply Reply Quote 0
              • P
                Perry
                last edited by

                Then you should update http://pfsense.best-view.net/updates/

                more info here http://pfsense.blogspot.com/2007/05/choosing-which-version-to-run.html

                /Perry
                doc.pfsense.org

                1 Reply Last reply Reply Quote 0
                • P
                  PhatBot
                  last edited by

                  Ok upgraded to 1.2-Beta-1 (Excellent job on the firmware upgrade routine guys. Quick and accurate.)

                  Still no go though.
                  Passes firewall rules but seems to get stuck in NAT or something.

                  1 Reply Last reply Reply Quote 0
                  • C
                    cmb
                    last edited by

                    Yeah I would have suspected a NAT bug in 1.0.1, there are a few of those that have been fixed in 1.2b1.

                    Do you have advanced outbound NAT enabled?

                    1 Reply Last reply Reply Quote 0
                    • P
                      PhatBot
                      last edited by

                      Yes, advanced NAT enabled.

                      1 Reply Last reply Reply Quote 0
                      • C
                        cmb
                        last edited by

                        Then it's a problem with your advanced NAT rules. Do you need it for some reason? If not, just disable it and your problem goes away.

                        1 Reply Last reply Reply Quote 0
                        • P
                          PhatBot
                          last edited by

                          Changed to normal NAT.
                          Still same problem though.

                          Very odd.

                          1 Reply Last reply Reply Quote 0
                          • P
                            Perry
                            last edited by

                            Is there be anything special with that leased line?

                            10.58.202./24 comes in via a leased line through a router with IP 10.58.112.1

                            maybe do some trace with pftop or tcpdump ( just a though )

                            /Perry
                            doc.pfsense.org

                            1 Reply Last reply Reply Quote 0
                            • C
                              cmb
                              last edited by

                              Yeah it's time to start capturing packets and seeing what's really happening.

                              1 Reply Last reply Reply Quote 0
                              • P
                                PhatBot
                                last edited by

                                Right… hehe... the thing is.....  :-\

                                I havn't got a clue how to do that.???
                                Could someone give me some pointers?

                                Thanks!

                                Also. Thanks for the help on this subject. I really appreciate you guys taking your free time to help me. :)

                                1 Reply Last reply Reply Quote 0
                                • P
                                  PhatBot
                                  last edited by

                                  Tried some TCPDUMP. Not really sure what to look for though.

                                  The thing I find strange is that I'm able to ping hosts on the remote subnet from the pfsense box.
                                  And the pfsense box also replies to pings from the remote subnet.
                                  Feels like the data is flowing like it should in our internal network.
                                  It just doesn't let me do nat for that subnet.

                                  1 Reply Last reply Reply Quote 0
                                  • P
                                    PhatBot
                                    last edited by

                                    In the Webgui Diagnostics: Show States I see
                                    ICMP 10.58.202.21:512 -> external-ip:35350 -> external-gw 0:0
                                    ICMP external-gw:512 <- 10.58.202.21 0:0
                                    when I try to ping from the host on the remote subnet to our ISP gateway.
                                    This should indicate that NAT is working like it should right?

                                    1 Reply Last reply Reply Quote 0
                                    • P
                                      Perry
                                      last edited by

                                      to check for a dns problem you could do something like this.

                                      from shell tcpdump -i if2 dst port 21

                                      from a client ftp://204.152.184.73/

                                      By that your can see what happens on IF2 when you logon to a ftpserver

                                      –--------------------------------------

                                      http://your-pfsense-ip/status.php

                                      you might find something under pfctl
                                      –------ !! Warning this is written by someone sitting in the sun  !! ------------

                                      /Perry
                                      doc.pfsense.org

                                      1 Reply Last reply Reply Quote 0
                                      • P
                                        PhatBot
                                        last edited by

                                        Tried some 1:1 NATing.
                                        Worked like a charm for all our subnets except the remote subnet which we have the trouble with.
                                        Starting to think that there must be something fishy with the router thats handling that subnet.

                                        More info later.

                                        1 Reply Last reply Reply Quote 0
                                        • P
                                          PhatBot
                                          last edited by

                                          Hi Perry,

                                          Here's the result after dumping it to a file and then importing it into Etherreal.

                                          dump.gif
                                          dump.gif_thumb

                                          1 Reply Last reply Reply Quote 0
                                          • P
                                            Perry
                                            last edited by

                                            did you try searching in http://your-pfsense-ip/status.php for 10.58.202.21 or 204.152.184.73 after the test, there must be some info there telling us what happens  ::)

                                            your can also use
                                            Diagnostics -> Packet Capture
                                            to trace ip's

                                            /Perry
                                            doc.pfsense.org

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