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

    Connect pfsense wan to tomatousb lan

    Scheduled Pinned Locked Moved General pfSense Questions
    4 Posts 2 Posters 1.4k 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
      gjaltemba
      last edited by

      I use a tomatousb router to build my wired Ethernet home network and connect to internet. I also have a separate lan network connected to a switch without internet. My goal is to use pfsense to provide internet to the switch. I am able to achieve this using a second tomatousb router but would like to use pfsense instead.

      modem ->
      tomatousb wan
      tomatousb lan 192.168.1.1 -

      pfsense wan 192.168.1.2 -
      pfsense lan 192.168.50.1

      The pfsense wan port is wired to a lan port on the tomatousb router. I can see 192.168.1.2 listed as a device without any leasetime on br0 interface in tomatousb. I cannot ping nor traceroute to 192.168.1.2 from the tomatousb router.

      How do I use 192.168.1.1 as a gateway and dns for 192.168.50.1 using pfsense?

      1 Reply Last reply Reply Quote 0
      • W
        wallabybob
        last edited by

        @gjaltemba:

        I cannot ping nor traceroute to 192.168.1.2 from the tomatousb router.

        Is pfSense blocking private IP addresses on WAN? See the Private Networks section on WAN -> Interfaces

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

          I have unchecked  Block Private Addresses and Block Bogon Networks options in the WAN interface. Apply changes and reboot pfsense 2.0.2

          Thank you for your time.

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

            Turns out to be a flaky nic. All is good with pfsense 2.0.3 connected. Sorry for any confusion I may have caused.

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