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

One of the interfaces setup as an additional isolated LAN not working

NAT
2
8
371
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.
  • K
    Kajetan321
    last edited by Jan 23, 2024, 10:06 PM

    Hello, I’m trying to configure one of my spare interfaces as an additional isolated LAN (I’m calling it Carleton). I’m following this tutorial here:

    https://docs.netgate.com/pfsense/en/latest/solutions/xg-7100/opt-lan.html

    The DHCP seems to works, a test computer gets assigned with an IP address but I’m unable to ping anything on the outside from that computer. I can’t even ping the gateway.

    Here’s how I set things up:

    Setting up the Carleton Interface
    pfSense > Interfaces > LAN3
    Description: Carleton
    IPv4 Config: Static IPv4
    IPv4 Address: 192.168.55.3 /24,

    Setting up DHCP
    Enable: Enable DHCP server on CARLETON interface
    Range 192.168.55.100 to 192.168.55.239

    Firewall:

    login-to-view

    login-to-view

    Please help. I have been at this the whole afternoon.

    V 1 Reply Last reply Jan 23, 2024, 10:19 PM Reply Quote 0
    • V
      viragomann @Kajetan321
      last edited by Jan 23, 2024, 10:19 PM

      @Kajetan321
      Note that this rule allows TCP only. It doesn't allow pings, which uses ICMP.
      Try protocol = any for testing.

      K 1 Reply Last reply Jan 23, 2024, 10:23 PM Reply Quote 0
      • K
        Kajetan321 @viragomann
        last edited by Jan 23, 2024, 10:23 PM

        @viragomann said in One of the interfaces setup as an additional isolated LAN not working:

        @Kajetan321
        Note that this rule allows TCP only. It doesn't allow pings, which uses ICMP.
        Try protocol = any for testing.

        I tried this and still no change.

        login-to-view

        V 1 Reply Last reply Jan 23, 2024, 10:25 PM Reply Quote 0
        • V
          viragomann @Kajetan321
          last edited by Jan 23, 2024, 10:25 PM

          @Kajetan321
          Now you limited the source to the interface address.
          Select "Carleton net" to limit it to the connected subnet.

          K 1 Reply Last reply Jan 23, 2024, 10:37 PM Reply Quote 0
          • K
            Kajetan321 @viragomann
            last edited by Kajetan321 Jan 23, 2024, 10:40 PM Jan 23, 2024, 10:37 PM

            @viragomann

            OK, changes made and I'm now able to ping google. This is great, I still can't ping the gateway though.

            login-to-view

            V 1 Reply Last reply Jan 23, 2024, 10:41 PM Reply Quote 0
            • V
              viragomann @Kajetan321
              last edited by Jan 23, 2024, 10:41 PM

              @Kajetan321
              What is this source now? An alias?
              If so does it include the computer, which you're testing from?

              I'd recommend to set all rule options to any for test period.

              Are you even able to ping the pfSense interface IP then?

              K 2 Replies Last reply Jan 23, 2024, 11:00 PM Reply Quote 0
              • K
                Kajetan321 @viragomann
                last edited by Jan 23, 2024, 11:00 PM

                This post is deleted!
                1 Reply Last reply Reply Quote 0
                • K
                  Kajetan321 @viragomann
                  last edited by Jan 23, 2024, 11:08 PM

                  @viragomann Thanks you it all works now. I was mistyping the ping address. It's time to go home.

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