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

    Cant access internet after adding 2nd Wan connection

    Scheduled Pinned Locked Moved Routing and Multi WAN
    7 Posts 3 Posters 2.2k 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.
    • G
      gme
      last edited by

      hi there.

      I have added another NIC to enable us to use our ADSL line as a fail over in case our main internet connection goes down.

      2nd wan interface is allocated IP from ISP DHCP, it gets and address OK. however when I followed the guide to setup fail over it didn't work when I disconnected Wan1. Therefore back to basics… can I route over Wan2 to get the internet...

      I tested the above by setting the gateway to the ADSL WAN2 interface in the firewall Lan Rule. However even after resetting states I could not ping 8.8.8.8

      I am getting traffic in and out because I also setup some port forwarding to a web server to come in on the ADSL public IP address and tested this OK from an external computer.

      Any ideas why I cant get out to the internet on WAN2? once this is resolved I am hoping that fail over will work.

      NB running absolute latest snapshot which I updated today

      Thanks for any advice

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

        show us your "routing groups" and your firewall rules.
        are you using squid on this machine ?

        1 Reply Last reply Reply Quote 0
        • G
          gme
          last edited by

          Nachtfalke

          thanks for the reply.

          Surely routing groups is irrelevant at this minute because I am just testing to send traffic out via the ADSL line.. When this has been verified working I will then create the Routing group again. There is currently no routing group setup since I reverted back to a Backup config I made after installing the 2nd NIC

          Firewall rule for lan is
          Proto    Dest    Port    Gateway    queue

          • *         *       ADLSGW   none

          we are not using squid.

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

            Oh, I'm sorry. I didn't realize that you just use one WAN.

            Did you change your ADSL-WAN as default gateway ?
            SYSTEM -> ROUTING

            Is the firewall rule you created in top of all other rules so it could be applied and not an other rule?

            1 Reply Last reply Reply Quote 0
            • G
              gme
              last edited by

              @Nachtfalke:

              Oh, I'm sorry. I didn't realize that you just use one WAN.

              Did you change your ADSL-WAN as default gateway ?
              SYSTEM -> ROUTING

              Is the firewall rule you created in top of all other rules so it could be applied and not an other rule?

              We have 2 Wans but I am trying to get everything to go out on the "new" adsl backup line which is WAN2.

              I havent set the ADSL as the default gateway. I just changed the Lan Firewall rule to push all outbound traffic through the ADSL gateway but I then cant get to internet access.

              I can however still get access OK from a remote machine that browses to a web page I have setup for port forwarding on the ADSL public IP.

              1 Reply Last reply Reply Quote 0
              • H
                heper
                last edited by

                perhaps the dns servers of your WAN1 ip are set…..

                it happens a lot that isp's only allow their customers to use their dns'.

                Set dns to 8.8.8.8 (google public dns) and see if that sorts it out

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

                  @heper:

                  perhaps the dns servers of your WAN1 ip are set…..

                  it happens a lot that isp's only allow their customers to use their dns'.

                  Set dns to 8.8.8.8 (google public dns) and see if that sorts it out

                  This couldn't be the problem, because he couldn't ping any public IPs.

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