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

    cant connect to internet with second WAN interface/ip

    Scheduled Pinned Locked Moved DHCP and DNS
    17 Posts 3 Posters 1.5k 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.
    • N
      netblues @odeplay
      last edited by

      @odeplay its what traceroute is using....

      O 1 Reply Last reply Reply Quote 0
      • O
        odeplay @netblues
        last edited by

        @netblues its like tracert function in cmd

        1 Reply Last reply Reply Quote 0
        • N
          netblues
          last edited by

          Icmp is the protocol used by traceroute.

          O JKnottJ 3 Replies Last reply Reply Quote 0
          • O
            odeplay @netblues
            last edited by

            @netblues ok ill try tomorrow to change the setup of my protocol. ill let you know if it works, thanks a lot dude

            1 Reply Last reply Reply Quote 0
            • JKnottJ
              JKnott @netblues
              last edited by JKnott

              @netblues said in cant connect to internet with second WAN interface/ip:

              Icmp is the protocol used by traceroute.

              Only on Windows. With Linux, BSD and Mac, UDP is default, with ICMP an option.

              PfSense running on Qotom mini PC
              i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
              UniFi AC-Lite access point

              I haven't lost my mind. It's around here...somewhere...

              N 1 Reply Last reply Reply Quote 0
              • N
                netblues @JKnott
                last edited by

                @jknott True, however the op is using windows (and the rule for tcp/udp would be applicable in the first place, so there will be no forum thread too :)

                1 Reply Last reply Reply Quote 0
                • O
                  odeplay @netblues
                  last edited by

                  @netblues ive already changed my protocol and the result is the same, however i checked the states from diagnostic and found this 0_1540772325315_state closed pfsense.png

                  maybe this is the one who blocks the internet from my new wan

                  1 Reply Last reply Reply Quote 0
                  • O
                    odeplay
                    last edited by

                    0_1540776664551_ping converge.png
                    from the image, i can ping facebook using my new / 2nd WAN

                    1 Reply Last reply Reply Quote 0
                    • N
                      netblues
                      last edited by

                      You are seeing declined syn, this is tcp related.
                      Trying to debug connectivity issues using facebook with its multitude ip's won't fly.

                      please post lan rules and nat configuration, and how you are testing..
                      stay with ip's at this stage. No alias.

                      And no reason to obfuscate private ip ranges too.

                      1 Reply Last reply Reply Quote 0
                      • O
                        odeplay
                        last edited by

                        hi, i already saw the problem, my outbound rules is set to manual and it is all directed to my first WAN.

                        thanks for the reply guys

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