Navigation

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

    [SOLVED!] routing does not work with disabled packet filter/NAT !?

    Firewalling
    3
    4
    2351
    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
      muellinger last edited by

      Hi,
      i have the following problem. I have a pfSense box running 1.2.2
      I want to connect 2 subnets.

      192.168.100.0/24 and 192.168.200.0/24

      The subnet 192.168.200.0 has the Standardgateway for the internet.

      My pfSense box has 192.168.100.254 on LAN and 192.168.200.253 on WAN.
      The Standardgateway for WAN is set to 192.168.200.254 (which is the correct ip of the Internetgateway).

      As long as NAT and Packet Filter are enabled. Internet from 192.168.100.0 via the 192.168.200.0 subnet works.
      But when i disable Packet Filter and NAT (both i really dont need here). Then i neither cant reach the 192.168.200.0 subnet nor the internet.

      Is there enythiong else i have to set up so pfSense justs connects both subnets inkluding routing to the internet?

      Thanks!

      Best regards
      Carsten

      1 Reply Last reply Reply Quote 0
      • GruensFroeschli
        GruensFroeschli last edited by

        I suppose you're trying to access a host in the 192.168.200.0/24 subnet.
        Since the default gateway of this subnet is not the pfSense, noone (including the default gateway of the 192.168.200.0/24 subnet) knows the way back to your 192.168.100.0/24 subnet.

        You need to create a static route on the default gateway 192.168.200.254 subnet pointing to 192.168.200.253 for the 192.168.100.0.
        But why do you want to disable the filter alltogether?
        If you just want to disable NAT you can do so under firewall –> NAT --> outbound, set to manual rule generation and delete all rules.

        We do what we must, because we can.

        Asking questions the smart way: http://www.catb.org/esr/faqs/smart-questions.html

        1 Reply Last reply Reply Quote 0
        • E
          Efonnes last edited by

          Yeah, without NAT you need a route on both gateways to get traffic through to the subnet on other side of each gateway.  On one side you have a default gateway, so you probably don't need to add an additional route; however, on the other side it does need a route.

          1 Reply Last reply Reply Quote 0
          • M
            muellinger last edited by

            Hi.
            Thanks for the help. Making the route solved the problem.
            I crash my head against the wall cause this is routing basics i should have known…  :D

            So this case is SOLVED!

            Thanks a lot!

            Carsten

            1 Reply Last reply Reply Quote 0
            • First post
              Last post