Navigation

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

    Static ip error

    Firewalling
    4
    10
    402
    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.
    • Z
      zkab last edited by

      Have just installed pfsense for the first time with interfaces red+green+blue … installation went OK and it looks good

      green range: 192.168.1.1-192.168.1.254 (pool 192.168.1.100-192.168.1.199)
      blue range: 192.168.2.1-192.168.2.254 (pool 192.168.2.100-192.168.2.199)

      When I create static ip:s on green it works OK but on blue I get error 'The IP address must lie in the blue subnet' when trying to get static for ip 192.168.2.10
      The ip is outside the pool so what is the problem ?
      I have pfsense 2.4.2 amd64

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

        Post screens of what you've actually done.

        1 Reply Last reply Reply Quote 0
        • Z
          zkab last edited by

          Here are my screenshots …

          pfsense.zip

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

            Interfaces - BLUE would have been more useful.  The Assignments page doesn't say much.

            You can attach your images directly here without zipping them btw.

            1 Reply Last reply Reply Quote 0
            • Z
              zkab last edited by

              Maybe I will explain what I want to achieve.
              I want to create 2 VLAN:s - BLUE/VLAN10 and GREEN/VLAN20.
              To VLAN10 I will attach Unifi AP:s & controller Unifi Cloud Key.
              To VLAN20 I will attach servers and desktops.
              My intention is to separate wifi and lan via VLAN:s and allow traffic between them via firewall rules.
              Not sure howto proceed with VLANs in my case since I have not experience with them.
              I hope you get the idea what I am after and give me guidelines …






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

                Assuming a standard /24 mask, you have two separate subnets.  POOLS are only significant as far as DHCP is concerned, you still have to make statics BELONG to its subnet.  You cannot shove a x.x.1.x static into a x.x.2.0 subnet and vice versa.

                1 Reply Last reply Reply Quote 0
                • Z
                  zkab last edited by

                  OK - understand …

                  1 Reply Last reply Reply Quote 0
                  • Z
                    zkab last edited by

                    @SammyWoo:

                    Assuming a standard /24 mask, you have two separate subnets.  POOLS are only significant as far as DHCP is concerned, you still have to make statics BELONG to its subnet.  You cannot shove a x.x.1.x static into a x.x.2.0 subnet and vice versa.

                    Still confused but at a higher level …

                    I checked my settings and I have 2 different subnets:
                    GREEN 192.168.1.0/24 with dhcp
                    BLUE: 192.168.2.0/24 with dhcp.
                    When I created a static ip (192.168.1.10) in GREEN it is OK but creating a static ip (192.168.2.10) in BLUE then I got error message
                    Both are outside their dhcp pool ... so I do not shove a x.x.1.x static into a x.x.2.0 subnet and vice versa
                    I mean it must be possible to define static ip on different subnet or ...
                    What have I missed ?

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

                      You fat-fingered your interface address.

                      (That's why we ask for screenshots of what you actually did. Not a description of what you think you have done.)

                      ![Screen Shot 2018-03-20 at 9.44.41 AM.png](/public/imported_attachments/1/Screen Shot 2018-03-20 at 9.44.41 AM.png)
                      ![Screen Shot 2018-03-20 at 9.44.41 AM.png_thumb](/public/imported_attachments/1/Screen Shot 2018-03-20 at 9.44.41 AM.png_thumb)

                      1 Reply Last reply Reply Quote 0
                      • Z
                        zkab last edited by

                        Thanks … that was the problem - feel a little bit embarrassed.
                        Now when I counted my fingers and kept then under surveillance pfsense worked like a Swiss railway clock.
                        My intention is to give static ip:s on both subnets (green & blue) and with firewall rules decide how the traffic will flow between devices.
                        I guess that it is doable and I have to do my homework on the firewall rules section.
                        Thanks again ... and I am learning more and more.

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

                        Products

                        • Platform Overview
                        • TNSR
                        • pfSense
                        • Appliances

                        Services

                        • Training
                        • Professional Services

                        Support

                        • Subscription Plans
                        • Contact Support
                        • Product Lifecycle
                        • Documentation

                        News

                        • Media Coverage
                        • Press
                        • Events

                        Resources

                        • Blog
                        • FAQ
                        • Find a Partner
                        • Resource Library
                        • Security Information

                        Company

                        • About Us
                        • Careers
                        • Partners
                        • Contact Us
                        • Legal
                        Our Mission

                        We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.

                        Subscribe to our Newsletter

                        Product information, software announcements, and special offers. See our newsletter archive to sign up for future newsletters and to read past announcements.

                        © 2021 Rubicon Communications, LLC | Privacy Policy