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

    Bridge LAN interfaces -> WAN NAT fails for one interface

    Scheduled Pinned Locked Moved NAT
    5 Posts 3 Posters 1.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.
    • C
      cubert
      last edited by

      I have a 4 nic box that has 1 WAN and 3 LAN interfaces.  I bridged the 3 LAN interfaces together and assigned an IP to the Bridge interface.

      All routing between Bridge interfaces are working so LAN can see WIFI interfaces all PC's can get DHCP from main server on LAN and see all shares on network as expected.

      The LAN interface can ping google but the WIFI interface users can not.

      Watching TCPDump on firewall I can see pings come in for all interfaces, I see ping from WIFI interface go out the WAN interface but not NATed… WIFI goes out WAN as local LAN addressing.  LAN goes out WAN as WAN address (As expected) and ping is returned. Ping gets to other end but has private address assigned to it so ping is never returned.

      Basic Auto Outbound NAT is enabled.

      What would cause 1 interface of a bridge to NAT and not another?

      Cube Dweller
      www.squidworks.net

      "Give a man a fish and feed him for a day, Teach a man to fish and loose a steady customer."

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

        Actually upon further review, the only interface that can get NAted correctly is the LAN interface the Opt interface and the WIFI interface both fail to NAT and keep sending their private IP out the WAN interface.

        Cube Dweller
        www.squidworks.net

        "Give a man a fish and feed him for a day, Teach a man to fish and loose a steady customer."

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

          If I remove the interfaces from the bridge and assign an IP to the interface then I can get Nated out correctly. When we add the interfaces bac to bridge and remove IP addresses from interface then local access works fine but again these 2 interfaces do not NAT out WAN they just go out WAN as is.

          Cube Dweller
          www.squidworks.net

          "Give a man a fish and feed him for a day, Teach a man to fish and loose a steady customer."

          1 Reply Last reply Reply Quote 0
          • DerelictD
            Derelict LAYER 8 Netgate
            last edited by

            Examine the firewall rules for all member interfaces.

            Chattanooga, Tennessee, USA
            A comprehensive network diagram is worth 10,000 words and 15 conference calls.
            DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
            Do Not Chat For Help! NO_WAN_EGRESS(TM)

            1 Reply Last reply Reply Quote 0
            • P
              phil.davis
              last edited by

              Since you are seeing packets leaving the WAN interface still with private LAN IPs, the firewall rules must be passing the traffic OK. Look in /tmp/rules.debug and see the rules that mention NAT. If you can't make sense of them yourself, then post them, along with a bit of detail on what IP address(es) are set on which interfaces.

              As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
              If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

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